From mboxrd@z Thu Jan 1 00:00:00 1970 From: John W. Linville Date: Mon, 10 Jan 2005 18:54:30 -0500 Subject: [U-Boot-Users] PPC970FX 64-bit processor In-Reply-To: <41E30B47.10908@orkun.us> References: <20050110151530.GA17790@tuxdriver.com> <200501101551.j0AFpOAq025585@il.marvell.com> <20050110173926.GD17790@tuxdriver.com> <41E30B47.10908@orkun.us> Message-ID: <20050110235423.GA27850@tuxdriver.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de > John W. Linville wrote: > >On Mon, Jan 10, 2005 at 05:53:11PM +0200, tzachi perelstein wrote: > > > > > >>I can be even more explicitly and suggest [.8, .16, .32, .64]. > >>What do you think? > > > > > >I think I like that even better. On Mon, Jan 10, 2005 at 05:09:59PM -0600, Tolunay Orkun wrote: > It would break compatibility with existing scripts and documentation of > everyone else. I think we should maintain earlier definitions at least > for existing 32-bit implementations. Perhaps...if that is the prevailing logic, then I think my original proposal (just adding a .ll) makes the most sense. Still, I think the bit-width based modifiers is the cleaner solution. Tzachi, perhaps you can #ifdef the cli code to only use the [.8, ..., .64] for new and/or 64-bit platforms? Just a thought... John -- John W. Linville linville at tuxdriver.com