From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize
Date: Wed, 06 Apr 2016 12:57:49 +0200 [thread overview]
Message-ID: <5704EBAD.4000704@denx.de> (raw)
In-Reply-To: <20160406090940.27b86500@amdc2363>
On 04/06/2016 09:09 AM, Lukasz Majewski wrote:
> Hi Steve, Marek, Sam
>
>> On Apr 5, 2016 3:07 PM, "Marek Vasut" <marex@denx.de> wrote:
>>>
>>> On 04/05/2016 08:31 PM, Steve Rae wrote:
>>>> commit 9e4b510 fastboot: OUT transaction length must be aligned to
>> wMaxPacketSize
>>>> breaks some boards...
>>>>
>>>> Therefore add a conditional Kconfig to optionally enable this
>>>> feature.
>>>
>>> Did you drill into it to figure out why this is needed ?
>>>
>>
>> Marek,
>> Let me clarify....
>> All my boards work with the original code (before the commit which
>> aligned the size to the wMaxPacketSize).... Since that commit, all my
>> boards are broken.
>> And you will notice in this patch, that none of my boards define this
>> CONFIG_ ...
>
> Guys, please correct me if I'm wrong, but the problem _is_ be caused
> by supporting different fastboot protocol versions.
>
> Unfortunately, there is no way to specify "version" in the protocol so
> different versions of fastboot application handle transmission
> differently.
>
> I think that Sam and Steve were trying to test the code by using their
> fastboot apps, but without any conclusion. Am I right there? Has
> something changed?
>
> I'm OK with Kconfig flag approach, if we don't have any reliable way to
> distinct protocol versions.
>
> One fastboot user my try it with this option enabled or disabled.
>
> What I would love to see is a proper entry into ./doc READMEs to
> clarify this issue (not necessarily with this patch series). It would
> help other users in the future.
Hm, if there are two protocol versions and the protocol is such a
braindead design that it doesn't send version in it's datagrams, then
instead of selecting one protocol version via Kconfig option at compile
time, we should add an optional arg for the fastboot command to select
which host you're talking to at run-time ?
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-04-06 10:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 18:31 [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize Steve Rae
2016-04-05 22:06 ` Marek Vasut
2016-04-06 5:35 ` Steve Rae
2016-04-06 7:09 ` Lukasz Majewski
2016-04-06 10:57 ` Marek Vasut [this message]
2016-04-06 11:01 ` Marek Vasut
2016-04-06 17:18 ` Steve Rae
2016-04-06 19:53 ` Marek Vasut
2016-04-06 20:45 ` Steve Rae
2016-04-06 20:57 ` Marek Vasut
2016-04-07 8:03 ` Lukasz Majewski
2016-04-07 7:36 ` Lukasz Majewski
2016-04-07 16:46 ` Sam Protsenko
2016-04-07 17:07 ` Steve Rae
2016-04-07 21:16 ` Sam Protsenko
2016-04-07 21:39 ` Steve Rae
2016-04-07 23:11 ` Sam Protsenko
2016-04-07 23:15 ` Steve Rae
2016-04-08 19:44 ` Tom Rini
2016-04-11 12:29 ` B, Ravi
2016-04-07 18:40 ` Marek Vasut
2016-04-11 11:34 ` Mugunthan V N
2016-04-11 15:22 ` Tom Rini
2016-04-12 11:19 ` Lukasz Majewski
2016-04-12 12:40 ` Roger Quadros
2016-04-12 13:37 ` Lukasz Majewski
2016-04-12 13:50 ` Roger Quadros
2016-04-13 1:55 ` Steve Rae
2016-04-14 11:15 ` Roger Quadros
2016-04-15 19:56 ` Steve Rae
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=5704EBAD.4000704@denx.de \
--to=marex@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox