From: Matt Porter <porter@cox.net>
To: Khai Trinh <kqtrinh@yahoo.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: driver for 440GP
Date: Thu, 25 Jul 2002 11:21:01 -0700 [thread overview]
Message-ID: <20020725112101.B24858@home.com> (raw)
In-Reply-To: <20020724220610.37041.qmail@web11503.mail.yahoo.com>; from kqtrinh@yahoo.com on Wed, Jul 24, 2002 at 03:06:10PM -0700
On Wed, Jul 24, 2002 at 03:06:10PM -0700, Khai Trinh wrote:
>
> Hi folks,
>
> I am trying to write a driver for the 440GP peripheral
> device with physical memory map of 0x1xxxxxxxx (total
> of 36 bits) on the PLB address space.
>
> When I get to do:
>
> request_mem_region() and then
> ioremap64()
>
> Don't I need a 64 bit request_mem_region() call? Is
> there such a kernel call before I call ioremap64()?
Two options for now:
1) Use the least significant 32-bits of the physical address to
do the region manipulation.
2) Don't register the region. We don't really do a good job
of this in most PPC code anyway.
In 2.5, we can make resource start/end u64's, but it's intrusive
enough that I can't imagine it going into 2.4 (I certainly
wouldn't ask for it). The region manipulation API would now use
u64's and printk formatting has to be handled since a u64 is
a different type on 32/64 platforms.
Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-07-25 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 22:06 driver for 440GP Khai Trinh
2002-07-25 18: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=20020725112101.B24858@home.com \
--to=porter@cox.net \
--cc=kqtrinh@yahoo.com \
--cc=linuxppc-embedded@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).