From: Jonas Larsson <jonas.larsson@netinsight.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Patches
Date: 15 Aug 2003 17:25:26 +0200 [thread overview]
Message-ID: <1060961126.26299.55.camel@doris> (raw)
In-Reply-To: <20030815151937.GC8421@buici.com>
On Fri, 2003-08-15 at 17:19, Marc Singer wrote:
> On Fri, Aug 15, 2003 at 02:21:48PM +0200, Jonas Larsson wrote:
> > I have a question regarding submitting patches.
> >
> > Should I send them to the mailing list or to the patch
> > tracking system at sourceforge? I've submitted a patch
> > to sourcforge already.
> >
> > The patch adds support for an environment variable 'arch'
> > which is passed as the ARM machine number to the kernel if
> > set. The u-boot behaviour is unchanged if 'arch' is not defined.
>
> That's an interesting idea, though I'm not sure I can see how it would
> be valuable in practice. Do you have systems where the hardware setup
> is identitical but the ARM CPU is different?
Nope. The arch number specifies what kind of arm-board the kernel is
booting on. One kernel binary is in my case able to handle 3 different
versions of boards (and its hard or dangerous to find out by probing
the board). The number is used to tell the kernel about how irq-lines
etc are wired on the board. Perhaps the name 'arch' is a bad choice,
perhaps "arm-mach" is better.
/ Jonas
next prev parent reply other threads:[~2003-08-15 15:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 12:21 [U-Boot-Users] Patches Jonas Larsson
2003-08-15 15:19 ` Marc Singer
2003-08-15 15:25 ` Jonas Larsson [this message]
2003-08-15 15:50 ` Marc Singer
2003-08-15 16:04 ` Jonas Larsson
2003-08-15 16:36 ` Marc Singer
2003-08-15 17:00 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2003-05-28 20:42 [U-Boot-Users] patches Matthew S. McClintock
2003-05-28 21:43 ` Wolfgang Denk
2003-05-28 22:27 ` Matthew S. McClintock
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=1060961126.26299.55.camel@doris \
--to=jonas.larsson@netinsight.net \
--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