No subject

limited set of features.  I'm not sure what the differences are between this
and the intel drivers.  Anyone know?

-- 
Greg Bair
gregbair at gmail.com

--0016e65b5ec61ca66d048f908352
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Mon, Sep 6, 2010 at 12:29 AM, Christo=
pher James Halse Rogers <span dir=3D"ltr">&lt;<a href=3D"mailto:raof at ubuntu=
.com">raof at ubuntu.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x;">
Hello X wranglers!<br>
<br>
It&#39;s that time of the release, again(!), where it&#39;s too late for a<=
br>
magical fix for i8xx to appear, and we need to work out the least-bad<br>
option to use as the default.<br>
<br>
It, again(!), looks like there&#39;s hope for the next release with Chris<b=
r>
Wilson&#39;s accel-less shadow branch, but there are still problems with<br=
>
that branch, it&#39;s not mainline, and it&#39;s too late to switch for<br>
Maverick.<br>
<br>
This, as I count it, leaves us with 3 options:<br>
<br>
1) Blacklist KMS on the cards, as we did for Lucid, and let VESA drive<br>
them. =A0This is my current favourite, and what we&#39;ve got in the kernel=
<br>
now.<br>
<br>
Pros:<br>
=A0* Users get the VESA driver, which should work.<br>
<br>
Cons:<br>
=A0* Laptops might not have the panel&#39;s native modes in their VESA bios=
,<br>
leading to suboptimal resolution or -vesa not working at all (there&#39;s a=
<br>
report of -vesa failing completely).<br>
=A0* Users need to fiddle with grub options or modprobe config to load the<=
br>
intel driver.<br>
<br>
2) Don&#39;t blacklist KMS, but drop these cards from X&#39;s autoload list=
.<br>
This will let fbdev take over.<br>
<br>
Pros:<br>
=A0* If KMS brings up the native mode, users get the native mode.<br>
=A0* Resolution can be set on the kernel command line.<br>
=A0* Dual-head will work in clone mode if second head is connected at boot<=
br>
time.<br>
<br>
Cons:<br>
=A0* Can&#39;t change resolution at runtime<br>
=A0* Non-default resolutions *must* be set on the kernel command line.<br>
=A0* User needs to generate an xorg.conf to use the intel driver.<br>
<br>
3) Do nothing, let the intel driver load on kms.<br>
<br>
Pros:<br>
=A0* If it doesn&#39;t crash, everything works.<br>
<br>
Cons:<br>
=A0* Lots of crashes.<br>
<br>
<br>
I favour option (1). =A0I think that the ability to switch resolution is<br=
>
likely to be more important than starting in the best possible<br>
resolution. =A0I also think that users are more likely to be familiar with<=
br>
the VESA driver, and be more likely to ask useful questions.<br>
<br>
We&#39;ll release-note this, again(!).<br>
<br>
Does anyone have any further insights or better ideas?<br>
<br>--<br>
Ubuntu-x mailing list<br>
<a href=3D"mailto:Ubuntu-x at lists.ubuntu.com">Ubuntu-x at lists.ubuntu.com</a><=
br>
Modify settings or unsubscribe at: <a href=3D"https://lists.ubuntu.com/mail=
man/listinfo/ubuntu-x" target=3D"_blank">https://lists.ubuntu.com/mailman/l=
istinfo/ubuntu-x</a><br>
<br></blockquote></div><br><br clear=3D"all">From my (admittedly limited) u=
nderstanding of vesa, it provides only a limited set of features. =A0I&#39;=
m not sure what the differences are between this and the intel drivers. =A0=
Anyone know?<div>
<br>-- <br>Greg Bair<div><a href=3D"mailto:gregbair at gmail.com" target=3D"_b=
lank">gregbair at gmail.com</a></div><br>
</div>

--0016e65b5ec61ca66d048f908352--