From: Leonardo Pereira Santos <lsantos@pd3.com.br>
To: Steven Blakeslee <BlakesleeS@embeddedplanet.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Can software discover MPC8xx variant?
Date: Wed, 29 Jan 2003 15:15:28 -0200 [thread overview]
Message-ID: <200301291515.28980.lsantos@pd3.com.br> (raw)
In-Reply-To: <D73A25AA6E54D511AD74009027B1110F3C05EC@ORION>
Ok, but in this case the hardware itself wouldn't know waht revision or
whatever it is. And they already have to change the processor, so you have to
change the hardware anyway, mount or not a few resistors shouldn't be hard.
On Wednesday 29 January 2003 15:02, you wrote:
> Or you could set it in some type of data structure in your bootloader. No
> hardware change this way.
>
> -----Original Message-----
> From: Leonardo Pereira Santos [mailto:lsantos@pd3.com.br]
> Sent: Wednesday, January 29, 2003 11:30 AM
> To: linuxppc-embedded@lists.linuxppc.org
> Subject: Re: Can software discover MPC8xx variant?
>
>
>
>
> As the 8xx family is supported by the kernel, I assume that what you want
> is to know if the 8xx processor running supports some feature? If this is
> the case, I can tell you how to do it the way I'd.
> You can define some ioport with pull-up and pool-down resistors and in the
> manufacturing process specifiy if this board is for product A, then you
> should use MPC850DSL and you will mount some of the pull-ups and
> pull-downs. If the board is for product B, then you should mount MPC850SAR
> and mount differently the pull-ups and downs. By reading the value on the
> selected pins, you might de able to know what board this is. This scheme
> can also be used to know what hardware revision your board have.
>
> On Wednesday 29 January 2003 12:13, Marius Groeger wrote:
> > On Wed, 29 Jan 2003, Alex Zeffertt wrote:
> > > Can anybody tell me if there is a way to identify which processor from
> > > the MPC8xx family software is running on. I hoped I could use the IMMR
> > > special purpose register. However, this only tells you the silicon
> > > revision, which can have the same value even if the processors are
> > > different!
> > >
> > > Does the processor type (e.g. 862, 857T, 857DSL) reside anywhere in the
> > > processor?
> >
> > U-Boot/PPCboots cpu/mpc8xx/cpu.c contains a lot of generic type
> > detection code, but even there the assumes that the basic type is
> > known at compile time.
> >
> > Regards,
> > Marius
>
> ---------------------------------------------------------------------------
>
> >-- Marius Groeger SYSGO Real-Time Solutions AG
> > mgroeger@sysgo.de Software Engineering Embedded and Real-Time
> > Software www.sysgo.de Voice: +49-6136-9948-0 Am Pfaffenstein 14
> > www.osek.de FAX: +49-6136-9948-10 55270 Klein-Winternheim, Germany
> > www.elinos.com
>
> - --
>
> Leonardo Pereira Santos
> Engenheiro de Projetos
> PD3 Tecnologia
> av. Pará 330/202
> (51) 3337 1237
>
> Today Fortune tells us:
> Are you scared of speed? If so, try Windows NT.
>
>
- --
Leonardo Pereira Santos
Engenheiro de Projetos
PD3 Tecnologia
av. Pará 330/202
(51) 3337 1237
Today Fortune tells us:
Is knowledge knowable? If not, how do we know that?
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-01-29 17:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 17:02 Can software discover MPC8xx variant? Steven Blakeslee
2003-01-29 17:15 ` Leonardo Pereira Santos [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-29 17:31 Steven Blakeslee
2003-01-29 16:29 Leonardo Pereira Santos
2003-01-29 13:56 Alex Zeffertt
2003-01-29 14:13 ` Marius Groeger
2003-01-30 20:52 ` Dan Malek
2003-02-03 9:58 ` Alex Zeffertt
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=200301291515.28980.lsantos@pd3.com.br \
--to=lsantos@pd3.com.br \
--cc=BlakesleeS@embeddedplanet.com \
--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 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.