From: Mark Douglas <mdouglas@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Ben Elliston <bje@redhat.com>, sid@sources.redhat.com
Subject: Re: endian attribute: setting or register?
Date: Thu, 31 May 2001 08:35:00 -0000 [thread overview]
Message-ID: <3B1665B0.91F43AD@redhat.com> (raw)
In-Reply-To: <20010531064435.B11758@redhat.com>
wouldn't it make more sense just to read the configuration reg that identifies
the endianess and then behave appropriately?
Mark
"Frank Ch. Eigler" wrote:
> Hi -
>
> On Thu, May 31, 2001 at 02:49:03PM +1000, Ben Elliston wrote:
> : The current base cpu classes include an "endian" attribute -- it's
> : currently added as a "register" type attribute. Should it be a
> : "setting" instead?
>
> Yes and no: some CPUs can switch endianness on the fly.
>
> : [...] by changing it, we save valuable real estate in
> : tksm's gui for the multitide of physical cpu registers
> : that may be listed. [...]
>
> tksm should be smarter about the layout of the attribute list windows.
>
> - FChE
>
> ------------------------------------------------------------------------
> Part 1.2Type: application/pgp-signature
next prev parent reply other threads:[~2001-05-31 8:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-30 21:50 Ben Elliston
2001-05-31 3:44 ` Frank Ch. Eigler
2001-05-31 8:35 ` Mark Douglas [this message]
2001-05-31 8:39 ` Frank Ch. Eigler
2001-05-31 8:41 ` Mark Douglas
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=3B1665B0.91F43AD@redhat.com \
--to=mdouglas@redhat.com \
--cc=bje@redhat.com \
--cc=fche@redhat.com \
--cc=sid@sources.redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).