public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] arm: fix some arch_number definition
Date: Thu, 22 Jan 2009 09:29:08 +0100	[thread overview]
Message-ID: <20090122082908.GC15551@game.jcrosoft.org> (raw)
In-Reply-To: <20090122074030.57565832E425@gemini.denx.de>

On 08:40 Thu 22 Jan     , Wolfgang Denk wrote:
> Dear Jean-Christophe PLAGNIOL-VILLARD,
> 
> In message <1232603494-14583-2-git-send-email-plagnioj@jcrosoft.com> you wrote:
> > 
> > diff --git a/board/armadillo/armadillo.c b/board/armadillo/armadillo.c
> > index ca5bd1d..e9be758 100644
> > --- a/board/armadillo/armadillo.c
> > +++ b/board/armadillo/armadillo.c
> > @@ -42,8 +42,7 @@ int board_init (void)
> >  	/* Activate LED flasher */
> >  	IO_LEDFLSH = 0x40;
> >  
> > -	/* arch number MACH_TYPE_ARMADILLO - not official*/
> > -	gd->bd->bi_arch_number = 83;
> > +	gd->bd->bi_arch_number = MACH_TYPE_ARMADILLO;
> >  
> >  	/* location of boot parameters */
> >  	gd->bd->bi_boot_params = 0xc0000100;
> 
> You actually CHANGE the arch_number here; you need the board
> maintainer's ACK for such a patch.
the ARMADILLO was changed in the current kernel it's not any more 83 but 615

83 is used for board that does not have any valid MACHINE ID
> 
> Note that there are other places where this is used - these must be
> changed, too - for example:
> 
> "board/lpc2292sodimm/lpc2292sodimm.c":
> 
>  42         /* arch number MACH_TYPE_ARMADILLO - not official*/
>  43         gd->bd->bi_arch_number = 83;
I've not find it in the official list so I've let as 83 (non registered board)
> 
> "board/siemens/SMN42/smn42.c":
> 
>  42         /* arch number MACH_TYPE_ARMADILLO - not official*/
>  43         gd->bd->bi_arch_number = 83;
ditto
> 
> I recommend you got through this again, more thoroughly.
> 
> > index 3ad756d..205bd3a 100644
> > --- a/board/cmc_pu2/cmc_pu2.c
> > +++ b/board/cmc_pu2/cmc_pu2.c
> > @@ -96,12 +96,7 @@ int board_init (void)
> >  	piob->PIO_PER = AT91C_PIO_PB3 | AT91C_PIO_PB4 |
> >  			AT91C_PIO_PB5 | AT91C_PIO_PB6;
> >  
> > -	/*
> > -	 * arch number of CMC_PU2-Board. MACH_TYPE_CMC_PU2 is not supported in
> > -	 * the linuxarm kernel, yet.
> > -	 */
> > -	/* gd->bd->bi_arch_number = MACH_TYPE_CMC_PU2; */
> > -	gd->bd->bi_arch_number = 251;
> > +	gd->bd->bi_arch_number = MACH_TYPE_CMC_PU2;
> >  	/* adress of boot parameters */
> >  	gd->bd->bi_boot_params = PHYS_SDRAM + 0x100;
> 
> You actually CHANGE the arch_number here; you need the board
> maintainer's ACK for such a patch.
as precedently it's the current MACHINE ID
251 is used for AT91RM9200

> 
> > diff --git a/board/imx31_phycore/imx31_phycore.c b/board/imx31_phycore/imx31_phycore.c
> > index ae93444..4b72d57 100644
> > --- a/board/imx31_phycore/imx31_phycore.c
> > +++ b/board/imx31_phycore/imx31_phycore.c
> > @@ -60,7 +60,7 @@ int board_init (void)
> >  	mx31_gpio_mux(MUX_CSPI2_MOSI__I2C2_SCL);
> >  	mx31_gpio_mux(MUX_CSPI2_MISO__I2C2_SDA);
> >  
> > -	gd->bd->bi_arch_number = 447;		/* board id for linux */
> > +	gd->bd->bi_arch_number = MACH_TYPE_MX31ADS;	/* board id for linux */
> >  	gd->bd->bi_boot_params = (0x80000100);	/* adress of boot parameters */
> 
> MX31ADS ?
> 
> > diff --git a/board/ns9750dev/ns9750dev.c b/board/ns9750dev/ns9750dev.c
> > index fc46244..b8f377b 100644
> > --- a/board/ns9750dev/ns9750dev.c
> > +++ b/board/ns9750dev/ns9750dev.c
> > @@ -68,7 +68,7 @@ int board_init( void )
> >  #warning Please register your machine at http://www.arm.linux.org.uk/developer/machines/?action=new
> >  	/* arch number of OMAP 1510-Board */
> >  	/* to be changed for OMAP 1610 Board */
> > -	gd->bd->bi_arch_number = 234;
> > +	gd->bd->bi_arch_number = MACH_TYPE_NS9750;
> 
> You actually CHANGE the arch_number here; you need the board
> maintainer's ACK for such a patch.
234 is use for OMAP_INNOVATOR not the ns9750 so I've correct it

I any board maintainer have a problem with it I'm open

Best Regards,
J.

  reply	other threads:[~2009-01-22  8:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-22  5:51 [U-Boot] [PATCH 0/1] arm/mach-types: sync with 2.6.28 and add generating tools support Jean-Christophe PLAGNIOL-VILLARD
2009-01-22  5:51 ` [U-Boot] [PATCH 1/1] arm: fix some arch_number definition Jean-Christophe PLAGNIOL-VILLARD
2009-01-22  6:51   ` Jens Gehrlein
2009-01-22  8:34     ` Jean-Christophe PLAGNIOL-VILLARD
2009-02-03 11:25       ` Guennadi Liakhovetski
2009-01-22  7:40   ` Wolfgang Denk
2009-01-22  8:29     ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2009-01-22 10:46       ` Wolfgang Denk
2009-01-22 11:13         ` Jean-Christophe PLAGNIOL-VILLARD
2009-01-22 16:33           ` Wolfgang Denk
2009-01-27 12:02           ` Detlev Zundel
2009-01-27 12:09             ` Wolfgang Denk
2009-01-27 13:05             ` Jean-Christophe PLAGNIOL-VILLARD
2009-01-22 11:21   ` Jean-Christophe PLAGNIOL-VILLARD
2009-01-22  7:42 ` [U-Boot] [PATCH 0/1] arm/mach-types: sync with 2.6.28 and add generating tools support Wolfgang Denk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090122082908.GC15551@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox