From: Oleg Verych <olecom@flower.upol.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: PnP Bios activation of parallel port prior to request_region
Date: Fri, 27 Oct 2006 21:38:37 +0000 (UTC) [thread overview]
Message-ID: <slrnek4vfg.39b.olecom@flower.upol.cz> (raw)
In-Reply-To: <200610260759.22237.dvhltc@us.ibm.com>
On 2006-10-26, Darren Hart <dvhltc@us.ibm.com> wrote:
> While working with a very simple demo parallel port interrupt driver, I found
> that request_region() will successfully return, regardless of whether or not
> the pnp calls have been made to activite the parallel port on a pnp system.
>
> The driver worked by just calling request_region() on another system, but on
> my laptop it wouldn't work unless I made the pnp activation calls before
> hand. The confusion came because the io range got assigned to my module,
> showed up in /proc/ioports, etc. So it appeared to be properly configured,
> but all the inb() calls returned 0xff.
>
> I know have something working, but just wanted to ask if it is considered
"now"?
> correct behavior for request_region() to succeed on an io range pertaining to
> a device that needs to be initialized by the pnp system and hasn't been.
I know that legacy parallel port must work regadless of any parport
modules, using /dev/port and BIOS setup for EPP/ECP etc.
If you really want to be answered, try to address message (or cc) to
e-mails mentioned in
- `linux/MAINTAINERS.*PARALLEL PORT*'
- `linux/drivers/parport/parport_pc.c'
____
prev parent reply other threads:[~2006-10-27 21:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 14:59 Darren Hart
2006-10-27 21:38 ` Oleg Verych [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=slrnek4vfg.39b.olecom@flower.upol.cz \
--to=olecom@flower.upol.cz \
--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®