Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 19 Sep 2002 13:53:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 19 Sep 2002 13:53:59 -0400 Received: from pc1-cwma1-5-cust128.swa.cable.ntl.com ([80.5.120.128]:15352 "EHLO irongate.swansea.linux.org.uk") by vger.kernel.org with ESMTP id ; Thu, 19 Sep 2002 13:53:58 -0400 Subject: Re: ide double init? + Re: BUG: Current 2.5-BK tree dies on boot! From: Alan Cox To: Patrick Mochel Cc: Jens Axboe , Anton Altaparmakov , Andre Hedrick , Linux Kernel In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 19 Sep 2002 19:02:30 +0100 Message-Id: <1032458550.27865.47.camel@irongate.swansea.linux.org.uk> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 982 Lines: 20 On Thu, 2002-09-19 at 18:48, Patrick Mochel wrote: > Yes, and that's the way it's set up: we check if the device has a driver > before we bind to it. However, dev->driver doesn't get set before the > device is registered with the core for PCI devices. That's fixed easily > enough. > > But, I'm a bit confused on where this is happening. The PCI layer will > probe for devices before any drivers are registered. The drivers are > registered, then they're attached to devices that were already discovered. > So, how are they getting init'ed twice? The IDE layer has to preserve ordering. It does that by doing pci device ordered scans at boot then handing the driver registrations over to the pci hotplug layer for new inserts. - 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/