| 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
| ||
|
Message-ID: <43e72e890908280923v376b5eeaub542201217f02fba@mail.gmail.com> Date: Fri, 28 Aug 2009 09:23:33 -0700 From: "Luis R. Rodriguez" <mcgrof@...il.com> To: Holger Schurig <hs4233@...l.mn-solutions.de> Cc: devel@...uxdriverproject.org, linux-wireless <linux-wireless@...r.kernel.org>, linux-kernel@...r.kernel.org, Greg KH <greg@...ah.com>, Christoph Hellwig <hch@....de> Subject: Re: ar9271 mailing list and driver project page On Fri, Aug 28, 2009 at 12:34 AM, Holger Schurig<hs4233@...l.mn-solutions.de> wrote: >> ar9271 and ar9170 seem to share a few things, one of which is >> firmware upload. ar9271's firmware upload routine was modified >> to make it match ar9170's as much as possible to share it on >> ath.ko > > Is it true that most devices which will use ath.ko won't ever use > firmware uploading? For now only usb devices require firmware loading, but so does ar6k, however I am not sure how fw upload works there so I cannot be certain the way to upload fw will be the same as with ar9170 and ar9271. > It's only a few Ath-USB devices, so maybe > you could do an ath_fw.ko for this. True, or ath_usb, or something, only thing is it might be overkill to just have 1 fw upload routine on a module for sharing. > (Somebody who's always working with embedded devices and likes to > keeps small :-) Hey thanks :) Luis -- 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/
Powered by blists - more mailing lists