On Mon, 2006-10-23 at 20:23 +0200, Johannes Berg wrote:
> (1) set shm offset 0x2e*2 to 0xFFF0 (not higher due to internal things,
> but that should be enough)
Actually, just clear the antenna diversity host flag (what we used to
call MicrocodeFlags) instead :)
johannes
signature.asc
Desc
On Mon, 2006-10-23 at 21:58 +0200, Michael Buesch wrote:
> Well, I'd like to test this, but as you know, we don't really
> have a usable driver for the WRT, yet. And that's the only device
> I have with two antennas. (Well, and the not-working CF card :D )
Well, you can always use a device that o
On Monday 23 October 2006 20:23, Johannes Berg wrote:
> Hi,
>
> Here's something that would make a nice hacking experiment for someone
> interested :) I'm very interested in the outcome.
>
> First, some theory.
> Antenna diversity is implemented in the MAC, i.e. the microcode. The
> microcode has
Hi,
Here's something that would make a nice hacking experiment for someone
interested :) I'm very interested in the outcome.
First, some theory.
Antenna diversity is implemented in the MAC, i.e. the microcode. The
microcode has a counter that it uses to determine if it should swap,
this counter i
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
On Mon, 2006-10-23 at 17:14 +0200, Ramanalinarivo Sandrinah Vonisoa
Annie wrote:
> > > > > > 2.6.18-to-wireless-2.6 + 2GB patch), I have my bcm4318 working.
> > > > > > 02:02.0 Network controller: Broadcom Corporation BCM4318
> > > > > What patch are you talking about? What firmware do you EXACTLY
> > > > > 2.6.18-to-wireless-2.6 + 2GB patch), I have my bcm4318 working.
> > > > > 02:02.0 Network controller: Broadcom Corporation BCM4318
> > > > What patch are you talking about? What firmware do you EXACTLY use?
> > > >From here: ftp://lwfinger.dynalias.org/
> > > I have the firmware listed f
On Mon, 2006-10-23 at 17:00 +0200, Ramanalinarivo Sandrinah Vonisoa
Annie wrote:
> On Sun, 2006-10-22 at 09:21 -0400, Daniel Gryniewicz wrote:
> > On Sun, 2006-10-22 at 22:06 +0200, Ramanalinarivo Sandrinah wrote:
> > > On Sun, 2006-10-22 at 08:52 -0400, Daniel Gryniewicz wrote:
> > >
> > > > 2.6.
On Sun, 2006-10-22 at 09:21 -0400, Daniel Gryniewicz wrote:
> On Sun, 2006-10-22 at 22:06 +0200, Ramanalinarivo Sandrinah wrote:
> > On Sun, 2006-10-22 at 08:52 -0400, Daniel Gryniewicz wrote:
> >
> > > 2.6.18-to-wireless-2.6 + 2GB patch), I have my bcm4318 working.
> > > 02:02.0 Network controlle
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 n
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
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lis
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 Sun, Oct 22, 2006 at 10:20:13PM +0200, Michael Buesch wrote:
> No success or failure reports on this one??
Sorry, got distracted by work, haven't had time to test it.
> Remember, without a response, this issue will never be fixed.
Well actually, I've never had watchdog timeouts. Only various
15 matches
Mail list logo
