linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: kronos@kronoz.cjb.net,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	James Simmons <jsimmons@infradead.org>
Subject: Re: EDID for radeonfb
Date: 21 Aug 2003 22:45:11 +0200	[thread overview]
Message-ID: <1061498711.18043.10.camel@gaston> (raw)
In-Reply-To: <20030821203931.55804.qmail@web14910.mail.yahoo.com>

On Thu, 2003-08-21 at 22:39, Jon Smirl wrote:
> The EDID code will allow the driver to ignore the BIOS copy in low RAM and use
> the ROM instead. Ben, could you make sure that the code to enable/access the
> ROM works on your Macs since I don't own one? Did you finish merging what was
> left of the Rage/Radeon PCI IDs from my patch?

The "Mac" cards don't have an x86 BIOS in ROM, they have an Open
Firmware instead, we need to fix proper detection of that, but that's
something I can try to do. I didn't finish merging it yet, I've been
quite busy with other drivers this week, radeonfb is on my todolist
for this week-end.

> EDID plus ROM will solve both problems: multiple adpaters and Mac portables
> needing EDID.

Yup (Note: the need for EDID in low RAM happened with x86 configs, on Macs,
I get it via the Open Firmware device tree).

Ben.




-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0

  reply	other threads:[~2003-08-21 21:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-19 22:33 EDID for radeonfb Kronos
2003-08-21 20:16 ` Benjamin Herrenschmidt
2003-08-21 20:39   ` Jon Smirl
2003-08-21 20:45     ` Benjamin Herrenschmidt [this message]
2003-08-21 20:51       ` Jon Smirl
2003-08-21 21:10         ` Benjamin Herrenschmidt
2003-08-21 21:21           ` Jon Smirl
2003-08-22  7:33             ` 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=1061498711.18043.10.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=jonsmirl@yahoo.com \
    --cc=jsimmons@infradead.org \
    --cc=kronos@kronoz.cjb.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).