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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 30 Jan 2007 14:00:24 -0800
From:	Roland Dreier <rdreier@...co.com>
To:	Greg KH <greg@...ah.com>
Cc:	Jeff Garzik <jeff@...zik.org>, linux-kernel@...r.kernel.org
Subject: Re: Free Linux Driver Development!

 > The Ralink wireless drivers are working to get their stuff upstream.  I
 > think there is only some wireless infrastructure needed to complete
 > before it gets into mainline, but you will have to ask them about this.
 > 
 > There was a wireless-mini-summit a week or so ago, so those developers
 > all know what is going on in that space right now.  They are facing a
 > number of different regulatory issues, combined with lack of
 > specifications from some vendors.  I don't think that the developers who
 > actually have specs are complaining about anything right now.

OK, one last reply before I give up on this thread...

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.

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.

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