From: David Gibson <david@gibson.dropbear.id.au>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Board names for 4xx
Date: Tue, 18 Sep 2001 10:38:33 +1000 [thread overview]
Message-ID: <20010918103833.C1183@zax> (raw)
In-Reply-To: <3BA61D1A.3A79E5B9@mvista.com>
On Mon, Sep 17, 2001 at 11:56:10AM -0400, Dan Malek wrote:
>
> Tom Rini wrote:
>
> > I do wish someone else would speak up tho. Does anyone out there have an
> > opinion?
>
> It depends how you want to use this information. In the kernel, it is very
> critical we clearly distinguish between the "core" (the thing that executes
> instructions), the peripherals (the real difference among the SOC-type
> processors), and the board design (which will determine how the peripherals
> are configured).
>
> If the information from /proc is just used for pretty print out of
> information, I really don't care. If there are applications that read
> this for some internal configuration and flexibility, we better have a
> standard format.
I don't see that we need to structure the information in the machine:
field for this purpose though - if the core and peripherals
information turns out to be important it belongs better in other
fields of /proc/cpuinfo, I think. We already have cpu: and we could
make a core: if it was necessary - or encode the core information into
cpu: it belongs there more than in machine: I think. Just the board
type (and revision, where we can find that information) seems the
closest match to what machine: gives on more normal PPC machines.
--
David Gibson | For every complex problem there is a
david@gibson.dropbear.id.au | solution which is simple, neat and
| wrong. -- H.L. Mencken
http://www.ozlabs.org/people/dgibson
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-09-18 0:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-14 4:44 Board names for 4xx David Gibson
2001-09-14 6:05 ` David Gibson
[not found] ` <20010914072847.R21906@cpe-24-221-152-185.az.sprintbbd.net>
2001-09-17 2:28 ` David Gibson
2001-09-17 4:16 ` Tom Rini
2001-09-17 15:56 ` Dan Malek
2001-09-17 16:11 ` Kenneth Johansson
2001-09-17 18:33 ` Tom Rini
2001-09-18 0:35 ` David Gibson
2001-09-18 2:08 ` Tom Rini
2001-09-18 0:38 ` David Gibson [this message]
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=20010918103833.C1183@zax \
--to=david@gibson.dropbear.id.au \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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 NNTP newsgroup(s).