From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Steven A. Falco" <sfalco@harris.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
hjk@linutronix.de, "Herrera-Bendezu, Luis" <lherrera@harris.com>,
linux-kernel@vger.kernel.org
Subject: Re: UIO: uio_mem does not handle devices above 4 GB address
Date: Tue, 16 Jun 2009 13:25:58 +1000 [thread overview]
Message-ID: <1245122758.12400.52.camel@pasglop> (raw)
In-Reply-To: <49D4BB9F.8050903@harris.com>
On Thu, 2009-04-02 at 09:20 -0400, Steven A. Falco wrote:
> struct uio_mem {
> phys_addr_t addr;
> phys_addr_t size;
> int memtype;
> void __iomem *internal_addr;
> struct uio_map *map;
> };
>
> A few other changes would be needed. We'd have to use something
> other than
Use a struct resource instead.
> return sprintf(buf, "0x%lx\n", mem->addr);
>
The struct resource has a printk format string.
Cheers,
Ben.
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Steven A. Falco" <sfalco@harris.com>
Cc: linux-kernel@vger.kernel.org, hjk@linutronix.de,
"Herrera-Bendezu, Luis" <lherrera@harris.com>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: UIO: uio_mem does not handle devices above 4 GB address
Date: Tue, 16 Jun 2009 13:25:58 +1000 [thread overview]
Message-ID: <1245122758.12400.52.camel@pasglop> (raw)
In-Reply-To: <49D4BB9F.8050903@harris.com>
On Thu, 2009-04-02 at 09:20 -0400, Steven A. Falco wrote:
> struct uio_mem {
> phys_addr_t addr;
> phys_addr_t size;
> int memtype;
> void __iomem *internal_addr;
> struct uio_map *map;
> };
>
> A few other changes would be needed. We'd have to use something
> other than
Use a struct resource instead.
> return sprintf(buf, "0x%lx\n", mem->addr);
>
The struct resource has a printk format string.
Cheers,
Ben.
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
next prev parent reply other threads:[~2009-06-16 3:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 13:20 UIO: uio_mem does not handle devices above 4 GB address Steven A. Falco
2009-06-16 3:25 ` Benjamin Herrenschmidt [this message]
2009-06-16 3:25 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2009-04-01 17:20 Herrera-Bendezu, Luis
2009-04-01 20:10 ` Hans J. Koch
2009-04-01 21:01 ` Herrera-Bendezu, Luis
2009-04-01 21:54 ` Hans J. Koch
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=1245122758.12400.52.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=hjk@linutronix.de \
--cc=lherrera@harris.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfalco@harris.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.