All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: schmitz <schmitz@biophys.uni-duesseldorf.de>
Cc: Michael Schmitz <schmitzmic@gmail.com>,
	Andreas Schwab <schwab@linux-m68k.org>,
	Linux/m68k <linux-m68k@vger.kernel.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 10:23:59 +0200	[thread overview]
Message-ID: <CAMuHMdXvN8MYqy81jjHpBDaNcbnS2dyWPWYMwak=9SA=9XPQBg@mail.gmail.com> (raw)
In-Reply-To: <533A74FB.606@biophys.uni-duesseldorf.de>

Hi Michael,

On Tue, Apr 1, 2014 at 10:12 AM, schmitz
<schmitz@biophys.uni-duesseldorf.de> wrote:
> While poking around in head.S, I came across a comment that stated the
> second page at the start of the kernel is used for the kernel page dir -
> that is the second page of virtual address space (FastRAM, in the case we
> care about here), not physcial address space, right?

The kernel is loaded in the second page of RAM. Initially, this page just
contains a few branches and the bootinfo versions. The code jumps to
_start, and the second page is reused for the kernel page dir:

ENTRY(_stext)
        bras    1f      /* Jump over bootinfo version numbers */
        .long   BOOTINFOV_MAGIC
        .long   MACH_AMIGA, AMIGA_BOOTI_VERSION
        ....
1:      jra     __start

.equ    kernel_pg_dir,_stext

.equ    .,_stext+PAGESIZE

ENTRY(_start)
        jra     __start
__INIT
ENTRY(__start)

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2014-04-01  8:24 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
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 [this message]
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='CAMuHMdXvN8MYqy81jjHpBDaNcbnS2dyWPWYMwak=9SA=9XPQBg@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=debian-68k@lists.debian.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=schmitz@biophys.uni-duesseldorf.de \
    --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.