From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [resent] New chapter in i.MX51 datasheet an issue?
Date: Tue, 08 May 2012 15:14:47 +0200 [thread overview]
Message-ID: <4FA91C47.4040201@denx.de> (raw)
In-Reply-To: <20120508140622.737b0fb1@archvile>
On 08/05/2012 14:06, David Jander wrote:
>> Go ahead in this direction. Then we can test on these boards (mx51evk /
>> vision2 / efikamx), the only ones having these issue).
>
> I agree we should only change the headers, but... if there are more i.MX51
> boards, they may all potentially need to fix their board code.... and that is
> up to them. Unfortunately this warning/wake-up call should come from Freescale
> themselves, but I have not heared anything from them.
What we can do is to change all MX51 boards in mainline (the three
boards we have already mentioned), explaining in the commit-id of the
patch why we change. We do not care about boards that were not pushed to
mainline.
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2012-05-08 13:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 10:08 [U-Boot] [resent] New chapter in i.MX51 datasheet an issue? David Jander
2012-05-06 16:15 ` Stefano Babic
2012-05-07 7:11 ` David Jander
2012-05-08 8:46 ` Stefano Babic
2012-05-08 10:23 ` Marek Vasut
2012-05-08 12:06 ` David Jander
2012-05-08 12:51 ` Marek Vasut
2012-05-09 9:31 ` David Jander
2012-05-08 13:14 ` Stefano Babic [this message]
2012-05-09 9:36 ` David Jander
2012-05-09 10:14 ` Stefano Babic
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=4FA91C47.4040201@denx.de \
--to=sbabic@denx.de \
--cc=u-boot@lists.denx.de \
/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.