From: "Hendricks, Kevin" <khendricks@ivey.uwo.ca>
To: Benjamin Herrenschmidt <bh40@calva.net>
Cc: Michel Ddnzer <daenzerm@student.ethz.ch>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: asm statement in include/asm not ansi conform
Date: Fri, 01 Sep 2000 11:42:25 -0400 [thread overview]
Message-ID: <39AFCE61.7D68ED0C@ivey.uwo.ca> (raw)
In-Reply-To: 20000901152428.28366@mailhost.mipsys.com
Hi,
> When someone finally decide to implement code that checks if we have or
> not a PC BIOS from which we can read the values. It's on my (long)
> todolist, I was more or less hoping that Kostas would do it before me,
> especially since I don't have an x86 card to test with.
As I remember things, the xf4 code does do a simple check to see if there is a
bios present. I once enabled this code and found out on my B+W G3 machine, it
passed that bios test but read completely bogus values (even if you converted
the data for endian issues) whereas on my G4, it completely failed the simple
bios check that was present.
Without a real xf86 card with a bios present to play with, there is really no
way to try and devise a better test. Even if a bios is present, wouldn't OF
still do the initialization?
I think we should submit it as is and ifdef it to powerpc and forget about it
until we find out what is up.
By the way, either way, the values calculated by that code should be fine (as
long as the main code clock rate is 2950) whether intialized by OF or an actual
bios so no real harm should be done (certainly better than their hardcoded
values used now).
My 2 cents.
Kevin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-09-01 15:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-30 17:48 asm statement in include/asm not ansi conform Marc Dietrich
2000-08-30 18:12 ` Michel Dänzer
2000-08-31 16:09 ` Marc Dietrich
2000-08-31 16:18 ` Michel Dänzer
2000-09-01 10:22 ` Timothy A. Seufert
2000-09-01 11:44 ` Michel Dänzer
2000-09-01 14:37 ` Benjamin Herrenschmidt
2000-09-01 14:47 ` Michel Dänzer
2000-09-01 15:03 ` Hendricks, Kevin
2000-09-01 15:25 ` Benjamin Herrenschmidt
2000-09-01 15:24 ` Benjamin Herrenschmidt
2000-09-01 15:42 ` Hendricks, Kevin [this message]
2000-09-01 16:14 ` Benjamin Herrenschmidt
2000-09-01 20:13 ` Geert Uytterhoeven
2000-09-02 14:37 ` Michel Dänzer
2000-09-05 9:48 ` Timothy A. Seufert
2000-08-31 16:24 ` Benjamin Herrenschmidt
2000-09-01 9:19 ` Marc Dietrich
2000-09-01 10:48 ` Michel Dänzer
2000-09-01 11:03 ` Benjamin Herrenschmidt
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=39AFCE61.7D68ED0C@ivey.uwo.ca \
--to=khendricks@ivey.uwo.ca \
--cc=bh40@calva.net \
--cc=daenzerm@student.ethz.ch \
--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).