From: Matt Porter <mporter@kernel.crashing.org>
To: Madhu Saravana Sibi Govindan <ssshayagriva@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: PowerPC/Linux device driver question
Date: Thu, 20 Oct 2005 13:21:50 -0700 [thread overview]
Message-ID: <20051020132150.A29677@cox.net> (raw)
In-Reply-To: <513a5e60510201256k64c0e4fan1557c28a0bdf920c@mail.gmail.com>; from ssshayagriva@gmail.com on Thu, Oct 20, 2005 at 02:56:21PM -0500
On Thu, Oct 20, 2005 at 02:56:21PM -0500, Madhu Saravana Sibi Govindan wrote:
> I'm not sure how to request this range of physical memory from the
> kernel. I thought I could use ioremap to map this range into the
> virtual space, but ioremap takes only an unsigned long as an argument,
> which is only 32 bits on 440GP. I don't think I can represent the range of my
> device with 32 bits.
>
> Could someone tell me how to solve the problem? I want this range of
> physical addresses to be associated with my device driver and how do I
> do that?
Use the ppc-specific ioremap64() call.
-Matt
prev parent reply other threads:[~2005-10-20 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 19:56 PowerPC/Linux device driver question Madhu Saravana Sibi Govindan
2005-10-20 20:21 ` Matt Porter [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=20051020132150.A29677@cox.net \
--to=mporter@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=ssshayagriva@gmail.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).