linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stuffed Crust <pizza@shaftnet.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: radeonfb: Add ATOM BIOS parsing v5b/v6 (rebased patch)
Date: Wed, 6 Sep 2006 18:00:27 -0400	[thread overview]
Message-ID: <20060906220027.GA30385@shaftnet.org> (raw)
In-Reply-To: <20060905153713.GA22789@shaftnet.org>


[-- Attachment #1.1: Type: text/plain, Size: 2109 bytes --]

Signed-Off-By:  Solomon Peachy <pizza@shaftnet.org>

Below is v5b of the ATOM BIOS patch.  Changes from v5:

 * LVDS/DFP with attached DDC port can be queried
 * LVDS/DFP won't be misdetected as CRT if a DDC port is connected.

  http://www.shaftnet.org/users/pizza/radeonfb-atom-2.6.17-v5b.diff
  http://www.shaftnet.org/users/pizza/radeonfb-atom-2.6.18-v5b.diff

Meanwhile, I've rolled in some other work to create v6 of the patch, 
this time against 2.6.18-rc6 only: 

  http://www.shaftnet.org/users/pizza/radeonfb-atom-2.6.18-v6.diff

Changes from v5b:

(Note -- many of these changes were taken in part from an older patch by
 Claudio Ciccan; I kept what was relevant and tossed the rest)

 * Added many new radeon PCI IDs (X300/X600/X700/X800/X850)
 * R4x0 series gets R300 tweaks (from Xorg)
 * Cap VRAM to 128M (Not really sure why.. related to mmap bugs?)
 * Add default_dynclk to builtin argument parsing.
 * Expanded the register mmio size to max (64k vs former 16k)
     (was there a reason why it wasn't already maxed?)
 * Initialization tweaks for R300 and RS300 (from Xorg)

I'd really like to see the v6 patch (or its successors) go in to 2.6.19, 
as the existing radeonfb driver simply won't work with newer radeon 
cards -- to say nothing about its multihead detection quirks.

So, I encourage everyone with a radeon card to give this new driver a 
whirl, especially if you have an X-series radeon board or if you were 
having head detection problems with the existing driver. 

Please run this with CONFIG_FB_RADEON_DEBUG on, so if something goes 
wrong I can get it fixed up.  

There at least one known corner case where things could go wrong
(LVDS/DFP port has an associated DDC port, but no EDID information is
available) but I'm already working on that.

See also:

  http://bugzilla.kernel.org/show_bug.cgi?id=6215

Ciao,

 - Solomon
-- 
Solomon Peachy        		       pizza at shaftnet dot org	 
Melbourne, FL                          ^^ (mail/jabber/gtalk) ^^
Quidquid latine dictum sit, altum viditur.          ICQ: 1318344


[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 373 bytes --]

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

[-- Attachment #3: Type: text/plain, Size: 182 bytes --]

_______________________________________________
Linux-fbdev-devel mailing list
Linux-fbdev-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel

  reply	other threads:[~2006-09-06 22:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-05 15:37 radeonfb: Add ATOM BIOS parsing (rebased patch) Stuffed Crust
2006-09-06 22:00 ` Stuffed Crust [this message]
2006-09-07  8:26   ` radeonfb: Add ATOM BIOS parsing v5b/v6 " Michel Dänzer
2006-11-09  5:25   ` radeonfb: Add ATOM BIOS parsing v6a (rebased) Stuffed Crust
2006-11-26 16:46     ` Luca Tettamanti
2006-11-02  5:33 ` radeonfb: Add ATOM BIOS parsing (rebased patch) Andrew Morton
2006-11-06 14:17   ` Stuffed Crust
2006-11-06 19:04     ` Andrew Morton

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=20060906220027.GA30385@shaftnet.org \
    --to=pizza@shaftnet.org \
    --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).