Hi Hannes,
On Fri, Nov 23, 2018 at 2:50 PM Hannes Schmelzer wrote:
>
>
>
> On 20.11.2018 16:34, Bin Meng wrote:
> > Hi Hannes,
> Hi Bin,
> thanks for having a look into and sorry for my late response.
>
> >
> > On Thu, Oct 11, 2018 at 2:41 PM Hannes Schmelzer
> > wrote:
> >>
> >> On 11.10.2018
On 20.11.2018 16:34, Bin Meng wrote:
Hi Hannes,
Hi Bin,
thanks for having a look into and sorry for my late response.
On Thu, Oct 11, 2018 at 2:41 PM Hannes Schmelzer wrote:
On 11.10.2018 08:01, Bin Meng wrote:
Hi Hannes,
Hi Bing,
thanks for very quick response on this.
On Thu, Oct
Hi Hannes,
On Thu, Oct 11, 2018 at 2:41 PM Hannes Schmelzer wrote:
>
>
> On 11.10.2018 08:01, Bin Meng wrote:
> > Hi Hannes,
> Hi Bing,
> thanks for very quick response on this.
> >
> > On Thu, Oct 11, 2018 at 1:45 PM Hannes Schmelzer
> > wrote:
> >> If we're booting some u-boot module with
On 11.10.2018 08:01, Bin Meng wrote:
Hi Hannes,
Hi Bing,
thanks for very quick response on this.
On Thu, Oct 11, 2018 at 1:45 PM Hannes Schmelzer
wrote:
If we're booting some u-boot module with compressed payload, we have to
use the pointer where the image really has been loaded (unzipped)
Hi Hannes,
On Thu, Oct 11, 2018 at 1:45 PM Hannes Schmelzer
wrote:
>
> If we're booting some u-boot module with compressed payload, we have to
> use the pointer where the image really has been loaded (unzipped) to
> instead the pointer to the payload of the u-boot module.
>
> Signed-off-by:
If we're booting some u-boot module with compressed payload, we have to
use the pointer where the image really has been loaded (unzipped) to
instead the pointer to the payload of the u-boot module.
Signed-off-by: Hannes Schmelzer
---
arch/x86/lib/bootm.c | 4 ++--
1 file changed, 2
6 matches
Mail list logo