Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 14 Jan 2002 08:46:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 14 Jan 2002 08:45:51 -0500 Received: from swazi.realnet.co.sz ([196.28.7.2]:44173 "HELO netfinity.realnet.co.sz") by vger.kernel.org with SMTP id ; Mon, 14 Jan 2002 08:45:33 -0500 Date: Mon, 14 Jan 2002 15:44:34 +0200 (SAST) From: Zwane Mwaikambo X-X-Sender: To: "Maciej W. Rozycki" Cc: Jim Studt , Linux Kernel Subject: Re: Problem with ServerWorks CNB20LE and lost interrupts In-Reply-To: Message-ID: 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 On Mon, 14 Jan 2002, Maciej W. Rozycki wrote: > Why to code complicated workarounds for broken firmware? It's so easy to > fix, so either bother the vendor for a fix or replace the system with a > sane one. Reading and understanding the Intel's MP spec is a day or at > most two worth of man's work. I wouldn't trust the vendor that refuses to > invest in a product even that little. You may have noticed the great deal of "hacks" which people have put into the kernel over the years to get it to work with the imperfect world of hardware. It makes you wonder wether we should waste our time supporting broken hardware... Then again if we didn't we'd only run on 0.1% of the boxes out there ;) But... i'm in no way advocating for adding more kludges. Regards, Zwane Mwaikambo - 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/