Re: mmap question on ppc440

2007-11-06 Thread Benjamin Herrenschmidt
> > The solution is libpciaccess and the new pci-rework branch of X which > > uses it, but I haven't had a chance to test that properly yet on 4xx. > > Um... because arch/powerpc 4xx doesn't have PCI support? :) You and > Valentine and Vitaly keep trading emails about it though, which is a > goo

Re: mmap question on ppc440

2007-11-06 Thread Josh Boyer
On Wed, 07 Nov 2007 09:02:10 +1100 Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote: > > On Tue, 2007-11-06 at 07:50 +0100, Stefan Roese wrote: > > On Monday 05 November 2007, Josh Boyer wrote: > > > > I am attempting to access the CPLD on the AMCC Sequoia board from > > > > user-land. I open /d

Re: mmap question on ppc440

2007-11-06 Thread Benjamin Herrenschmidt
On Tue, 2007-11-06 at 07:50 +0100, Stefan Roese wrote: > On Monday 05 November 2007, Josh Boyer wrote: > > > I am attempting to access the CPLD on the AMCC Sequoia board from > > > user-land. I open /dev/mem, and mmap it, then try to access the > > > resulting pointer. That works fine when acces

Re: mmap question on ppc440

2007-11-05 Thread Stefan Roese
On Monday 05 November 2007, Josh Boyer wrote: > > I am attempting to access the CPLD on the AMCC Sequoia board from > > user-land. I open /dev/mem, and mmap it, then try to access the > > resulting pointer. That works fine when accessing physical addresses > > that correspond to RAM, but as soon

Re: mmap question on ppc440

2007-11-05 Thread Josh Boyer
On Mon, 05 Nov 2007 16:02:59 -0500 "Steven A. Falco" <[EMAIL PROTECTED]> wrote: > I am attempting to access the CPLD on the AMCC Sequoia board from > user-land. I open /dev/mem, and mmap it, then try to access the > resulting pointer. That works fine when accessing physical addresses > that c