Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262387AbUKVUmj (ORCPT ); Mon, 22 Nov 2004 15:42:39 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262354AbUKVUlb (ORCPT ); Mon, 22 Nov 2004 15:41:31 -0500 Received: from fw.osdl.org ([65.172.181.6]:2976 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S262376AbUKVUhf (ORCPT ); Mon, 22 Nov 2004 15:37:35 -0500 Date: Mon, 22 Nov 2004 12:36:58 -0800 (PST) From: Linus Torvalds To: Len Brown cc: Chris Wright , Adrian Bunk , Bjorn Helgaas , Kernel Mailing List , Andrew Morton Subject: Re: 2.6.10-rc2 doesn't boot (if no floppy device) In-Reply-To: Message-ID: References: <20041115152721.U14339@build.pdx.osdl.net> <1100819685.987.120.camel@d845pe> <20041118230948.W2357@build.pdx.osdl.net> <1100941324.987.238.camel@d845pe> <1101150469.20006.46.camel@d845pe> <1101155077.20006.110.camel@d845pe> 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: 1060 Lines: 26 On Mon, 22 Nov 2004, Linus Torvalds wrote: > > And that's exactly why I think the "minimally disruptive" fix is to not > disable them at all, but just fix up ELCR for anything that was already > enabled. Since that _is_ what "disable + re-enable" ends up actually > doing. Oh, and I think one alternative at this point is obviously to just go back to the "re-enable all interrupts early in the boot" code. Clearly we need to do _something_ for 2.6.10, and I want it to be something that is pretty much equivalent to what we _do_ have testing coverage of. Just to keep safe. I actually _like_ the "enable links only when needed" thing, which is why I'd prefer to look for alternatives. But I like even more not having to worry about strange hw setups, so "minimal fixing" really is pretty important. 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/