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

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?

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

--- Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
> 
> > Ok, I've a working implementation of the I2C code for radeonfb :)
> > The bug was very stupid: 0x50 became 0x20 and I spent a couple of weeks
> > wondering why it didn't work...
> > 
> > I've tested the code on a R300 board but it should work on any radeon. I
> > need a couple of day to merge  it into radeonfb and to test. I'll send a
> > patch ASAP.
> 
> Hi !
> 
> It would be real cool if you could start from the radeonfb version
> that is at bk://ppc.bkbits.net/linuxppc-2.5-benh (It needs my previously
> posted Power Management patch to fbdev to build, but you can just
> comment out 2 lines to make it build & run without it).
> 
> I'm currently having maintainership of this driver and I'll have an
> update sent to James rsn based on that tree, so that would simplify
> the merging significantly.
> 
> Ben.
> 


=====
Jon Smirl
jonsmirl@yahoo.com

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com


-------------------------------------------------------
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:06 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 [this message]
2003-08-21 20:45     ` Benjamin Herrenschmidt
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=20030821203931.55804.qmail@web14910.mail.yahoo.com \
    --to=jonsmirl@yahoo.com \
    --cc=benh@kernel.crashing.org \
    --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).