From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: devel@linuxdriverproject.org,
linux-wireless <linux-wireless@vger.kernel.org>,
linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: ar9271 mailing list and driver project page
Date: Fri, 28 Aug 2009 09:23:33 -0700 [thread overview]
Message-ID: <43e72e890908280923v376b5eeaub542201217f02fba@mail.gmail.com> (raw)
In-Reply-To: <200908280934.53681.hs4233@mail.mn-solutions.de>
On Fri, Aug 28, 2009 at 12:34 AM, Holger
Schurig<hs4233@mail.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
prev parent reply other threads:[~2009-08-28 16:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 2:43 ar9271 mailing list and driver project page Luis R. Rodriguez
2009-08-28 7:34 ` Holger Schurig
2009-08-28 16:23 ` Luis R. Rodriguez [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43e72e890908280923v376b5eeaub542201217f02fba@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=devel@linuxdriverproject.org \
--cc=greg@kroah.com \
--cc=hch@lst.de \
--cc=hs4233@mail.mn-solutions.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox