On Sat, Feb 10, 2007 at 06:55:50AM +0100, Michael Buesch wrote:
> We don't know.
>
> It's likely that old cards still work with v4 firmware, but we don't know and
> it has to be tested.
>
> Care to do so?
I'll check the revision of my 4306, but I think it's probably too new to
be useful, unfor
I'm testing the latest dscape code (from Michael's tree) on a bcm4311.
Performance is much better than before. The only problem I've seen so
far is the following in the kernel logs:
[ 743.064000] bcm43xx_d80211: ASSERTION FAILED (0) at:
ubuntu/wireless/d80211/bcm43xx/bcm43xx_dma.c:1012:parse_c
On Saturday 10 February 2007 17:27, Matthew Garrett wrote:
> I'm testing the latest dscape code (from Michael's tree) on a bcm4311.
> Performance is much better than before. The only problem I've seen so
> far is the following in the kernel logs:
>
> [ 743.064000] bcm43xx_d80211: ASSERTION FAIL
On Friday, 9 February 2007 17:53, Michael Buesch wrote:
> On Friday 09 February 2007 17:18, Larry Finger wrote:
> > After a suspend/resume cycle, bcm43xx-softmac has lost its association with
> > the AP and requires manual intervention. This situation is fixed by making
> > one of softmac's interna
On Sat, Feb 10, 2007 at 06:00:59PM +0100, Michael Buesch wrote:
> Strange. THat shouldn't happen.
> Can you post complete dmesg?
Attached.
--
Matthew Garrett | [EMAIL PROTECTED]
Feb 10 16:06:02 vaio kernel: [0.00] Linux version 2.6.20-7-generic
([EMAIL PROTECTED]) (gcc version 4.1.2 20
Rafael,
Rafael J. Wysocki wrote:
>
> I'm running with this patch applied right now, but the association is lost
> after the resume anyway. I have to reload bcm43xx to make it associate with
> the AP again (no big deal).
Please send me the output of iwconfig and ifconfig after the resume, but b
I'm testing with your bcm43xx git tree, which I'm guessing is the
current ssb code. The only problem I've found is that there doesn't seem
to be any sysfs relationship between the ssb bus and (in this case) the
PCI device that it's associated with. Is this fixable? Right now it
appears as an en
On Saturday 10 February 2007 21:46, Matthew Garrett wrote:
> I'm testing with your bcm43xx git tree, which I'm guessing is the
> current ssb code. The only problem I've found is that there doesn't seem
> to be any sysfs relationship between the ssb bus and (in this case) the
> PCI device that it
On Sat, Feb 10, 2007 at 10:03:57PM +0100, Michael Buesch wrote:
> On Saturday 10 February 2007 21:46, Matthew Garrett wrote:
> > I'm testing with your bcm43xx git tree, which I'm guessing is the
> > current ssb code. The only problem I've found is that there doesn't seem
> > to be any sysfs relat
Miles Lane wrote:
> I am testing this patch applied to the wireless-net git tree.
> The card is a Linksys WPC54G. The card is still getting very
> weak signal strength and the connection seems unresponsive
> most of the time.
As the subject says, the patch was for 4311 and 4312 cards. The 4318's
On Saturday 10 February 2007 23:11, Matthew Garrett wrote:
> On Sat, Feb 10, 2007 at 10:03:57PM +0100, Michael Buesch wrote:
> > On Saturday 10 February 2007 21:46, Matthew Garrett wrote:
> > > I'm testing with your bcm43xx git tree, which I'm guessing is the
> > > current ssb code. The only probl
On Sat, 2007-02-10 at 22:11 +, Matthew Garrett wrote:
> Ok, here's a patch. The stack of PCMCIA headers are needed to get the
> pcmcia_device structure. Seems to work fine for PCI - I don't have any
> PCMCIA devices. The SSB devices now appear underneath the PCI device
> rather than in the t
On Saturday 10 February 2007 23:56, Pavel Roskin wrote:
> On Sat, 2007-02-10 at 22:11 +, Matthew Garrett wrote:
> > Ok, here's a patch. The stack of PCMCIA headers are needed to get the
> > pcmcia_device structure. Seems to work fine for PCI - I don't have any
> > PCMCIA devices. The SSB devi
> > I have one more test to try... I am strangely never able to associate
> > with the wifi router in my girlfriend's apartment, however it is a
> > crappy old D-Link B-series router. I'll try it next time I get a
> > chance. (I've long suspected the reason is that she lives in an
> > apartment b
> It's likely that old cards still work with v4 firmware, but we don't know and
> it has to be tested.
>
> Care to do so?
I'm fairly sure the reason for dropping the old cards is that the
on-board memory which holds the firmware isn't large enough to hold
the newer firmware. I can't find my do
Matthew Garrett wrote:
> Ok, here's a patch. The stack of PCMCIA headers are needed to get the
> pcmcia_device structure. Seems to work fine for PCI - I don't have any
> PCMCIA devices. The SSB devices now appear underneath the PCI device
> rather than in the top level of /sys/devices.
What ab
16 matches
Mail list logo
