On Thu, 2006-10-26 at 11:33 -0400, Dan Williams wrote:
> The one blocker I can think of here is startup scripts on various
> distributions. Most of those are shell, and they usually rely on
> iwconfig quite heavily. Getting those converted to wpa_supplicant
> wouldn't be a trivial amount of work
On Thu, 2006-10-26 at 14:41 -0700, Simon Barber wrote:
> Getting people to use wpa_supplicant almost exclusivly as the interface
> for wireless will improve a lot of things. One thing that might help
> here is to do some work on the wpa_cli - to make it easier for the
> startup scripts to do what t
Tourrilhes;
Hong Liu; Jouni Malinen
Subject: Re: [RFC] [PATCH 0/3] Add Regulatory Domain support to d80211
On Thu, 2006-10-26 at 11:04 -0400, Luis R. Rodriguez wrote:
> On 10/26/06, Dan Williams <[EMAIL PROTECTED]> wrote:
> > While wpa_supplicant is certainly the main client for
On Thu, 2006-10-26 at 11:04 -0400, Luis R. Rodriguez wrote:
> On 10/26/06, Dan Williams <[EMAIL PROTECTED]> wrote:
> > While wpa_supplicant is certainly the main client for stuff directly
> > related to setting up a connection, there are quite a few other users of
> > general WE calls to pull infor
On 10/26/06, Dan Williams <[EMAIL PROTECTED]> wrote:
While wpa_supplicant is certainly the main client for stuff directly
related to setting up a connection, there are quite a few other users of
general WE calls to pull information out of the card, or to receive scan
events.
How about we just d
On Thu, 2006-10-26 at 10:35 -0400, Dan Williams wrote:
> > - I'd like to see a header cleanup, it's necessary. Part of the problem
> >here is all the sub-ioctl WE foo. Clean that up by moving them into
> >cfg80211 as required, there's basically one user, wpa_supplicant (and
> >maybe h
On Thu, 2006-10-26 at 00:00 +0200, Johannes Berg wrote:
> On Wed, 2006-10-25 at 13:43 -0400, Luis R. Rodriguez wrote:
>
> > I guess my hope was that d80211 would just be more than a softmac
> > implementation. When I hear wireless stack I don't think "softmac
> > implementation", I think a robust
On Wed, 2006-10-25 at 13:43 -0400, Luis R. Rodriguez wrote:
> I guess my hope was that d80211 would just be more than a softmac
> implementation. When I hear wireless stack I don't think "softmac
> implementation", I think a robust set of headers and device
> definitions which all wireless devices
On 10/24/06, Michael Wu <[EMAIL PROTECTED]> wrote:
On Tuesday 24 October 2006 18:03, Luis R. Rodriguez wrote:
> 1. Anyone working on completing FullMAC support on d80211?
That doesn't really make sense. Fullmac devices should just use WE or cfg80211
because they, for the most part, do what d80211
On 10/25/06, Jiri Benc <[EMAIL PROTECTED]> wrote:
On Tue, 24 Oct 2006 13:41:12 -0400, Luis R. Rodriguez wrote:
> Sure -- we can have on the ieee80211_conf struct an array of all
> regulatory domains stack values that the device supports
> (REGDOMAIN_FCC or 0x10 for FCC for example) if the develop
On Tue, 24 Oct 2006 13:41:12 -0400, Luis R. Rodriguez wrote:
> Sure -- we can have on the ieee80211_conf struct an array of all
> regulatory domains stack values that the device supports
> (REGDOMAIN_FCC or 0x10 for FCC for example) if the developer agrees
> the device has been certified to match t
> Cc: David Kimdon; netdev@vger.kernel.org; Jiri Benc; John W. Linville;
> Jean Tourrilhes
> Subject: Re: [RFC] [PATCH 0/3] Add Regulatory Domain support to d80211
>
> On 10/24/06, Simon Barber <[EMAIL PROTECTED]> wrote:
> > The Client MLME code in the kernel was only
3:03 PM
To: Simon Barber
Cc: David Kimdon; netdev@vger.kernel.org; Jiri Benc; John W. Linville;
Jean Tourrilhes
Subject: Re: [RFC] [PATCH 0/3] Add Regulatory Domain support to d80211
On 10/24/06, Simon Barber <[EMAIL PROTECTED]> wrote:
> The Client MLME code in the kernel was only ever w
On Tuesday 24 October 2006 18:03, Luis R. Rodriguez wrote:
> 1. Anyone working on completing FullMAC support on d80211?
That doesn't really make sense. Fullmac devices should just use WE or cfg80211
because they, for the most part, do what d80211 does in firmware. There are
also strange hybrid de
On 10/24/06, Simon Barber <[EMAIL PROTECTED]> wrote:
The Client MLME code in the kernel was only ever written to be used for
quick testing. It does not have good roaming performance, and was never
intended to be a complete client. The right place for the Client MLME is
in userspace, where it can
John W. Linville; Jean Tourrilhes
Subject: Re: [RFC] [PATCH 0/3] Add Regulatory Domain support to d80211
Hi,
> The following patches extend 802.11 regulatory domain support of the
> d80211 wireless stack through two modules:
>
> 1. ieee80211_regdomains
> 2. iso3166-1
I am glad to
On 10/24/06, David Kimdon <[EMAIL PROTECTED]> wrote:
Hi,
> The following patches extend 802.11 regulatory domain support of the
> d80211 wireless stack through two modules:
>
> 1. ieee80211_regdomains
> 2. iso3166-1
I am glad to see this work, this is something that we need a solution
for. I d
On 10/24/06, John W. Linville <[EMAIL PROTECTED]> wrote:
On Tue, Oct 24, 2006 at 01:33:32AM -0400, Luis R. Rodriguez wrote:
> On 10/23/06, Johannes Berg <[EMAIL PROTECTED]> wrote:
> >On Mon, 2006-10-23 at 18:41 -0400, Luis R. Rodriguez wrote:
> >
> >> The current setup on d80211.h makes regulator
On 10/24/06, Johannes Berg <[EMAIL PROTECTED]> wrote:
Alright, here's more now that I can think clearly again :)
> ISO 3166-1, as part of the ISO 3166 standard, provides codes for the names
> of countries and dependent areas. It was first published in 1974 by
> the International Organization for
Hi,
> The following patches extend 802.11 regulatory domain support of the
> d80211 wireless stack through two modules:
>
> 1. ieee80211_regdomains
> 2. iso3166-1
I am glad to see this work, this is something that we need a solution
for. I do wonder if we can push most of this out of the kernel
On Tue, Oct 24, 2006 at 01:33:32AM -0400, Luis R. Rodriguez wrote:
> On 10/23/06, Johannes Berg <[EMAIL PROTECTED]> wrote:
> >On Mon, 2006-10-23 at 18:41 -0400, Luis R. Rodriguez wrote:
> >
> >> The current setup on d80211.h makes regulatory domains device
> >> specific. I believe this should be ch
Alright, here's more now that I can think clearly again :)
> ISO 3166-1, as part of the ISO 3166 standard, provides codes for the names
> of countries and dependent areas. It was first published in 1974 by
> the International Organization for Standardization (ISO) and defines three
> different cod
On 10/23/06, Johannes Berg <[EMAIL PROTECTED]> wrote:
On Mon, 2006-10-23 at 18:41 -0400, Luis R. Rodriguez wrote:
> The current setup on d80211.h makes regulatory domains device
> specific. I believe this should be changed to be stack-specific --
> that is, all drivers adhere to the restrictions
On Mon, 2006-10-23 at 18:41 -0400, Luis R. Rodriguez wrote:
> The current setup on d80211.h makes regulatory domains device
> specific. I believe this should be changed to be stack-specific --
> that is, all drivers adhere to the restrictions set by the stack's
> current regulatory domain.
There
24 matches
Mail list logo
