From: Olaf Hering <olaf@aepfle.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: paulus@samba.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Use check_legacy_ioport() for ISAPnP
Date: Mon, 2 Oct 2006 12:00:50 +0200 [thread overview]
Message-ID: <20061002100050.GA14083@aepfle.de> (raw)
In-Reply-To: <1159782124.4801.10.camel@pmac.infradead.org>
On Mon, Oct 02, David Woodhouse wrote:
> On Mon, 2006-10-02 at 11:38 +0200, Olaf Hering wrote:
> >
> > The new check in parport_pc_init() will prevent the probing of PCI
> > devices. I guess the correct fix would be a sophisticated
> > pmac_check_legacy_ioport() that checks if baseport is available on
> > some PCI device:
>
> That or only call check_legacy_ioport() when we're poking _gratuitously_
> at legacy space, not when there's a properly-detected port.
It is CONFIG_PARPORT_PC_SUPERIO=y that is causing trouble. Lets see what
lkml has to say about this config option.
prev parent reply other threads:[~2006-10-02 10:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 7:18 [PATCH] Use check_legacy_ioport() for ISAPnP David Woodhouse
2006-09-27 8:18 ` Olaf Hering
2006-09-27 12:49 ` David Woodhouse
2006-09-27 13:05 ` Olaf Hering
2006-10-02 9:38 ` Olaf Hering
2006-10-02 9:42 ` David Woodhouse
2006-10-02 10:00 ` Olaf Hering [this message]
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=20061002100050.GA14083@aepfle.de \
--to=olaf@aepfle.de \
--cc=dwmw2@infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).