From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell King - ARM Linux Date: Fri, 17 Jan 2003 00:02:24 +0000 Subject: [U-Boot-Users] kernel parameters for ARM In-Reply-To: <20030117000749.GQ3691@pengutronix.de>; from robert@schwebel.de on Fri, Jan 17, 2003 at 01:07:49AM +0100 References: <20030115232914.GA3691@pengutronix.de> <3E26970A.5090800@elsoft.ch> <20030116200646.GK3691@pengutronix.de> <3E26D8DB.2000604@elsoft.ch> <20030117000749.GQ3691@pengutronix.de> Message-ID: <20030117000224.G21507@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 Fri, Jan 17, 2003 at 01:07:49AM +0100, Robert Schwebel wrote: > On Thu, Jan 16, 2003 at 05:07:55PM +0100, David M?ller wrote: > > The values stored in U-Boot's "gd->bd->bi_boot_params" variable and > > the "BOOT_PARAMS" macro in the machine specific "arch" file of > > ARMLinux have to be equal. AFAICS there is not passing in of the > > pointer to the tag list in r2, at least not in the kernel i'm looking > > at. > > Ah, ok, that does work. > > Russell, the documentation in Documentation/arm/Booting seems to be > missleading. Is the BOOT_PARAMS method the right way to go? If yes, how > does the kernel know which address the bootloader uses to store the > tagged list? See my mail from about 5 minutes ago explaining this.