From: Josh Wu <josh.wu@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] sdcard with messed up partition table with FAT signature on header
Date: Thu, 5 Jun 2014 16:34:19 +0800 [thread overview]
Message-ID: <53902B8B.9010600@atmel.com> (raw)
In-Reply-To: <CAAJwJQm_j1FsqAdSEvmYh+jaiVoA61ZOj79rcgrBnhn2DPT-QQ@mail.gmail.com>
Hi, Darwin
On 6/5/2014 11:13 AM, Darwin Dingel wrote:
> Hi,
>
> I have a sdcard with a messed up partition table with a FAT signature on
> the header. This is readable under linux but not when I do a 'fatls' which
> results in "Partition 1 not valid on device 0".
Do you define the CONFIG_DOS_PARTITION in your board config head file
(include/configs/xxxx.h)?
If not defined that macro will cause above error.
Best Regards,
Josh Wu
>
> Before get_device_and_partition() was introduced this was still working
> because reading the 'fatls' will call fat_register_device(). After it fails
> to detect a valid partition due to the messed up partition table, it will
> then search the header for a FAT signature as a fallback and will continue
> to read it as a PBR. 'fatls' will be able to read it afterward.
>
> Unfortunately, this will now fail on the latest code. I have a patch to do
> the fallback check but under get_partition_info_extended(). However I am
> unsure if there is really a reason for the absence this FAT signature
> checking before failing fatls command.
>
> Do anyone have ideas on a reason for this FAT signature checking not being
> implemented in get_device_and_partition() (or
> get_partition_info_extended())?
>
>
> Thanks,
>
> Darwin
>
>
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
next prev parent reply other threads:[~2014-06-05 8:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 3:13 [U-Boot] sdcard with messed up partition table with FAT signature on header Darwin Dingel
2014-06-05 8:34 ` Josh Wu [this message]
2014-06-05 8:44 ` darwind1
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=53902B8B.9010600@atmel.com \
--to=josh.wu@atmel.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 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.