All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [swupdate] Re: SWUpdate - U-Boot environment library dependency
Date: Thu, 22 Nov 2018 17:00:25 +0100	[thread overview]
Message-ID: <20181122160025.B3E0D240403@gemini.denx.de> (raw)
In-Reply-To: <CAAh8qswJ-hf_FCvTdOggpS4MO6pThKLefjYxcquaBuhKfdQO2w@mail.gmail.com>

Dear Simon,

In message <CAAh8qswJ-hf_FCvTdOggpS4MO6pThKLefjYxcquaBuhKfdQO2w@mail.gmail.com> you wrote:
>
> > I don't know your board.
> >
> > It may be intentional, for example if there are size restrictions
> > for the SPL wich don't allow to include the CRC32 code...
> >
>
> I don't think this is intentional. I discussed this in another thread with
> Marek by now. There is no reference to the CRC code in the files in
> common/spl or the funtions called by it.

Depending on hardware capabilities, this may be indeed intentional,
for example to keep the size of the SPL below a certain limit or to
allow for other, more critical features instead.

> Searching the whole code, I cannot see anything that checks the uImage CRC
> from standard SPL. And I don't see board specific controls to do this
> check, did I miss something?

This may well be possible.  But then, this is usually stage two
already - the ROM bootloader did not check any SPL checksum
either...

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Perl itself is  usually  pretty  good  about  telling  you  what  you
shouldn't do. :-)     - Larry Wall in <11091@jpl-devvax.JPL.NASA.GOV>

  reply	other threads:[~2018-11-22 16:00 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-04 10:30 [U-Boot] SWUpdate - U-Boot environment library dependency Andreas Reichel
2018-11-20 21:11 ` Simon Goldschmidt
2018-11-20 23:10   ` Marek Vasut
2018-11-21  9:10     ` [U-Boot] [swupdate] " Stefano Babic
2018-11-21  9:20       ` Wolfgang Denk
2018-11-21 14:31         ` Marek Vasut
2018-11-21 14:56           ` Stefano Babic
2018-11-21 15:31             ` [U-Boot] " Simon Goldschmidt
2018-11-21 15:34               ` Marek Vasut
2018-11-21 16:23       ` [U-Boot] [swupdate] " Otavio Salvador
2018-11-21  8:31   ` [U-Boot] " Wolfgang Denk
2018-11-21  9:33     ` [U-Boot] [swupdate] " Stefano Babic
2018-11-21 10:14       ` Simon Goldschmidt
2018-11-21 10:22         ` Jan Kiszka
2018-11-21 10:49         ` Stefano Babic
2018-11-21 11:45           ` Wolfgang Denk
2018-11-21 11:56             ` Simon Goldschmidt
2018-11-21 12:22               ` Wolfgang Denk
2018-11-21 13:30             ` Stefano Babic
2018-11-21 14:27               ` Wolfgang Denk
2018-11-21 14:37                 ` Simon Goldschmidt
2018-11-21 15:01                   ` Stefano Babic
2018-11-21 15:41                   ` Wolfgang Denk
2018-11-21 15:48                     ` Simon Goldschmidt
2018-11-21 15:56                       ` Wolfgang Denk
2018-11-21 17:06                       ` Simon Goldschmidt
2018-11-22 14:22                         ` Wolfgang Denk
2018-11-22 14:41                           ` Simon Goldschmidt
2018-11-22 16:00                             ` Wolfgang Denk [this message]
2018-11-22 16:05                               ` Simon Goldschmidt
2018-11-21 11:38       ` Wolfgang Denk
2018-11-21 13:16         ` Stefano Babic
2018-11-21 14:23           ` Wolfgang Denk
2018-11-21 15:13             ` Simon Goldschmidt
2018-11-21  9:19   ` Stefano Babic
2018-11-21 10:02     ` Jan Kiszka
2018-11-21 10:21     ` Simon Goldschmidt
2018-11-21 11:05       ` Stefano Babic
2018-11-21 11:13         ` Simon Goldschmidt
2018-11-21 11:52           ` Stefano Babic
2019-03-04 16:26   ` 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=20181122160025.B3E0D240403@gemini.denx.de \
    --to=wd@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.