All of lore.kernel.org
 help / color / mirror / Atom feed
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] ARM: bcm2835: convert to multi-platform
Date: Tue, 12 Mar 2013 22:28:54 -0600	[thread overview]
Message-ID: <51400086.5090300@wwwdotorg.org> (raw)
In-Reply-To: <20130313020732.GA27654@S2101-09.ap.freescale.net>

On 03/12/2013 08:07 PM, Shawn Guo wrote:
> On Tue, Mar 12, 2013 at 12:22:12PM -0600, Stephen Warren wrote:
>>>> TO DO:
>>>> * It'd be nice to restore uncompress.h. I need to take a look at Shawn
>>>>   Guo's patches related to this, and presumably rebase this on top of
>>>>   them.
>>>
>>> You do not need to restore uncompress.h, and from what I've seen,
>>> with my patches in place, uncompress debug will probably just work
>>> on BCM2835 out of box (you need to have DEBUG_LL selected for BCM2835).
>>
>> Should the usual "Uncompressing kernel" message show up automatically
>> then? I don't think it did, which is why I mentioned that "TO DO". I
>> almost always run with DEBUG_LL enabled and earlyprintk in the kernel
>> command-line, but I should double-check I didn't accidentally drop it
>> when testing this patch.
> 
> Yes, if you have both DEBUG_LL and DEBUG_BCM2835 set, I would expect
> you can see "Uncompressing kernel" message.

Ah yes. I just tried it again, and it does work perfectly. Thanks.

  reply	other threads:[~2013-03-13  4:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12  4:59 [RFC PATCH] ARM: bcm2835: convert to multi-platform Stephen Warren
2013-03-12  8:02 ` Shawn Guo
2013-03-12 18:22   ` Stephen Warren
2013-03-13  2:07     ` Shawn Guo
2013-03-13  4:28       ` Stephen Warren [this message]
2013-03-12 12:33 ` Arnd Bergmann
2013-03-13  4:38 ` Stephen Warren

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=51400086.5090300@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=linux-arm-kernel@lists.infradead.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.