From: schmitz <schmitz@biophys.uni-duesseldorf.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Michael Schmitz <schmitzmic@gmail.com>,
Linux/m68k <linux-m68k@vger.kernel.org>,
Debian m68k <debian-68k@lists.debian.org>,
Michael Schmitz <schmitz@debian.org>
Subject: Re: [PATCH 2/2] m68k/atari - atafb: convert allocation of fb ram to new interface
Date: Sat, 22 Mar 2014 14:28:43 +1300 [thread overview]
Message-ID: <532CE74B.6010406@biophys.uni-duesseldorf.de> (raw)
In-Reply-To: <CAMuHMdVq=XEW_aVnu=M8skWYbiAOxOjNyT9zoZqTLUM0HxiM-Q@mail.gmail.com>
Hi Geert,
>>> kernel_set_cachemode(screen_base, screen_len,
>>> IOMAP_WRITETHROUGH);
>>>
>>> woops, that won't work with the virt_to_phys() above, nor with transparent
>>> translation. I guess it writes to a non-existent pointer table,
>>> causing the crash?
>>>
>> You mean kernel_set_cachemode wants a physical address?
>>
>
> No, it wants memory mapped using the page tables. Probably it will
> work only for System RAM, not for MMIO mapped in head.S.
>
I've disabled both to check, no change. ST-RAM (4 MB of it) is mapped
per page tables in head.S so we should be fine.
>
>> The last log line I get is:
>>
>> atafb_init: start
>> atafb_init: initializing Falcon hw
>> atafb: screen_base ff001000 real_screen_base 00001000 screen_len 69632
>> Determined 640x400, depth 1
>> virtual 640x870
>>
>> which is a bit further down.
>>
>> I guess it dies in register_framebuffer() - the next log entry is missing:
>>
>> fb_info(&fb_info, "frame buffer device, using %dK of video memory\n",
>> screen_len >> 10);
>>
>
> And register_framebuffer() will write to the frame buffer, I think.
> So info->screen_base may be incorrect.
>
> Yep:
>
> static void atafb_set_disp(struct fb_info *info)
> {
> atafb_get_var(&info->var, info);
> atafb_get_fix(&info->fix, info);
>
> info->screen_base = (void *)info->fix.smem_start;
> }
>
> Missing atari_stram_to_virt().
>
Should have had phys_to_virt() before I guess. Thanks.
> Any other casts that indicate bugs? ;-)
>
Probably - I'll go over the source again. My port of atafb a few years
back was none too subtle.
Cheers,
Michael
next prev parent reply other threads:[~2014-03-22 1:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 7:23 [PATCH 1/2] m68k/atari - stram: alloc ST-RAM pool even if kernel not in ST-RAM Michael Schmitz
2014-03-19 7:23 ` [PATCH 2/2] m68k/atari - atafb: convert allocation of fb ram to new interface Michael Schmitz
2014-03-19 8:01 ` Geert Uytterhoeven
2014-03-20 8:17 ` schmitz
2014-03-20 8:33 ` Geert Uytterhoeven
2014-03-22 1:28 ` schmitz [this message]
2014-03-22 7:36 ` schmitz
2014-03-19 7:51 ` [PATCH 1/2] m68k/atari - stram: alloc ST-RAM pool even if kernel not in ST-RAM Geert Uytterhoeven
2014-03-20 8:23 ` schmitz
2014-03-20 8:35 ` Geert Uytterhoeven
2014-03-22 1:32 ` schmitz
2014-03-23 20:02 ` Geert Uytterhoeven
2014-03-19 8:18 ` Andreas Schwab
2014-03-20 6:35 ` Patrice Mandin
2014-03-22 8:47 ` [PATCH 0/2] m68k/atari - make atafb work with kernel loaded to FastRAM Michael Schmitz
2014-03-23 0:28 ` schmitz
2014-03-22 8:47 ` [PATCH 1/2] m68k/atari - stram: alloc ST-RAM pool even if kernel not in ST-RAM Michael Schmitz
2014-03-22 8:47 ` [PATCH 2/2] m68k/atari - atafb: convert allocation of fb ram to new interface 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=532CE74B.6010406@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=schmitz@debian.org \
--cc=schmitzmic@gmail.com \
/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