All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Hirst <rhirst@linuxcare.com>
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] request_region()
Date: Tue, 3 Apr 2001 00:11:14 +0100	[thread overview]
Message-ID: <20010403001114.F9198@linuxcare.com> (raw)

My 715/old, with a cvs head kernel, has no entries in /proc/ioports.
If I change our IO_SPACE_LIMIT in io.h from 0x00ffffff to 0xfffffff,
I get

apollo:~# cat /proc/ioports 
f0800000-f08fffff : ASP
  f0800000-f0800013 : reserved
  f0800020-f0800020 : led_data
  f0824800-f0824802 : parport0
  f0826000-f0826010 : i82596
apollo:~# 


(others won't see the i82596 entry, that is local to my tree)


So, normally they don't show up because their addresses are above
IO_SPACE_LIMIT, and luckily none of them check for error returns
from request_region().

I also have:

apollo:~# cat /proc/iomem 
f0825100-f082513f : sim700


Should all that ASP related stuff be doing a request_mem_region()
so they show up in /proc/iomem rather than /proc/ioports?

If so, does that have implications for EISA devices which will appear
under ASP, where we might want to use exisiting drivers that do
request_region()?

from io.h:

/* IO Port space is :      BBiiii   where BB is HBA number. */
#define IO_SPACE_LIMIT 0x00ffffff


Richard

             reply	other threads:[~2001-04-02 23:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-02 23:11 Richard Hirst [this message]
2001-04-03  3:06 ` [parisc-linux] request_region() Grant Grundler
2001-04-03  9:05   ` Richard Hirst
2001-04-03 16:41     ` Matthew Wilcox
2001-04-04  0:25       ` Grant Grundler
2001-04-03 23:57     ` Grant Grundler
2001-04-04  0:10       ` 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=20010403001114.F9198@linuxcare.com \
    --to=rhirst@linuxcare.com \
    --cc=parisc-linux@lists.parisc-linux.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.