All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stuffed Crust <pizza@shaftnet.org>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [patch] [radeonfb] Radeon M26 and ATOM bios support (take 4)
Date: Wed, 01 Mar 2006 14:46:29 +1100	[thread overview]
Message-ID: <1141184789.4157.30.camel@localhost.localdomain> (raw)
In-Reply-To: <20060301033338.GA20460@shaftnet.org>


> 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.  

Or just write a small howto and I will do the job :) I've been very busy
lately mostly due to my newborn child, thus I didn't help more than
that, but I'm really interested in your work. I also want to bring along
a bunch of fixes like the memory mapping fixes I've been doing on X.org
radeon driver recently.

> 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..)

Agreed. (And X too btw ...)

In fact, we need a way to provide the driver with the full connector
mapping I think, in case it can't be obtained from the firmware.

> 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. 

module option is the easy/cheap way but sucks in some ways... sysfs per
device instance is nice but a bit "too late" unless we have a way for
the driver to re-probe... which is a good thing to have anyway since we
might finally deal with screen hotplug :)

In fact, a mix of both might do the trick... module/kernel argument for
a default override and sysfs for "live" override ?

I would however not bother too much at the moment with that. Let's get
the rest working first

> 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)

Thanks.

I'll look at your stuff in more detail asap and will then let it simmer
in -mm if I'm happy enough for at least a kernel version...

Ben.




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

  reply	other threads:[~2006-03-01  3:46 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
2006-03-01  3:46               ` Benjamin Herrenschmidt [this message]
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=1141184789.4157.30.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=pizza@shaftnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.