From: Aras Vaichas <arasv@magtech.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: mmaping an IO port device
Date: Thu, 13 Dec 2007 10:57:24 +1100 [thread overview]
Message-ID: <47607564.2040900@magtech.com.au> (raw)
In-Reply-To: <4760727E.2090906@magtech.com.au>
Aras Vaichas wrote:
> I then call ioread16(FPGA_base + FPGA_register) for both x86 and ARM
> and it all works perfectly. No problems there.
Oop, sorry I lied a little. I actually use inw/outw for the x86 version.
e.g. inw( FPGA_REG_IO_BASE + FPGA_register);
but the main problem still stands ...
Aras
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
next prev parent reply other threads:[~2007-12-12 23:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 23:45 mmaping an IO port device Aras Vaichas
2007-12-12 23:57 ` Aras Vaichas [this message]
2007-12-13 0:39 ` H. Peter Anvin
2007-12-13 1:04 ` Aras Vaichas
[not found] <fa.noVJACisdR+sMNi3JjMxD+zdqf8@ifi.uio.no>
2007-12-13 0:52 ` Robert Hancock
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=47607564.2040900@magtech.com.au \
--to=arasv@magtech.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox