Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Cc: Martin Jansa <martin.jansa@gmail.com>
Subject: Re: [meta-handheld v2] linux-kexecboot: use kernel_conf_variable like linux.inc does and respect CMDLINE_DEBUG
Date: Fri, 25 Nov 2011 12:34 +0000	[thread overview]
Message-ID: <1734371.1v8iFp6Vj1@helios> (raw)
In-Reply-To: <20111121115213.GF3565@jama.jama.net>

On Monday 21 November 2011 12:52:13 Martin Jansa wrote:
> On Mon, Nov 21, 2011 at 11:43:46AM +0100, Andrea Adami wrote:
> > On Sun, Nov 20, 2011 at 12:26 PM, Martin Jansa <martin.jansa@gmail.com>
> > wrote: Martin,
> > 
> > I agree for the use kernel_conf_variable but I'm unsure about
> > CMDLINE_DEBUG. In fact, I hardcoded it purposedly with commit 8929166
> > with the
> > following reasons:
> > 
> > * Being a second-stage bootloader we don't expect any output on screen.
> > * Adding 'debug' as commandline arg is pointless because
> > * linux-kexecboot is compiled without debug and printk in order
> > * to minimize the size.
> > * Full debug implies not only editing the commandline (e.g. earlyprintk)
> > * but re-enabling full debug options in the defconfigs
> 
> I had some issues with 3.2.0-rc2 when used as linux-kexecboot, that's
> why I've added this, but later found out that it's really a bit
> incomplete, that's why I have followup patch for this:
> https://gitorious.org/shr/meta-handheld/commit/6bc710615b587fc0bfd8fc4372cad
> 0de5599dd82?format=patch
> 
> But with latest SRCREV it works again, so in theory I don't need it, but
> still it would be usefull to have easy way to debug even this stage
> (maybe you still remember older kernel version where it worked fine
> as 3rd stage and failed to boot as 2nd stage..).
> 
> BTW: here is upgrade to 3.2.0-rc2 with those changes to
> linux-kexecboot.inc applied
> https://gitorious.org/shr/meta-handheld/commit/27ca3d24353a5473f4f1aade00ba7
> a52b667e28c?format=patch
> 
> (be aware that I do rebase that branch sometimes so if those commits are
> not valid anymore just look at last few commits in that branch).

As discussed on IRC I've merged the latest version of this branch to meta-
handheld master now, thanks.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



      reply	other threads:[~2011-11-25 12:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-20 10:06 [meta-handheld 1/2] linux-kexecboot: use kernel_conf_variable like linux.inc does and respect CMDLINE_DEBUG Martin Jansa
2011-11-20 10:06 ` [meta-handheld 2/2] linux-git: move CMDLINE_DEBUG to linux-git.inc to be used also for linux-kexecboot Martin Jansa
2011-11-20 11:26 ` [meta-handheld v2] linux-kexecboot: use kernel_conf_variable like linux.inc does and respect CMDLINE_DEBUG Martin Jansa
2011-11-21 10:43   ` Andrea Adami
2011-11-21 11:52     ` Martin Jansa
2011-11-25 12:34       ` Paul Eggleton [this message]

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=1734371.1v8iFp6Vj1@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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