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: Mon, 4 Feb 2013 19:46:14 +0100	[thread overview]
Message-ID: <201302041946.14480.marex@denx.de> (raw)
In-Reply-To: <CAP9ODKq0sE0SD+UvvNVnSZ43cdMgE77tTeHhcnY_DYOWTaeghQ@mail.gmail.com>

Dear Otavio Salvador,

> On Mon, Feb 4, 2013 at 4:12 PM, Fabio Estevam <festevam@gmail.com> wrote:
> > On Thu, Jan 24, 2013 at 4:39 PM, Marek Vasut <marex@denx.de> wrote:
> >> PATCH:
> >> diff --git a/tools/mxsboot.c b/tools/mxsboot.c
> >> index 6c05aa4..d92c39f 100644
> >> --- a/tools/mxsboot.c
> >> +++ b/tools/mxsboot.c
> >> @@ -551,7 +551,7 @@ static int mx28_create_sd_image(int infd, int outfd)
> >> 
> >>         fsize = lseek(infd, 0, SEEK_END);
> >>         lseek(infd, 0, SEEK_SET);
> >> 
> >> -       size = fsize + 512;
> >> +       size = fsize + 4 * 512;
> >> 
> >>         buf = malloc(size);
> >>         if (!buf) {
> >> 
> >> @@ -559,7 +559,7 @@ static int mx28_create_sd_image(int infd, int outfd)
> >> 
> >>                 goto err0;
> >>         
> >>         }
> >> 
> >> -       ret = read(infd, (uint8_t *)buf + 512, fsize);
> >> +       ret = read(infd, (uint8_t *)buf + 4 * 512, fsize);
> >> 
> >>         if (ret != fsize) {
> >>         
> >>                 ret = -1;
> >>                 goto err1;
> >> 
> >> @@ -574,8 +574,8 @@ static int mx28_create_sd_image(int infd, int outfd)
> >> 
> >>         cb->drv_info[0].chip_num = 0x0;
> >>         cb->drv_info[0].drive_type = 0x0;
> >>         cb->drv_info[0].tag = 0x1;
> >> 
> >> -       cb->drv_info[0].first_sector_number = sd_sector + 1;
> >> -       cb->drv_info[0].sector_count = (size - 1) / 512;
> >> +       cb->drv_info[0].first_sector_number = sd_sector + 4;
> >> +       cb->drv_info[0].sector_count = (size - 4) / 512;
> >> 
> >>         wr_size = write(outfd, buf, size);
> >>         if (wr_size != size) {
> > 
> > My mx28evk does not boot with this patch applied.
> 
> As it does not work in mx28evk I'd prefer to use my previously
> proposed patch as it keeps clear what is done for mx23 and mx28. What
> people think?

NAK. Your patch is just adding churn, which the bootrom ignores. Did you manage 
to get reply from FSL why the bootrom ignores it already?

Best regards,
Marek Vasut

  reply	other threads:[~2013-02-04 18: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 [this message]
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

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=201302041946.14480.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