linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Kostas Gewrgiou <gewrgiou@imbc.gr>
Cc: Michel Dänzer <daenzerm@student.ethz.ch>,
	"Hendricks, Kevin" <khendricks@ivey.uwo.ca>,
	Josh Huber <huber@mclx.com>,
	Linux/PowerPC Devel List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: dual head r128
Date: Fri, 13 Oct 2000 18:21:27 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.10.10010131819430.381-100000@cassiopeia.home> (raw)
In-Reply-To: <Pine.LNX.4.21.0010122029001.1217-100000@idd-01.imbc.gr>


On Thu, 12 Oct 2000, Kostas Gewrgiou wrote:
> On Thu, 12 Oct 2000, Michel [iso-8859-1] Dänzer wrote:
> > So this code from the current X CVS:
> >
> >     R128ReadBIOS(0x0000, info->VBIOS, R128_VBIOS_SIZE);
> >     if (info->VBIOS[0] != 0x55 || info->VBIOS[1] != 0xaa) {
> >         xf86DrvMsg(pScrn->scrnIndex, X_WARNING,
> >                    "Video BIOS not detected in PCI space!\n");
> >
> > only checks if there is a ROM, not if it's a BIOS?
>
> Right, from the pci spec the table is something like this
> Offset    Length    Value    Description
> 0h          1        55h    ROM Signature, byte 1
> 1h          1        AAh    ROM Signature, byte 2
> ...
> 18h-19h     2        xx     Pointer to PCI Data Structure
>
> PCI Data Structure
> Offset    Length  Description
> ...
> 14           1    Code Type
> ..
>
> Code Type is 0 for bios and 1 for OF
>
> So you'll have to add one more test to check for BIOS/OF

IIRC, it's also possible to have one ROM that contains both x86 BIOS and
F-Code Open Firmware stuff. It may require compression to achieve this due to
the limited size to the ROM. I think I saw this on the Firmworks website, an
eon ago.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2000-10-13 16:21 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-12 14:30 dual head r128 Hendricks, Kevin
2000-10-12 16:11 ` Kostas Gewrgiou
2000-10-12 17:22   ` Michel Dänzer
2000-10-12 17:44     ` Kostas Gewrgiou
2000-10-12 21:25       ` Michel Dänzer
2000-10-13 15:26         ` Kostas Gewrgiou
2000-10-13 16:21       ` Geert Uytterhoeven [this message]
     [not found] <Pine.LNX.4.10.10010132302530.381-100000@cassiopeia.home>
2000-10-13 21:36 ` Benjamin Herrenschmidt
2000-10-13 21:47   ` Michel Lanners
2000-10-14 10:13     ` Benjamin Herrenschmidt
2000-10-14 10:21   ` Geert Uytterhoeven
     [not found] <19340906102959.14429@192.168.1.2>
2000-10-12 17:57 ` Gabriel Paubert
     [not found] <200010121619.TAA27476@ns0.imbc.gr>
2000-10-12 17:08 ` Kostas Gewrgiou
  -- strict thread matches above, loose matches on Subject: below --
2000-10-12 16:25 Hendricks, Kevin
2000-10-12 13:41 Hendricks, Kevin
2000-10-12 14:10 ` Kostas Gewrgiou
2000-10-11 18:17 Josh Huber
2000-10-11 18:43 ` Michel Dänzer
2000-10-11 18:52   ` Josh Huber
2000-10-11 19:04     ` Tom Rini
2000-10-11 19:09     ` Michel Dänzer
2000-10-11 19:26       ` Josh Huber
2000-10-11 22:48         ` Michel Dänzer
2000-10-13 17:16           ` Josh Huber
2000-10-12 13:09     ` Kostas Gewrgiou
2000-10-12 15:13       ` Benjamin Herrenschmidt
2000-10-12 15:49         ` Gabriel Paubert
2000-10-12 16:40           ` David Edelsohn
2000-10-17  0:12           ` Paul Mackerras
2000-10-17  5:56             ` Michel Lanners
2000-10-17 10:41             ` Benjamin Herrenschmidt
2000-10-17 13:45               ` Geert Uytterhoeven
2000-10-17 17:17                 ` Benjamin Herrenschmidt
2000-10-12 16:44         ` Kostas Gewrgiou
2000-10-11 21:01 ` Gabriel Paubert

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=Pine.LNX.4.10.10010131819430.381-100000@cassiopeia.home \
    --to=geert@linux-m68k.org \
    --cc=daenzerm@student.ethz.ch \
    --cc=gewrgiou@imbc.gr \
    --cc=huber@mclx.com \
    --cc=khendricks@ivey.uwo.ca \
    --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).