On Fri, 4 Apr 2014, I wrote:
On Wed, 2 Apr 2014, Michael Schmitz wrote:
It may be possible to boot Linux with MacOS running in 24-bit mode,
and ISTR that this leads to a large number of memory chunks.
The chunk size would still be 16 MB, perhaps?
Looking at the Penguin source,
On Thu, 3 Apr 2014, Scott Holder wrote:
On 4/1/2014 8:23 AM, Finn Thain wrote:
It may be possible to boot Linux with MacOS running in 24-bit mode,
and ISTR that this leads to a large number of memory chunks. The
Penguin documentation says use 32-bit mode (which means installing
On Wed, 2 Apr 2014, Michael Schmitz wrote:
Hi Finn,
It may be possible to boot Linux with MacOS running in 24-bit mode,
and ISTR that this leads to a large number of memory chunks. The
Penguin
The chunk size would still be 16 MB, perhaps?
Looking at the Penguin source, findRAM()
On 4/1/2014 8:23 AM, Finn Thain wrote:
On Tue, 1 Apr 2014, Geert Uytterhoeven wrote:
snip
Don't know about Mac,
It may be possible to boot Linux with MacOS running in 24-bit mode, and
ISTR that this leads to a large number of memory chunks. The Penguin
documentation says use 32-bit mode
Hi Michael,
On Mon, Mar 31, 2014 at 11:24 PM, Michael Schmitz schmitz...@gmail.com wrote:
do we know the size of the first memory chunk early enough in head.S?
Maybe it's time to increase INIT_MAPPED_SIZE at least in cases where
we know that there's more than 4 MB in the first memchunk ...
Hi Geert,
do we know the size of the first memory chunk early enough in head.S?
Maybe it's time to increase INIT_MAPPED_SIZE at least in cases where
we know that there's more than 4 MB in the first memchunk ...
How do you know? You would have to reimplement the check paging_init
Hi Michael,
On Tue, Apr 1, 2014 at 9:39 AM, schmitz
schm...@biophys.uni-duesseldorf.de wrote:
On Mon, Mar 31, 2014 at 11:24 PM, Michael Schmitz schmitz...@gmail.com
wrote:
do we know the size of the first memory chunk early enough in head.S?
Maybe it's time to increase INIT_MAPPED_SIZE at
Hi Michael,
On Tue, Apr 1, 2014 at 9:45 AM, schmitz
schm...@biophys.uni-duesseldorf.de wrote:
do we know the size of the first memory chunk early enough in head.S?
Maybe it's time to increase INIT_MAPPED_SIZE at least in cases where
we know that there's more than 4 MB in the first memchunk ...
Hi Geert,
Hi Michael,
On Tue, Apr 1, 2014 at 9:39 AM, schmitz
schm...@biophys.uni-duesseldorf.de wrote:
On Mon, Mar 31, 2014 at 11:24 PM, Michael Schmitz schmitz...@gmail.com
wrote:
do we know the size of the first memory chunk early enough in head.S?
Maybe it's time to increase
Hi Michael,
On Tue, Apr 1, 2014 at 10:12 AM, schmitz
schm...@biophys.uni-duesseldorf.de wrote:
While poking around in head.S, I came across a comment that stated the
second page at the start of the kernel is used for the kernel page dir -
that is the second page of virtual address space
schmitz schm...@biophys.uni-duesseldorf.de writes:
What size FastRAM did precipitate that bug for you, Andreas?
It's the combination of kernel size and FastRAM setting that matters.
You can easily watch it by adding the bootmem_debug kernel parameter.
Andreas.
--
Andreas Schwab,
On Tue, 1 Apr 2014, Geert Uytterhoeven wrote:
On Tue, Apr 1, 2014 at 1:52 AM, Michael Schmitz wrote:
do we know the size of the first memory chunk early enough in
head.S? Maybe it's time to increase INIT_MAPPED_SIZE at least in
cases where we know that there's more than 4 MB in
Hi Finn,
Don't know about Mac,
It may be possible to boot Linux with MacOS running in 24-bit mode, and
ISTR that this leads to a large number of memory chunks. The Penguin
The chunk size would still be 16 MB, perhaps?
(Unless Geert is right and interleaving means multiple small memory
Hi Michael,
On Sun, Mar 30, 2014 at 1:01 AM, Michael Schmitz schmitz...@gmail.com wrote:
see the following patch series for the hopefully final word on
the 'make ST-RAM pool accessible for kernels running from FastRAM'
story.
When submitting a take three, please annotate the individual
Andreas,
do we know the size of the first memory chunk early enough in head.S?
Maybe it's time to increase INIT_MAPPED_SIZE at least in cases where
we know that there's more than 4 MB in the first memchunk ...
Cheers,
Michael
On Tue, Apr 1, 2014 at 9:58 AM, Andreas Schwab
Don't top post!
Michael Schmitz schmitz...@gmail.com writes:
do we know the size of the first memory chunk early enough in head.S?
Maybe it's time to increase INIT_MAPPED_SIZE at least in cases where
we know that there's more than 4 MB in the first memchunk ...
How do you know? You would
Michael Schmitz schmitz...@gmail.com writes:
see the following patch series for the hopefully final word on
the 'make ST-RAM pool accessible for kernels running from FastRAM'
story.
Would you mind sharing your config? I'm always getting a panic very
early, even before
17 matches
Mail list logo
