From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marc Singer Date: Fri, 15 Aug 2003 08:50:43 -0700 Subject: [U-Boot-Users] Patches In-Reply-To: <1060961126.26299.55.camel@doris> References: <1060950108.26299.50.camel@doris> <20030815151937.GC8421@buici.com> <1060961126.26299.55.camel@doris> Message-ID: <20030815155043.GA14764@buici.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de > > 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. > Yes, I understand that. It is also important that the board setup be compatible which is the responsibility of uboot. Which seems to be true in your case. None of the Arm chips I've used have this feature. While they can be dynamically detected without danger, it is just as easy to make separate u-boot builds for each. Which chips are you using?