linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@cs.anu.edu.au>
To: bryanc@ihug.co.nz
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: I/O Port Conflicts with PCI devices?
Date: Tue, 2 Feb 1999 10:23:49 +1100	[thread overview]
Message-ID: <199902012323.KAA24452@tango.anu.edu.au> (raw)
In-Reply-To: <l03130300b2dbb10d21bc@[172.16.10.14]> (message from Bryan Christianson on Tue, 2 Feb 1999 08:42:28 +1300)


Bryan Christianson <bryanc@ihug.co.nz> wrote:

> The following listing of /proc/pci shows that I have 2 devices reporting an
> I/O port of 0x400. Is this possible or am I not seeing the whole truth
> here? When I try to access the port (with inl() or outl()), the machine
> panics. I published this panic on the list last week and had no response.

Most likely neither devices is responding to I/O-space accesses
because the PCI_COMMAND_IO bit (enable response to I/O space accesses)
in the PCI command register isn't set.  That would explain the machine
check when you try to access the device.

Paul.

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

  reply	other threads:[~1999-02-01 23:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-01 19:42 I/O Port Conflicts with PCI devices? Bryan Christianson
1999-02-01 23:23 ` Paul Mackerras [this message]
1999-02-02  6:33   ` Bryan Christianson
1999-02-02  8:41 ` Gabriel Paubert

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=199902012323.KAA24452@tango.anu.edu.au \
    --to=paulus@cs.anu.edu.au \
    --cc=Paul.Mackerras@cs.anu.edu.au \
    --cc=bryanc@ihug.co.nz \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).