From: Brian Swetland <swetland@google.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Arve Hj?nnev?g" <arve@android.com>,
kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [3/3,ARM] msm: add minimal board file for HTC Dream device
Date: Sun, 1 Nov 2009 15:33:39 -0800 [thread overview]
Message-ID: <a55d774e0911011533xf9b1285k7dc92745f2fb4edf@mail.gmail.com> (raw)
In-Reply-To: <20091101231950.GF20740@elf.ucw.cz>
On Sun, Nov 1, 2009 at 3:19 PM, Pavel Machek <pavel@ucw.cz> wrote:
>>
>> Pretty sure it's something later than .29
>
> I guess I should try 2.6.31.
>
>> Does enabling DEBUG_LL help? If something's dying before the serial
>> port is registered, you might never see any console chatter.
>
> DEBUG_LL does not help. Is that early_printk() equivalent?
> With DEBUG_ICEDC I don't even get "uncompressing linux" message.
ICEDCC will try to send messages to JTAG DCC.
Sticking a call to printascii(printk_buf) after the vscnprintf() in
vprintk() in kernel/printk.c is sometimes useful alongside DEBUG_LL
(so that printks will go to the serial port immediately).
> Yes, I believe it dies before serial registration :-(. Being able to
> call puts() that decompressor uses would be useful...
>
>> Also, I believe you'll want to pass console=ttyMSM2,115200n8 on the
>> kernel commandline (-c parameter to fastboot or mkbootimg).
>
> I'm using "console=ttyMSM2 rootdelay=5 fbcon=rotate:1" that worked for
> me on another kernel version...
>
next prev parent reply other threads:[~2009-11-01 23:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-01 22:13 Pavel Machek
2009-11-01 23:01 ` Brian Swetland
2009-11-01 23:19 ` Pavel Machek
2009-11-01 23:33 ` Brian Swetland [this message]
2009-11-02 11:23 ` Pavel Machek
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=a55d774e0911011533xf9b1285k7dc92745f2fb4edf@mail.gmail.com \
--to=swetland@google.com \
--cc=arve@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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
all inboxes | Powered by JetHome®