Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268381AbUILA3M (ORCPT ); Sat, 11 Sep 2004 20:29:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268392AbUILA3L (ORCPT ); Sat, 11 Sep 2004 20:29:11 -0400 Received: from fw.osdl.org ([65.172.181.6]:16064 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S268381AbUILA2y (ORCPT ); Sat, 11 Sep 2004 20:28:54 -0400 Date: Sat, 11 Sep 2004 17:28:25 -0700 (PDT) From: Linus Torvalds To: Jon Smirl cc: Christoph Hellwig , Dave Airlie , Alan Cox , =?ISO-8859-1?Q?Felix_K=FChling?= , DRI Devel , lkml Subject: Re: radeon-pre-2 In-Reply-To: <9e4733910409111721534b2e6d@mail.gmail.com> Message-ID: References: <9e47339104090919015b5b5a4d@mail.gmail.com> <9e47339104091010221f03ec06@mail.gmail.com> <1094835846.17932.11.camel@localhost.localdomain> <9e47339104091011402e8341d0@mail.gmail.com> <20040911132727.A1783@infradead.org> <9e47339104091109111c46db54@mail.gmail.com> <9e473391040911105448c3f089@mail.gmail.com> <9e4733910409111721534b2e6d@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1625 Lines: 39 On Sat, 11 Sep 2004, Jon Smirl wrote: > On Sat, 11 Sep 2004 11:13:17 -0700 (PDT), Linus Torvalds > wrote: > > So I'd much rather see the "hey, somebody else might have stolen my > > hardware, and now I need to re-initialize" as the _basic_ model. That just > > allows others to do their own thing, and play well together. More > > importantly, it allows the existing status quo, which means that if we > > take that as the basic approach, we _never_ have to make a complete flag > > day when we switch over to "_this_ driver does everything". See? > > We already have a mechanism for this: suspend/resume. Jon, you're not making sense any more. This discussion is just ridiculous, and I don't think it's worth cc'ing me if people can't try to work together, since I'm sadly not going to have time to actually implement any of this myself. If you are claiming that we should suspend/resume the whole chip just because two different programs want to access it, you're just crazy. We clearly _do_ have different subsystems already working together accessign the same chip, and they are _not_ doing stupid things like you are suggesting. They _work_. Today. No suspend/resume involved. That interaction has some troubles, and we're trying to _fix_ them. We're not trying to make idiotic statments. Yours was a singularly idiotic statment. Linus - 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/