linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Cc: Jon Smirl <jonsmirl@gmail.com>
Subject: Re: XGL/mesa-solo and fbdev
Date: Tue, 22 Feb 2005 18:22:36 +1100	[thread overview]
Message-ID: <1109056956.5412.107.camel@gaston> (raw)
In-Reply-To: <9e47339105022111483136bd56@mail.gmail.com>

On Mon, 2005-02-21 at 14:48 -0500, Jon Smirl wrote:
> XGL/mesa-solo is a project that has been going on for about a year and
> a half now to get X running on top of OpenGL instead of the existing
> 2D XAA drivers. XGL allows a vastly improved user experience as
> demonstrated at the recent X developer's conference. Removing the 2D
> drivers from X means that things like mode setting need to come from
> someplace else, like fbdev.
> 
> To make this project work XGL/mesa-solo needs support for these things
> at the minimum:
> 1) resetting of secondary cards
> 2) mode setting on all heads, not just the primary one
> 3) hardware cursor control
> 4) control of mode setting/cursor etc by users, not just root
> 5) DRM and fbdev need to not conflict
> 
> We are try to get everything in the stack working together before OLS
> this summer. I've posted code to implement some of these features and
> I'm seeking solutions for making the rest work. Does this look like
> something that can get finished in the next month or so? We also need
> time to get all of the layers above fbdev using the new support.

Finishing that in the next month or so is extremely optimist :)

I think we should do it the linux way, that is not take deadlines too
seriously, just do the stuff.

The first step is putting fbdev's and DRM driver together. I think it's
worth doing a stub right now rather than hacking radeonfb and the radeon
DRM together, because all other PCI card drivers at least will have the
same issues, and for various reasons, you may wnat to only use "half" of
it (that is not use the fbdev side or not use the DRM side), at least
for a while. (radeonfb doesn't always work 100% on all x86's)

The second step is to add video memory management & arbitration.

The third step is to add missing "features" like dual head etc.... and
the appropriate fbdev API changes to do it properly.

Ben.




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  parent reply	other threads:[~2005-02-22  7:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-21 19:48 XGL/mesa-solo and fbdev Jon Smirl
2005-02-21 21:16 ` James Simmons
2005-02-22  7:22 ` Benjamin Herrenschmidt [this message]
2005-02-22 17:31   ` James Simmons

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=1109056956.5412.107.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=jonsmirl@gmail.com \
    --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).