Dear Rob Herring,
In message
you wrote:
>
> > You are mixing some pretty much unrelated things here, which is IMO
> > not a good idea. Limiting the size for load operations is one thing,
> > but buffer size is something totally different. These must not be
> > mixed up. Please keep in mind th
On Tue, Apr 15, 2014 at 4:59 PM, Wolfgang Denk wrote:
> Dear Rob,
>
> In message <1397157488-8695-2-git-send-email-robherri...@gmail.com> you wrote:
>>
>> Various commands that load images have no checks that a loaded image
>> does not exceed the available RAM space and will happily continue
>> ov
Dear Rob,
In message <1397157488-8695-2-git-send-email-robherri...@gmail.com> you wrote:
>
> Various commands that load images have no checks that a loaded image
> does not exceed the available RAM space and will happily continue
> overwriting u-boot or other RAM that should not be touched. Also,
Hi Rob,
> From: Rob Herring
>
> Various commands that load images have no checks that a loaded image
> does not exceed the available RAM space and will happily continue
> overwriting u-boot or other RAM that should not be touched. Also,
> some commands such as USB DFU or fastboot need to know th
On Thu, Apr 10, 2014 at 02:18:03PM -0500, Rob Herring wrote:
> From: Rob Herring
>
> Various commands that load images have no checks that a loaded image
> does not exceed the available RAM space and will happily continue
> overwriting u-boot or other RAM that should not be touched. Also,
> some
From: Rob Herring
Various commands that load images have no checks that a loaded image
does not exceed the available RAM space and will happily continue
overwriting u-boot or other RAM that should not be touched. Also,
some commands such as USB DFU or fastboot need to know the maximum
buffer size
6 matches
Mail list logo
