headers
Johannes Berg | 1 Feb 14:07
Favicon

[RFC] cfg80211 merge

On Thu, 2007-02-01 at 01:54 +0200, Tomas Winkler wrote:
> As far as I tested cfg80211 compatibility mode is incomplete. You
> cannot run hostapd over it
> If I recall correctly PRISM2_IOCTL_PRISM2_PARAM and friends are not
> passed to d80211 

It's a priv ioctl, it's not supposed to be passed on.

johannes (who is getting positively pissed off about such requests)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part
Url :
http://lists.tuxdriver.org/pipermail/wireless/attachments/20070201/efd11861/attachment.pgp
Permalink | Reply |
headers
Tomas Winkler | 1 Feb 15:04
Picon

[RFC] cfg80211 merge

Can you elaborate shortly.  I'm not from time 0 on this list.
Thanks.

On 2/1/07, Johannes Berg <johannes at sipsolutions.net> wrote:
>
> On Thu, 2007-02-01 at 01:54 +0200, Tomas Winkler wrote:
> > As far as I tested cfg80211 compatibility mode is incomplete. You
> > cannot run hostapd over it
> > If I recall correctly PRISM2_IOCTL_PRISM2_PARAM and friends are not
> > passed to d80211
>
> It's a priv ioctl, it's not supposed to be passed on.
>
> johannes (who is getting positively pissed off about such requests)
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.tuxdriver.org/pipermail/wireless/attachments/20070201/397cf333/attachment.htm
Permalink | Reply |
headers
Jiri Benc | 1 Feb 15:12
Picon

[RFC] cfg80211 merge

On Thu, 1 Feb 2007 16:04:53 +0200, Tomas Winkler wrote:
> Can you elaborate shortly.  I'm not from time 0 on this list.
> Thanks.

Use Google and list archives, that's why their exist.

 Jiri

--

-- 
Jiri Benc
SUSE Labs
Permalink | Reply |
headers
Johannes Berg | 1 Feb 15:11
Favicon

[RFC] cfg80211 merge

On Thu, 2007-02-01 at 16:04 +0200, Tomas Winkler wrote:
> Can you elaborate shortly.  I'm not from time 0 on this list.

Well. cfg80211 will replace the common wext ioctls. All the private wext
ioctls will not be handled there.

The rationale is that
 (1) it doesn't delete priv ioctls, they'll still work for the migration
     period
 (2) you can't rely on private ioctls having a certain meaning for each
     driver, ie. other drivers are free the reassign numbers of
     sub-ioctls
 (3) any behaviour that is generally useful should be standardised.

johannes
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part
Url :
http://lists.tuxdriver.org/pipermail/wireless/attachments/20070201/7a106843/attachment.pgp
Permalink | Reply |
headers
Tomas Winkler | 2 Feb 19:18
Picon

[RFC] cfg80211 merge

Johannes
I don't know who is missing something here, but what I'm saying that (1) is
not correct. priv ioctls don't work with compatibility  set on.
In any case I'll check it again to be sure and I will apologize if I'm not
correct.
I definitely agree on two other  points.

Thanks
Tomas

On 2/1/07, Johannes Berg <johannes at sipsolutions.net> wrote:
>
> On Thu, 2007-02-01 at 16:04 +0200, Tomas Winkler wrote:
> > Can you elaborate shortly.  I'm not from time 0 on this list.
>
> Well. cfg80211 will replace the common wext ioctls. All the private wext
> ioctls will not be handled there.
>
> The rationale is that
> (1) it doesn't delete priv ioctls, they'll still work for the migration
>      period
> (2) you can't rely on private ioctls having a certain meaning for each
>      driver, ie. other drivers are free the reassign numbers of
>      sub-ioctls
> (3) any behaviour that is generally useful should be standardised.
>
> johannes
>
>
>
(Continue reading)

Permalink | Reply |

Gmane