On Thu, 6 May 2004, Keith Whitwell wrote:

> Jon Smirl wrote:
> > --- Jens Owen <[EMAIL PROTECTED]> wrote:
> >
> >>Six years ago, most devices could not handle this type of restriction
> >>efficiently.  Things have improved on the high end; but the low end
> >>devices, are still very similar to what we had back in the day.  Even
> >>today, I would be very cautious of deploying an architecture where no
> >>devices can be touched from user space.  This will really box many
> >>driver developers into a corner they can't get out of.  Is that worth it
> >>for support of graphics pipeline hot plugging?  If you would like to get
> >
> >
> > It not's the graphics cards that are being hotplugged, it's other cards in the
> > system. If xfree hasn't coordinated with the kernel, the kernel hotplug code
> > could easily map the new hardware right on top of the Xfree HW.
>
> This doesn't sound like a huge problem, XFree could simply inform the kernel
> about what it has done, or use a kernel api to do the mappings for it.  It
> doesn't seem to require moving the driver to kernel space.

One problem that I encountered is that DRM driver does not know how to
reinitialize video mode in case of a lockup. So it would be real nice to
have DRM and FB merged so that a failed WaitForIdle could reinit the
hardware and call FB mode setting code to restore video mode.

Thus this part of 2d driver *wants* to be inside the kernel.

As far as acceleration - either 2d or 3d - it makes sense for it to stay
in userspace..

                        best

                          Vladimir Dergachev

>
> Keith
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Sleepycat Software
> Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
> deliver higher performing products faster, at low TCO.
> http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
> --
> _______________________________________________
> Dri-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/dri-devel
>


-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to 
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to