From: Richard Purdie <richard.purdie@linuxfoundation.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 00:00:46 +0000 [thread overview]
Message-ID: <1322179246.10928.38.camel@ted> (raw)
In-Reply-To: <CAP9ODKrBxULKL=3ZHhGiOU4g7+uM=ke+43sDU=h67CvU_q7bAA@mail.gmail.com>
On Tue, 2011-11-22 at 15:24 -0200, Otavio Salvador wrote:
> On Tue, Nov 22, 2011 at 15:14, Phil Blundell <philb@gnu.org> wrote:
> On Tue, 2011-11-22 at 13:47 +0000, Otavio Salvador wrote:
> > Xorg VESA driver calls DGAInit enforcing this symbol to be
> available
> > to the driver to work.
>
> Maybe it would be better to patch vesa.c to not require this
> symbol
> rather than forcing it on in the server for everyone. Or
> alternatively,
> if you genuinely want DGA, maybe make it a PACKAGECONFIG
> option.
>
> What worries me is that this changed lately as it were working fine.
>
> When xserver-xorg were update to 1.11 this has changed behind the
> scenes. This used to be disabled on lite flavour only.
Looking at vesa.c, there is quite a chunk of code in there depending on
DGA.
Is there any harm to building DGA apart from an extra package? Its a
self contained module isn't it?
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...
Cheers,
Richard
next prev parent reply other threads:[~2011-11-25 0:07 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 [this message]
2011-11-25 10:41 ` Otavio Salvador
2011-11-25 11:03 ` Phil Blundell
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=1322179246.10928.38.camel@ted \
--to=richard.purdie@linuxfoundation.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