From: Jes Sorensen <jes@trained-monkey.org>
To: Randolph Chung <tausq@debian.org>
Cc: Grant Grundler <grundler@dsl2.external.hp.com>,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] sys/io.h
Date: 25 Jun 2002 12:18:31 -0400 [thread overview]
Message-ID: <m3fzzbmiw8.fsf@trained-monkey.org> (raw)
In-Reply-To: Randolph Chung's message of "Mon, 24 Jun 2002 08:39:59 -0700"
>>>>> "Randolph" == Randolph Chung <tausq@debian.org> writes:
>> I'm trying to build tulip-diag.c from scyld.com and am getting the
>> following error msg: gsyprf11:~# gcc -O tulip-diag.c -o tulip-diag
>> tulip-diag.c:58:20: sys/io.h: No such file or directory
>> tulip-diag.c:1347:24: warning: multi-line string literals are
>> deprecated
>>
>> On ia64, sys/io.h comes from gsyprf3:~# dpkg -S sys/io.h
>> libc6.1-dev: /usr/include/sys/io.h
>>
>> But we don't have the equivalent for parisc (hppa). Ideas?
Randolph> ISTR this has to do with the fact that we do not want
Randolph> to/cannot expose the {in,out}[bwl] primitives to
Randolph> userspace. Is the tulip-diag program trying to write to port
Randolph> space directly?
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.
Jes
next prev parent reply other threads:[~2002-06-25 16:18 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 [this message]
2002-06-25 16:29 ` Matthew Wilcox
2002-06-25 18:43 ` Jes Sorensen
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=m3fzzbmiw8.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 \
/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.