From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Antonino Sergi <Antonino.Sergi@roma1.infn.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: isa memory address
Date: Mon, 08 Nov 2004 08:46:41 -0800 [thread overview]
Message-ID: <418FA2F1.2090003@osdl.org> (raw)
In-Reply-To: <1099901664.2718.92.camel@delphi.roma1.infn.it>
Antonino Sergi wrote:
> Hi,
>
> I'm working with an old data acquisition system that uses an 8-bit card
> in an ISA slot (address 0xd0000), by a simple driver I ported from
> kernel 1.1.x to 2.2.24.
>
> It works fine, but I'd like to have features by newer kernels (2.4 or
> even 2.6), like new filesystems support.
>
> On kernels >=2.4.0 check_region returns -EBUSY for that address,
> but it is not actually used; I tried to understand if something has been
> changed/removed, because of obsolescence of devices, in IO management,
> but I couldn't.
>
> Does anybody have any explanation/suggestion?
Please post contents of /proc/iomem .
I'm guessing that it will show something like:
000e0000-000effff : Extension ROM
(but for address 000d0000).
So then the question becomes how to assign/allocate it for your
driver.
You might have to dummy up a call to release_resource() first,
then use request_resource() to acquire it.
Or just use the addresses anyway.... even though check_region() says
-EBUSY. BTW, check_region() is deprecated in 2.6.x, so if your
driver could just use request_region() and release_region(), that
would be better.
> Thank you
>
> Best Regards,
>
> Antonino Sergi
>
> PS:As I'm not subscribed, please CC me your answers.
--
~Randy
next prev parent reply other threads:[~2004-11-08 17:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 8:14 isa memory address Antonino Sergi
2004-11-08 16:46 ` Randy.Dunlap [this message]
2004-11-09 5:46 ` Antonino Sergi
2004-11-09 15:42 ` Antonino Sergi
2004-11-09 16:56 ` Maciej W. Rozycki
2004-11-10 9:37 ` Antonino Sergi
2004-11-11 3:54 ` Maciej W. Rozycki
2004-11-12 17:10 ` Antonino Sergi
2004-11-16 16:22 ` Antonino Sergi
2004-11-17 15:00 ` Antonino Sergi
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=418FA2F1.2090003@osdl.org \
--to=rddunlap@osdl.org \
--cc=Antonino.Sergi@roma1.infn.it \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.