Re: [microblaze-uclinux] New vendor+board with autoconfig wont co-operate with u-boot config

[John Williams <jwilliams@xxxxxxxxxxxxxx>]

Hi Olof,

Olof Backing wrote:

> I have read the migration guides and how to configure u-boot. But  
> nevertheless I can't stop u-boot from trying to build network support  
> for our network-less board. I can see the #if's that is looking to  
> ethernet (lite) but u-boot still thinks the board includes network.
>
> Please point me to the correct documentation where it says how to make  
> auto-config and u-boot play!

Looking at the source code it's not obvious to me how to tell u-boot 
that you have no network interface at all.  You can disable the network 
commands (ping, arp ...), which we do (see 
u-boot/include/configs/petalinux-microblaze-auto.h)

but u-boot toplevel makefile descends into u-boot/net unconditionally.

Let me ping the local u-boot expert and see what he says.

A simple alternative is a null driver, just declare the eth_init(), 
eth_halt(), eth_send() and eth_receive() functions, and have them return 
sensible do-nothing values.

It's worth asking -  if you have no ethernet device I'm not sure if 
u-boot makes a lot of sense for you anyway?  Some minor tweaks on FSBOOT 
could have you booting the kernel straight from flash.

Regards,

John
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/