<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - DRM / KMS bootup error on VX900 platform"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94473#c28">Comment # 28</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - DRM / KMS bootup error on VX900 platform"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94473">bug 94473</a>
from <span class="vcard"><a class="email" href="mailto:kevinbrace@gmx.com" title="Kevin Brace <kevinbrace@gmx.com>"> <span class="fn">Kevin Brace</span></a>
</span></b>
<pre>(In reply to HuangRan from <a href="show_bug.cgi?id=94473#c21">comment #21</a>)
Hi Frank,
<span class="quote">> Hi Kevin,
>
>
> >
> > I saw the new bug report you filed regarding the HDMI.
> > I am thinking that this bug you originally filed for (AGP related issue)
> > probably existed when James wrote the code, and possibly he never bothered
> > to fix it or did not noticed it.
> > How do you think?
>
> I am not sure on this, with my debugging yesterday on the kernel, I found
> dev->agp is NULL which leads drm_agp_acquire() return NULL.
> -------------------------------------
> if (!dev->agp)
> return -ENODEV;
> -------------------------------------
> But for UMS driver, it does not return such error, so I still need
> investigate how UMS driver deals with that.
>
> Thanks,
> Frank</span >
I am wondering if a DRM API needs to be called that tests the device to see if
it is an AGP device.
At least from PCI configuration space registers, there is a way to tell this.</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>