From: Paul Mackerras <paulus@au1.ibm.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
benh@kernel.crashing.org
Subject: ide-cs problem (was Re: any chance of 2.6.0-test*?)
Date: Tue, 14 Jan 2003 13:32:43 +1100 [thread overview]
Message-ID: <15907.30411.916585.622130@argo.ozlabs.ibm.com> (raw)
In-Reply-To: <1042469960.18624.9.camel@irongate.swansea.linux.org.uk>
Alan Cox writes:
> The ide release code isnt safe in any context.
Do you mean ide_release in ide-cs.c, or ide_unregister in ide.c?
> The code is currently written on the basis that people don't mangle
> free interfaces (the free up code restores stuff which I grant is
Well, the problem is that there is no way to say that there is a hwif
present without any drives. The low-level driver (i.e. pmac.c) has to
leave hwif->present = 0, because if you set hwif->present = 1 then the
ide probe code won't go looking for drives. The probe code then only
sets hwif->present = 1 if it finds a drive. If hwif->present gets
left at 0 then it is liable to be taken over for a pcmcia card.
What would be good is a way to say "I know this hwif is definitely
present, please probe for devices attached to it, but don't decide
it's not present if you don't find any devices". I would like pmac.c
to be able to set hwif->present = 1 but still have the probe code go
looking for devices.
Regards,
Paul.
next prev parent reply other threads:[~2003-01-14 2:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030110165441$1a8a@gated-at.bofh.it>
[not found] ` <20030110165505$38d9@gated-at.bofh.it>
2003-01-11 12:27 ` any chance of 2.6.0-test*? Andi Kleen
2003-01-11 13:01 ` Russell King
2003-01-11 13:13 ` Andi Kleen
2003-01-11 14:39 ` Alan Cox
2003-01-11 14:06 ` Andi Kleen
2003-01-11 15:31 ` Alan Cox
2003-01-11 15:25 ` Andi Kleen
2003-01-11 19:18 ` Alan Cox
2003-01-13 3:33 ` Paul Mackerras
2003-01-13 14:59 ` Alan Cox
2003-01-13 18:36 ` Benjamin Herrenschmidt
2003-01-14 2:32 ` Paul Mackerras [this message]
2003-01-19 16:05 ` Pavel Machek
[not found] ` <20030112094007$1647@gated-at.bofh.it>
2003-01-12 9:56 ` Fixing the tty layer was " Andi Kleen
2003-01-13 6:41 ` Dipankar Sarma
2003-01-13 7:25 ` Andi Kleen
2003-01-13 8:12 ` Dipankar Sarma
2003-01-13 9:15 ` Russell King
2003-01-13 9:36 ` Dipankar Sarma
2003-01-13 6:45 ` Greg KH
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=15907.30411.916585.622130@argo.ozlabs.ibm.com \
--to=paulus@au1.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=benh@kernel.crashing.org \
--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®