All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Martyn Welch <martyn.welch@gefanuc.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: Booting 2.6.29-rc3 on mpc8661d_hpcn failing
Date: Tue, 03 Feb 2009 07:49:13 +1100	[thread overview]
Message-ID: <1233607753.18767.103.camel@pasglop> (raw)
In-Reply-To: <49871D3E.80809@gefanuc.com>


> >> commit 64b3d0e8122b422e879b23d42f9e0e8efbbf9744
> >> Author: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> >>
> >>   powerpc/mm: Rework usage of _PAGE_COHERENT/NO_CACHE/GUARDED
> >>
> >> I tried reverting it, but as I had kinda thought, that really didn't 
> >> help.
> >>
> >> I'm just recompiling to check that I didn't screw-up during the 
> >> bisection.
> > 

Is this a chip that must not have M set ? Or something else ? You guys
have to help if you CC me, I have about 0 idea what a MPC8661d is :-)

Also, does 4c456a67f501b8b15542c7c21c28812bf88f484b help ?
> 
Cheers,
Ben.

  reply	other threads:[~2009-02-02 20:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30 12:31 Booting 2.6.29-rc3 on mpc8661d_hpcn failing Martyn Welch
2009-01-30 13:17 ` Martyn Welch
2009-01-30 14:42 ` Kumar Gala
2009-01-30 16:47   ` Becky Bruce
2009-02-02  9:36     ` Martyn Welch
2009-02-02 15:45       ` Kumar Gala
2009-02-02 16:00         ` Martyn Welch
2009-02-02 16:11           ` Kumar Gala
2009-02-02 16:20             ` Martyn Welch
2009-02-02 20:49               ` Benjamin Herrenschmidt [this message]
2009-02-03 12:22                 ` Martyn Welch
2009-02-03 15:50                   ` Martyn Welch
2009-02-04  0:47                     ` Benjamin Herrenschmidt
2009-02-04 12:22                       ` Martyn Welch
2009-02-10 15:40                         ` Kumar Gala
2009-02-10 20:58                           ` Kumar Gala

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=1233607753.18767.103.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=martyn.welch@gefanuc.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.