On Tuesday 14 September 2004 00:28, Jon Smirl wrote:
> Doesn't the base platform need to be designed to also treat individual
> heads as resources?
>
> fbdev only sets the mode on a single head. My cards have more that one
> head. When I tried adding mode setting to DRM so that I could handle
> my other heads there was a big uproar that fbdev owns mode setting and
> that code shouldn't be duplicated. Making fbdev support more than one
> head means that it's API has to be redesigned.
What do you mean?
Your driver has 2 heads, both of which have independent outputs and
separate framebuffers, then register your driver twice:
display0->fb0->framebuffer0-|
common par
display1->fb1->framebuffer1-|
Or outputs are interdependent with a common framebuffer, then register the
driver once:
par0
display0->fb0->framebuffer-|
par1
Or outputs are independent, but shares a common framebuffer, then register
driver twice, each info with the same pointer to framebuffer:
par0
display0->fb0-|
framebuffer
display1->fb1-|
par1
Tony
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
