l Ellerman
,
Subject
Re: application needs fast access
to physi
On Thu, 18 Nov 2010 14:46:16 -0600
wrote:
> Hello Scott,
>
> Do you know whether this patch is necessary if I were to use alloc_bootmem
> () (to set aside a region of contiguous physical memory) instead of the
> kernel parameter "mem=256"?
It should not be needed in that case.
-Scott
On Thu, 18 Nov 2010 10:55:21 -0600
wrote:
> Thanks for the replies.
>
> In the Linux Device Drivers book regarding mmap(), it states:
>
>Mapping a device means associating a range of user-space addresses to
>device memory.
>Whenever the program reads or writes in the assigned addres
steven@teradyne.com,
steven_...@notes.teradyne.com,
linuxppc-dev@lists.ozlabs.org
Subject
On Thu, Nov 18, 2010 at 11:24:22PM +1100, Michael Ellerman wrote:
> On Wed, 2010-11-17 at 16:03 -0600, steven@teradyne.com wrote:
> > My application needs a fast way to access a specific physical DDR
> > memory region. The application runs on an MPC8548 PowerPC which has an
> > MMU. I've tried
> On Wed, 2010-11-17 at 16:03 -0600, steven@teradyne.com wrote:
> > My application needs a fast way to access a specific physical DDR
> > memory region. The application runs on an MPC8548 PowerPC which has
an
> > MMU. I've tried two approaches that are typical for Linux, mmap()
and
> > using
On Wed, 2010-11-17 at 16:03 -0600, steven@teradyne.com wrote:
> My application needs a fast way to access a specific physical DDR
> memory region. The application runs on an MPC8548 PowerPC which has an
> MMU. I've tried two approaches that are typical for Linux, mmap() and
> using a kernel mod
