From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from fed1rmmtao10.cox.net (fed1rmmtao10.cox.net [68.230.241.29]) by ozlabs.org (Postfix) with ESMTP id 0828E2BC0F for ; Tue, 28 Sep 2004 17:01:37 +1000 (EST) Date: Tue, 28 Sep 2004 00:01:24 -0700 From: Matt Porter To: Segher Boessenkool Message-ID: <20040928000124.H30772@home.com> References: <4158DD68.2060707@sonartech.com.au> <20040927221323.A30581@home.com> <20040927224825.B30772@home.com> <7C908338-1113-11D9-8370-000A95A4DC02@kernel.crashing.org> <20040927231438.D30772@home.com> <20040927233749.E30772@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from segher@kernel.crashing.org on Tue, Sep 28, 2004 at 01:45:27AM -0500 Cc: David Gardiner , linuxppc-embedded@ozlabs.org Subject: Re: powerpc with gigabit card hanging List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, Sep 28, 2004 at 01:45:27AM -0500, Segher Boessenkool wrote: > >> Sure. But the interrupt _assignment_ should be done by firmware. > > > > I can't argue with ideaology. > > It's not ideology; it's what the PCI spec says. > > >> p.s. And I know this isn't always practically possible; but why > >> then support a product like that at all, in the Open Source > >> community? > > > > By this reasoning, we should also not support the many BIOS/OF > > platforms that report incorrect data and have to have their > > reported data fixed up by the kernel. That's gross too by the > > same measure. > > There is a difference between patching some errors and doing > all the work yourself. I see your point of view and disagree. > But hey, let not me stop you from doing this. Don't worry, you won't. :) -Matt