public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Scott Holder <scott@iamscott.net>
To: Finn Thain <fthain@telegraphics.com.au>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Michael Schmitz <schmitz@mail.biophys.uni-duesseldorf.de>,
	Andreas Schwab <schwab@linux-m68k.org>,
	Michael Schmitz <schmitzmic@gmail.com>,
	Linux/m68k <linux-m68k@vger.kernel.org>,
	debian m68k <debian-68k@lists.debian.org>
Subject: Re: [PATCH 0/4] Atari kernel-in-FastRAM patches, take three
Date: Thu, 03 Apr 2014 23:43:06 -0400	[thread overview]
Message-ID: <533E2A4A.2040107@iamscott.net> (raw)
In-Reply-To: <alpine.LNX.2.00.1404012153360.16187@nippy.intranet>

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 (which means installing Mode32 if you
> have old MacOS and old ROMs). The only Mac I have here is running MacOS
> 7.6 so I can't test 24-bit mode. You can see the debug output from Penguin
> below.

I happen to have my crazy PearPC/Mac OS X-booting LC475 still up and 
running with a 7.5.5 system folder on it. I rebooted it into 24-bit mode 
and loading Penguin does give a warning that 32-bit mode works better. 
Attempting to boot generates:

*** Too many memory ranges!!!
Error:
*** setup_ram_mappings() failure - too many mappings

I have a 64mb simm in this LC475; I tried popping it out (leaving me 
with 4mb) and it actually did attempt to unpack the kernel, but there's 
too little memory to do it. I have a bagful of smaller 72-pin simms 
kicking around somewhere; I'll have to dig it out of the closet and try 
it again.

Sadly my IIci is still misbehaving due to bad caps. I do have a working 
840AV here... I believe it should work in 24-bit mode. I don't have any 
older 32-bit unclean Macs of the era when 24-bit was normal to try with 
to see if maybe the memory controller works better.

>
>> but I have some memories of interleaved banks and such...
> There are some Mac models with memory controllers that do interleaving. I
> don't know whether interleaving is relevant here. I'd have to consult the
> Penguin source code to know whether it behaves differently on different
> models.

All I can say here is I ran 2.0-era kernels on a Quadra 840AV which does 
have interleaved RAM way back in the day just fine. I haven't yet gotten 
modern kernels (even the setup that works on the LC475) booting on it 
yet; sadly I'm not much good for coding or debug tracing.

Scott

  parent reply	other threads:[~2014-04-04  3:43 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-30  0:01 [PATCH 0/4] Atari kernel-in-FastRAM patches, take three Michael Schmitz
2014-03-30  0:01 ` [PATCH 1/4] m68k/atari - stram: alloc ST-RAM pool even if kernel not in ST-RAM Michael Schmitz
2014-03-30 19:11   ` Geert Uytterhoeven
2014-03-31  1:58     ` Michael Schmitz
2014-03-30  0:01 ` [PATCH 2/4] m68k/atari - atafb: convert allocation of fb ram to new interface Michael Schmitz
2014-03-30 19:11   ` Geert Uytterhoeven
2014-03-30  0:01 ` [PATCH 3/4] m68k/atari - ataflop: use correct virt/phys translation for DMA buffer Michael Schmitz
2014-03-31  7:46   ` Geert Uytterhoeven
2014-03-31 14:28     ` Jens Axboe
2014-03-30  0:01 ` [PATCH 4/4] m68k/atari - atari_scsi: " Michael Schmitz
2014-03-31  7:48   ` Geert Uytterhoeven
2014-03-30 22:34 ` [PATCH 0/4] Atari kernel-in-FastRAM patches, take three Andreas Schwab
2014-03-31  1:55   ` Michael Schmitz
2014-03-31 20:58     ` Andreas Schwab
2014-03-31 21:24       ` Michael Schmitz
2014-03-31 22:39         ` Andreas Schwab
2014-03-31 23:52           ` Michael Schmitz
2014-04-01  7:28             ` Geert Uytterhoeven
2014-04-01  7:45               ` schmitz
2014-04-01  7:50                 ` Geert Uytterhoeven
2014-04-01 12:23               ` Finn Thain
2014-04-01 12:41                 ` Geert Uytterhoeven
2014-04-01 18:56                 ` Michael Schmitz
2014-04-04  6:12                   ` Finn Thain
2014-04-09  6:44                     ` Finn Thain
2014-04-04  3:43                 ` Scott Holder [this message]
2014-04-04  6:08                   ` Finn Thain
2014-04-01  7:24         ` Geert Uytterhoeven
2014-04-01  7:39           ` schmitz
2014-04-01  7:49             ` Geert Uytterhoeven
2014-04-01  8:12               ` schmitz
2014-04-01  8:23                 ` Geert Uytterhoeven
2014-04-01  9:06             ` Andreas Schwab
2014-03-31  7:42 ` Geert Uytterhoeven
2014-03-31  7:54   ` Michael Schmitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=533E2A4A.2040107@iamscott.net \
    --to=scott@iamscott.net \
    --cc=debian-68k@lists.debian.org \
    --cc=fthain@telegraphics.com.au \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=schmitz@mail.biophys.uni-duesseldorf.de \
    --cc=schmitzmic@gmail.com \
    --cc=schwab@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox