All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher Friesen" <cfriesen@nortelnetworks.com>
To: linux-kernel@vger.kernel.org
Subject: problem accessing /dev/port
Date: Thu, 22 Nov 2001 17:05:14 -0500	[thread overview]
Message-ID: <3BFD769A.376003D5@nortelnetworks.com> (raw)


To begin, I'm running 2.2.17 with some patches.

I'm attempting to have a userspace app read and write I/O ports on a powerpc
machine.  The obvious method (iopl()) doesn't seem to be available (using glibc,
but sys/io.h doesn't exist).

When I try and access /dev/port with a small utility that works fine on my PIII,
I get the error message "Device not configured".  The file exists in /dev and
has the same permissions on both machines.

Do I need to enable something in the kernel to support this?  Where is this
configured?

Thanks,

Chris

-- 
Chris Friesen                    | MailStop: 043/33/F10  
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-22 22:05 Christopher Friesen [this message]
2001-11-23  3:55 ` problem accessing /dev/port Paul Mackerras

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=3BFD769A.376003D5@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --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.