From: Diego <diego.ml@zoho.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Issue with USB mass storage (thumb drives)
Date: Tue, 10 May 2016 14:04:02 +0200 [thread overview]
Message-ID: <1538078.ET8cfR6BQf@ip-192-168-197-87.eu-west-1.compute.internal> (raw)
In-Reply-To: <572A6B6E.6060401@denx.de>
In data mercoled? 4 maggio 2016 23:36:46, Marek Vasut ha scritto:
> On 05/04/2016 04:06 PM, Diego wrote:
> > In data mercoled? 4 maggio 2016 13:45:57, Marek Vasut ha scritto:
> >> On 05/04/2016 11:13 AM, Diego wrote:
> >>> <snip>
> >>> So I see three options:
> >>> 1) 65535 default with quirk table
> >>> 2) 32767 default without quirk table
> >>> 3) 32767 default with quirk table
> >>>
> >>> Personally I think 3) would be the safest solution, but I think 2) would
> >>> at
> >>> least work for most thumb drives.
> >>
> >> 1) with the quirk table would be the way to go, modern(ish) drives
> >> should work fine with 65535 .
> >
> > I personally can't see any improvement with more recent thumb drives,
> > quite the opposite.
> >
> > <snip>
> > Why are you saying modern(ish) drives should work?
>
> Hmmmmm :-(
>
> > For others following the thread, please post your experience, especially
> > with more recent drives (remember to test with files >16MB).
>
> I don't think it's really worth doing a thread about which sticks work
> and which don't. I would find it much more valuable to address this
> issue properly. I wonder if it would make sense to, instead of starting
> with a big value which might not work, start with a small(er) value and
> increase it with each subsequent block transfer. Quite similarly to what
> TCP does. Would you be willing to look into it ?
>
Hi Marek,
so your proposal is to ramp up transferred block size during transfer?
What's the rationale behind the proposal? In other words, why do you think it
will fix the problem?
Regarding implementing your proposal, it might take me very long to find some
time to dedicate to it, so if anybody else wants to step up before I look at
it, just raise your hand.
Bests,
Diego
next prev parent reply other threads:[~2016-05-10 12:04 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 10:35 [U-Boot] Issue with USB mass storage (thumb drives) Schrempf Frieder
2016-02-02 16:28 ` Fabio Estevam
2016-02-02 16:39 ` Marek Vasut
2016-02-03 7:40 ` Schrempf Frieder
2016-02-03 7:45 ` Hannes Schmelzer
2016-02-03 9:34 ` Marek Vasut
2016-02-03 9:40 ` Marek Vasut
2016-02-03 9:55 ` Fabio Estevam
2016-02-03 10:15 ` Schrempf Frieder
2016-02-03 11:12 ` Marek Vasut
2016-02-03 11:49 ` Schrempf Frieder
2016-02-03 16:40 ` Marek Vasut
2016-02-03 19:16 ` Sergei Temerkhanov
2016-02-04 8:21 ` Schrempf Frieder
2016-02-04 11:28 ` Marek Vasut
2016-02-08 8:41 ` Hannes Schmelzer
2016-02-08 14:58 ` Marek Vasut
2016-02-12 15:53 ` Simon Glass
2016-02-12 16:04 ` Hannes Schmelzer
2016-02-18 10:05 ` Schrempf Frieder
2016-02-18 15:32 ` Marek Vasut
2016-02-18 17:14 ` Fabio Estevam
2016-02-22 7:03 ` Schrempf Frieder
2016-02-22 17:51 ` Maxime Jayat
2016-02-22 17:59 ` Fabio Estevam
2016-02-23 6:38 ` Hannes Schmelzer
2016-02-24 17:43 ` Marek Vasut
2016-02-25 4:13 ` Simon Glass
2016-02-25 17:56 ` Marek Vasut
2016-02-26 1:56 ` Simon Glass
2016-04-14 13:20 ` Diego
2016-04-15 10:53 ` Marek Vasut
2016-04-15 12:13 ` Diego
2016-04-18 23:54 ` Marek Vasut
2016-04-25 8:16 ` Stefan Roese
2016-04-27 2:14 ` Marek Vasut
2016-04-27 9:04 ` Diego
2016-04-27 16:13 ` Marek Vasut
2016-04-28 13:04 ` Diego
2016-04-28 22:49 ` Marek Vasut
2016-04-29 7:58 ` Diego
2016-05-03 21:01 ` Marek Vasut
2016-05-04 9:13 ` Diego
2016-05-04 11:45 ` Marek Vasut
2016-05-04 14:06 ` Diego
2016-05-04 21:36 ` Marek Vasut
2016-05-10 12:04 ` Diego [this message]
2016-05-10 12:32 ` Marek Vasut
2016-05-20 5:07 ` Rajesh Bhagat
2016-05-20 11:52 ` Marek Vasut
2016-02-04 8:06 ` Schrempf Frieder
2016-10-14 9:01 Michael Kasprowicz
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=1538078.ET8cfR6BQf@ip-192-168-197-87.eu-west-1.compute.internal \
--to=diego.ml@zoho.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.