[U-Boot] Why u-boot & linux uses different machineid for at91rm9200dk

[U-Boot] Why u-boot & linux uses different machineid for at91rm9200dk

[vibi sreenivasan]

Hello,
	Why u-boot & linux uses different machine id for at91rm9200dk.
	is seems that u-boot is using 0x000000FB & linux is using
	0x00000106.

	Can we fix this in u-boot itself ?

Thanks & Regards
vibi sreenivasan

[U-Boot] Why u-boot & linux uses different machineid for at91rm9200dk

[Wolfgang Denk]

Dear vibi sreenivasan,

In message <1250062753.2419.8.camel@HunTEr> you wrote:
>
> 	Why u-boot & linux uses different machine id for at91rm9200dk.

do they? well, which exact versions of U-Boot and Linux are you
talking about?

> 	is seems that u-boot is using 0x000000FB & linux is using
> 	0x00000106.
> 
> 	Can we fix this in u-boot itself ?

In U-Boot I see:

	-> grep MACH_TYPE_AT91RM9200DK include/asm-arm/mach-types.h
	#define MACH_TYPE_AT91RM9200DK         262
	#  define machine_arch_type     MACH_TYPE_AT91RM9200DK
	# define machine_is_at91rm9200dk()      (machine_arch_type ==
	# MACH_TYPE_AT91RM9200DK)

262 = 0x106.

This iseems to be what Linux uses, too, and what is officially
registered.

Maybe you should update your code?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
You can't have everything... where would you put it?  - Steven Wright

[U-Boot] Why u-boot & linux uses different machineid for at91rm9200dk

[vibi sreenivasan]

hello Wolfgang Denk,
On Wed, 2009-08-12 at 21:44 +0200, Wolfgang Denk wrote:
> Dear vibi sreenivasan,
> 
> In message <1250062753.2419.8.camel@HunTEr> you wrote:
> >
> > 	Why u-boot & linux uses different machine id for at91rm9200dk.
> 
> do they? well, which exact versions of U-Boot and Linux are you
> talking about?
> 
> > 	is seems that u-boot is using 0x000000FB & linux is using
> > 	0x00000106.
> > 
> > 	Can we fix this in u-boot itself ?
> 
> In U-Boot I see:
> 
> 	-> grep MACH_TYPE_AT91RM9200DK include/asm-arm/mach-types.h
> 	#define MACH_TYPE_AT91RM9200DK         262
> 	#  define machine_arch_type     MACH_TYPE_AT91RM9200DK
> 	# define machine_is_at91rm9200dk()      (machine_arch_type ==
> 	# MACH_TYPE_AT91RM9200DK)
> 
> 262 = 0x106.
> 
> This iseems to be what Linux uses, too, and what is officially
> registered.
> 
> Maybe you should update your code?
Thanks for your support, i was using an older version of u-boot.

Thanks & Regards
vibi sreenivasan
> 
> Best regards,
> 
> Wolfgang Denk
> 

[U-Boot] Why u-boot & linux uses different machineid for at91rm9200dk

[Ulf Samuelsson]

vibi sreenivasan skrev:
> hello Wolfgang Denk,
> On Wed, 2009-08-12 at 21:44 +0200, Wolfgang Denk wrote:
>> Dear vibi sreenivasan,
>>
>> In message <1250062753.2419.8.camel@HunTEr> you wrote:
>>> 	Why u-boot & linux uses different machine id for at91rm9200dk.
>> do they? well, which exact versions of U-Boot and Linux are you
>> talking about?
>>
>>> 	is seems that u-boot is using 0x000000FB & linux is using
>>> 	0x00000106.

The AT91RM9200DK needs one mach-id for linux-2.4 and another for 2.6

Reason is hidden in history.

BR
Ulf Samuelsson