From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Reserving an ATA interface
Date: 03 May 2003 19:08:26 +0200 [thread overview]
Message-ID: <1051981705.7818.63.camel@gaston> (raw)
In-Reply-To: <1051981168.4107.58.camel@gaston>
> Such an interface can't really know what slot will be
> picked by ide_register_hw() and can't "prepare" the HWIF with
> special iops, so it won't be much harmed by the fact we are
> calling init_hwif_data, but still, we should ultimately think
> about splitting completely the fact of allocating an hwif slot,
> setting it up, and triggering a probe on it. Those are 3 different
> things that are currently mixed in bad ways. I don't beleive
> fixing that fits in the 2.6 timeframe though.
I just though about another possible crap, though I haven't looked
enough to be sure, but PCI interfaces with no device will trigger
a similar problem as "empty" ide-pmac interfaces in that sense that
they will change dma ops, possibly mmio ops, etc.... If they hold
no device, their hwif->present will not be set, and thus the hwif
slot can possibly get re-used by thing like ide-cs (or anybody else
that rely on ide_register_hw() to allocate a new slot) without
those changes to hwif done by the PCI interface beeing cleared.
So my patch may actually fix some cases there too.
Ben.
next prev parent reply other threads:[~2003-05-03 16:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-03 9:33 Reserving an ATA interface Benjamin Herrenschmidt
2003-05-03 16:42 ` Bartlomiej Zolnierkiewicz
2003-05-03 16:59 ` Benjamin Herrenschmidt
2003-05-03 17:08 ` Benjamin Herrenschmidt [this message]
2003-05-03 17:21 ` Bartlomiej Zolnierkiewicz
2003-05-03 18:39 ` Benjamin Herrenschmidt
2003-05-03 19:31 ` Bartlomiej Zolnierkiewicz
2003-05-03 19:40 ` Benjamin Herrenschmidt
2003-05-03 17:12 ` Bartlomiej Zolnierkiewicz
2003-05-04 1:28 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2003-05-03 21:24 Chuck Ebbert
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=1051981705.7818.63.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--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