linux-kernel - Re: Free Linux Driver Development!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87ejpce21x.fsf@mid.deneb.enyo.de>
Date:	Tue, 30 Jan 2007 20:40:10 +0100
From:	Florian Weimer <fw@...eb.enyo.de>
To:	Greg KH <greg@...ah.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Free Linux Driver Development!

* Greg KH:

>> This reminds of the the utterly broken dl2k network driver (which has
>> got interrupt handling problems and doesn't properly synchronize with
>> DMA transfers, IIRC).  Hardware specs are available, and I guess I
>> could even provide a hardware sample, maybe even two.  (If the
>> community provides driver support, it shouldn't matter if the vendor
>> actually supports development.)
>
> Have you tried contacting the network driver developers to work these
> issues out?

Yes, sort of: <http://article.gmane.org/gmane.linux.kernel/448446>
There weren't any replies, unfortunately.  Do you think a repost would
make sense?

Our subsequent debugging revealed that either all the cards in our
sample were simply broken (but they seemed to work just fine with the
driver from FreeBSD-current), or something related to the DMA handling
in the driver was not quite right.  It looked as if the kernel and the
NIC couldn't agree on the contents of the ring buffer.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/