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] [PATCH 2/2 v12] Introduced btrfs file-system with btrload command
Date: Thu, 09 May 2013 23:43:52 +0200	[thread overview]
Message-ID: <20130509214352.92D213811AF@gemini.denx.de> (raw)
In-Reply-To: <518BB8C7.3090704@codethink.co.uk>

Dear Adnan Ali,

In message <518BB8C7.3090704@codethink.co.uk> you wrote:
> 
> > - Why do we have to calculate the crc32c_table[] at runtime?  Our
> >    regular CRC code uses a pre-calculated table; we should do the same
> >    here.
>         This is part of the port. But pre-calculated table can be manually
> created.

Not manually.  It should be done at compile time, suing basically the
same code.

> > - Compare the code for crc32c_cal() in the patch with the definition
> >    of DO_CRC(x) in "lib/crc32.c" - to me, it appears to be the same for
> >    little endian code (it is redundant?), but different for big endian
> >    systems - which raises the question if this code has ever been
> >    tested on a BE machine?
>          My code uses lib/crc32.c and i have only tested it on
>        mx53loco manchine.

I tend to believe thatit will not work on a big endian system, then.

> > - The code claims to be derived from "Linux kernel crypto/crc32c.c";
> >    but I cannot find such code in that file.
>        I think yes but part of part from syslinux. I have also added
>      SHA1 of commit so don't know.

Please provide an exact reference where this code is coming from.

> > - The implementation of crc32c_cal() suffers from a few other problems
> >    (like not triggering the watchdog, which will cause problems on
> >    systems that use one).
>        I think that is true as its not using main line crc32 code.

We probably should do that, then.

Thanks.

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
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
Drawing on my fine command of language, I said nothing.

  reply	other threads:[~2013-05-09 21:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-04  9:41 [U-Boot] [PATCH 0/2 v12] Btrfs filesystem port to U-boot Adnan Ali
2013-05-04  9:41 ` [U-Boot] [PATCH 1/2 v12] Enable Btrfs support in mx53loco config Adnan Ali
2013-05-04  9:41 ` [U-Boot] [PATCH 2/2 v12] Introduced btrfs file-system with btrload command Adnan Ali
2013-05-05  7:28   ` Wolfgang Denk
2013-05-05 14:52     ` Tom Rini
2013-05-05 15:15       ` Wolfgang Denk
2013-05-09 14:55         ` Adnan Ali
2013-05-09 21:43           ` Wolfgang Denk [this message]
2013-05-12 12:00             ` Adnan Ali
2013-05-12 18:20               ` Wolfgang Denk

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=20130509214352.92D213811AF@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.