[Top] [All Lists]

Re: Bus error after successful mmap of physical address

To: Alex Gonzalez <>
Subject: Re: Bus error after successful mmap of physical address
From: Ralf Baechle <>
Date: Wed, 22 Aug 2007 19:08:27 +0100
Cc: linux-mips <>
In-reply-to: <>
Original-recipient: rfc822;
References: <>
User-agent: Mutt/1.5.14 (2007-02-12)
On Wed, Aug 22, 2007 at 06:31:22PM +0100, Alex Gonzalez wrote:

> I am sure there is a basic reason why this is not working but I just
> can't see it.
> I am booting with mem=512MB and trying to access a memory region at
> 0xC0000000 mapped by a fixed TLB entry.

Is 0xC0000000 a physical or virtual address.  If it's a virtual address
your mapping will conflict with other mappings generated by the kernel and
you will need additional hacks to protect the address space from being
used by the kernel for other purposes.

> My driver does,
> vma->vm_flags = vma->vm_flags | VM_IO | VM_RESERVED ;
> vma->vm_page_prot = pgprot_noncached(vma->vm_page_prot) ;
> // open device
>       vadr = mmap( NULL , 1024*1024 ,

This is the reason why I was asking if 0xC0000000 was a physical address.
mmap needs a physical address.

>       if(vadr == MAP_FAILED)
>       {
>               perror("mmap failed.\n");
>               exit(-1);
>       }
> That goes OK, but then if I try to read or write from vadr I get a "Bus 
> error".

Assuming device is a /dev/mem descriptor that is looking ok.  However - you
will be getting an uncached mapping from mmap so the performance will suck
rocks through a straw.

Anyway, you have 64-bit hardware, use it.  On a 64-bit kernel you can just
address all your memory through XKPHYS without the need for any TLB entries.


<Prev in Thread] Current Thread [Next in Thread>