Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759821AbXE2Ot0 (ORCPT ); Tue, 29 May 2007 10:49:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758924AbXE2OtP (ORCPT ); Tue, 29 May 2007 10:49:15 -0400 Received: from gprs189-60.eurotel.cz ([160.218.189.60]:1715 "EHLO spitz.ucw.cz" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1758760AbXE2OtO (ORCPT ); Tue, 29 May 2007 10:49:14 -0400 Date: Tue, 29 May 2007 14:26:32 +0000 From: Pavel Machek To: Jon Smirl Cc: Dave Airlie , Jesse Barnes , Jeff Garzik , Jesse Barnes , linux-kernel@vger.kernel.org, "Antonino A. Daplas" Subject: Re: [RFC] enhancing the kernel's graphics subsystem Message-ID: <20070529142631.GA6460@ucw.cz> References: <465228E2.1030405@garzik.org> <9e4733910705211726q38be6843ndac49f8adc25aad0@mail.gmail.com> <200705211856.56228.jbarnes@virtuousgeek.org> <9e4733910705220727t605f2522tc4eb97257735c0fb@mail.gmail.com> <21d7e9970705220735j37bc8eeck87db7193c08c4c24@mail.gmail.com> <9e4733910705220813i479a68faxf365697962317c60@mail.gmail.com> <21d7e9970705221025r2f798dc5x310947db040c6521@mail.gmail.com> <9e4733910705221258v660d8f42j16cc596ca820e8b8@mail.gmail.com> <20070528201213.GA5840@ucw.cz> <9e4733910705281357x592f0853re9492efdb5ef82e8@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9e4733910705281357x592f0853re9492efdb5ef82e8@mail.gmail.com> User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1700 Lines: 51 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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/