From: John W. Linville <linville@tuxdriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PPC970FX 64-bit processor
Date: Mon, 10 Jan 2005 18:54:30 -0500 [thread overview]
Message-ID: <20050110235423.GA27850@tuxdriver.com> (raw)
In-Reply-To: <41E30B47.10908@orkun.us>
> 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
next prev parent reply other threads:[~2005-01-10 23:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 15:12 [U-Boot-Users] PPC970FX 64-bit processor Tzachi Perelstein
2005-01-10 15:15 ` John W. Linville
2005-01-10 15:53 ` tzachi perelstein
2005-01-10 16:15 ` Wolfgang Denk
2005-01-10 17:39 ` John W. Linville
2005-01-10 23:09 ` Tolunay Orkun
2005-01-10 23:54 ` John W. Linville [this message]
2005-01-10 15:45 ` Wolfgang Denk
2005-01-11 14:05 ` John W. Linville
2005-01-11 16:33 ` tzachi perelstein
-- strict thread matches above, loose matches on Subject: below --
2004-12-08 15:14 Tzachi Perelstein
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=20050110235423.GA27850@tuxdriver.com \
--to=linville@tuxdriver.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.