|Re: [hatari-devel] Running Linux in Hatari?|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Running Linux in Hatari?
- From: Thomas Huth <th.huth@xxxxxxxxx>
- Date: Sun, 17 Mar 2019 11:09:48 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1552817390; bh=bONYMNjmvdv2A01JW2443olbEWLh4upppBCB0QsvCMU=; h=Date:From:To:Subject:From; b=GP1TNozKg3KTHIP9URd1Y4T4jCzomNrs2oK1DAiiNmYdG0Huo9k/cX2fGj757U1j6 oZw906Z1o9DbBfH2iRM8a3qt2jjL7yj3ZF0wzA9JuxmhdFGpspukPdohaABhf7Ezoy 7tmqpqzdSu5PEeD5krVjYIsJEd1GhewDUf/3pWRj5sMHqHQpE/3ImKM05hOHAyyO1a 6ZzBRjwKxJCS/27ir0kISjfr4s7YmWOm7cTxE348M+aEZ96p57SqnwSmSpyelrVzxT id2eQlPGkxUdfXDLLgOlW2vlo78m7AwItI1pClp+HEz+z5ovpPOC5caxsB6Jd+ZFvc Tz3ZPr05NRp5Q==
Am Sat, 16 Mar 2019 23:02:56 +0200
schrieb Eero Tamminen <oak@xxxxxxxxxxxxxx>:
> On 3/16/19 4:12 AM, Thorsten Otto wrote:
> > On Samstag, 16. März 2019 01:29:00 CET Eero Tamminen wrote:
> >> What exactly the --lilo option does?
> > Essentially, it is a bootloader for the linux kernel built into
> > aranym. The parameters are taken from the config file:
> > [LILO]
> > Kernel = system/vmlinux
> > Args = root=/dev/hda1 video=atafb:vga16 stram_swap=0 debug=par
> > Ramdisk =
> > LoadToFastRam = No
> >> is there some specific API that should be implemented?
> > Yes, the kernel expects certain things to be passed via a bootinfo
> > structure. It is implemented in
> > https://github.com/aranym/aranym/blob/master/src/ bootos_linux.cpp
> Thanks. I've adapted the code for Hatari (needed some defines from
> kernel headers), but it doesn't work fully yet.
> Nicolas and others, is it OK if I push that code to Hatari repository?
Don't you want to wait till you've got it running? Otherwise this might
confuse users who spot the --lilo option and try to use it...
> It adds [LILO] section to config file, and --lilo <bool> command line.
> For now I've put lilo.c into falcon/ subdirectory, as Linux needs 030+
> CPU (and lilo.c errors otherwise), but I'm not sure is that the best
The falcon subdirectory sounds wrong, since this is not related to
Falcon hardware emulation. I think it should go into the main src