<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - No mouse cursor (invisible) with dual monitors and DVI/VGA "Y" cable, no display on DVI"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94259#c22">Comment # 22</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - No mouse cursor (invisible) with dual monitors and DVI/VGA "Y" cable, no display on DVI"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94259">bug 94259</a>
from <span class="vcard"><a class="email" href="mailto:huangran@iscas.ac.cn" title="HuangRan <huangran@iscas.ac.cn>"> <span class="fn">HuangRan</span></a>
</span></b>
<pre>Hi Kevin,
(In reply to Kevin Brace from <a href="show_bug.cgi?id=94259#c19">comment #19</a>)
<span class="quote">> Hi Eric,
>
> I think I have some explanations on why the cursor does not show up on your
> screen.
> The way VIA Technologies Chrome family of IGP (Integrated Graphics
> Processor) works is that it contains 2 display controllers internally.
> They call this IGA1 and IGA2 (I do not know what IGA stands for.).</span >
IGA should be VIA's display engine(I asked this from VIA's engineer before). As
I worked for RADEON driver, each IGA should has its HW cursor and as you said,
the IGA engine do the HW cursor show/hide/content changing.
<span class="quote">> Most likely what is going on is that OpenChrome is not really using one of
> the display controller, but the display controller is still functioning.
> What this means is that the display controller hardware is still running,
> but because OpenChrome is not really using this display controller, it is
> not turning on the hardware cursor.</span >
So can I understand that current UMS driver does not enable HW cursor? So why
not enable SW cursor instead before HW one is working?
Thanks,
Frank</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>