From: Dan Williams <dcbw@redhat.com>
To: Nick Kossifidis <mickflemm@gmail.com>
Cc: Holger Schurig <hs4233@mail.mn-solutions.de>,
linux-wireless@vger.kernel.org,
Neshama Parhoti <pneshama@gmail.com>
Subject: Re: Getting Started
Date: Thu, 07 Feb 2008 11:15:04 -0500 [thread overview]
Message-ID: <1202400904.1689.4.camel@localhost.localdomain> (raw)
In-Reply-To: <1202400596.1689.2.camel@localhost.localdomain>
On Thu, 2008-02-07 at 11:09 -0500, Dan Williams wrote:
> On Thu, 2008-02-07 at 17:04 +0200, Nick Kossifidis wrote:
> > > For example, the openmoko people are writing a mac80211 driver
> > > for ar6k. Not every driver is already in the wireless-2.6 git
> > > tree.
> >
> > [OT]
> >
> > As far as i know Atheros released a GPLed driver along with their SDIO stack.
> > http://sourceforge.net/projects/sdio-linux/
> >
> > Do you have a plan to include this in kernel ? What's the status ?
>
> 2.6.24 already has an SDIO stack; hence the Atheros one is redundant.
> The openmoko people already have a port of their ar6k driver to the
> in-kernel SDIO stack.
Which of course means that one big barrier to including the ar6k driver
is already removed. You can browse the ar6k openmoko code at:
http://svn.openmoko.org/developers/sameo/patches/ar6k-ng/
Dan
next prev parent reply other threads:[~2008-02-07 16:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 13:11 Getting Started Neshama Parhoti
2008-02-07 13:26 ` Johannes Berg
2008-02-07 13:27 ` Johannes Berg
2008-02-07 13:32 ` Neshama Parhoti
2008-02-07 13:35 ` Johannes Berg
2008-02-07 13:51 ` Neshama Parhoti
2008-02-07 13:35 ` Holger Schurig
2008-02-07 13:49 ` Neshama Parhoti
2008-02-07 13:55 ` Holger Schurig
2008-02-07 15:04 ` Nick Kossifidis
2008-02-07 16:09 ` Dan Williams
2008-02-07 16:15 ` Dan Williams [this message]
2008-02-07 16:17 ` Nick Kossifidis
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=1202400904.1689.4.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=hs4233@mail.mn-solutions.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mickflemm@gmail.com \
--cc=pneshama@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