From: Tony Lindgren <tony@atomide.com>
To: Cory Maccarrone <darkstar6262@gmail.com>
Cc: linux-omap@vger.kernel.org, miknix@gmail.com,
a.j.buxton@gmail.com, linwizard-devel@lists.sf.net
Subject: Re: Commit 0c8219f0... breaks omap7xx support
Date: Mon, 8 Mar 2010 18:46:02 -0800 [thread overview]
Message-ID: <20100309024602.GQ2900@atomide.com> (raw)
In-Reply-To: <6cb013311003081751u2c7cd8c6v59472ee85ac90e77@mail.gmail.com>
* Cory Maccarrone <darkstar6262@gmail.com> [100308 17:49]:
> On Mon, Mar 8, 2010 at 4:48 PM, Tony Lindgren <tony@atomide.com> wrote:
> > * Cory Maccarrone <darkstar6262@gmail.com> [100306 20:53]:
>
> > If you don't have any serial output with that, then try this:
> >
> > - reset some branch to 4f2c49fedf
> > - make sure you have DEBUG_LL and EARLY_PRINTK enabled in your .config
> > - check that you have earlyprintk also in the kernel cmdline
> > - apply the following patch for the uncompress code
> >
>
> This worked. I was able to boot in with DEBUG_LL enabled and
> everything appears to be working properly.
OK, then that means the debug-macro.S changes for busyuart macro
are OK.
> Any other hints? I'm going to start looking at the changes, I'm
> beginning to understand them more.
Well the next patch gets rid of the hardcoded port addresses.
The debug port number is stored in uncompress.h based on the
machine ID.
Maybe try this next: Reset your test branch to commit
0c8219f0302d0d27fda52c790d38406801e547ec, then take a look at
arch/arm/plat-omap/include/plat/uncompress.h in a text editor.
Then see if there's an entry for your board in __arch_decomp_setup.
Is the DEBUG_LL_OMAP7XX(1, herald) correct? Is port 1 the right
UART to use?
If there's no entry, then you need to add a DEBUG_LL_OMAP7XX line
suitable for your board.
If you see something like "Uncompressing Linux..." then your know
the uncompress.h part is working. Once you get that working, then
it's time to look at the debug-macro.S again, see the addruart
macro that reads the debug port number from UART1 scratchpad
register.
Regards,
Tony
next prev parent reply other threads:[~2010-03-09 2:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-07 4:56 Commit 0c8219f0... breaks omap7xx support Cory Maccarrone
2010-03-09 0:48 ` Tony Lindgren
2010-03-09 1:51 ` Cory Maccarrone
2010-03-09 2:46 ` Tony Lindgren [this message]
2010-03-09 3:06 ` Cory Maccarrone
2010-03-09 15:56 ` Tony Lindgren
2010-03-09 23:41 ` Cory Maccarrone
2010-03-15 18:29 ` Tony Lindgren
2010-03-15 19:08 ` Tony Lindgren
2010-05-29 4:01 ` Cory Maccarrone
2010-05-31 8:21 ` 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=20100309024602.GQ2900@atomide.com \
--to=tony@atomide.com \
--cc=a.j.buxton@gmail.com \
--cc=darkstar6262@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=linwizard-devel@lists.sf.net \
--cc=miknix@gmail.com \
/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.