Re: Sparc64 and ATI fb, cannot mmap() - why?

From: Richard Henderson (rth@twiddle.net)
Date: Thu Jun 22 2000 - 02:22:31 EST


On Wed, Jun 21, 2000 at 10:57:30PM -0700, David S. Miller wrote:
> Indeed. Aside from the mmap64 issue, what else are you missing?
>
> That's about it. In fact I think it's nicer if the user doesn't
> need to know how big physical addresses are, nor anything about
> them anyways, just to mmap device regions.

I guess I don't mind a dedicated syscall for mapping these.

> The PPC folks indicate they need to be able to tell the app some
> kind of shift value for forming the address in load/store instruction
> on the PCI I/O and MEM regions it maps. Aparently, this shift value
> is different on different PPC machines which is why the app needs to
> obtain it as opposed to just knowing when it is __powerpc__ what to use.

Huh. Are you sure this is ppc? It sounds awfully like
Alpha sparse i/o. I wasn't aware of anyone else with this
sort of braindamage.

r~

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Fri Jun 23 2000 - 21:00:23 EST