Michael Buesch wrote:
Yes. 2.6.19-rc is still older code than 2.6.18.1.
The stuff from 2.6.18.1 (which is the same as wireless-2.6)
will be merged into 2.6.19-rc soon.
2.6.18.1 produced the oops in the earlier mail
wireless-2.6 did *not* produce the oops, instead I get the behavior of
plain 2.6
On Monday 23 October 2006 16:35, Daniel Drake wrote:
> Michael Buesch wrote:
> > Yeah, try to find out why.
> > I can only repeat myself: No developer has got a PCI-E card.
> > If there are problems, everybody has to find out by himself why
> > it does not work.
> > Try to find out why it can not d
Michael Buesch wrote:
Yeah, try to find out why.
I can only repeat myself: No developer has got a PCI-E card.
If there are problems, everybody has to find out by himself why
it does not work.
Try to find out why it can not determine the CHIP-ID.
Any point diagnosing this when this does not happ
Michael Buesch wrote:
Please try 2.6.18.1 or wireless-2.6.
wireless-2.6.git has the same problems as the earlier reports on
2.6.19-rc2: ifconfig up,down,up fails, plus it's hard to get connectivity.
Daniel
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a m
On Monday 23 October 2006 15:22, Daniel Drake wrote:
> Michael Buesch wrote:
> > Please try 2.6.18.1 or wireless-2.6.
> >
>
>
> 2.6.18.1 (with the PCI-E patch) crashes on modprobe:
>
> bcm43xx driver
> ACPI: PCI Interrupt Link [LK1E] enabled at IRQ 11
> ACPI: PCI Interrupt :03:00.0[A] -> Li
Michael Buesch wrote:
Please try 2.6.18.1 or wireless-2.6.
2.6.18.1 (with the PCI-E patch) crashes on modprobe:
bcm43xx driver
ACPI: PCI Interrupt Link [LK1E] enabled at IRQ 11
ACPI: PCI Interrupt :03:00.0[A] -> Link [LK1E] -> GSI 11 (level,
low) -> IRQ 11
PCI: Setting latency timer of
On Friday 20 October 2006 20:25, Daniel Drake wrote:
> Michael Buesch wrote:
> > Which kernel are you using exactly?
>
> 2.6.19-rc2
Please try 2.6.18.1 or wireless-2.6.
--
Greetings Michael.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL P
Michael Buesch wrote:
Which kernel are you using exactly?
2.6.19-rc2
bcm43xx: Radio turned off
bcm43xx: DMA-32 0x0200 (RX) max used slots: 7/64
bcm43xx: DMA-32 0x02A0 (TX) max used slots: 0/512
bcm43xx: DMA-32 0x0280 (TX) max used slots: 0/512
bcm43xx: DMA-32 0x0260 (TX) max used slots: 0/512
On Friday 20 October 2006 17:46, Daniel Drake wrote:
> Hi Larry,
>
> Larry Finger wrote:
> > From: Stefano Brivio <[EMAIL PROTECTED]>
> >
> > The current bcm43xx driver does not contain code to handle PCI-E interfaces
> > such as the BCM4311 and BCM4312. This patch, originally written by Stefano
Hi Larry,
Larry Finger wrote:
From: Stefano Brivio <[EMAIL PROTECTED]>
The current bcm43xx driver does not contain code to handle PCI-E interfaces
such as the BCM4311 and BCM4312. This patch, originally written by Stefano
Brivio adds the necessary code to enable these interfaces.
I am testin
On Monday 16 October 2006 06:18, Larry Finger wrote:
> From: Stefano Brivio <[EMAIL PROTECTED]>
>
> The current bcm43xx driver does not contain code to handle PCI-E interfaces
> such as the BCM4311 and BCM4312. This patch, originally written by Stefano
> Brivio adds the necessary code to enable th
From: Stefano Brivio <[EMAIL PROTECTED]>
The current bcm43xx driver does not contain code to handle PCI-E interfaces
such as the BCM4311 and BCM4312. This patch, originally written by Stefano
Brivio adds the necessary code to enable these interfaces.
Signed-off-by: Stefano Brivio <[EMAIL PROTECT
12 matches
Mail list logo
