Re: New proposed DRM interface design

Jon Smirl
2004-09-05T16:05:31Z

They have to be merged. Cards with two heads need the mode set on each
head. fbdev only sets the mode on one head. If I teach fbdev how to
set the mode of the other head fbdev needs to learn about memory
management. The DRM memory management code is complex and is a big
chunk of the driver.

I would also like to fix things so that we can have two logged in
users, one on each head. This isn't going to work if one them uses
fbdev and keeps swithing the chip to 2D mode while the other user is
in 3D mode. The chip needs to stay in 3D mode with the CP running.

We're not going to get OOPS display while running X without merging.
Something I would really like to have since I just had some and was
force to hook up a serial console.

It is just plain stupid having multiple device drivers fighting over
control of a single piece of hardware. I thought we went over this
multiple times at OLS. There have been email discussions about this
since March.

On Sun, 05 Sep 2004 15:44:34 +0100, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Sul, 2004-09-05 at 16:33, Jon Smirl wrote:
> > Then how am I going to merge fbdev and DRM so that we don't have two
> > drivers fighting over the same hardware?
>
> Everyone else in the discussions but you seemed to have no plans to
> merge them, yet you keep going back to that plan and ignoring the other
> opinions.
>
> If you are merging them then something is wrong in the design. The only
> things they fundamentally share are knowledge of the current display
> layout, and state management for rendering.
>
> As you say "if BSD isn't even going to use the code". So why are you
> trying to make it hard for the BSD side ? They've got a perfectly good
> frame buffer layer too and not suprisingly it has the same requirements
> for knowledge.
>
> Alan
>
>

--
Jon Smirl
jonsmirl@gmail.com