From: Paul Nasrat <pnasrat@uk.now.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: mlan@cpu.lu, linuxppc-dev@lists.linuxppc.org
Subject: Re: Airport in BenH's kernels
Date: Sun, 6 May 2001 22:47:46 +0100 [thread overview]
Message-ID: <20010506224746.A21305@uk.now.com> (raw)
In-Reply-To: <20010506202801.14354@smtp.wanadoo.fr>; from benh@kernel.crashing.org on Sun, May 06, 2001 at 10:28:01PM +0200
On Sun, May 06, 2001 at 10:28:01PM +0200, Benjamin Herrenschmidt wrote:
>
> Thanks ! The driver have been a pretty quickly moving target lately
> as Jean Tourrihles and I were working to finally have a common code
> base for airport and orinoco_cs without duplicating the driver.
>
> The new driver is getting close to completion now and things should
> finally stabilize.
OK - I'm not a major C hacker but I'm trying to get a good feel for the driver with my interest in 802.11b generally. What seems interesting is that the MacOS software config's the card so that a linux box running managed mode can pick it up easily. It seems to be the most accesible point to access to infrastructure mode.
I'd like to look into writing stuff for this - as well as potentially some user space stuff for ad-hoc networking. I probably need some pointers on endian clean programming but just a url/book ref and I'll get stuck in.
Paul
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-05-06 21:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-06 20:11 Airport in BenH's kernels Michel Lanners
2001-05-06 20:28 ` Benjamin Herrenschmidt
2001-05-06 20:51 ` Airport in BenH's kernels (a few tips & tricks) Michel Lanners
2001-05-06 21:47 ` Paul Nasrat [this message]
2001-05-06 22:53 ` Airport in BenH's kernels Benjamin Herrenschmidt
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=20010506224746.A21305@uk.now.com \
--to=pnasrat@uk.now.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mlan@cpu.lu \
/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;
as well as URLs for NNTP newsgroup(s).