Hi!
> >> >> These are not isolated problems. Linux needs a
> >> >properly designed
> >> >> graphics subsystem. One way to achieve that is to
> >> >design it all on
> >> >> paper first so that we can try and locate the
> >> >interactions between
> >> >> modules. For example the current mode setting
> >design
> >> >is definitely
> >> >> broken for multi-seat support, that's because you
> >> >didn't take that
> >> >> feature into account when writing the code.
> >> >
> >> >No it isn't the code Jesse posted can handle
> >multi-seat
> >> >fine in the
> >> >areas that it makes sense as we've pointed out to you
> >> >you cannot just
> >>
> >> The code doesn't create one device per CRTC. Missing
> >> that feature
> >> means that we need a persistent root priv app around
> >> that owns the
> >> single device and then listens for messages from each
> >> seat asking it
> >> to do things. That root priv app is not necessary, it
> >is
> >> a security
> >> risk and it should be eliminated.
> >
> >Fine, submit a patch. But don't block other people
> >patches just
> >because they do not address your favourite problem.
>
> I have already implemented this once and submitted a
> patch.
Seems you were not persistent enough. 'I submitted a patch long time
ago' is still no reason to block new work.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
