Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

On Thu, Apr 14, 2016 at 4:15 AM, Roger Quadros wrote: > Steve, > > On 13/04/16 04:55, Steve Rae wrote: > > On Tue, Apr 12, 2016 at 6:50 AM, Roger Quadros wrote: > >> Lukasz, > >> > >> On 12/04/16 16:37, Lukasz Majewski wrote: > >>> Hi Roger, > >>> > Hi, >

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

Steve, On 13/04/16 04:55, Steve Rae wrote: > On Tue, Apr 12, 2016 at 6:50 AM, Roger Quadros wrote: >> Lukasz, >> >> On 12/04/16 16:37, Lukasz Majewski wrote: >>> Hi Roger, >>> Hi, On 12/04/16 14:19, Lukasz Majewski wrote: > Hi Tom, Mugunthan > >> On Mon,

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

On Tue, Apr 12, 2016 at 6:50 AM, Roger Quadros wrote: > Lukasz, > > On 12/04/16 16:37, Lukasz Majewski wrote: >> Hi Roger, >> >>> Hi, >>> >>> On 12/04/16 14:19, Lukasz Majewski wrote: Hi Tom, Mugunthan > On Mon, Apr 11, 2016 at 05:04:56PM +0530, Mugunthan V N wrote:

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

Lukasz, On 12/04/16 16:37, Lukasz Majewski wrote: > Hi Roger, > >> Hi, >> >> On 12/04/16 14:19, Lukasz Majewski wrote: >>> Hi Tom, Mugunthan >>> On Mon, Apr 11, 2016 at 05:04:56PM +0530, Mugunthan V N wrote: > On Friday 08 April 2016 12:10 AM, Marek Vasut wrote: >> On 04/07/2016

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

Hi Roger, > Hi, > > On 12/04/16 14:19, Lukasz Majewski wrote: > > Hi Tom, Mugunthan > > > >> On Mon, Apr 11, 2016 at 05:04:56PM +0530, Mugunthan V N wrote: > >>> On Friday 08 April 2016 12:10 AM, Marek Vasut wrote: > On 04/07/2016 06:46 PM, Sam Protsenko wrote: > > On Thu, Apr 7, 2016

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

Hi, On 12/04/16 14:19, Lukasz Majewski wrote: > Hi Tom, Mugunthan > >> On Mon, Apr 11, 2016 at 05:04:56PM +0530, Mugunthan V N wrote: >>> On Friday 08 April 2016 12:10 AM, Marek Vasut wrote: On 04/07/2016 06:46 PM, Sam Protsenko wrote: > On Thu, Apr 7, 2016 at 10:36 AM, Lukasz Majewski

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

Hi Tom, Mugunthan > On Mon, Apr 11, 2016 at 05:04:56PM +0530, Mugunthan V N wrote: > > On Friday 08 April 2016 12:10 AM, Marek Vasut wrote: > > > On 04/07/2016 06:46 PM, Sam Protsenko wrote: > > >> On Thu, Apr 7, 2016 at 10:36 AM, Lukasz Majewski > > >> wrote: > > >>> Hi

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

On Mon, Apr 11, 2016 at 05:04:56PM +0530, Mugunthan V N wrote: > On Friday 08 April 2016 12:10 AM, Marek Vasut wrote: > > On 04/07/2016 06:46 PM, Sam Protsenko wrote: > >> On Thu, Apr 7, 2016 at 10:36 AM, Lukasz Majewski > >> wrote: > >>> Hi Steve, > >>> > No -- I do

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

Tom > -Original Message- > From: U-Boot [mailto:u-boot-boun...@lists.denx.de] On Behalf Of Tom Rini > Sent: Saturday, April 09, 2016 1:14 AM > To: Sam Protsenko > Cc: Marek Vasut; Steve Rae; U-Boot Mailing List > Subject: Re: [U-Boot] [PATCH v2] fastboot: OUT trans

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

On Friday 08 April 2016 12:10 AM, Marek Vasut wrote: > On 04/07/2016 06:46 PM, Sam Protsenko wrote: >> On Thu, Apr 7, 2016 at 10:36 AM, Lukasz Majewski >> wrote: >>> Hi Steve, >>> No -- I do not believe that this issue is caused by different fastboot (client)

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

On Fri, Apr 08, 2016 at 02:11:48AM +0300, Sam Protsenko wrote: [snip] > The only actual documentation for fastboot protocol I found is [1], > and I don't see any mention of alignment there at all. So it wouldn't > surprise me if that patch was done just out of of empiric > observations. Which

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

On Thu, Apr 7, 2016 at 4:11 PM, Sam Protsenko wrote: > On Fri, Apr 8, 2016 at 12:39 AM, Steve Rae wrote: > > > > > > On Thu, Apr 7, 2016 at 2:16 PM, Sam Protsenko < > semen.protse...@linaro.org> > > wrote: > >> > >> On Thu, Apr 7, 2016 at 8:07

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

On Fri, Apr 8, 2016 at 12:39 AM, Steve Rae wrote: > > > On Thu, Apr 7, 2016 at 2:16 PM, Sam Protsenko > wrote: >> >> On Thu, Apr 7, 2016 at 8:07 PM, Steve Rae wrote: >> > Hi Sam, >> > >> > On Thu, Apr 7, 2016 at 9:46

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

On Thu, Apr 7, 2016 at 2:16 PM, Sam Protsenko wrote: > On Thu, Apr 7, 2016 at 8:07 PM, Steve Rae wrote: > > Hi Sam, > > > > On Thu, Apr 7, 2016 at 9:46 AM, Sam Protsenko < > semen.protse...@linaro.org> > > wrote: > >> > >> On Thu, Apr 7, 2016

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

On Thu, Apr 7, 2016 at 8:07 PM, Steve Rae wrote: > Hi Sam, > > On Thu, Apr 7, 2016 at 9:46 AM, Sam Protsenko > wrote: >> >> On Thu, Apr 7, 2016 at 10:36 AM, Lukasz Majewski >> wrote: >> > Hi Steve, >> > >> >> No -- I do

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

On 04/07/2016 06:46 PM, Sam Protsenko wrote: > On Thu, Apr 7, 2016 at 10:36 AM, Lukasz Majewski > wrote: >> Hi Steve, >> >>> No -- I do not believe that this issue is caused by different fastboot >>> (client) versions (the executable that runs on the host computer - >>>

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

Hi Sam, On Thu, Apr 7, 2016 at 9:46 AM, Sam Protsenko wrote: > On Thu, Apr 7, 2016 at 10:36 AM, Lukasz Majewski > wrote: > > Hi Steve, > > > >> No -- I do not believe that this issue is caused by different fastboot > >> (client) versions (the

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

On Thu, Apr 7, 2016 at 10:36 AM, Lukasz Majewski wrote: > Hi Steve, > >> No -- I do not believe that this issue is caused by different fastboot >> (client) versions (the executable that runs on the host computer - >> Linux, Windows, Mac, etc.) >> I have personally

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

Hi Marek, > On 04/06/2016 10:45 PM, Steve Rae wrote: > > Thanks for the reply, Marek > > > > On Wed, Apr 6, 2016 at 12:53 PM, Marek Vasut > > wrote: > > > > On 04/06/2016 07:18 PM, Steve Rae wrote: > > > No -- I do not believe that this issue

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

Hi Steve, > No -- I do not believe that this issue is caused by different fastboot > (client) versions (the executable that runs on the host computer - > Linux, Windows, Mac, etc.) > I have personally attempted three (3) different versions, and the > results are consistent. > > And no I don't

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

On 04/06/2016 10:45 PM, Steve Rae wrote: > Thanks for the reply, Marek > > On Wed, Apr 6, 2016 at 12:53 PM, Marek Vasut > wrote: > > On 04/06/2016 07:18 PM, Steve Rae wrote: > > No -- I do not believe that this issue is caused by different

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

Thanks for the reply, Marek On Wed, Apr 6, 2016 at 12:53 PM, Marek Vasut wrote: > On 04/06/2016 07:18 PM, Steve Rae wrote: > > No -- I do not believe that this issue is caused by different fastboot > > (client) versions (the executable that runs on the host computer - > >

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

On 04/06/2016 07:18 PM, Steve Rae wrote: > No -- I do not believe that this issue is caused by different fastboot > (client) versions (the executable that runs on the host computer - > Linux, Windows, Mac, etc.) > I have personally attempted three (3) different versions, and the > results are

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

No -- I do not believe that this issue is caused by different fastboot (client) versions (the executable that runs on the host computer - Linux, Windows, Mac, etc.) I have personally attempted three (3) different versions, and the results are consistent. And no I don't think that I "am the only

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

On 04/06/2016 07:35 AM, Steve Rae wrote: > > On Apr 5, 2016 3:07 PM, "Marek Vasut" > 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... >>

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

On 04/06/2016 09:09 AM, Lukasz Majewski wrote: > Hi Steve, Marek, Sam > >> On Apr 5, 2016 3:07 PM, "Marek Vasut" wrote: >>> >>> On 04/05/2016 08:31 PM, Steve Rae wrote: commit 9e4b510 fastboot: OUT transaction length must be aligned to >> wMaxPacketSize breaks some

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

Hi Steve, Marek, Sam > On Apr 5, 2016 3:07 PM, "Marek Vasut" 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

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

On Apr 5, 2016 3:07 PM, "Marek Vasut" 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. >

Re: [U-Boot] [PATCH v2] fastboot: OUT transaction length must be aligned to wMaxPacketSize

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 ? >