Re: [PATCH] bcm43xx-d80211: proper implementation of virtual interface support

2006-05-05 Thread Jiri Benc
On Fri, 05 May 2006 12:15:40 +0200, Johannes Berg wrote: > On Fri, 2006-05-05 at 07:45 +0200, Ulrich Kunitz wrote: > > But there could be also > > support for one interface in AP and the other in STA mode. > > That's actually a much more interesting use case for WDS. You don't need different MAC

Re: [PATCH] bcm43xx-d80211: proper implementation of virtual interface support

2006-05-05 Thread Johannes Berg
On Fri, 2006-05-05 at 07:45 +0200, Ulrich Kunitz wrote: > But there could be also > support for one interface in AP and the other in STA mode. That's actually a much more interesting use case for WDS. johannes signature.asc Description: This is a digitally signed message part

Re: [PATCH] bcm43xx-d80211: proper implementation of virtual interface support

2006-05-04 Thread Ulrich Kunitz
> The actual problem is with receiving. ACK frames need to be sent exactly > after SIFS interval (10 or 16 microseconds depending on a PHY, +/- 10%) > after last bit of the frame was received. This means it cannot be done in a > software. You need to tell the hardware about MAC address you are usin

Re: [PATCH] bcm43xx-d80211: proper implementation of virtual interface support

2006-05-04 Thread Jiri Benc
Thu, 4 May 2006 22:55:58 +0200, Ivo van Doorn pise: > On Thursday 4 May 2006 21:26, Marcus Better wrote: > > I wonder what exactly is causing this limitation? Why isn't it just a > > matter of software support? > > Hardware limitations probably. For example the Ralink devices. > The MAC address mu

Re: [PATCH] bcm43xx-d80211: proper implementation of virtual interface support

2006-05-04 Thread Ivo van Doorn
On Thursday 4 May 2006 21:26, Marcus Better wrote: > Jiri Benc wrote: > > This is unnecessary. AFAIK bcm43xx hardware doesn't support more than one > > interface at a time (not counting monitor interfaces as those are somewhat > > special). > > I wonder what exactly is causing this limitation? Why

Re: [PATCH] bcm43xx-d80211: proper implementation of virtual interface support

2006-05-04 Thread Marcus Better
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jiri Benc wrote: > This is unnecessary. AFAIK bcm43xx hardware doesn't support more than one > interface at a time (not counting monitor interfaces as those are somewhat > special). I wonder what exactly is causing this limitation? Why isn't it just a

Re: [PATCH] bcm43xx-d80211: proper implementation of virtual interface support

2006-05-02 Thread Jiri Benc
On Mon, 1 May 2006 21:35:00 +0200, Michael Buesch wrote: > --- wireless-dev.orig/drivers/net/wireless/d80211/bcm43xx/bcm43xx.h > 2006-04-28 16:13:40.0 +0200 > +++ wireless-dev/drivers/net/wireless/d80211/bcm43xx/bcm43xx.h > 2006-05-01 20:25:31.0 +0200 > @@ -626,10 +626,34

[PATCH] bcm43xx-d80211: proper implementation of virtual interface support

2006-05-01 Thread Michael Buesch
Hi, Jiri, please review this patch for things that might look strange to you. :) -- This replaces the bcm43xx-d80211 virtual interfaces hack by a correct implementation with support for monitor during oper. Index: wireless-dev/drivers/net/wireless/d80211/bcm43xx/bcm43xx.h ==