linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stuffed Crust <pizza@shaftnet.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [patch] [radeonfb] Radeon M26 and ATOM bios support (take 4)
Date: Tue, 28 Feb 2006 22:33:38 -0500	[thread overview]
Message-ID: <20060301033338.GA20460@shaftnet.org> (raw)
In-Reply-To: <1140736521.8264.49.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1440 bytes --]

On Fri, Feb 24, 2006 at 10:15:21AM +1100, Benjamin Herrenschmidt wrote:
> > I'm unsure how to best to proceed from here, so this patch is it until 
> > I get some more directed feedback.  
> 
> I'll review properly next week.

I've since completely gutted the radeon_probe_screens code, and now it 
takes advantage of (and relies heavily on) the connector table stuffs.  
It's far, far cleaner now, yay!   

I basically have two chunks of remaining code to write:

1) The OpenFirmware stuff, which basically requires some re-jiggering of 
   arguments passed in and return codes.  
2) User-specified layout code isn't smart enough to try the secondary 
   connectors if the primary connectors don't have anything connected.
   (This could be lessened by extending the syntax to explicitly state 
    CRT,CRT2,DFP,DFP2,etc..)

Then there's the big open question of how we should allow the user
to override the connector table, in case we mis-detect or don't have a
table to begin with.  If we have DDC enabled we can build a 
connector table by probing all DDC ports, using the existing logic. 

Thoughts?

(This work builds on the radeon-atom-4 patch, and is definately in the 
 "heavily experimental" stage.  I'll post a patch once I have time to 
 clean it up and fix the first two points)

 - Solomon
-- 
Solomon Peachy        				 ICQ: 1318344
Melbourne, FL
Quidquid latine dictum sit, altum viditur.

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

  reply	other threads:[~2006-03-01  3:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-03 20:44 [patch] [radeonfb] Radeon Mobility X700 (M26) and ATOM bios support Stuffed Crust
2006-01-03 23:29 ` Petr Vandrovec
2006-01-05  9:59 ` Benjamin Herrenschmidt
2006-01-05 20:13   ` Stuffed Crust
2006-02-14 21:28 ` Benjamin Herrenschmidt
2006-02-22 22:19   ` Stuffed Crust
2006-02-23  6:09     ` Stuffed Crust
2006-02-23  6:50       ` Benjamin Herrenschmidt
2006-02-23 22:36         ` [patch] [radeonfb] Radeon M26 and ATOM bios support (take 4) Stuffed Crust
2006-02-23 23:15           ` Benjamin Herrenschmidt
2006-03-01  3:33             ` Stuffed Crust [this message]
2006-03-01  3:46               ` Benjamin Herrenschmidt
2006-03-01 16:56                 ` Gabor Gombas
2006-03-01 20:36                 ` Stuffed Crust
2006-03-01 21:34                   ` [patch] [radeonfb] Radeon M26 and ATOM bios support (take 5) Stuffed Crust
2006-03-01 21:47                     ` 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=20060301033338.GA20460@shaftnet.org \
    --to=pizza@shaftnet.org \
    --cc=benh@kernel.crashing.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).