<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 02/27/15 10:21 AM, Jonathan Adams
wrote:<br>
</div>
<blockquote
cite="mid:CAKr4wiQDKmd+6aqbTejSY8nbi=KBHT2RRht6ZJ4zsxB9T_bCbg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Is it impossible to "sticky" the intel driver, or is it
incompatible with other new components?<br>
<br>
</div>
Jon<br>
</div>
</blockquote>
Seems like it is just version-updated to non-working one without
consulting testing.<br>
Or at least without solution for all existing users. <br>
<br>
Cleaning up hipster-2015 to the old one with old version, seems
nicest solution,<br>
with ability to add new one for testing.<br>
Even if it start suddenly working with illumos patched with KMS, it
is not solution for present installs and all with not newest Intel
graphics.<br>
Yet, Ken has all that in mind.<br>
<blockquote
cite="mid:CAKr4wiQDKmd+6aqbTejSY8nbi=KBHT2RRht6ZJ4zsxB9T_bCbg@mail.gmail.com"
type="cite">
<div class="gmail_extra"><br>
<div class="gmail_quote">On 27 February 2015 at 00:47, Nikola M
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:minikola@gmail.com" target="_blank">minikola@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span class=""> <br>
<div>On 02/24/15 11:44 AM, ken mays via oi-dev wrote:<br>
</div>
<blockquote type="cite">
<div
style="color:#000;background-color:#fff;font-family:HelveticaNeue,Helvetica
Neue,Helvetica,Arial,Lucida
Grande,sans-serif;font-size:16px">
<div dir="ltr"><span>No, we didn't. You'll see that
it was all worth it. Ingenuity is risky business
- just own it, and embrace it.</span></div>
<div dir="ltr"><span>Either breathe fire or blow
smoke signals - or stand still.</span></div>
<div dir="ltr"><span><br>
</span></div>
<div dir="ltr"><span>~K</span></div>
</div>
</blockquote>
</span> We have large majority of already working installs
with borked X. <br>
It needs ability to use existing working Intel driver in
one way or another , (as I mentioned in lengthy mail)
because it is currently busted and we can't afford to ship
busted X/Intel in any form (it ruins experience for large
enough of people to just drop usage and testing.. en
masse).<br>
<br>
</div>
<br>
_______________________________________________<br>
oi-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:oi-dev@openindiana.org">oi-dev@openindiana.org</a><br>
<a moz-do-not-send="true"
href="http://openindiana.org/mailman/listinfo/oi-dev"
target="_blank">http://openindiana.org/mailman/listinfo/oi-dev</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
oi-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:oi-dev@openindiana.org">oi-dev@openindiana.org</a>
<a class="moz-txt-link-freetext" href="http://openindiana.org/mailman/listinfo/oi-dev">http://openindiana.org/mailman/listinfo/oi-dev</a></pre>
</blockquote>
<br>
</body>
</html>