On Sa, 2009-09-12 at 00:56 +0200, Gábor Stefanik wrote:
> 2009/9/12 Gábor Stefanik <netrolller...@gmail.com>:
> > On Fri, Sep 11, 2009 at 10:54 PM, Thomas Ilnseher <il...@gmx.de> wrote:
> >> Hi List,
> >>
> >> I installed the latest version of OpenWRT on a ASUS WL-520GU.
> >> I compiles a few kernel patches to make the OpenWRT kernel (2.6.28.10)
> >> compatible with compat wireless.
> >>
> >> Than I patched OpenWRT to build compat-wireless-09-02
> >>
> >> As said, It yields an instant crash:
> >>
> >> cfg80211: World regulatory domain updated:
> >>        (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> >>        (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> >>        (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
> >>        (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
> >>        (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> >>        (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> >> b43-phy0: Broadcom 5354 WLAN found (core revision 13)
> >> Decompressing..........done <== CFE Again, no usefull stuff on teh RS232
> >> port
> >>
> >> FWIW, I add the patches for the kernel.
> >
> > These patches are probably not enough - there were more changes to the
> > ssb module since 2.6.28. You will probably need to compile a new
> > kernel from wireless-testing or net-next-2.6 (linux-next & linux-2.6
> > may also work). (God luck doing that in the OpenWRT build system...)
I will try to copy all ssb files from compat-wireless to the 2.6.28.10
kernel, and create a patch. 

I assume the kernel will crash on boot then, cause I'd need some changes
in /arch/mips/....

I can probably hack the build system to support a newer kernel, but the
problem remains that there are a gazillion patches that need porting :/

So I think the next thing to do is a diff of that ssb stuff, and see
what's changed.

The main Issue is that I can't get any usefull information what's going
on- I see only the single line above. 

As far as I understand the code (that I've read so far) It should printk
some driver message BEFORE this message.

I've seen some verbosity parameter, I will play with that.


> 
> Oops... that was Good's hand. :)
> 
> >
> >>
> >>
> >> _______________________________________________
> >> Bcm43xx-dev mailing list
> >> Bcm43xx-dev@lists.berlios.de
> >> https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
> >>
> >>
> >
> >
> >
> > --
> > Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
> >
> 
> 
> 

_______________________________________________
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to