From: David Jander <david.jander@protonic.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] [resent] New chapter in i.MX51 datasheet an issue?
Date: Wed, 9 May 2012 11:36:26 +0200 [thread overview]
Message-ID: <20120509113626.2d4a86c5@archvile> (raw)
In-Reply-To: <4FA91C47.4040201@denx.de>
On Tue, 08 May 2012 15:14:47 +0200
Stefano Babic <sbabic@denx.de> wrote:
> 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.
Seems reasonable. Are you also implying that you are willing to propose a
patch? (Swapping the two values seems fairly trivial....)
Best regards,
--
David Jander
Protonic Holland.
next prev parent reply other threads:[~2012-05-09 9:36 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
2012-05-09 9:36 ` David Jander [this message]
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=20120509113626.2d4a86c5@archvile \
--to=david.jander@protonic.nl \
--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.