From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Wayne Warren <wwarren@emacinc.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Adeos I-Pipe patch problem on vendor-specific kernel
Date: Thu, 04 Oct 2012 20:02:09 +0200 [thread overview]
Message-ID: <506DCF21.2000606@xenomai.org> (raw)
In-Reply-To: <506DC2DA.5000105@xenomai.org>
On 10/04/2012 07:09 PM, Gilles Chanteperdrix wrote:
> On 10/04/2012 06:57 PM, Wayne Warren wrote:
>> Gilles,
>>
>> Thanks for your help!
>>
>> The ArmPorting guide is helpful, but unfortunately the first tip and
>> trick did not reveal any boot messages. I had to add a function
>> declaration for "printascii" to get the code to compile. I have
>> CONFIG_DEBUG_KERNEL, CONFIG_DEBUG_LL, and CONFIG_EARLY_PRINTK enabled
>> and have passed the boot parameter "earlyprintk" when attempting to
>> boot.
>
> Either you enable CONFIG_EARLY_PRINTK and pass earlyprintk on the
> command line, that is the "new" way.
>
> Or, you do the printascii in printk trick, that is the "old" way.
>
> If you do both, you should see everything printed twice.
> If you do not see anything, it probably means that printascii does not
> work for your platform. To get it working, you have to look at
> arch/arm/your-machine/include/mach/debug-macro.S
> And of course, your kernel has to be compiled for only one board, if the
> UART used by these macros depends on the board.
Ah, if it is an OMAP based processor, you need to add a call to
_DEBUG_LL_ENTRY for your processor in
arch/arm/plat-omap/include/plat/uncompress.h, it may be what is missing.
--
Gilles.
next prev parent reply other threads:[~2012-10-04 18:02 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 21:08 [Xenomai] Adeos I-Pipe patch problem on vendor-specific kernel Wayne Warren
2012-10-02 21:32 ` Gilles Chanteperdrix
2012-10-02 21:35 ` Gilles Chanteperdrix
2012-10-04 16:57 ` Wayne Warren
2012-10-04 17:09 ` Gilles Chanteperdrix
2012-10-04 18:02 ` Gilles Chanteperdrix [this message]
2012-10-05 8:06 ` Gilles Chanteperdrix
2012-10-05 18:47 ` Wayne Warren
2012-10-05 20:16 ` Gilles Chanteperdrix
2012-10-05 21:47 ` Wayne Warren
2012-10-05 22:43 ` Gilles Chanteperdrix
2012-10-06 4:29 ` Wayne Warren
2012-10-06 9:46 ` Gilles Chanteperdrix
2012-10-09 20:55 ` Wayne Warren
2012-10-09 21:12 ` Gilles Chanteperdrix
2012-10-19 21:22 ` Wayne Warren
2012-10-20 1:33 ` Gilles Chanteperdrix
2012-10-22 19:22 ` Wayne Warren
2012-10-22 19:25 ` Gilles Chanteperdrix
2012-10-22 19:34 ` Wayne Warren
2012-10-22 21:12 ` Gilles Chanteperdrix
2012-10-23 15:32 ` Wayne Warren
2012-10-23 20:12 ` Gilles Chanteperdrix
2012-10-24 17:32 ` Wayne Warren
2012-10-24 17:38 ` Gilles Chanteperdrix
2012-10-24 17:55 ` Wayne Warren
2012-10-24 18:05 ` Gilles Chanteperdrix
2012-10-24 18:26 ` Wayne Warren
2012-10-24 18:36 ` Gilles Chanteperdrix
2012-10-24 17:36 ` Wayne Warren
2012-10-24 17:57 ` Gilles Chanteperdrix
2012-10-20 8:24 ` Gilles Chanteperdrix
2012-10-19 21:32 ` Wayne Warren
2012-10-20 1:36 ` Gilles Chanteperdrix
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=506DCF21.2000606@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=wwarren@emacinc.com \
--cc=xenomai@xenomai.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.