Felipe Maya wrote:
> the compilation is succeded for me, but eth doesn't respond for any ping.
> (BCM5354 WL500GPV2)
>
> CONFIG_B44=y
> CONFIG_B44_PCI_AUTOSELECT=y
> CONFIG_B44_PCICORE_AUTOSELECT=y
> CONFIG_B44_PCI=y
>
>
>
> ---- Mensagem Original ----
> From: "Peter Denison" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED], "OpenWrt Development List"
> <openwrt-devel@lists.openwrt.org>
> Sent: Ter, Maio 20, 2008 5:23 am
> Subject: Re: [OpenWrt-Devel] brcm47xx 2.6 still does not compile
>
> On Mon, 19 May 2008, Steve Brown wrote:
>
>   
>> Dirk Nehring wrote:
>>     
>>> [...]
>>> make[5]: Leaving directory
>>>       
> `/home/technik/dnehring/openwrt/build_dir/linux-brcm47xx/linux-2.6.25.1'
>   
>>> make[5]: Entering directory
>>>       
> `/home/technik/dnehring/openwrt/build_dir/linux-brcm47xx/linux-2.6.25.1'
>   
>>>   CHK     include/linux/version.h
>>>   CHK     include/linux/utsrelease.h
>>>   CALL    scripts/checksyscalls.sh
>>>   CHK     include/linux/compile.h
>>>   CC      drivers/ssb/driver_pcicore.o
>>> drivers/ssb/driver_pcicore.c: In function 'ssb_pcicore_fixup_pcibridge':
>>> drivers/ssb/driver_pcicore.c:314: error: implicit declaration of function
>>>       
> 'pcibios_enable_device'
>   
>>> make[7]: *** [drivers/ssb/driver_pcicore.o] Error 1
>>> make[6]: *** [drivers/ssb] Error 2
>>> make[5]: *** [drivers] Error 2
>>> make[5]: Leaving directory
>>>       
> `/home/technik/dnehring/openwrt/build_dir/linux-brcm47xx/linux-2.6.25.1'
>   
>>> make[4]: ***
>>>       
> [/home/technik/dnehring/openwrt/build_dir/linux-brcm47xx/linux-2.6.25.1/.image]
> Error 2
>   
>>> make[4]: Leaving directory
>>>       
> `/home/technik/dnehring/openwrt/target/linux/brcm47xx'
>   
>>> And, iproute2 must be updated (works with iproute2-2.6.25.tar.bz2).
>>>       
>
> Yes. I have a patch waiting to go in, but I'm waiting for confirmation (or
> time to test it) that it works under older kernels as well.
>   
>> I added the following to config-2.6.25.
>>
>> CONFIG_PCI=y
>> CONFIG_SYS_HAS_EARLY_PRINTK=y
>> CONFIG_EARLY_PRINTK=y
>> # CONFIG_MEMSTICK is not set
>> # CONFIG_SGI_IP28 is not set
>> # CONFIG_THERMAL is not set
>>
>> The config_pci is to get the declaration for pcibios_enable_device to be
>> included. A better solution would be to add the missing ifdef around
>> that code.
>>     
>
> Not really. The platform has PCI, so that config setting should be set.
> Possibly there are some config dependencies that should go in so that you
> don't get a compilation failure.
>
>   
>> I was pretty surprised at having to add the commented lines. If they
>> aren't there, you get questions from the 'make oldconfig' during the
>> kernel build.
>>     
>
> Sorry. If I understood exactly where to set things to get the right
> resultant .config, it would work more often.
>
>   
>> The early printk stuff was to try to figure why it would boot on a
>> Buffalo whr-hp-54g, but not an Asus wl520gu. I still don't know why.
>>     
>
> CONFIG_BCM47XX sets CONFIG_SYS_HAS_EARLY_PRINTK, so you shouldn't need to
> set that. I can't work out where CONFIG_EARLY_PRINTK is set in my config,
> maybe by hand? That should probably go in.
>
> --
> Peter Denison
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
>
>
>
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>   
My BCM5354 (Asus WL520gu) hangs on on boot after the "Entry at 
0x80001000". Nothing after.

The same image boots fine on a BCM4704 (Asus WL500GP) and a BCM5352 
(Buffalo WHR-HP-G54). I managed to get some output from the cfe putchar 
function at the start of setup_arch. So it's hanging prior to that. I'm 
sure how to debug this. Probably just wait for somebody better at it 
than me.

Where did you get the V2? I haven't found anybody in the US that stocks 
them yet. The FCC pix shows what looks like a jtag header. That would 
sure be handy for times like this.

Steve

_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Reply via email to