Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 16 Mar 2002 17:28:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 16 Mar 2002 17:28:15 -0500 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:55307 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Sat, 16 Mar 2002 17:28:06 -0500 Date: Sat, 16 Mar 2002 14:26:23 -0800 (PST) From: Linus Torvalds To: Alan Cox cc: "Eric W. Biederman" , Jeff Garzik , Anders Gustafsson , , , Subject: Re: [PATCH] devexit fixes in i82092.c 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 Sat, 16 Mar 2002, Alan Cox wrote: > > In the general reboot case yes it is a BIOS bug. In the general Linux > > booting Linux case there is no BIOS involved. > > In that case yes I can see why you want to turn the bus masters off when you > boot the new kernel Truning bus masters off is easy enough, and could just be done by some generic PCI reboot code. But for a linux-linux boot I think you also want to turn off interrupt generation to make sure some device isn't screaming on some irq, and that definitely requires explicit help by the driver itself. One question that hasn't come up: do we actually want to use the "remove" function for this, or have a separate shutdown function? Are there reasons to not use "remove" for shutdown? 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/