-----Original Message----- From: u-boot-users-admin@lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net]On Behalf Of Steven Scholz Sent: Thursday, June 23, 2005 11:12 AM To: u-boot-users@lists.sourceforge.net Subject: Re: [U-Boot-Users] u-boot r1 machine type value to AT91RM9200 2.6.12 kernel

Sascha,

I tried to use the linux 2.6.12 release for AT91RM9200, but when I

started

with u-boot 1.1.2 the Kernel stopped.

It is a custom board? Did you register a MACH_NUMBER?

I can configure a working kernel with the option 'config NAKED_Boot= y ', but with this option it's not possible to pass any bootarguments to the

kernel.

How can I pass the corret R1 value for the machine type ('0xfb') from

u-boot

1.1.2 to the kernel?

In you board_init() do something like:

/* arch number of AT91RM9200 */ /*gd->bd->bi_arch_number = 251;*/ gd->bd->bi_arch_number = MACH_TYPE_MULTIIO; /* adress of boot parameters */ gd->bd->bi_boot_params = PHYS_SDRAM + 0x100;

The last working kernel in combination with u-boot was 2.6.12rc4. What changes in the u-boot source do I have to maintain relating to these boot options? Or is it possible to pass the r1 value in between the 'bootargs'

of

the u-boot enviroment?

No.

Just make sure your board_init() sets the correct (TM) arch_number.

See kernel sources

linux-2.6.12/arch/arm/boot/compressed/head-at91rm9200.S

-- Steven

Hi Steven,

#define MACH_TYPE_AT91RM9200EK 705

is the right choice for starting 2.6.12, but the old 2.612rcX kernels need 251 (0xfb) ;-)

Thanks Sascha