All of lore.kernel.org
 help / color / mirror / Atom feed
From: schmitz <schmitz@biophys.uni-duesseldorf.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
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, 01 Apr 2014 21:12:43 +1300	[thread overview]
Message-ID: <533A74FB.606@biophys.uni-duesseldorf.de> (raw)
In-Reply-To: <CAMuHMdX4erc4mAQAOiyL3D-CYoLCembqq_zmcLK7LuUT7hxAcg@mail.gmail.com>

Hi Geert,
> Hi Michael,
>
> On Tue, Apr 1, 2014 at 9:39 AM, schmitz
> <schmitz@biophys.uni-duesseldorf.de> wrote:
>   
>>> On Mon, Mar 31, 2014 at 11:24 PM, Michael Schmitz <schmitzmic@gmail.com>
>>> wrote:
>>>       
>>>> 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 ...
>>>>         
>>> "get_bi_record BI_MEMCHUNK" will return a pointer to the first mem_info
>>> struct.
>>>       
>> Yep, that's as far as I got - if I read bootinfo.h right, this will need to
>> have an offset of 12 bytes added to get to the size member, correct?
>>     
>
> Nope, only 4. A0 points to the bootinfo record payload, which is of
> type struct mem_info * in this case:
>   

Right - should have read on to find the get_bi_record defs.

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?

Still wondering why the kernel in FastRAM won't reboot cleanly...

Cheers,

    Michael

  reply	other threads:[~2014-04-01  8:12 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 [this message]
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=533A74FB.606@biophys.uni-duesseldorf.de \
    --to=schmitz@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.