From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: u-boot@lists.denx.de
Subject: fat: handle Windows formatted partition (thru USB Mass Storage)
Date: Fri, 17 Jan 2020 15:12:41 +0900 [thread overview]
Message-ID: <20200117061240.GO28530@linaro.org> (raw)
In-Reply-To: <CAHp75Vc3dcJPf0hhEWJet_f24994gxMY2V_n_SSBzk3EG1OGPQ@mail.gmail.com>
On Thu, Jan 16, 2020 at 10:31:49PM +0200, Andy Shevchenko wrote:
> On Thu, Jan 16, 2020 at 9:20 PM Heinrich Schuchardt <xypron.glpk@gmx.de> wrote:
> > On 1/16/20 11:39 AM, Andy Shevchenko wrote:
> > >
> > >>> Obviously U-Boot's fat code cannot handle it.
> > >>
> > >> So precisely, U-Boot cannot handle nested partition( table)s?
> > >
> > > Seems so. We need to be able to supply the partition number we would
> > > like to open, something like
> > > cmd <interface> [<dev>[:<partition>[:<nested partition>]]]
> > > otherwise it will require some (error prone) heuristics to understand
> > > which one user would like to use.
> > >
> >
> > I have formatted a USB stick Windows 10.
>
> That is *not* the case I'm describing.
>
> Maybe I described it wrong. Let me try again.
>
> Prerequisites:
> - the board with U-Boot and installed Linux OS on eMMC
> - g_multi module in Linux OS that shares *one of the eMMC partitions*
> (pay attention here) as a disk to Windows host
I also misunderstood your assumption above; You are developing
a linux-based USB gadget for Windows (10)?
> Now, when you format that exposed disk (which is actually a partition
> on eMMC!) in Windows, you will get nested partitioning.
So why do you want to access *that* partition from U-Boot on the board?
I don't think it is a common case.
-Takahiro Akashi
> P.S. I can easily reproduce this on real device with latest U-Boot.
> U-Boot has obvious issue with recognizing such disks.
>
> --
> With Best Regards,
> Andy Shevchenko
next prev parent reply other threads:[~2020-01-17 6:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 8:29 [U-Boot] [PATCH] fs: fat: handle deleted directory entries correctly AKASHI Takahiro
2019-11-27 4:34 ` AKASHI Takahiro
2019-12-05 22:09 ` Tom Rini
2020-01-13 10:52 ` fat: handle Windows formatted partition (thru USB Mass Storage) Andy Shevchenko
2020-01-13 10:53 ` Fwd: " Andy Shevchenko
2020-01-13 16:34 ` Tom Rini
2020-01-13 17:55 ` Heinrich Schuchardt
2020-01-13 19:15 ` Andy Shevchenko
2020-01-13 19:22 ` Andy Shevchenko
2020-01-13 20:58 ` Andy Shevchenko
2020-01-13 21:05 ` Heinrich Schuchardt
2020-01-13 21:52 ` Andy Shevchenko
2020-01-13 23:14 ` Heinrich Schuchardt
2020-01-14 8:21 ` Andy Shevchenko
2020-01-14 8:23 ` Andy Shevchenko
2020-01-14 12:43 ` Andy Shevchenko
2020-01-14 13:16 ` Andy Shevchenko
2020-01-15 0:12 ` AKASHI Takahiro
2020-01-16 2:01 ` AKASHI Takahiro
2020-01-16 10:39 ` Andy Shevchenko
2020-01-16 19:20 ` Heinrich Schuchardt
2020-01-16 20:31 ` Andy Shevchenko
2020-01-17 6:12 ` AKASHI Takahiro [this message]
2020-01-17 9:47 ` Andy Shevchenko
2020-01-17 14:51 ` Tom Rini
2020-01-21 0:39 ` AKASHI Takahiro
2020-01-21 16:13 ` Andy Shevchenko
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=20200117061240.GO28530@linaro.org \
--to=takahiro.akashi@linaro.org \
--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