From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] xserver-xorg: do not disable-dga as VESA driver requires it
Date: Fri, 25 Nov 2011 11:03:37 +0000 [thread overview]
Message-ID: <1322219018.26081.70.camel@phil-desktop> (raw)
In-Reply-To: <1322179246.10928.38.camel@ted>
On Fri, 2011-11-25 at 00:00 +0000, Richard Purdie wrote:
> Looking at vesa.c, there is quite a chunk of code in there depending on
> DGA.
I guess the question is, is this chunk of code actually doing anything
useful/important, or is it just there to support DGA on VESA? If the
latter then people who don't need/want DGA (which is probably everybody,
nowadays) can just take it out.
All that said, I would have thought that the VESA driver itself was
pretty much a fringe interest in this day and age. Is anybody really
using that on a shipping system? If it's just for qemux86 test harness
purposes then maybe we could turn on the vesafb driver in the kernel and
use the straight framebuffer driver in Xorg rather than the VESA one.
> Is there any harm to building DGA apart from an extra package? Its a
> self contained module isn't it?
I don't think it's that self-contained. Admittedly it isn't all that
big either, but still.
> If so, we should just be able to turn it on, package it separately and
> forget about it?
>
> Of course the ideal solution would be for someone to convert the vesa
> driver to use the xrandr API...
I don't quite understand what xrandr has to do with that. How does this
relate to DGA?
p.
next prev parent reply other threads:[~2011-11-25 11:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 13:47 [PATCH 0/1] xserver-xorg support to VESA driver Otavio Salvador
2011-11-22 13:47 ` [PATCH 1/1] xserver-xorg: do not disable-dga as VESA driver requires it Otavio Salvador
2011-11-22 17:14 ` Phil Blundell
2011-11-22 17:24 ` Otavio Salvador
2011-11-25 0:00 ` Richard Purdie
2011-11-25 10:41 ` Otavio Salvador
2011-11-25 11:03 ` Phil Blundell [this message]
2011-11-25 11:08 ` Richard Purdie
2011-11-25 11:57 ` Phil Blundell
2011-11-25 11:08 ` Otavio Salvador
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=1322219018.26081.70.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox