From: "Randy.Dunlap" <rddunlap@osdl.org>
To: gene.heskett@verizon.net
Cc: willy@debian.org, linux-scsi@vger.kernel.org,
kernel-janitor-discuss@lists.sourceforge.net
Subject: Re: advansys regions [Re: 2.4 vs 2.6 versions of include/linux/ioport.h]
Date: Wed, 6 Aug 2003 11:50:35 -0700 [thread overview]
Message-ID: <20030806115035.24c8f03b.rddunlap@osdl.org> (raw)
In-Reply-To: <200308061435.43458.gene.heskett@verizon.net>
On Wed, 6 Aug 2003 14:35:43 -0400 Gene Heskett <gene.heskett@verizon.net> wrote:
...
| >> | >| ----
| >> | >| First, the define itself is missing in the 2.6 version.
| >
| >What define? check_region() is still there, just as an inline
| > function, not a macro.
| >
| I found that later.
|
| >> | >| Many drivers seem to use this call, and in that which I'm
| >> | >| trying to build, the nforce and advansys modules use it. And
| >> | >| while the modules seem to build, they do not run properly.
| >
| >Explain? Has someone broken check_region?
|
| Its now marked __deprecated. The module builds while indicating the
| errors, but gets into a bus reset loop and hangs in the second
| iteration of it.
So the kernel driver, without mods, is broken?
I didn't realize this earlier.
| >> I'm not terribly interested in spending much time on this driver,
| >> so the simplest thing to do IMO is to emulate check_region() with
| >> pairs of request_region() and release_region() calls. Yes, this
| >> is still racy, just like check_region() was. Is that a problem
| >> in your machine environment?
| >
| >I think this is the wrong thig to do. Leaving the check_region()
| >calls there indicate this driver still needs to be fixed properly.
| >Replacing them with unsafe uses of request & release_region leaves
| > the driver racy and removes the indication.
--
~Randy For Linux-2.6, see:
http://www.kernel.org/pub/linux/kernel/people/davej/misc/post-halloween-2.5.txt
next prev parent reply other threads:[~2003-08-06 18:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200308051041.08078.gene.heskett@verizon.net>
[not found] ` <20030805075758.31f51879.rddunlap@osdl.org>
[not found] ` <200308052050.07841.gene.heskett@verizon.net>
2003-08-06 17:40 ` advansys regions [Re: 2.4 vs 2.6 versions of include/linux/ioport.h] Randy.Dunlap
2003-08-06 17:59 ` Matthew Wilcox
2003-08-06 18:02 ` Randy.Dunlap
2003-08-06 18:35 ` Gene Heskett
2003-08-06 18:50 ` Randy.Dunlap [this message]
2003-08-06 19:18 ` Gene Heskett
2003-08-06 23:20 ` Gene Heskett
2003-08-06 18:31 ` Gene Heskett
2003-08-07 7:36 ` Christoph Hellwig
2003-08-07 9:33 ` Gene Heskett
2003-08-07 9:47 ` Christoph Hellwig
2003-08-07 18:34 ` Gene Heskett
2003-08-07 18:42 ` Randy.Dunlap
2003-08-07 19:40 ` Gene Heskett
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=20030806115035.24c8f03b.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=gene.heskett@verizon.net \
--cc=kernel-janitor-discuss@lists.sourceforge.net \
--cc=linux-scsi@vger.kernel.org \
--cc=willy@debian.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