From: Jes Sorensen <jes@trained-monkey.org>
To: Matthew Wilcox <willy@debian.org>
Cc: Randolph Chung <tausq@debian.org>,
Grant Grundler <grundler@dsl2.external.hp.com>,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] sys/io.h
Date: 25 Jun 2002 14:43:14 -0400 [thread overview]
Message-ID: <m3k7onjj25.fsf@trained-monkey.org> (raw)
In-Reply-To: Matthew Wilcox's message of "Tue, 25 Jun 2002 17:29:50 +0100"
>>>>> "Matthew" == Matthew Wilcox <willy@debian.org> writes:
Matthew> On Tue, Jun 25, 2002 at 12:18:31PM -0400, Jes Sorensen wrote:
>> You really should support it similar to what we do on
>> ia64. Ie. there's a Linux API here that allows you to map 'I/O'
>> ports and access them. Basing the code on what's in the ia64 glibc
>> tree would make it quite easy to get it up and running.
Matthew> Um, we can't. To do a port space access on Dino is:
Matthew> acquire spin lock write address to register perform read or
Matthew> write access to a different register release spin lock
Matthew> i do hope you're not about to suggest emulating the proposed
Matthew> interface by unmapping an address range and handling this in
Matthew> the fault handler
Well then make it a syscall and do it in the kernel - yes it's not
pretty but if the architecture requires it then thats the way to get
around it.
Jes
next prev parent reply other threads:[~2002-06-25 18:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-24 15:00 [parisc-linux] sys/io.h Grant Grundler
2002-06-24 15:39 ` Randolph Chung
2002-06-25 16:18 ` Jes Sorensen
2002-06-25 16:29 ` Matthew Wilcox
2002-06-25 18:43 ` Jes Sorensen [this message]
2002-06-25 18:46 ` Jes Sorensen
2002-06-25 18:33 ` Grant Grundler
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=m3k7onjj25.fsf@trained-monkey.org \
--to=jes@trained-monkey.org \
--cc=grundler@dsl2.external.hp.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=tausq@debian.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 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.