From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] fatls shows duplicated entries with long and short names
Date: Mon, 14 Oct 2013 12:07:37 -0400 [thread overview]
Message-ID: <20131014160737.GE5843@oliver-linux> (raw)
In-Reply-To: <525C1514.5030307@digi.com>
On Mon, Oct 14, 2013 at 06:00:20PM +0200, Hector Palacios wrote:
> Dear Marek,
>
> I noticed that 'fatls' displays duplicated filenames (short and
> long) for every file in the media:
>
> # fatls mmc 0
> 2083460 uimage-myplatform
> 2083460 uimage~1
> 1520 rootfs-dummy.jffs2
> 1520 rootfs~1.jff
> 3294952 uimage
> 3294952 uimage
>
> The guilty commit is ff04f6d1224d8952b566b8671222151495883073 by
> you, who moved the chksum calculation out of an if() and now the
> code never enters this:
>
> #ifdef CONFIG_SUPPORT_VFAT
> else if (dols == LS_ROOT && csum == prevcksum) {
> prevcksum = 0xffff;
> dentptr++;
> continue;
> }
> #endif
>
> Could you please check?
Can you please provide more details about your platform and what U-Boot
rev you see this on exactly? I haven't seen anything like this on
Beaglebone Black recently, for example.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20131014/146f80ab/attachment.pgp>
next prev parent reply other threads:[~2013-10-14 16:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 16:00 [U-Boot] fatls shows duplicated entries with long and short names Hector Palacios
2013-10-14 16:04 ` Marek Vasut
2013-10-14 16:07 ` Tom Rini [this message]
2013-10-14 16:57 ` Jagan Teki
2013-10-15 7:16 ` Hector Palacios
2013-10-15 7:21 ` Jagan Teki
2013-10-15 7:26 ` Albert ARIBAUD
2013-11-22 19:31 ` drambo
2013-11-22 20:50 ` Tom Rini
2013-11-22 21:13 ` Wolfgang Denk
2013-11-22 23:30 ` drambo
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=20131014160737.GE5843@oliver-linux \
--to=trini@ti.com \
--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