Hi Nelson!

On Wed, 17 Jun 2009 04:31:57 +0200, Nelson Castillo wrote:
> On Sun, Jun 14, 2009 at 9:02 AM, Luca Capello<[email protected]> wrote:
>> New config setting for the default value of xglamo_hack_enabled.
[...]
> I'm a little confused with 2 options for (almost) the same thing. I
> know it's not the same thing but still...  If you wanted it to be
> disabled you would need to use a different .config anyway because it
> is enabled by default.
>
> Why is this useful? (I might be missing something here).

What you are missing is distributions (like Debian) providing both
xf86-video-glamo and Xglamo.  Thus, while xf86-video-glamo should be the
default for new Debian installations, with the current .config based on
gta02_moredrivers one can only use Xglamo out of the box, because of the
workaround enabled by default.  On the contrary, not providing the
workaround will be a problem for Xglamo users.  Let me remind you that
xf86-video-glamo has at least one annoying bug compared to Xglamo:

  http://bugs.debian.org/529078
  http://docs.openmoko.org/trac/ticket/2288

The solution I see can be double:

1) simply make xglamo_hack_enabled 0 by default

2) my (transitioning) patch

The first solution seems the correct one to my non-programmer eyes: the
bug is not in the kernel, thus if there is the kernel provides a
workaround, it should be activated by the user.  OTOH, I still do not
understand why Debian seems to be the only distribution providing (and
using) xf86-video-glamo, which means that with the first solution all
the other distributions should activate the workaround at boot.  Again,
I consider this the *proper* solution, but I admit it seems a no-op.

FWIW, on Debian we can already disable the config option for the
workaround, given that:

1) only xf86-video-glamo is properly speaking distributed by Debian,
   since xserver-xglamo is still not in main, but in the external, thus
   unofficial, pkg-fso repository

     http://pkg-fso.alioth.debian.org

2) I, with my Debian xserver-xglamo maintainer hat on, will shortly
   remove xserver-xglamo from the pkg-fso repository, as explained at

     http://lists.alioth.debian.org/pipermail/pkg-fso-maint/2009-May/001140.html

However, in this case if anyone wants to compile her/his own Xglamo,
then she/he needs a non-Debian kernel.

Another option would be to patch the Debian kernel to compile the
workaround, but disable it by default: would this be a better solution?

Thx, bye,
Gismo / Luca

Attachment: pgpRRJh01hdn5.pgp
Description: PGP signature

Reply via email to