From: Michael Schmitz <schmitz@mail.biophys.uni-duesseldorf.de>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Michael Schmitz <schmitzmic@gmail.com>,
Linux/m68k <linux-m68k@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
debian m68k <debian-68k@lists.debian.org>
Subject: Re: [PATCH 0/4] Atari kernel-in-FastRAM patches, take three
Date: Tue, 1 Apr 2014 01:52:16 +0200 [thread overview]
Message-ID: <20140331235216.GA2109@mail.biophys.uni-duesseldorf.de> (raw)
In-Reply-To: <87txae2dt4.fsf@igel.home>
Andreas,
> Don't top post!
Sorry - gurgle made me do it :')
>
> Michael Schmitz <schmitzmic@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 have to reimplement the check paging_init
> does.
I see - as a heuristic, we can probably assume that the first memchunk is
the relevant one, and especially in the case of FastRAM, also the larger
one.
Does this hold for Amiga/Mac/VME as well?
Cheers,
Michael
>
> Andreas.
>
> --
> Andreas Schwab, schwab@linux-m68k.org
> GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
> "And now for something completely different."
>
>
> --
> To UNSUBSCRIBE, email to debian-68k-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: https://lists.debian.org/87txae2dt4.fsf@igel.home
next prev parent reply other threads:[~2014-03-31 23:59 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 [this message]
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
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=20140331235216.GA2109@mail.biophys.uni-duesseldorf.de \
--to=schmitz@mail.biophys.uni-duesseldorf.de \
--cc=debian-68k@lists.debian.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.