From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jens Axboe <axboe@suse.de>
Cc: Anton Altaparmakov <aia21@cantab.net>,
Andre Hedrick <andre@linux-ide.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ide double init? + Re: BUG: Current 2.5-BK tree dies on boot!
Date: 19 Sep 2002 11:58:30 +0100 [thread overview]
Message-ID: <1032433110.26669.30.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20020919100831.GC31033@suse.de>
On Thu, 2002-09-19 at 11:08, Jens Axboe wrote:
> Seems to be ide probe calling the pci probe functions, and then they get
> called by the pci layer later when they register. Dunno what the best
> way to handle this is. Alan quotes ordering constraints as the reason.
> Then maybe the easiest fix is to just do
Something is very wrong if they initialize twice. Hacking chipset_init
is not a fix its an ugly hack.
They should end up on the ide queue to init, then transfer to the core
PCI hotplug layer. The hotplug layer won't call the setups again because
the device is already owned by the driver that grabbed it.
In 2.4 at least pci_register_driver checks that it doesnt do that
pci_for_each_dev(dev) {
if (!pci_dev_driver(dev))
count += pci_announce_device(drv, dev);
}
2.5 should do the same
Alan
next prev parent reply other threads:[~2002-09-19 10:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-18 20:44 Anton Altaparmakov
2002-09-18 22:58 ` Anton Blanchard
2002-09-19 8:47 ` Jens Axboe
2002-09-19 9:33 ` ide double init? + " Anton Altaparmakov
2002-09-19 9:45 ` Jens Axboe
2002-09-19 10:08 ` Jens Axboe
2002-09-19 10:58 ` Alan Cox [this message]
2002-09-19 11:14 ` Jens Axboe
2002-09-19 13:28 ` Alan Cox
2002-09-19 13:27 ` Jens Axboe
2002-09-19 17:48 ` Patrick Mochel
2002-09-19 18:02 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1032433110.26669.30.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=aia21@cantab.net \
--cc=andre@linux-ide.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®