Re: [Linux-fbdev-devel] [PATCH] aty128fb 15/16 bit cleanup

[Sven L. <lu...@dp...>]

On Wed, Jun 27, 2001 at 11:18:07PM +0200, Michel D=E4nzer wrote:
> Sven LUTHER wrote:
> > But again, X actually thinks that they are responsible for handling t=
he
> > card, and the DRI follows their lead. It is the X driver who handles =
the
> > switch between the 2D and various 3D contexts.
>=20
> That's not correct. In the DRI context, the X server is one of many cli=
ents
> the DRM mediates hardware access between.

mmm, but itis the X driver which fournish the register save/restore routi=
ns,
at least that is how i see it. True it is the drm who calls them, i think=
, but
still, if you have no X running, i don't know how the save/restore stuff =
is
handled.

I suppose you could have any user app initializing the drm with the conte=
c=3Dxt
swithc function, but X and drm are very thigly intertwined.

Also, it seems the drm modules (or builtins) know really nothing about th=
e
underlaying hardware, it is the X server who tells them where the chip is=
, and
what kind of chip to use.

> > How will using hardware access on the console handle this ?
>=20
> I imagine fbcon would have to be a client of the DRM as well.

Sure, but will it not conflict with X ? DRI was built with 1 2D client an=
d
multiple 3d client in mind. I don't think it will run with more than 1 D2
client right now.

That said, my knowledge is rather fragmentary, it comes from studying the
glint driver (hardly the most advanced DRI support, altough it was the fi=
rst
DRI implementation back then)in hope to find time to implement DRI suppor=
t for
giamma + permedia3 or permedia3 alone.

Friendly,

Sven Luther