[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] New vendor+board with autoconfig wont co-operate with u-boot config
On Fri, March 14, 2008 01:24, John Williams wrote:
> 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.
But u-boot's framework checks for different settings in the higher .config file from
(peta)linux when it comes to base addresses for SDRAM, FLASH, UART etc. Why can't it
look for and take diffeerent descissions depending on the pure existance of an
> You can disable the network
> commands (ping, arp ...), which we do (see
I might end up making manual modifications, but I have seen a lot of #if's in the
code, like in u-boot/include/configs/petalogix-microblaze-auto.h where you
#define CFG_SDRAM_BASE CONFIG_XILINX_ERAM_START
#if defined(CONFIG_XILINX_ETHERNET_0_INSTANCE) || defined(CONFIG_XILINX_ETHERNET
#define REMOVE_COMMANDS (CFG_CMD_MMC | CFG_CMD_IMLS)
#define CONFIG_COMMANDS ((CFG_CMD_DHCP | CONFIG_CMD_DFL | CFG_CMD_CACHE
| CFG_CMD_PING) & ~REMOVE_COMMANDS)
#define REMOVE_COMMANDS (CFG_CMD_MMC | CFG_CMD_IMLS | CFG_CMD_NET)
#define CONFIG_COMMANDS (CONFIG_CMD_DFL | CFG_CMD_CACHE & ~REMOVE_COMMAN
> 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.
During development it would be convenient to speed up download over RS232 and
decrease the turn-around time. I have already managed to boot the kernel from FLASG
with fs-boot so I'm just trying to support another group of developers.
Contactor Data AB Office: +46 (0)8 752 81 00
Finlandsgatan 14 Mobile: +46 (0)70 995 98 99
SE-164 74 KISTA Fax: +46 (0)8 752 05 30
microblaze-uclinux mailing list
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/