From: Takayuki Yamaizumi <zumi@yamato.ibm.co.jp>
To: Adrian Cox <apc@agelectronics.co.uk>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: G3 Upgrade Questions....
Date: 30 Jul 1999 10:38:52 +0900 [thread overview]
Message-ID: <lcemhq29xv.fsf@yamato.ibm.com> (raw)
In-Reply-To: Adrian Cox's message of "Thu, 29 Jul 1999 10:09:17 +0100"
Hi, Adrian,
Thanks for your advice,
adrian> I'm a little confused by this patch, because it is very different from
adrian> Motorola's application note AN1800/D (Programming the Thermal Assist
adrian> Unit in the MPC750 Microprocessor).
adrian> http://www.mot.com/SPS/PowerPC/teksupport/teklibrary/appnotes/an1800.pdf
I've never checked that document, so I download it (but, today I
have no spare time for reading, sorry). That patch is based on
cpu_temp in the older vger kernel which was commented out in 2.1.119
(or around this version, I remember. And still being commented out in
the latest kernel.) and have been created only using Motorola's
"PowerPC 750 User's Manual"
http://www.mot.com/SPS/PowerPC/library/750_um.pdf
as reference.
adrian> 1) No calibration. The board vendor is supposed to calibrate the TAU
adrian> before shipping the board, then supply the calibration value. I'm not
adrian> sure whether Apple do this.
adrian> 2) Why all the time spent doing bit reversals? Why not just fix the
adrian> broken values in processor.h and test the correct bits to start with?
Currently, I don't care about the definition in
include/asm-ppc/processor.h, but should be fixed if broken. I also
have been confusing why bit reversal is needed for reading
"reasonable" value of tempearture.
--
Takayuki Yamaizumi
Software Development Lab, IBM Japan.
E-mail: ty@tokusen.org, ty@kamoi.imasy.or.jp (Home)
zumi@yamato.ibm.co.jp (Office)
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-07-30 1:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-27 22:39 G3 Upgrade Questions ian geiser
1999-07-28 0:09 ` Paul Mackerras
1999-07-28 22:12 ` Jeremy Fitzhardinge
1999-07-29 0:47 ` I still cannot get L2cr to activate! ian reinhart geiser (ADMIN)
1999-07-29 4:46 ` G3 Upgrade Questions Takayuki Yamaizumi
1999-07-29 9:09 ` Adrian Cox
1999-07-30 1:38 ` Takayuki Yamaizumi [this message]
1999-07-30 11:38 ` Charles Lepple
[not found] ` <v04011707b3c5d8700e76@[199.174.198.69]>
[not found] ` <37A05228.3DFEDF87@msoe.edu>
1999-07-29 13:59 ` I still cannot get L2cr to activate! Jerry Quinn
1999-07-29 15:15 ` ian reinhart geiser (ADMIN)
1999-07-28 4:39 ` G3 Upgrade Questions Neil Jolly
1999-07-28 12:53 ` ian reinhart geiser (ADMIN)
[not found] <87emhr7ocz.fsf@hades.nocrew.net>
1999-07-29 11:50 ` Geert Uytterhoeven
1999-07-29 12:12 ` Stefan Berndtsson
1999-07-29 12:32 ` Chris Ridd
1999-07-29 12:55 ` Gabriel Paubert
1999-07-29 13:30 ` Andreas Bogk
-- strict thread matches above, loose matches on Subject: below --
1999-07-29 14:11 David DeHaven
1999-07-29 16:57 Ron Chmara
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=lcemhq29xv.fsf@yamato.ibm.com \
--to=zumi@yamato.ibm.co.jp \
--cc=apc@agelectronics.co.uk \
--cc=linuxppc-dev@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).