Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 7 Oct 2001 17:53:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 7 Oct 2001 17:53:42 -0400 Received: from lightning.swansea.linux.org.uk ([194.168.151.1]:28425 "EHLO the-village.bc.nu") by vger.kernel.org with ESMTP id ; Sun, 7 Oct 2001 17:53:24 -0400 Subject: Re: Linux should not set the "PnP OS" boot flag To: jdthood@mail.com (Thomas Hood) Date: Sun, 7 Oct 2001 22:59:16 +0100 (BST) Cc: alan@lxorguk.ukuu.org.uk (Alan Cox), linux-kernel@vger.kernel.org In-Reply-To: <1002474604.831.134.camel@thanatos> from "Thomas Hood" at Oct 07, 2001 01:10:00 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > I append the patch that shows the sort of thing that I think needs > to be done. (This patch includes the change from spin_lock to > spin_lock_irqsave.) The patch would need to be accompanied by the > addition of stuff to allow the user to define CONFIG_PNPOS. Would it not be better to tackle the job head on ? If the pnpbios scan as it walks the devices configured them would that do the job ? - 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/