From: Dan Malek <dan@mvista.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-embedded@lists.linuxppc.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: Board names for 4xx
Date: Mon, 17 Sep 2001 11:56:10 -0400 [thread overview]
Message-ID: <3BA61D1A.3A79E5B9@mvista.com> (raw)
In-Reply-To: 20010916211605.D14279@cpe-24-221-152-185.az.sprintbbd.net
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.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-09-17 15:56 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 [this message]
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
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=3BA61D1A.3A79E5B9@mvista.com \
--to=dan@mvista.com \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.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).