From: Gerd Hoffmann <kraxel@redhat.com>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: shashank chaturvedi <chaturvedi9950@gmail.com>,
linux-usb@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: xhci Portsc register issue
Date: Fri, 26 Oct 2012 09:12:12 +0200 [thread overview]
Message-ID: <508A37CC.5060900@redhat.com> (raw)
In-Reply-To: <20121025153552.GA5205@xanatos>
Hi,
> But I'm not sure, since I've never attempted to memory map PCI registers
> from userspace. I was under the impression that you just can't do that.
You can mmap /sys/bus/pci/devices(${device}/resource0. Just hacked up a
tool which dumps the capability registers this way:
http://www.kraxel.org/cgit/usb-tools/tree/usb-print-caps.c
cheers,
Gerd
prev parent reply other threads:[~2012-10-26 7:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALuomMuUD4xSaCUT6MZn3ZV2gjXnuBUhkz78PgXZ6XgV4e-NvA@mail.gmail.com>
2012-10-25 15:36 ` xhci Portsc register issue Sarah Sharp
2012-10-25 16:45 ` Bjorn Helgaas
2012-10-25 22:37 ` Peter Stuge
[not found] ` <CALuomMs-Z_PH3KpEPDgjBr5oy86Go2G2PAxu_k2yxgzWwRhJYQ@mail.gmail.com>
2012-10-26 17:17 ` Sarah Sharp
2012-10-26 7:12 ` Gerd Hoffmann [this message]
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=508A37CC.5060900@redhat.com \
--to=kraxel@redhat.com \
--cc=chaturvedi9950@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sarah.a.sharp@linux.intel.com \
/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).