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: <45BFCE41.6020500@garzik.org>
Date:	Tue, 30 Jan 2007 18:01:21 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	Roland Dreier <rdreier@...co.com>
CC:	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org
Subject: Re: Free Linux Driver Development!

Roland Dreier wrote:
> I thought you wrote tg3 without docs and without help from Broadcom?

We had docs and Broadcom's GPL'd driver.

> To repeat, my point is that the drivers used most by users of
> enterprise distros will get written with or without vendor docs or
> help.  Drivers for hardware that only a few people care about probably
> won't be written and definitely won't be maintained by volunteers even
> if the vendor publishes docs.  And I think that's pretty much what I
> said in both of the paragraphs you quoted above.

You're changing your story.  After first over-simplifying what Greg 
posted, you were complaining about Greg being disingenuous, when in fact 
Greg was doing nothing but describing (in a new and different way) how 
Linux drivers are already written.

Furthermore, presuming that drivers "definitely won't be maintained by 
volunteers" is rather presumptuous considering that volunteers are 
lining up, according to Greg.

I'm glad I didn't have a negative nelly like you around when I first got 
into fbdev driver hacking, my entry into the Linux kernel world.  "Don't 
bother, son, nobody wants you around anyway."

	Jeff

-
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/