On Wed, 22 May 2019, Serge Semin wrote:
> > > The problem might be fixed there by the next patch:
> > > ---
> > > diff --git a/arch/mips/dec/prom/memory.c b/arch/mips/dec/prom/memory.c
> > > index 5073d2ed78bb..5a0c734b5d04 100644
> > > --- a/arch/mips/dec/prom/memory.c
> > > +++ b/arch/mips/dec/p
On Wed, May 22, 2019 at 03:44:47PM +0200, Geert Uytterhoeven wrote:
> Hi Serge,
>
> ...
>
> >
> > The problem might be fixed there by the next patch:
> > ---
> > diff --git a/arch/mips/dec/prom/memory.c b/arch/mips/dec/prom/memory.c
> > index 5073d2ed78bb..5a0c734b5d04 100644
> > --- a/arch/mips/d
Hi Serge,
On Wed, May 22, 2019 at 3:34 PM Serge Semin wrote:
> On Wed, May 22, 2019 at 10:14:47AM +0200, Geert Uytterhoeven wrote:
> > On Wed, May 22, 2019 at 10:08 AM Mike Rapoport wrote:
> > > On Wed, May 22, 2019 at 09:47:04AM +0200, Geert Uytterhoeven wrote:
> > > > On Tue, May 21, 2019 at 5
Hello folks,
On Wed, May 22, 2019 at 10:14:47AM +0200, Geert Uytterhoeven wrote:
> Hi Mike,
>
> On Wed, May 22, 2019 at 10:08 AM Mike Rapoport wrote:
> > On Wed, May 22, 2019 at 09:47:04AM +0200, Geert Uytterhoeven wrote:
> > > On Tue, May 21, 2019 at 5:53 PM Mike Rapoport wrote:
> > > > On Tue
Hi Mike,
On Wed, May 22, 2019 at 10:08 AM Mike Rapoport wrote:
> On Wed, May 22, 2019 at 09:47:04AM +0200, Geert Uytterhoeven wrote:
> > On Tue, May 21, 2019 at 5:53 PM Mike Rapoport wrote:
> > > On Tue, May 21, 2019 at 04:56:39PM +0200, Geert Uytterhoeven wrote:
> > > > On Wed, Apr 24, 2019 at
On Wed, May 22, 2019 at 09:47:04AM +0200, Geert Uytterhoeven wrote:
> Hi Mike,
>
> On Tue, May 21, 2019 at 5:53 PM Mike Rapoport wrote:
> > On Tue, May 21, 2019 at 04:56:39PM +0200, Geert Uytterhoeven wrote:
> > > On Wed, Apr 24, 2019 at 12:50 AM Serge Semin
> > > wrote:
> > > > The reserved_en
Hi Serge,
On Tue, May 21, 2019 at 6:39 PM Serge Semin wrote:
> On Tue, May 21, 2019 at 06:53:10PM +0300, Mike Rapoport wrote:
> > On Tue, May 21, 2019 at 04:56:39PM +0200, Geert Uytterhoeven wrote:
> > > On Wed, Apr 24, 2019 at 12:50 AM Serge Semin
> > > wrote:
> > > > The reserved_end variable
Hi Mike,
On Tue, May 21, 2019 at 5:53 PM Mike Rapoport wrote:
> On Tue, May 21, 2019 at 04:56:39PM +0200, Geert Uytterhoeven wrote:
> > On Wed, Apr 24, 2019 at 12:50 AM Serge Semin
> > wrote:
> > > The reserved_end variable had been used by the bootmem_init() code
> > > to find a lowest limit o
Hello Geert, Mike
On Tue, May 21, 2019 at 06:53:10PM +0300, Mike Rapoport wrote:
> Hi Geert,
>
> On Tue, May 21, 2019 at 04:56:39PM +0200, Geert Uytterhoeven wrote:
> > Hi Serge,
> >
> > On Wed, Apr 24, 2019 at 12:50 AM Serge Semin
> > wrote:
> > > The reserved_end variable had been used by th
Hi Geert,
On Tue, May 21, 2019 at 04:56:39PM +0200, Geert Uytterhoeven wrote:
> Hi Serge,
>
> On Wed, Apr 24, 2019 at 12:50 AM Serge Semin wrote:
> > The reserved_end variable had been used by the bootmem_init() code
> > to find a lowest limit of memory available for memmap blob. The original
>
Hi Serge,
On Wed, Apr 24, 2019 at 12:50 AM Serge Semin wrote:
> The reserved_end variable had been used by the bootmem_init() code
> to find a lowest limit of memory available for memmap blob. The original
> code just tried to find a free memory space higher than kernel was placed.
> This limitat
Hello Paul
On Thu, May 02, 2019 at 06:45:39PM +, Paul Burton wrote:
> Hi Serge,
>
> On Thu, May 02, 2019 at 05:24:37PM +0300, Serge Semin wrote:
> > Just reviewed and tested your series on my machine. I tagged the whole
> > series
> > in a response to the cover-letter of [1].
>
> Thanks for
Hi Serge,
On Thu, May 02, 2019 at 05:24:37PM +0300, Serge Semin wrote:
> Just reviewed and tested your series on my machine. I tagged the whole series
> in a response to the cover-letter of [1].
Thanks for the review & testing; that series is now in mips-next.
> Could you please proceed with thi
Hello,
Serge Semin wrote:
> The reserved_end variable had been used by the bootmem_init() code
> to find a lowest limit of memory available for memmap blob. The original
> code just tried to find a free memory space higher than kernel was placed.
> This limitation seems justified for the memmap ra
On Tue, Apr 30, 2019 at 10:58:33PM +, Paul Burton wrote:
Hello Paul
> Hi Serge,
>
> On Fri, Apr 26, 2019 at 03:00:36AM +0300, Serge Semin wrote:
> > > 1) Older systems generally had something like an ISA bus which used
> > > addresses below the kernel, and bootloaders like YAMON left be
Hi Serge,
On Fri, Apr 26, 2019 at 03:00:36AM +0300, Serge Semin wrote:
> > 1) Older systems generally had something like an ISA bus which used
> > addresses below the kernel, and bootloaders like YAMON left behind
> > functions that could be called right at the start of RAM. This sort
> >
On Wed, Apr 24, 2019 at 10:43:48PM +, Paul Burton wrote:
> Hi Serge,
>
> On Wed, Apr 24, 2019 at 01:47:40AM +0300, Serge Semin wrote:
> > The reserved_end variable had been used by the bootmem_init() code
> > to find a lowest limit of memory available for memmap blob. The original
> > code jus
Hi Serge,
On Wed, Apr 24, 2019 at 01:47:40AM +0300, Serge Semin wrote:
> The reserved_end variable had been used by the bootmem_init() code
> to find a lowest limit of memory available for memmap blob. The original
> code just tried to find a free memory space higher than kernel was placed.
> This
18 matches
Mail list logo
