All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Aaro Koskinen <aaro.koskinen@nokia.com>,
	Kevin Hilman <khilman@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Code for v2.6.39 merge window frozen, patches archived
Date: Wed, 13 Apr 2011 18:09:50 +0300	[thread overview]
Message-ID: <20110413150948.GB13345@atomide.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1104131041590.24613@xanadu.home>

* Nicolas Pitre <nicolas.pitre@linaro.org> [110413 17:46]:
> On Wed, 13 Apr 2011, Tony Lindgren wrote:
> > 
> > With the device tree append patch reverting commit
> > d239b1dc093d551046a909920b5310c1d1e308c1 does not help, and reverting
> > 6d7d0ae51574943bf571d269da3243257a2d15db requires some manual merging..
> 
> You cannot use the DT append patch without 6d7d0ae515 in place.  The 
> later is a prerequisite for the former.

OK.
 
> > Anyways, that might be another way to reproduce the problem if these
> > issues are related.
> 
> I've started to instrument the problematic CONFIG_KERNEL_LZMA case.  So 
> far this is still a mystery.
> 
> Do you have problems with the DT append patch even with 
> CONFIG_KERNEL_GZIP=y?

Yup. The devicetree data gets trashed by decompress_kernel
with CONFIG_KERNEL_GZIP too with the append patch.

DT data before decompress_kernel:
edfe0dd0 2c010000 38000000 f0000000

DT data after decompress_kernel:
10000000 00000001 38000000 f0000000

So first 8 (not 16 bytes like I mentioned earlier) get trashed.

Regards,

Tony

  reply	other threads:[~2011-04-13 15:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 19:25 Code for v2.6.39 merge window frozen, patches archived Tony Lindgren
2011-03-15  3:05 ` Nishanth Menon
2011-03-15 15:09   ` Kevin Hilman
2011-03-15 15:20     ` Menon, Nishanth
2011-03-15 17:54 ` Aaro Koskinen
2011-03-15 20:07   ` Cousson, Benoit
2011-03-15 20:32     ` aaro.koskinen
2011-03-16 13:49     ` Aaro Koskinen
2011-03-16 14:33       ` Cousson, Benoit
2011-03-16 15:32         ` Tony Lindgren
2011-03-16 17:26           ` Aaro Koskinen
2011-03-16 17:10         ` Aaro Koskinen
2011-03-29 23:32           ` Tony Lindgren
2011-03-30 15:23             ` Kevin Hilman
2011-03-31 14:53               ` Aaro Koskinen
2011-04-02  2:42                 ` Nicolas Pitre
2011-04-13 14:04                   ` Tony Lindgren
2011-04-13 14:34                     ` Aaro Koskinen
2011-04-15 13:41                       ` Jarkko Nikula
2011-04-13 14:49                     ` Nicolas Pitre
2011-04-13 15:09                       ` Tony Lindgren [this message]
2011-04-19 10:13                         ` Tony Lindgren
2011-04-19 13:27                           ` Nicolas Pitre
2011-04-19 14:15                             ` Tony Lindgren
2011-03-16 14:07 ` G, Manjunath Kondaiah
2011-03-16 14:20   ` G, Manjunath Kondaiah
2011-03-16 14:39     ` Kishore Kadiyala

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=20110413150948.GB13345@atomide.com \
    --to=tony@atomide.com \
    --cc=aaro.koskinen@nokia.com \
    --cc=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=nicolas.pitre@linaro.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 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.