public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2 v3] arm: suen3, suen3_v1, mgcoge2_arm_p1a support
Date: Wed, 3 Feb 2010 17:53:31 +0100	[thread overview]
Message-ID: <201002031753.31595.sr@denx.de> (raw)
In-Reply-To: <4B699BA5.6090001@denx.de>

On Wednesday 03 February 2010 16:52:05 Heiko Schocher wrote:
> >> +
> >> +	str = getenv("mach_type");
> >> +	if (str != NULL) {
> >> +		mach_type = simple_strtoul(str, NULL, 10);
> >> +		printf("Overwriting MACH_TYPE with %d!!!\n", mach_type);
> >> +		gd->bd->bi_arch_number = mach_type;
> >> +	}
> >> +	return 0;
> >
> > Pls avoid this, the machine types should be predefined and registered
> > first for the board support that you are adding. Why do you need this in
> > environment?.
> 
> Stefan, can you answer this?

Yes.

The SUEN3 mach-type is already registered. But we wanted to use one U-Boot 
image on this system (early suen3), and boot the "normal" mainline Linux 
kernel (with the registered mach-type) and a specific Linux kernel image from 
the Linux kernel distributed from Marvell (2.6.22 based). And this kernel 
image had a different MACH_TYPE number. So we added this method to dynamically 
change the mach-type passed to the Linux kernel.

I have no idea if this is still needed for Keymile. But I also think this 
doesn't "hurt". So I'm voting to keep it for now.

Cheers,
Stefan

--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de

  reply	other threads:[~2010-02-03 16:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07  7:56 [U-Boot] arm: suen3, suen3_v1, mgcoge2_arm_p1a support Heiko Schocher
2010-01-17 23:51 ` Wolfgang Denk
2010-01-18  8:34   ` Heiko Schocher
2010-01-18  9:31     ` Stefan Roese
2010-01-27  7:23   ` Heiko Schocher
2010-01-27  7:30     ` [U-Boot] [PATCH 1/2 v2] cramfs: make cramfs usable on non NOR flash Heiko Schocher
2010-01-27 19:28       ` Wolfgang Denk
2010-01-28  7:30         ` Heiko Schocher
2010-01-28 10:15           ` Wolfgang Denk
2010-01-28 11:02             ` Heiko Schocher
2010-01-27  7:31     ` [U-Boot] [PATCH 2/2 v2] arm: suen3, suen3_v1, mgcoge2_arm_p1a support Heiko Schocher
2010-01-27 13:50       ` Tom
2010-01-27 14:43         ` Heiko Schocher
2010-01-28 13:54           ` Tom
2010-01-27 19:49       ` Wolfgang Denk
2010-02-01  7:37       ` [U-Boot] [PATCH 2/2 v3] " Heiko Schocher
2010-02-02 18:07         ` Prafulla Wadaskar
2010-02-03  6:42           ` Wolfgang Denk
2010-02-03 15:52           ` Heiko Schocher
2010-02-03 16:53             ` Stefan Roese [this message]
2010-02-03 22:32             ` Scott Wood
2010-02-04  7:24               ` Heiko Schocher
2010-02-08 19:23                 ` Scott Wood
2010-02-10  7:09             ` Heiko Schocher
2010-02-10  7:41               ` Prafulla Wadaskar
2010-02-10  9:27                 ` Heiko Schocher

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=201002031753.31595.sr@denx.de \
    --to=sr@denx.de \
    --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