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: <45BFC2CF.8010603@garzik.org>
Date:	Tue, 30 Jan 2007 17:12:31 -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:
> Sure, Ralink drivers will get upstream eventually.  But by the time
> the drivers get merged, Ralink will have stopped making the chips that
> it supports (or so I read, http://www.linuxemporium.co.uk/products/wireless/)!
> I don't think that taking a year or two to merge a driver is going to
> impress a vendor, especially since the reverse-engineered Broadcom
> wireless driver is probably going to go upstream at just about the
> same time.

You mean the bcm43xx wireless driver that's been upstream for months?

> An uncharitable vendor might decide it's not worth publishing specs,
> since the Linux guys can reverse engineer the Windows driver just as
> fast anyway.

Most vendors are likely to focus on examples that are in the statistical 
(and competitive) majority, where publishing specs led to a driver 
supported by an enterprise distro.

	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/