From: Dan Malek <dan@embeddededge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Time Base register definitions inccorrect in asm-ppc/processor.h
Date: Mon, 7 Nov 2005 09:43:05 -0500 [thread overview]
Message-ID: <785c17b72560644d889e2a0657b2199c@embeddededge.com> (raw)
In-Reply-To: <200511071000.31398.sr@denx.de>
On Nov 7, 2005, at 4:00 AM, Stefan Roese wrote:
> After a quick look in some other ppc manuals (AMCC and Freescale) this
> seems
> to be not only a 440GX problem, but a generic ppc problem. I will
> prepare a
> patch for this.
If you just use the proper assembler instructions for the mttb/mftb
variants,
the assembler will chose the right encoding for the processor model.
> I didn't find any code referencing these registers.
This is why I don't like people just arbitrarily going through the
manuals and generating such #defines. If we don't use something,
let's not define it. How are you going to test a patch to "fix" this
stuff
if it isn't used? Just delete it and forget it.
Thanks.
-- Dan
next prev parent reply other threads:[~2005-11-07 14:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-05 17:43 [U-Boot-Users] Time Base register definitions inccorrect in asm-ppc/processor.h Mike Wellington
2005-11-07 9:00 ` Stefan Roese
2005-11-07 14:43 ` Dan Malek [this message]
2005-11-25 3:22 ` Mike Wellington
2005-11-25 8:16 ` Wolfgang Denk
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=785c17b72560644d889e2a0657b2199c@embeddededge.com \
--to=dan@embeddededge.com \
--cc=u-boot@lists.denx.de \
/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