public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Thorsten Glaser <tg@debian.org>
Cc: linux-m68k@vger.kernel.org
Subject: Re: [PATCH] m68k: Increase initial mapping to 16MB if possible
Date: Tue, 29 Apr 2014 12:33:44 +0200	[thread overview]
Message-ID: <8738gwxw53.fsf@igel.home> (raw)
In-Reply-To: <loom.20140429T121132-254@post.gmane.org> (Thorsten Glaser's message of "Tue, 29 Apr 2014 10:11:55 +0000 (UTC)")

Thorsten Glaser <tg@debian.org> writes:

> Andreas Schwab <schwab <at> linux-m68k.org> writes:
>
>> If the size of the first memory chunk is at least 16MB increase the
>> initial mapping to 16MB instead of 4MB.  This makes it possible to map
>
> Why not always?

Always what?

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."

  reply	other threads:[~2014-04-29 10:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24 10:24 [PATCH] m68k: Increase initial mapping to 16MB if possible Andreas Schwab
2014-04-25  9:37 ` Michael Schmitz
2014-04-29 10:11 ` Thorsten Glaser
2014-04-29 10:33   ` Andreas Schwab [this message]
2014-04-29 16:29     ` Geert Uytterhoeven
2014-04-29 16:43       ` Andreas Schwab
2014-04-30  7:38         ` Michael Schmitz
2014-05-25 16:57           ` Geert Uytterhoeven
2014-05-26  1:28             ` Michael Schmitz
2014-06-28 12:46             ` Andreas Schwab
2014-06-28 13:26               ` Geert Uytterhoeven
2014-06-28 13:49                 ` Andreas Schwab
2014-06-28 14:29                   ` Geert Uytterhoeven
2014-06-28 14:36                     ` Andreas Schwab
2014-06-28 15:55                       ` Geert Uytterhoeven
2014-06-28 16:27                         ` Andreas Schwab
2014-07-06  9:31                           ` Geert Uytterhoeven
2014-07-07 22:11                             ` Andreas Schwab
2014-07-08  7:23                               ` Geert Uytterhoeven

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=8738gwxw53.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=tg@debian.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