Re: [hatari-devel] SCU/VME register access?

[Eero Tamminen <oak@xxxxxxxxxxxxxx>]

Hi Christian,

On 13.6.2024 22.16, Christian Zietz wrote:
> > Attached is image I sent to Nicolas.
> >
> > Usage info:
> > https://github.com/hatari/hatari/blob/master/doc/m68k-linux.txt#L334
> >
> > Just remove "debug=nfcon" from the options in step 2).
>
> I immediately spotted something that will preclude me from testing on
> real HW: "Tell bootstrap program to load kernel to ST-RAM". My TT only
> has 4 MiB of ST-RAM (but 256 MiB of TT-RAM). With a kernel that is about
> 4.8 MB in size, this won't work. Unless the kernel can also be loaded
> into TT-RAM.

While I've noted this in the m68k-linux.txt, in 2019, for linux v5.0, 
when it's started with Hatari LILO:
-----------------------------------------------------------------
- Linux barfs at ST-RAM memory range given after TT-RAM.  However,
  if kernel is loaded to TT-RAM and ST-RAM range is given before
  TT-RAM range, kernel crashes.  Based on mails from 2013, this
  seems to be a known Linux/Atari issue

  Workaround: Hatari lilo.c gives ST-RAM before TT-RAM in bootinfo
------------------------------------------------------------------

At least v6.9 kernel boot seem to work fine when started by bootstrap 
program, if I drop the "-s" option from "bootargs", and define only 4MB 
ST-RAM in Hatari.


	- Eero