linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	Holger Schurig <hs4233@mail.mn-solutions.de>,
	linux-wireless@vger.kernel.org
Subject: Re: questions regarding removing the depencency on CONFIG_IEEE80211
Date: Tue, 04 Dec 2007 12:10:19 -0500	[thread overview]
Message-ID: <1196788219.7894.3.camel@localhost.localdomain> (raw)
In-Reply-To: <1196787568.10274.26.camel@johannes.berg>

On Tue, 2007-12-04 at 17:59 +0100, Johannes Berg wrote:
> > I was thinking about lib80211 this morning too; specifically the code
> > that everyone has to write to convert local BSS entries into WEXT scan
> > results.  The problem is that drivers have different ideas of what a BSS
> > is.  I think the _first_ thing to do is to define a BSS structure (I
> > used the ipw2x00 bss structure in libertas when doing this) that all the
> > fullmac drivers can use (airo, atmel, libertas, orinoco, etc).  Then,
> > each driver can fill out that structure from it's internal scan result,
> > and hand that off to the lib80211 bss list handling code.  We could have
> > a help that these driver's get_scan calls to convert the internal list
> > into WEXT scan results.  The important thing is getting these drivers to
> > fill out the common bss structure when their firmware returns a scan
> > result.  We could even make the lib80211 code handle scan result aging
> > internally.  Could have helper functions to allocate and dispose of the
> > bss list instead of having to duplicate that code in every driver (it's
> > already in airo & libertas, and I posted a patch that dupes it again for
> > orinoco).
> 
> Sounds good though I think this in particular is cfg80211 functionality
> because over time that will want to export scan results via nl80211 too.

Good point; that might be a great way to move forward and start getting
cfg80211 functionality into the fullmac drivers.

Dan



  reply	other threads:[~2007-12-04 17:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-04 10:40 questions regarding removing the depencency on CONFIG_IEEE80211 Holger Schurig
2007-12-04 10:53 ` Holger Schurig
2007-12-04 14:56   ` Dan Williams
2007-12-04 15:25     ` John W. Linville
2007-12-04 15:29       ` Dan Williams
2007-12-04 15:54         ` Holger Schurig
2007-12-04 16:59         ` Johannes Berg
2007-12-04 17:10           ` Dan Williams [this message]
2007-12-04 16:58       ` Johannes Berg
2007-12-04 15:04 ` Dan Williams
2007-12-04 15:47   ` Holger Schurig
2007-12-04 15:56     ` Dan Williams
2007-12-04 16:57 ` 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=1196788219.7894.3.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=hs4233@mail.mn-solutions.de \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).