Re: [PATCH] b43: Fix some TX/RX locking issues

2008-05-01 Thread Michael Buesch
John, did you drop this patch? I can't see it in git and your latest push, while a patch submitted later is in there. On Friday 25 April 2008, Michael Buesch wrote: This fixes some TX/RX related locking issues. With this patch applied, some of the PHY transmission errors are fixed.

Re: BCM4308 rev 3 owner, willing to help (want to make an access point)

2008-05-01 Thread Francis Galiegue
2008/5/1 Johannes Berg [EMAIL PROTECTED]: unencrypted AP -- success; [WPA] -- segfault http://johannes.sipsolutions.net/patches/kernel/all/2008-05-01-00:32/023-mac80211-fix-debugfs-key.patch Better, but not there yet... At least now it doesn't segfault. I ran again hostapd with

[PATCH 0/3] Add API for weak DMA masks

2008-05-01 Thread Michael Buesch
This patchset adds API and one user for a weak dma_set_mask(). Weak means that it will fallback to smaller masks in case the DMA subsystem rejects a big mask. Currently such rejection may happen if the driver requests a 64bit mask on a VIA machine, for example. dma_set_mask_weak() will fallback to

[PATCH 3/3] b43: Use the new weak DMA-mask API

2008-05-01 Thread Michael Buesch
This adds a user for the new weak DMA mask API. This removes the b43 DMA mask probe loop. Signed-off-by: Michael Buesch [EMAIL PROTECTED] Index: linux-2.6/drivers/net/wireless/b43/dma.c === ---

[PATCH 1/3] Add dma_set_mask_weak() API

2008-05-01 Thread Michael Buesch
This adds a new DMA subsystem API call for weak setting of the DMA mask. Weak means that it will fallback to smaller masks in case the DMA subsystem rejects a big mask. Currently such rejection may happen if the driver requests a 64bit mask on a VIA machine, for example. dma_set_mask_weak() will

[PATCH 2/3] ssb: Add weak DMA-mask API

2008-05-01 Thread Michael Buesch
This adds a weak variant of ssb_dma_set_mask(). Signed-off-by: Michael Buesch [EMAIL PROTECTED] Index: linux-2.6/drivers/ssb/main.c === --- linux-2.6.orig/drivers/ssb/main.c 2008-05-01 13:19:53.0 +0200 +++

Re: [PATCH 0/3] Add API for weak DMA masks

2008-05-01 Thread Michael Buesch
On Thursday 01 May 2008 17:36:18 Christoph Hellwig wrote: On Thu, May 01, 2008 at 04:38:15PM +0200, Michael Buesch wrote: This patchset adds API and one user for a weak dma_set_mask(). Weak means that it will fallback to smaller masks in case the DMA subsystem rejects a big mask.

Re: [PATCH 0/3] Add API for weak DMA masks

2008-05-01 Thread Michael Buesch
On Thursday 01 May 2008 17:43:58 Christoph Hellwig wrote: On Thu, May 01, 2008 at 05:42:04PM +0200, Michael Buesch wrote: Yeah. because it has to be done in every driver. So we put the implementation into a central place, instead of reimplementing the wheel over and over again. This way we

Re: [PATCH 0/3] Add API for weak DMA masks

2008-05-01 Thread Michael Buesch
On Thursday 01 May 2008 17:58:26 Christoph Hellwig wrote: On Thu, May 01, 2008 at 05:47:26PM +0200, Michael Buesch wrote: We've discussed that and this behaviour is not acceptable, as the driver must know about a possible fallback in case it can do 32bit DMA more efficiently than 64bit DMA,

Re: [PATCH 1/3] Add dma_set_mask_weak() API

2008-05-01 Thread Michael Buesch
On Thursday 01 May 2008 18:20:45 Alan Cox wrote: On Thu, 1 May 2008 16:40:16 +0200 Michael Buesch [EMAIL PROTECTED] wrote: This adds a new DMA subsystem API call for weak setting of the DMA mask weak is an odd term - and we use weak for things like weak symbols so it might be

Re: [PATCH 0/3] Add API for weak DMA masks

2008-05-01 Thread Michael Buesch
On Thursday 01 May 2008 18:30:04 Jesse Barnes wrote: On Thursday, May 01, 2008 9:07 am Michael Buesch wrote: On Thursday 01 May 2008 17:58:26 Christoph Hellwig wrote: On Thu, May 01, 2008 at 05:47:26PM +0200, Michael Buesch wrote: We've discussed that and this behaviour is not

Re: [PATCH 0/3] Add API for weak DMA masks

2008-05-01 Thread Michael Buesch
On Thursday 01 May 2008 19:22:55 Jesse Barnes wrote: On Thursday, May 01, 2008 10:16 am Michael Buesch wrote: Ok, will redo the patches with that added and the name changed. Most drivers just do the fallback themselves, right? Right. So it makes sense to just update the current

Re: [PATCH 0/3] Add API for weak DMA masks

2008-05-01 Thread Michael Buesch
On Thursday 01 May 2008 19:27:35 Jesse Barnes wrote: On Thursday, May 01, 2008 10:16 am Michael Buesch wrote: So it makes sense to just update the current code to fallback, and update drivers wanting specific mask values to check afterwards. I hate to inflict that kind of driver wide

Re: b43 generates an excesive amount of log

2008-05-01 Thread Abel Camarillo Ojeda
Yea it was mac80211 debugging. I disabled it at the Kconfig and rebuild the module. Very thanks. On Tue, Apr 29, 2008 at 6:57 AM, Johannes Berg [EMAIL PROTECTED] wrote: Apr 29 01:13:17 lambda kernel: b 9c 13 c7 42 a5 ca 5c 3f e5 f0 e8 98 81 10 d0 ed 6b That is certainly not coming

Re: [PATCH] b43: Fix some TX/RX locking issues

2008-05-01 Thread John W. Linville
On Thu, May 01, 2008 at 12:08:10PM +0200, Michael Buesch wrote: John, did you drop this patch? I can't see it in git and your latest push, while a patch submitted later is in there. No, I'm sorry. I fat-fingered my patches. I've still got it, and it will go in the next round. John On

Re: BCM4308 rev 3 owner, willing to help (want to make an access point)

2008-05-01 Thread Francis Galiegue
2008/5/1 Francis Galiegue [EMAIL PROTECTED]: 2008/5/1 Johannes Berg [EMAIL PROTECTED]: unencrypted AP -- success; [WPA] -- segfault http://johannes.sipsolutions.net/patches/kernel/all/2008-05-01-00:32/023-mac80211-fix-debugfs-key.patch Better, but not there yet...

Fwd: BCM4308 rev 3 owner, willing to help (want to make an access point)

2008-05-01 Thread Stefanik Gábor
On Thu, May 1, 2008 at 11:05 PM, Francis Galiegue [EMAIL PROTECTED] wrote: 2008/5/1 Francis Galiegue [EMAIL PROTECTED]: 2008/5/1 Johannes Berg [EMAIL PROTECTED]: unencrypted AP -- success; [WPA] -- segfault

Re: BCM4308 rev 3 owner, willing to help (want to make an access point)

2008-05-01 Thread Francesco Gringoli
Just a question (for Francis): how does the AP work? Have you tried very stressing tests with traffic crossing the AP? We do have problems when the channel is saturated, it seems that the BCM device acting as AP stops sending beacons and the BSS goes down, we need to reconfigure everything