On Sunday 14 January 2007 17:39, Pavel Roskin wrote:
> Quoting Michael Buesch <[EMAIL PROTECTED]>:
>
> > Ok, nice.
> > Can you send me a complete dmesg log after you brought up the card
> > and tried to assoc/send some packets?
>
> Attached.
Ok, thanks. I don't see something unusual.
You should
Quoting Michael Buesch <[EMAIL PROTECTED]>:
> Ok, nice.
> Can you send me a complete dmesg log after you brought up the card
> and tried to assoc/send some packets?
Attached.
--
Regards,
Pavel Roskin
ACPI: PCI Interrupt :0c:00.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer
On Sunday 14 January 2007 15:18, Pavel Roskin wrote:
> Quoting Michael Buesch <[EMAIL PROTECTED]>:
>
> > Already done. Please pull my tree and check if it still crashes.
>
> The crash is gone! Thanks! Still no association though.
Ok, nice.
Can you send me a complete dmesg log after you brought
Quoting Michael Buesch <[EMAIL PROTECTED]>:
> Already done. Please pull my tree and check if it still crashes.
The crash is gone! Thanks! Still no association though.
> > Actually, I could scan, and I got 7 access points around. Only one is in
> my
> > apartment.
>
> RX sensitivity is not qui
On Sunday 14 January 2007 03:10, Pavel Roskin wrote:
> Quoting Michael Buesch <[EMAIL PROTECTED]>:
>
> > > I haven't looked at the code yet, but I tried to locate the bad commit. I
> > tried
> > > commit a13f85d8a8eb40dfd157ab78c2fb91b5765b7b9d, which is your last merge,
> > just
> > > before the
Quoting Michael Buesch <[EMAIL PROTECTED]>:
> > I haven't looked at the code yet, but I tried to locate the bad commit. I
> tried
> > commit a13f85d8a8eb40dfd157ab78c2fb91b5765b7b9d, which is your last merge,
> just
> > before the SSB changes.
>
> Yeah, sure. I know that this is the commit which
On Saturday 13 January 2007 20:30, Pavel Roskin wrote:
> Quoting Michael Buesch <[EMAIL PROTECTED]>:
>
> > I looked more closely at it, but I really can't see why it oopses.
> > Any idea what's happening there?
>
> I haven't looked at the code yet, but I tried to locate the bad commit. I
> trie
Quoting Michael Buesch <[EMAIL PROTECTED]>:
> I looked more closely at it, but I really can't see why it oopses.
> Any idea what's happening there?
I haven't looked at the code yet, but I tried to locate the bad commit. I tried
commit a13f85d8a8eb40dfd157ab78c2fb91b5765b7b9d, which is your last
On Saturday 13 January 2007 08:45, Pavel Roskin wrote:
> Quoting Michael Buesch <[EMAIL PROTECTED]>:
>
> > > drivers/ssb/driver_mips/mips.c includes asm/time.h, which is missing on
> > > x86_64. It also refers to struct ssb_serial_ports, which is not defined
> > > anywhere.
> >
> > Yeah, CONFIG_S
Quoting Michael Buesch <[EMAIL PROTECTED]>:
> > drivers/ssb/driver_mips/mips.c includes asm/time.h, which is missing on
> > x86_64. It also refers to struct ssb_serial_ports, which is not defined
> > anywhere.
>
> Yeah, CONFIG_SSB_MIPS should depend on the MIPS CPU.
> Which kconfig option do you
On Friday 12 January 2007 08:25, Pavel Roskin wrote:
> Hello, Michael!
>
> I've tried the master branch of bcm43xx-wireless-dev.git for the first
> time. The results are not encouraging so far (although I'm quite new to
> this chipset).
>
> drivers/ssb/driver_mips/mips.c includes asm/time.h, whi
Hello, Michael!
I've tried the master branch of bcm43xx-wireless-dev.git for the first
time. The results are not encouraging so far (although I'm quite new to
this chipset).
drivers/ssb/driver_mips/mips.c includes asm/time.h, which is missing on
x86_64. It also refers to struct ssb_serial_ports
In case you wonder what's the future of bcm43xx, here's
a list of changes in my bcm43xx development tree:
bcm43xx-d80211: Add some PHY register definitions.
bcm43xx-d80211: Move ILT stuff to OFDM table stuff
bcm43xx-d80211: Remove PHY OFDM routing bit, if we are on A-PHY.
b
13 matches
Mail list logo
