From: "stanley.miao" <stanley.miao@windriver.com>
To: jagan kernel <jagan.kernel@gmail.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: ARM: CONFIG_DEBUG_LL not giving any early print logs
Date: Mon, 29 Aug 2011 10:32:53 +0800 [thread overview]
Message-ID: <4E5AFA55.30109@windriver.com> (raw)
In-Reply-To: <CANjRM=Z2DxBuNscCNpQaqDyTYTb8Ty_-cP56eKTGS0DjP+iHmg@mail.gmail.com>
That patch has not been merged.
Stanley.
jagan kernel wrote:
> Hi Stanley,
>
> As your inputs on lkml.org <http://lkml.org>, I enabled CONFIG_DEBUG_LL
> but I didn't get any early print logs on my
> console.
>
> Please help I have ported 3.0 to new arm target, target doesn't boot,
> not showing any
> prints on console.
>
> Thanks for your time.
>
> Regards,
> Jagan
parent reply other threads:[~2011-08-29 2:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CANjRM=Z2DxBuNscCNpQaqDyTYTb8Ty_-cP56eKTGS0DjP+iHmg@mail.gmail.com>]
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=4E5AFA55.30109@windriver.com \
--to=stanley.miao@windriver.com \
--cc=jagan.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.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