public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Thorsten Glaser <tg@debian.org>
To: linux-m68k@vger.kernel.org
Subject: Re: Atari TT (next)
Date: Fri, 27 Jan 2012 17:01:56 +0000 (UTC)	[thread overview]
Message-ID: <loom.20120127T175834-143@post.gmane.org> (raw)
In-Reply-To: CAOmrzkLH18VCY0dzJPM14dn5ccWmSBkiPzq8EFqnCDHiM3bECQ@mail.gmail.com

Michael Schmitz <schmitzmic <at> googlemail.com> writes:

> >> Can you try to have the kernel placed in ST-RAM?
> >
> > No, the kernel is too big. I've only got 4MB ST-RAM. And getting more on

The guys at the Atari booth at OpenRheinRuhr had the same problem,
they also had a 4/4 MiB split.

> You may have to pare the kernel down to the bare minimum (i.e.
> modularize about everything you don't need to boot to initrd). Not
> sure where the limit for this is these days.

Note that the Debian kernel does not use initrd to boot (to the
finally installed system), especially as those tools are built
with klibc, which is currently still broken on m68k, and thus
contains everything needed to get into an ext3fs / from disc,
and then some. I don’t think you should be using a distro kernel
made under such constraints (nor should the distro kernel be
stripped more down considering the problems; I think there may
even be flavours that don’t _support_ initrd, outside the image
that is) but compile a stripped-down one yourself.

> >> You're right, this should be possible to test with ARAnyM - the
> >> behavior is not new though. Loading the kernel in TT-RAM has been
> >> problematic on the Falcon for a long time now.

I don’t know about that; ARanyM has a built-in LILO, so I never
saw any TOS (except when using AfrOS, but that’s a whole different
beast)…

bye,
//mirabilos

  parent reply	other threads:[~2012-01-27 17:02 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-07  1:27 Atari TT (next) Alan Hourihane
2012-01-07  6:47 ` Michael Schmitz
2012-01-07 16:59   ` Alan Hourihane
2012-01-08  0:46   ` Alan Hourihane
2012-01-08  4:13     ` Michael Schmitz
2012-01-08  9:35       ` Andreas Schwab
2012-01-08  9:42       ` Alan Hourihane
2012-01-08 23:51         ` Michael Schmitz
2012-01-08 23:59           ` Alan Hourihane
2012-01-09  0:05             ` Michael Schmitz
2012-01-09  0:14               ` Alan Hourihane
2012-01-09  0:23               ` Andreas Schwab
2012-01-09  3:17                 ` Michael Schmitz
2012-01-09  1:03               ` Alan Hourihane
2012-01-09  1:25                 ` Alan Hourihane
2012-01-09 10:40                   ` Andreas Schwab
2012-01-09 11:22                     ` Alan Hourihane
2012-01-09 12:14                     ` Geert Uytterhoeven
2012-01-09 12:40                       ` Tuomas Vainikka
2012-01-09 14:10                       ` [PATCH] m68k: fix assembler constraint to prevent overeager gcc optimisation Andreas Schwab
2012-01-22 10:15                         ` Geert Uytterhoeven
2012-01-22 10:53                           ` Geert Uytterhoeven
2012-01-22 12:42                           ` Andreas Schwab
2012-01-09  3:16                 ` Atari TT (next) Michael Schmitz
2012-01-27 17:01           ` Thorsten Glaser [this message]
2012-01-28 20:33             ` Michael Schmitz
2012-01-29  0:57               ` Thorsten Glaser
2012-01-29  9:42                 ` Geert Uytterhoeven
2012-01-29 19:55                   ` Thorsten Glaser
2012-01-29 21:56                     ` Geert Uytterhoeven
2012-01-08 10:20       ` Geert Uytterhoeven
2012-01-08 19:21         ` Michael Schmitz
2012-01-08 19:53           ` Geert Uytterhoeven
2012-01-08 23:42             ` Michael Schmitz
2012-01-08 22:05           ` Andreas Schwab
2012-01-08 23:39             ` Michael Schmitz
2012-01-08 23:49               ` Alan Hourihane
2012-01-08 23:58                 ` Michael Schmitz
2012-01-08 13:36 ` Andreas Schwab
2012-01-08 14:42   ` Alan Hourihane
2012-01-08 19:24   ` Michael Schmitz
2012-01-08 17:45 ` Geert Uytterhoeven
2012-01-08 19:50   ` Alan Hourihane

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=loom.20120127T175834-143@post.gmane.org \
    --to=tg@debian.org \
    --cc=linux-m68k@vger.kernel.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