linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: wolfking <wolfking2000@msn.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: can't access PCIe card under sbc8548
Date: Thu, 30 May 2013 17:40:18 -0700 (PDT)	[thread overview]
Message-ID: <1369960818166-71847.post@n7.nabble.com> (raw)
In-Reply-To: <1369931365.14679.7@snotra>

hi, scott:
  Thanks for replying!
> In what specific way does it not work?
  when I use iowrite8 to write, things seem OK, the codes continue running,
  when I use ioread8 to read, the console I use freezes. The console stops
  responding.
> Why can't it succeed?  Is there nothing mapped at 0xfc7fc000?
  My PCIe card's local bus register is at BAR0+0xC7, so the driver should
access 0xfc7fc027 and the following 7 bytes. But When I access the areas:
ioread8 just freezes. 



--
View this message in context: http://linuxppc.10917.n7.nabble.com/can-t-access-PCIe-card-under-sbc8548-tp71775p71847.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.

  reply	other threads:[~2013-05-31  0:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30  3:42 can't access PCIe card under sbc8548 wolfking
2013-05-30  5:56 ` tiejun.chen
2013-05-30  7:19   ` wolfking
2013-05-30  8:47     ` tiejun.chen
2013-05-30  9:15       ` wolfking
2013-05-30  9:30         ` tiejun.chen
2013-05-30  7:32   ` wolfking
2013-05-30 10:42     ` tiejun.chen
2013-05-30 12:49       ` wolfking
2013-05-30 16:24         ` Scott Wood
2013-05-31  1:34           ` tiejun.chen
2013-05-31  2:27             ` wolfking
2013-05-31 10:00           ` Benjamin Herrenschmidt
2013-05-30 10:02 ` wolfking
2013-05-30 10:08   ` tiejun.chen
2013-05-30 12:45     ` wolfking
2013-05-30 16:29 ` Scott Wood
2013-05-31  0:40   ` wolfking [this message]
2013-05-31 10:01     ` Benjamin Herrenschmidt
2013-05-31 12:46       ` wolfking
2013-06-08  7:00         ` wolfking

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=1369960818166-71847.post@n7.nabble.com \
    --to=wolfking2000@msn.com \
    --cc=linuxppc-dev@ozlabs.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).