From: eric@eukrea.com (Eric Bénard)
To: linux-arm-kernel@lists.infradead.org
Subject: imx27 - hanging at freeing init memory -- getting some junk characters here after on console ..
Date: Mon, 23 Nov 2009 21:02:37 +0100 [thread overview]
Message-ID: <4B0AEA5D.6090500@eukrea.com> (raw)
In-Reply-To: <ba4215e10911230907s78e4bdfftc8cba93857ae9fca@mail.gmail.com>
Hi,
Martin Fuzzey wrote :
>> Assuming this is the reference hardware which you're running on, others
>> should be able to reproduce this error. Unfortunately I can't help here,
>> as I don't have access to any MX2 based hardware. Anyone else?
>>
> Mainline (2.6.32rc5) works fine on MX21 for me.
>
> I also have a MX27 based board (Eukrea CPUMX27 module not a ADS) which
> worked fine on 2.6.30 (haven't tried since - could do so if no one
> else has a ADS handy).
>
2.6.32-rc5 still works fine on CPUMX27 (i.MX27 + console on UART1 with
TX/RX/RTS/CTS wired + OpenEmbedded generated rootfs).
How is wired your UART ? Is it using RTS/CTS ?
Is the iomux properly setup ?
Eric
next prev parent reply other threads:[~2009-11-23 20:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 7:39 imx27 - hanging at freeing init memory -- getting some junk characters here after on console Vadivelan M
2009-11-04 13:15 ` Daniel Mack
2009-11-06 5:42 ` Vadivelan M
2009-11-10 6:49 ` Daniel Mack
2009-11-10 9:14 ` Andy Green
2009-11-17 4:04 ` Vadivelan M
2009-11-17 7:17 ` Daniel Mack
2009-11-17 8:27 ` Vadivelan M
2009-11-17 9:17 ` Daniel Mack
2009-11-17 11:59 ` Vadivelan M
2009-11-17 12:39 ` Daniel Mack
2009-11-23 17:07 ` Martin Fuzzey
2009-11-23 20:02 ` Eric Bénard [this message]
[not found] ` <OFEF3C8131.8C4BB129-ON65257665.003C2B08-65257665.003C2B0A@tcs.com>
2009-11-05 11:07 ` Daniel Mack
2009-12-05 15:15 ` Subramani Venkatesh
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=4B0AEA5D.6090500@eukrea.com \
--to=eric@eukrea.com \
--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).