From: Dan Malek <dan@embeddededge.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Kumar Gala <galak@freescale.com>,
linuxppc-embedded list <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH] ppc32: 8xx pq platform system descriptions
Date: Sun, 21 Aug 2005 21:28:56 -0400 [thread overview]
Message-ID: <b3aa1ae4c201e865b6dfbef68253983b@embeddededge.com> (raw)
In-Reply-To: <20050821235524.GE6746@dmt.cnet>
On Aug 21, 2005, at 7:55 PM, Marcelo Tosatti wrote:
> - Do you have any plans on actually using device model information by
> drivers (as was done in the mpc8xxx/gianfar) on m8xx? Its not very
> clear
> to me what are the the practical advantages of that?
It may be nice if we can do that. We have to be careful about sharing
CPM drivers between the 8xx and CPM2 (82xx/83xx/85xx). It's tempting,
but I still believe the differences outweigh the similarities. The
overhead
of trying to use common drivers would be quite costly on the 8xx.
> - I don't know whether its possible to retrieve 8xx CPUID information
> (if there is any). Can't find anything in the manual.
We really can't. The PVR only represents the processor core
information,
and for the most part they are all the same. It used to be we could use
the CPM microcode version, but these are now nearly the same. Some
attempts have been made to probe for CPM peripherals that don't exist,
but it seems on some parts the CPM is the same and the signals just
aren't
bonded out of the chip.
For the most part, the person doing the kernel configuration just simply
has to know what part they are using. You have to select the proper
peripherals, and you need the board support for the IO pin routing.
In an embedded environment where resources still need to be
carefully managed, I don't think this is unrealistic.
Thanks.
-- Dan
prev parent reply other threads:[~2005-08-22 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 19:01 [PATCH] ppc32: 8xx pq platform system descriptions Vitaly Bordug
2005-08-19 20:14 ` Kumar Gala
2005-08-21 23:55 ` Marcelo Tosatti
2005-08-22 1:28 ` Dan Malek [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=b3aa1ae4c201e865b6dfbef68253983b@embeddededge.com \
--to=dan@embeddededge.com \
--cc=galak@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=marcelo.tosatti@cyclades.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 NNTP newsgroup(s).