<br><br><div class="gmail_quote">On Tue, Dec 14, 2010 at 12:11 AM, Jerome Glisse <span dir="ltr"><<a href="mailto:j.glisse@gmail.com">j.glisse@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div class="h5">On Mon, Dec 13, 2010 at 10:18 AM, Arnd Bergmann <<a href="mailto:arnd@arndb.de">arnd@arndb.de</a>> wrote:<br>
> On Monday 13 December 2010, Jammy Zhou wrote:<br>
>> On Mon, Dec 13, 2010 at 4:45 AM, Linus Walleij <<a href="mailto:linus.walleij@linaro.org">linus.walleij@linaro.org</a>>wrote:<br>
>><br>
>> > On 11 December 2010 22:41, Arnd Bergmann <<a href="mailto:arnd@arndb.de">arnd@arndb.de</a>> wrote:<br>
>> ><br>
>> > * amd-gpu -- a single but huge driver for the GPU. As is normally the<br>
>> >> case with GPU drivers, we can expect long discussions<br>
>> >> before it will get considered for mainline<br>
>> >> 4 patches<br>
>> >> 98 files changed, 278321 insertions(+), 0 deletions(-)<br>
>> >><br>
>> ><br>
>> > Just out of curiosity, following the discussion between Dave Airlie<br>
>> > and Codeaurora this summer re GPU driver shims.<br>
>> ><br>
>> > Is the AMD GPU exposing all functionality in its kernel driver or<br>
>> > is there some userspace blob somewhere with lots of e.g. GL<br>
>> > goodies?<br>
>> ><br>
>> All the functionality for the kernel driver of AMD GPU Z430/Z160 (now<br>
>> belongs to Qualcom) is exposed. But we need accompanied userspace library to<br>
>> call these functionality (buffer management, command submission, ...).<br>
><br>
> Who owns these components? If it's closed source, the only options we<br>
> have are lobbying for complete release of the specs for a reimplementation<br>
> or reverse-engineering the drivers, which may at least get easier with<br>
> a user space driver than it would be with a kernel driver.<br>
><br>
> Until there is a solution with an open source user space part, I would<br>
> suggest that the driver better be dropped from the Freescale BSP and<br>
> we should at least not waste time reviewing it.<br>
><br>
> Arnd<br>
<br>
</div></div>From a quick look it also seems that the API exposed to userspace<br>
would allow easy abuse of the GPU to access any system ram. There is a<br>
reason we do expensive command checking in the other amd gpu driver<br>
(drivers/gpu/drm/radeon/*cs.c files)<br></blockquote><div><br>No, the memory used by the GPU is reserved at boot time, so I think there is no such a problem.<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Cheers,<br>
<font color="#888888">Jerome<br>
</font></blockquote></div><br>