From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-test11-pre7: isapnp hang
Date: 19 Nov 2000 17:22:09 -0800 [thread overview]
Message-ID: <8v9uc1$5c5$1@cesium.transmeta.com> (raw)
In-Reply-To: <8v9rf6$54k$1@cesium.transmeta.com> <E13xfQ1-0003CR-00@the-village.bc.nu>
Followup to: <E13xfQ1-0003CR-00@the-village.bc.nu>
By author: Alan Cox <alan@lxorguk.ukuu.org.uk>
In newsgroup: linux.dev.kernel
>
> > Try reserving ports 0x300-0x31f on the kernel command line
> > ("reserve=0x300,0x20").
> >
> > I'm surprised isapnp uses a port in such a commonly used range,
> > though.
>
> It seems to be a combination of two bugs. The one I posted a patch for and
> something odd that is taking port 0x279 before the pnp probe is run, which
> suggests a link order issue. Although in truth _nobody_ should be claing
> that anyway
>
It seems to me that it would be better to initialize all the (non-PnP)
ISA cards first, and have them claim their preferred ranges. Now you
can pick the PnP isolate port out of what is left, and also have a
much better idea of what is available.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-20 1:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-19 23:34 2.4.0-test11-pre7: isapnp hang Tim Waugh
2000-11-20 0:09 ` Alan Cox
2000-11-20 0:19 ` Alan Cox
2000-11-20 9:23 ` Tim Waugh
2000-11-20 0:32 ` H. Peter Anvin
2000-11-20 1:06 ` Alan Cox
2000-11-20 1:22 ` H. Peter Anvin [this message]
2000-11-20 12:45 ` 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='8v9uc1$5c5$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--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