Stefan Monnier schrieb:
>> Now `iwlist scan' works, and I even got it up and running with
>> wpa_supplicant. Thank you.
>
> So, it works, but there are some problems:
>
> My ssh connections to the WL700gE box seem to always hang after
> a (fairly short) while. When the connection hangs, I can s
Tomasz Chmielewski schrieb:
> Michael Buesch schrieb:
>
> (...)
>
> Code: a021 8ec3000c 8fa40050 <9074> 9082038a 0202102b
> 1446 3c04c010 3c028002
> Kernel panic - not syncing: Fatal exception in interrupt
This behaves... interesting.
Paste it after bo
Michael Buesch schrieb:
(...)
Code: a021 8ec3000c 8fa40050 <9074> 9082038a 0202102b
1446 3c04c010 3c028002
Kernel panic - not syncing: Fatal exception in interrupt
>>> This behaves... interesting.
>>>
>>> Paste it after booting, and it will print two warnings.
>>>
On Saturday 05 July 2008 20:31:34 Tomasz Chmielewski wrote:
> Tomasz Chmielewski schrieb:
> > Tomasz Chmielewski schrieb:
> >> Tomasz Chmielewski schrieb:
> >>> Steve Brown schrieb:
> >>>
> >>> (...)
> >>>
> >>> And I don't think firmware is loaded - I have exactly the same
> >>> output wh
It was not the same thing with wl500gpv2, still conflicted with the B44.
The last test was done with the compat-wireless-2008-07-05. Still
missing something.
[Kernel-2.6.25.9 compat-wireless-2008-07-05]
[EMAIL PROTECTED]:/lib/modules/2.6.25.9# insmod ieee80211_crypt.ko
[EMAIL PROTECTED]:/lib/mod
> Now `iwlist scan' works, and I even got it up and running with
> wpa_supplicant. Thank you.
So, it works, but there are some problems:
My ssh connections to the WL700gE box seem to always hang after
a (fairly short) while. When the connection hangs, I can still ping my
WL700gE box, and also I
Tomasz Chmielewski schrieb:
> Tomasz Chmielewski schrieb:
>> Tomasz Chmielewski schrieb:
>>> Steve Brown schrieb:
>>>
>>> (...)
>>>
>>> And I don't think firmware is loaded - I have exactly the same
>>> output when I don't even have /lib/firmware/b43 directory.
>>>
>>>
>>>
>
Tomasz Chmielewski schrieb:
> Tomasz Chmielewski schrieb:
>> Steve Brown schrieb:
>>
>> (...)
>>
>> And I don't think firmware is loaded - I have exactly the same
>> output when I don't even have /lib/firmware/b43 directory.
>>
>>
>>
> I cannot reproduce your results. Fo
>> >> The b43 driver now loads, loads firmware and returns scan results.
>> > With the above patch (and a freshly updated svn checkout of Kamikaze),
>> > my WL700gE indeed loads the driver, it seems to load the firmware as
>> > well, but something goes wrong afterwards and I don't get any network
>
Tomasz Chmielewski schrieb:
> Steve Brown schrieb:
>
> (...)
>
> And I don't think firmware is loaded - I have exactly the same
> output when I don't even have /lib/firmware/b43 directory.
>
>
>
I cannot reproduce your results. For me, the patch works fine.
>>> Could
Steve Brown schrieb:
(...)
And I don't think firmware is loaded - I have exactly the same
output when I don't even have /lib/firmware/b43 directory.
>>> I cannot reproduce your results. For me, the patch works fine.
>>
>> Could you post your kernel .config?
>>
> I hav
Tomasz Chmielewski wrote:
> Steve Brown schrieb:
>> Tomasz Chmielewski wrote:
>>> Stefan Monnier schrieb:
>>>
>>> (...)
>>>
>>>
> The b43 driver now loads, loads firmware and returns scan results.
>
With the above patch (and a freshly updated svn checkout of Kamikaze),
my
Steve Brown schrieb:
> Tomasz Chmielewski wrote:
>> Stefan Monnier schrieb:
>>
>> (...)
>>
>>
The b43 driver now loads, loads firmware and returns scan results.
>>> With the above patch (and a freshly updated svn checkout of Kamikaze),
>>> my WL700gE indeed loads the driver, it
Tomasz Chmielewski wrote:
> Stefan Monnier schrieb:
>
> (...)
>
>
>>> The b43 driver now loads, loads firmware and returns scan results.
>>>
>> With the above patch (and a freshly updated svn checkout of Kamikaze),
>> my WL700gE indeed loads the driver, it seems to load the firmware as
>>
On Saturday 05 July 2008 11:25:23 Tomasz Chmielewski wrote:
> Stefan Monnier schrieb:
>
> (...)
>
> >> The b43 driver now loads, loads firmware and returns scan results.
> >
> > With the above patch (and a freshly updated svn checkout of Kamikaze),
> > my WL700gE indeed loads the driver, it seem
Stefan Monnier schrieb:
(...)
>> The b43 driver now loads, loads firmware and returns scan results.
>
> With the above patch (and a freshly updated svn checkout of Kamikaze),
> my WL700gE indeed loads the driver, it seems to load the firmware as
> well, but something goes wrong afterwards and I
> Can you try the following patch?
[...]
> +if (dev->bus->bustype != SSB_BUSTYPE_PCI) {
> +/* This SSB device is not on a PCI host-bus. So the IRQs are
> + * not routed through the PCI core.
> + * So we must not enable routing through the PCI core. */
> +goto ou
Felipe Maya wrote:
> Hi Steve,
>
> I'm happy too with the result, but..
> I did the test with the patch that Michael sent (with and without)
> disabling the function ssb_pcicore_dev_irqvecs_enable following the
> e-mails, without the same result. (Kernel 2.6.25.9-wl500gpv2).
>
> Steve can you ver
Hi Steve,
I'm happy too with the result, but..
I did the test with the patch that Michael sent (with and without)
disabling the function ssb_pcicore_dev_irqvecs_enable following the
e-mails, without the same result. (Kernel 2.6.25.9-wl500gpv2).
Steve can you verify the modifications of the test
Forgot the cc's. And to close the thread.
Michael Buesch wrote:
> On Friday 04 July 2008 21:39:46 Steve Brown wrote:
>
>> Michael Buesch wrote:
>>
>>> On Tuesday 01 July 2008 21:50:43 Steve Brown wrote:
>>>
>>>
It looks like (almost) every other phy register doesn't respond.
On Friday 04 July 2008 21:39:46 Steve Brown wrote:
> Michael Buesch wrote:
> > On Tuesday 01 July 2008 21:50:43 Steve Brown wrote:
> >
> >> It looks like (almost) every other phy register doesn't respond. I put
> >> in a large (200us) delay between accesses with no change in behaviour.
> >> If
Michael Buesch wrote:
> On Tuesday 01 July 2008 21:50:43 Steve Brown wrote:
>
>> It looks like (almost) every other phy register doesn't respond. I put
>> in a large (200us) delay between accesses with no change in behaviour.
>> If it is timing, it must be on the pci bus side of the core.
>>
On Tuesday 01 July 2008 21:50:43 Steve Brown wrote:
> It looks like (almost) every other phy register doesn't respond. I put
> in a large (200us) delay between accesses with no change in behaviour.
> If it is timing, it must be on the pci bus side of the core.
Ah this is a minipci card?
Can you
Michael Buesch wrote:
> I'm sorry, I cannot tell you what causes this. But I guess, however,
> it is some change in the ssb setup code that broke this.
>
>
Here's some more evidence. I scanned the phy register space using
get_dbe. Here are the results:
Addr Value
3e0 0x3207 (looks ok)
3
On Sunday 29 June 2008 21:04:28 Steve Brown wrote:
> Michael Buesch wrote:
> > On Sunday 29 June 2008 15:12:47 Steve Brown wrote:
> >
> >> What should I do next?
> >>
> >
> > Can you try this patch?
> >
> > Index: wireless-testing/drivers/net/wireless/b43/main.c
> >
Michael Buesch wrote:
> On Sunday 29 June 2008 15:12:47 Steve Brown wrote:
>
>> What should I do next?
>>
>
> Can you try this patch?
>
> Index: wireless-testing/drivers/net/wireless/b43/main.c
> ===
> --- wireless-testing.orig
On Sunday 29 June 2008 15:12:47 Steve Brown wrote:
> What should I do next?
Can you try this patch?
Index: wireless-testing/drivers/net/wireless/b43/main.c
===
--- wireless-testing.orig/drivers/net/wireless/b43/main.c 2008-06-2
Steve Brown wrote:
> Peter Denison wrote:
>
>> Rather than saying "current svn", it would really help if you can
>> state the exact revision you're using. To summarise the reports at
>> #3510 and here, b43 seems to work on r10154, but not on r11363, r11372
>> or r11579.
>>
>> Unfortunately, I
Peter Denison wrote:
> Rather than saying "current svn", it would really help if you can
> state the exact revision you're using. To summarise the reports at
> #3510 and here, b43 seems to work on r10154, but not on r11363, r11372
> or r11579.
>
> Unfortunately, I don't have a huge amount of tim
On Fri, 27 Jun 2008, Steve Brown wrote:
> Stefan Monnier wrote:
>> I'm trying to use my WL-700gE's wifi card with the b43 driver but bumped
>> into the problem reported at https://dev.openwrt.org/ticket/3510.
>>
>> This is with revision 11579 of the svn trunk.
>>
>> Is there something I can do to
Stefan Monnier wrote:
> I'm trying to use my WL-700gE's wifi card with the b43 driver but bumped
> into the problem reported at https://dev.openwrt.org/ticket/3510.
>
> This is with revision 11579 of the svn trunk.
>
> Is there something I can do to try and help resolve this problem?
>
>
>
I'm trying to use my WL-700gE's wifi card with the b43 driver but bumped
into the problem reported at https://dev.openwrt.org/ticket/3510.
This is with revision 11579 of the svn trunk.
Is there something I can do to try and help resolve this problem?
Stefan
___
32 matches
Mail list logo
