From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell King - ARM Linux Date: Wed, 30 Jan 2008 15:47:40 +0000 Subject: [U-Boot-Users] [PATCH] make the machid configurable via theenvironment (Was: [PATCH] Changed load address and entrypoint for uImage to ZRELADDR + 6MB) In-Reply-To: <000201c8634b$546ee570$8901a8c0@atmel.com> References: <20080130080849.GA25875@digi.com> <000201c8634b$546ee570$8901a8c0@atmel.com> Message-ID: <20080130154740.GA29330@flint.arm.linux.org.uk> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Wed, Jan 30, 2008 at 10:33:46AM +0100, Ulf Samuelsson wrote: > Nicolas Pitre wrote: > > > But does U-Boot properly provide machine information to the kernel these > > > days? I have been and still being burned by U-Boot hardcoding the > > > _wrong_ machine ID, and therefore custom built kernels from k.o simply > > > won't boot on those boards without hacking the kernel source. > > With "our" U-Boot you can override the compiled-in machid with an > > environment variable. I didn't implement this patch but I think it's > > not that difficult. I will check tomorrow if I can easily get a patch > > out of our scm. > > I proposed this patch for a long time, but it was rejected by Wolfgang. One solution to that problem is to have someone who maintains a separate tree for uboot which does have the feature in. Then it becomes a matter of community choice whether they use the official tree or the tree with sensible machine-id configurability. That way, those who want the configurability can have it, and Wolfgang can avoid having his tree polluted with useful features he doesn't want.