From: Andreas Schwab <schwab@linux-m68k.org>
To: Alan Hourihane <alanh@fairlite.co.uk>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: Atari TT (next)
Date: Sun, 08 Jan 2012 14:36:50 +0100 [thread overview]
Message-ID: <m2vcoml3il.fsf@igel.home> (raw)
In-Reply-To: <4F079F6B.8080502@fairlite.co.uk> (Alan Hourihane's message of "Sat, 07 Jan 2012 01:27:07 +0000")
Alan Hourihane <alanh@fairlite.co.uk> writes:
> Now the next problem is that the console is all corrupted because atafb
> initializes and shows this...
>
> atafb_init: start
> atafb_init: initializing TT hw
> atafb: screen_base 0046e000 real_screen_base 0046e000 screen_len 311296
> Determined 640x480, depth 4
> virtual 640x972
>
> Now, that screen_base is above 4MB, and I've only got 4MB STRAM.
screen_base is a virtual address, the physical address is actually
0x146e000.
> But there's also this further up the boot log.
>
> Ignoring memory chunk at 0x0:0x400000 before the first chunk
Since 12d810c1b8c2b913d48e629e2b5c01d105029839 (m68k: discontinuous
memory support) there is no longer support for memory regions with
physical addresses that are out of order. Before that, if the kernel
was loaded to TT-RAM the ST-RAM was virtually mapped just after TT-RAM.
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."
next prev parent reply other threads:[~2012-01-08 13:36 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
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 [this message]
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=m2vcoml3il.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=alanh@fairlite.co.uk \
--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