Messages in this thread | | | From | Glenn Burkhardt <> | Subject | Re: remap_page_range64() for PPC | Date | Sun, 17 Oct 2004 09:17:04 -0400 |
| |
On Saturday 16 October 2004 02:32 am, Matt Porter wrote: > On Fri, Oct 15, 2004 at 11:46:42PM -0400, Glenn Burkhardt wrote: > > I'm writing an application to run on a PowerPC with a 2.4 embedded > > Linux kernel, and I want to make device registers for our custom > > hardware accessable from user space with mmap(). The physical address > > of the device is above the 4gb boundary (we attach to the 440's > > external peripheral bus), so a standard 'remap_page_range()' call > > won't work. > > <snip> > > This has come up several times on the ppc lists (but since we still > don't have archives back, nobody can search anyway). I dropped ^^^^^^ > 2.4 and 2.5 patches in source.mvista.com:/pub/linuxppc/ a long ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > time ago. You just need to update your board-specific fixup routine > in that version or just make a copy or remap_page_range() into your > driver and use u64 for the phys address.
Do you mean that you applied a patch, or had one and decided not to use it? I just looked at mm/memory.c didn't notice anything substantially different in remap_page_range(). To which module was the patch applied?
Thanks for verifying that the approach I took was correct, which was to use u64 for the phys address for remap_page_range().
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |