From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: benh@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org, Stefan Roese <sr@denx.de>
Subject: Re: mmap question on ppc440
Date: Tue, 6 Nov 2007 16:59:09 -0600 [thread overview]
Message-ID: <20071106165909.0e80fb4e@zod.rchland.ibm.com> (raw)
In-Reply-To: <1194386530.6523.37.camel@pasglop>
On Wed, 07 Nov 2007 09:02:10 +1100
Benjamin Herrenschmidt <benh@kernel.crashing.org> 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 /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 as I try to access the CPLD at
> > > > physical address 0xc0000000, I get an infinite machine check.
> > >
> > > That's because the CPLD is actually at physical address 0x1C0000000.
> > > Yay for 36-bit physical addresses.
> >
> > Right. Are you using arch/ppc or arch/powerpc? If it's arch/ppc you could
> > give the following patch a try:
> >
> > @@ -275,6 +275,14 @@
> > {
> > size_t size = vma->vm_end - vma->vm_start;
> >
> > +#if defined(CONFIG_44x) && !defined(CONFIG_PPC_MERGE)
> > + /*
> > + * 2006-08-07: sr
> > + * Needed on 44x-er systems for 36bit addresses (like pci on 440gx)
> > + */
> > + vma->vm_pgoff = (fixup_bigphys_addr(vma->vm_pgoff << PAGE_SHIFT, size) >> PAGE_SHIFT);
> > +#endif
> > +
> > if (!valid_mmap_phys_addr_range(vma->vm_pgoff, size))
> > return -EINVAL;
>
> I think we need to ditch the bigphys fixup stuff and come up with a way
> to make /dev/mem work with the actual 36 bits offsets (after all, it's
> all pgoff, it should work).
We did ditch bigphys in arch/powerpc. mmap64 works apparently.
> The other problem is X of course... 32 bits X server currently cannot
> cope with physical addresses > 32 bits at all. They will just blow up or
> randomly scribble over /dev/mem.
>
> 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
good sign.
josh
next prev parent reply other threads:[~2007-11-06 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 21:02 mmap question on ppc440 Steven A. Falco
2007-11-05 21:16 ` Josh Boyer
2007-11-06 6:50 ` Stefan Roese
2007-11-06 22:02 ` Benjamin Herrenschmidt
2007-11-06 22:59 ` Josh Boyer [this message]
2007-11-06 23:31 ` Benjamin Herrenschmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071106165909.0e80fb4e@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sr@denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).