From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] arm: Defer lookup of machine_type and vet of atags to setup.c
Date: Wed, 12 Jan 2011 15:52:16 +0000 [thread overview]
Message-ID: <20110112155215.GB11039@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTi=29LB66j123ufMHQk=46hGYdmR4nZZQFnN=Tku@mail.gmail.com>
On Wed, Jan 12, 2011 at 08:46:44AM -0700, Grant Likely wrote:
> Looks like I've hit a hiccup though. When I remove the first call to
> __lookup_machine_type, then it is only called after the MMU is turned
> on and the kernel is no longer able to output the list of configured
> machine ids when it doesn't recognize the value in r1 (tested with
> qemu versatile emulation). I'm still investigating, so I'll defer
> reposting the patch until I've got this issue solved.
It only does this when DEBUG_LL is enabled - at which point you have
printascii, printhex8, etc available (although there's no prototype
for them.)
You could use snprintf() to format a message and then use printascii()
(conditional on CONFIG_DEBUG_LL as the existing code does) as well as
printk("%s", buffer). That means if you have a debugger you can dump
the kernel ring buffer and see the message, or see it via the serial
port/debugging channel if DEBUG_LL is enabled.
next prev parent reply other threads:[~2011-01-12 15:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 2:15 [RFC] arm: Defer lookup of machine_type and vet of atags to setup.c Grant Likely
2011-01-11 3:19 ` Nicolas Pitre
2011-01-11 5:21 ` Grant Likely
2011-01-11 10:40 ` Russell King - ARM Linux
2011-01-11 15:36 ` Grant Likely
2011-01-11 15:48 ` Russell King - ARM Linux
2011-01-12 15:46 ` Grant Likely
2011-01-12 15:52 ` Russell King - ARM Linux [this message]
2011-01-12 16:24 ` Grant Likely
2011-01-12 16:32 ` Russell King - ARM Linux
2011-01-12 16:53 ` Nicolas Pitre
2011-01-12 17:16 ` Grant Likely
2011-01-12 17:25 ` Russell King - ARM Linux
2011-01-12 17:49 ` Grant Likely
2011-02-07 15:55 ` Tony Lindgren
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=20110112155215.GB11039@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).