Linux wireless drivers development
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@atheros.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "linux-wireless\@vger.kernel.org"
	<linux-wireless@vger.kernel.org>,
	"gregkh\@suse.de" <gregkh@suse.de>,
	"linville\@tuxdriver.com" <linville@tuxdriver.com>,
	"devel\@linuxdriverproject.org" <devel@linuxdriverproject.org>
Subject: Re: Plan for ath6kl cleanup
Date: Fri, 20 May 2011 17:45:07 +0300	[thread overview]
Message-ID: <87liy1qvm4.fsf@atheros.com> (raw)
In-Reply-To: <1305901563.2681.9.camel@aeonflux> (Marcel Holtmann's message of "Fri, 20 May 2011 07:26:03 -0700")

Marcel Holtmann <marcel@holtmann.org> writes:

> Hi Kalle,

Hi Marcel,

>> We have been thinking about how to get ath6kl out from staging and get
>> it to a first class citizen under drivers/net/wireless. There's quite a
>> lot of work to do get ath6kl cleaned up and the prospect of doing all
>> that through the staging-next tree wasn't that exciting. We would be
>> sending hundreds of patches and it would take a long time to cleanup the
>> driver. And the disconnection from the wireless core development also
>> sounded very daunting (cfg80211 API changes etc.).
>
> my main question is why do you still bother with this driver and not
> re-write it as a mac80211 driver from scratch. It seems to be more
> softmac than fullmac anyway. Or am I mistaken here?

Actually ar6003, the chip ath6kl supports, is a fullmac. It can take
ethernet frames, all authentication/association frames are created by
the firmware and firmware manages the roaming as well. So there isn't
anything mac80211 could do.

> The source code of the current staging driver is 5 MB in size. That is
> by far the largest staging driver. Even brcm80211 is smaller.

Yeah, the driver is huge. But once the cleanup is done it will be a lot
smaller.

Kalle

      reply	other threads:[~2011-05-20 14:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-20 13:13 Plan for ath6kl cleanup Kalle Valo
2011-05-20 13:36 ` Greg KH
2011-05-20 14:29   ` Christoph Hellwig
2011-05-20 16:51     ` Joe Perches
2011-05-21  3:11       ` Greg KH
2011-05-20 14:33   ` Kalle Valo
2011-05-21  5:24     ` Dan Carpenter
2011-05-20 14:26 ` Marcel Holtmann
2011-05-20 14:45   ` Kalle Valo [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=87liy1qvm4.fsf@atheros.com \
    --to=kalle.valo@atheros.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@suse.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=marcel@holtmann.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