From: Rami Rosen <ramirose@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Linux Kernel Wireless stack presentation
Date: Thu, 20 Aug 2009 10:22:38 +0300 [thread overview]
Message-ID: <eb3ff54b0908200022mf4d2950v366c82698dfe440b@mail.gmail.com> (raw)
In-Reply-To: <43e72e890908200012x23b7773dvf215676726a514e5@mail.gmail.com>
Luis,
First, thanks for your quick response.
> * Ditch iwconfig and refer to iw
I do mention also iw; for example, in slide 70, slide 111.
My impression is that both set of tools, wireless-tools and iw, will
coexist for the next
near future and maybe beyond.
> * ath5k/ath9k do not have any firmware burned onto any "ROM", the
> devices just do not require software, everything is done by the driver
Thanks for the info!
Regards,
Rami Rosen
On Thu, Aug 20, 2009 at 10:12 AM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
> On Thu, Aug 20, 2009 at 12:02 AM, Rami Rosen<ramirose@gmail.com> wrote:
>> Folks,
>>
>> I am giving on Thursday next week a lecture about the Linux Kernel
>> Wireless stack in a
>> Linux User Group in Herzelia (Israel).
>>
>> The slides are available online now, so I thought some of you might
>> be interested
>> to take a look; the presentation is very detailed (over 110 pages).
>>
>> see:
>> http://tuxology.net/wp-content/uploads/2009/08/wirelessLecHerzelinux.pdf
>
> A few comments:
>
> * Ditch iwconfig and refer to iw
> * ath5k/ath9k do not have any firmware burned onto any "ROM", the
> devices just do not require software, everything is done by the driver
>
> Luis
>
next prev parent reply other threads:[~2009-08-20 7:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 7:02 Linux Kernel Wireless stack presentation Rami Rosen
2009-08-20 7:12 ` Luis R. Rodriguez
2009-08-20 7:22 ` Rami Rosen [this message]
2009-08-20 7:31 ` Luis R. Rodriguez
2009-08-20 9:22 ` Johannes Berg
2009-08-20 10:14 ` Rami Rosen
2009-08-25 10:29 ` Rami Rosen
2009-08-25 10:37 ` Johannes Berg
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=eb3ff54b0908200022mf4d2950v366c82698dfe440b@mail.gmail.com \
--to=ramirose@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
/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