linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Aaron Pace <kodiakuppercut@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: Large physical address support on e500 platform
Date: Thu, 21 Jan 2010 23:27:58 -0700	[thread overview]
Message-ID: <bc81dc641001212227w429b0f33hab1e541e69a11bf7@mail.gmail.com> (raw)

> >
> > Its possible that we've broken module/vmalloc support with
> > "Large physical addressing".? Its not something I've
> > tried in a while.? What kernel/git SHA are you using.
> >

>I'm just pulling in from the main kernel tree git.
>My current version is 2.6.33-rc4-00193-gd1e4922-dirty,
>but it had not changed since 2.6.33-rc2
>
>I started from 2.6.32, but I don't remember if I had a large PA
>support enabled there.

Just to second this issue, the following commit is what broke this:

[76acc2c1a7a9a8c2cae7e9cf8d0a8b374a48aa94]

I didn't have time to delve into the whys & hows, but this commit
caused the same issue on an 8572 platform.
Reverting this one change allows everything (including 36-bit memory
access) to work correctly, as before.

-Aaron Pace

             reply	other threads:[~2010-01-22  6:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-22  6:27 Aaron Pace [this message]
2010-01-25 16:46 ` Large physical address support on e500 platform Kumar Gala
2010-01-25 17:06   ` Aaron Pace
2010-01-25 17:25     ` Kumar Gala
2010-05-13 12:01       ` Kumar Gala
2010-05-13 12:05       ` Kumar Gala
  -- strict thread matches above, loose matches on Subject: below --
2010-01-19  6:54 Alex Dubov
2010-01-19 19:13 ` Kumar Gala
2010-01-20  1:34   ` Alex Dubov

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=bc81dc641001212227w429b0f33hab1e541e69a11bf7@mail.gmail.com \
    --to=kodiakuppercut@gmail.com \
    --cc=linuxppc-dev@ozlabs.org \
    /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).