public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mxs: mxsboot: Add support for SD card generation for i.MX23
Date: Sat, 26 Jan 2013 18:46:33 +0100	[thread overview]
Message-ID: <201301261846.34015.marex@denx.de> (raw)
In-Reply-To: <CAP9ODKo2ZmygpNqiJecwUL-Aq0fwNUUkKb+VBfLqkb7XTG=vAw@mail.gmail.com>

Dear Otavio Salvador,

> On Sat, Jan 26, 2013 at 3:03 PM, Marek Vasut <marex@denx.de> wrote:
> > Dear Otavio Salvador,
> > 
> > Putting Stefano on Cc, why is he omitted?
> > 
> >> On Fri, Jan 25, 2013 at 10:40 AM, Marek Vasut <marex@denx.de> wrote:
> >> >> On Thu, Jan 24, 2013 at 4:31 PM, Otavio Salvador
> >> >> 
> >> >> <otavio@ossystems.com.br> wrote:
> >> >> > I prefer to have this as is and share documentation with mx28. The
> >> >> > NAND ought to be done providing same interface so one doc for it
> >> >> > all. I think change it in next version is wrong and confuse users.
> >> >> 
> >> >> Ping?
> >> >> 
> >> >> We won't be able to get rid of mxsboot for NAND use-case so I'd
> >> >> prefer to have it for SD as well. For me it does not matter much as
> >> >> I use OE and it automates it all; but for ordinary user it is
> >> >> important to it to be consistent so all 'mxs' SoC would work same
> >> >> way from user point of view.
> >> >> 
> >> >> If we find a better way of doing things in future we can base on this
> >> >> and improve it later but please let's get it in and move forward...
> >> > 
> >> > Does my proposed patch not work for you? (the one which shifts the
> >> > bootstream payload to block 4 in partition 1)
> >> 
> >> I gave it a try today.
> >> 
> >> And it works for mx23evk; I did not test it in mx28.
> >> 
> >> So what is the plan? I did not check the NAND format yet to know if it
> >> is the same between mx28 and mx23 but I do want the machines merged as
> >> soon as possible so people can play with it and find bugs.
> > 
> > The plan is to:
> > 1) Figure out what's with MX23 -- did you place FSL supp. ticket already?
> 
> I contacted someone internal which is trying to find it out.

Please fill a support ticket.

> > 2) If 1) fails, try my patch on mx28 (since mx23 ignores it anyway and we
> > can't figure out why?)
> 
> I'd prefer to go with 2 in meanwhile. Could you please prepare a patch for
> it?

Fabio, can you test on mx28 please?

Best regards,
Marek Vasut

      reply	other threads:[~2013-01-26 17:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-24 17:54 [U-Boot] [PATCH] mxs: mxsboot: Add support for SD card generation for i.MX23 Otavio Salvador
2013-01-24 17:56 ` Marek Vasut
2013-01-24 18:03   ` Otavio Salvador
2013-01-24 18:08     ` Marek Vasut
2013-01-24 18:31       ` Otavio Salvador
2013-01-24 18:39         ` Marek Vasut
2013-02-04 18:12           ` Fabio Estevam
2013-02-04 18:15             ` Otavio Salvador
2013-02-04 18:46               ` Marek Vasut
2013-02-04 18:50                 ` Otavio Salvador
2013-02-04 20:58                   ` Marek Vasut
2013-02-04 18:45             ` Marek Vasut
2013-01-25 12:35         ` Otavio Salvador
2013-01-25 12:40           ` Marek Vasut
2013-01-26 15:50             ` Otavio Salvador
2013-01-26 17:03               ` Marek Vasut
2013-01-26 17:19                 ` Otavio Salvador
2013-01-26 17:46                   ` Marek Vasut [this message]

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=201301261846.34015.marex@denx.de \
    --to=marex@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox