Hi Heiko,
> Hello Lukasz,
>
> Am 16.05.2014 10:58, schrieb Lukasz Majewski:
> > Hi Wolfgang, Tom,
> >
> >> Hi Wolfgang,
> >>
> >>> Dear Lukasz,
> >>>
> >>> In message<20140515090904.32f1d13d@amdc2363> you wrote:
>
> >> What I complained about is the change in behaviour. I asked
> >
Hi Heiko,
>
> Hello Lukasz,
>
> Am 16.05.2014 10:58, schrieb Lukasz Majewski:
> > Hi Wolfgang, Tom,
> >
> >> Hi Wolfgang,
> >>
> >>> Dear Lukasz,
> >>>
> >>> In message<20140515090904.32f1d13d@amdc2363> you wrote:
>
> >> What I complained about is the change in behaviour. I asked
> >>
Hello Lukasz,
Am 16.05.2014 10:58, schrieb Lukasz Majewski:
Hi Wolfgang, Tom,
Hi Wolfgang,
Dear Lukasz,
In message<20140515090904.32f1d13d@amdc2363> you wrote:
What I complained about is the change in behaviour. I asked
to make the existing behaviour the default, so unaware users
will
Hi Wolfgang, Tom,
> Hi Wolfgang,
>
> > Dear Lukasz,
> >
> > In message <20140515090904.32f1d13d@amdc2363> you wrote:
> > >
> > > > > What I complained about is the change in behaviour. I asked
> > > > > to make the existing behaviour the default, so unaware users
> > > > > will not be affected
Hi Wolfgang,
> Dear Lukasz,
>
> In message <20140515154334.626923b4@amdc2363> you wrote:
> >
> > > This reinforces my speculation that you are actually addressing
> > > the wrong problem. Instead of adding new code and environment
> > > variables and making the system even more complex, we shou
Dear Lukasz,
In message <20140515154334.626923b4@amdc2363> you wrote:
>
> > This reinforces my speculation that you are actually addressing the
> > wrong problem. Instead of adding new code and environment variables
> > and making the system even more complex, we should just leave
> > everything
Hi Wolfgang,
> Dear Lukasz,
>
> In message <20140515090904.32f1d13d@amdc2363> you wrote:
> >
> > > > What I complained about is the change in behaviour. I asked to
> > > > make the existing behaviour the default, so unaware users will
> > > > not be affected. Only if you intentionally want some
Dear Lukasz,
In message <20140515090904.32f1d13d@amdc2363> you wrote:
>
> > > What I complained about is the change in behaviour. I asked to make
> > > the existing behaviour the default, so unaware users will not be
> > > affected. Only if you intentionally want some other behaviour you
> > > c
Hello Lukasz,
Sorry for answering so late to this thread ...
Am 15.05.2014 09:09, schrieb Lukasz Majewski:
Hi Tom, Wolfgang,
On Fri, May 09, 2014 at 10:31:54AM +0200, Wolfgang Denk wrote:
Dear Lukasz,
In message<20140509085203.31133238@amdc2363> you wrote:
For automated tests I use MD5 a
Hi Tom, Wolfgang,
> On Fri, May 09, 2014 at 10:31:54AM +0200, Wolfgang Denk wrote:
> > Dear Lukasz,
> >
> > In message <20140509085203.31133238@amdc2363> you wrote:
> > >
> > > For automated tests I use MD5 and compare this value before
> > > sending data to target via DFU and after I read it. T
On Fri, May 09, 2014 at 10:31:54AM +0200, Wolfgang Denk wrote:
> Dear Lukasz,
>
> In message <20140509085203.31133238@amdc2363> you wrote:
> >
> > For automated tests I use MD5 and compare this value before sending
> > data to target via DFU and after I read it. This testing is done purely
> > on
Hi Wolfgang,
> Dear Lukasz,
>
> In message <20140509085203.31133238@amdc2363> you wrote:
> >
> > For automated tests I use MD5 and compare this value before sending
> > data to target via DFU and after I read it. This testing is done
> > purely on HOST machine.
>
> This is unsufficient. You sh
Dear Lukasz,
In message <20140509085203.31133238@amdc2363> you wrote:
>
> For automated tests I use MD5 and compare this value before sending
> data to target via DFU and after I read it. This testing is done purely
> on HOST machine.
This is unsufficient. You should always verify the image on
Hi Wolfgang,
> Dear Lukasz Majewski,
>
> In message <1399552067-31208-1-git-send-email-l.majew...@samsung.com>
> you wrote:
> > Up till now the CRC32 of received data was calculated
> > unconditionally. The standard crc32 implementation causes long
> > delay when large images were uploaded.
> >
Dear Lukasz Majewski,
In message <1399552067-31208-1-git-send-email-l.majew...@samsung.com> you wrote:
> Up till now the CRC32 of received data was calculated unconditionally.
> The standard crc32 implementation causes long delay when large images
> were uploaded.
>
> The "dfu_hash_algo" environm
On Thursday, May 08, 2014 at 02:27:47 PM, Lukasz Majewski wrote:
> Up till now the CRC32 of received data was calculated unconditionally.
> The standard crc32 implementation causes long delay when large images
> were uploaded.
>
> The "dfu_hash_algo" environment variable gives the opportunity to
>
Up till now the CRC32 of received data was calculated unconditionally.
The standard crc32 implementation causes long delay when large images
were uploaded.
The "dfu_hash_algo" environment variable gives the opportunity to
enable on demand (when e.g. debugging) the hash (crc32) calculation.
It can
17 matches
Mail list logo
