From: "Gerhard Pircher" <gerhard_pircher@gmx.net>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Crash with highmem support enabled
Date: Wed, 25 Oct 2006 09:45:14 +0200 [thread overview]
Message-ID: <20061025074514.236980@gmx.net> (raw)
In-Reply-To: <17726.63354.839675.689493@cargo.ozlabs.ibm.com>
-------- Original-Nachricht --------
Datum: Wed, 25 Oct 2006 15:34:50 +1000
Von: Paul Mackerras <paulus@samba.org>
An: "Gerhard Pircher" <gerhard_pircher@gmx.net>
Betreff: Re: Crash with highmem support enabled
> Gerhard Pircher writes:
>
> > I guess this has something to do with the IO block mapping, which is
> > implemented in the amigaone_setup.c file and looks like this:
>
> Why on earth are you still using io_block_mapping?
What should be used instead? ioremap()? The io_block_mapping() code was copied over from the PReP platform code in arch/ppc/platforms/.
In the meantime I found out that highmem failed due to the IO block mapping (sometimes it is good to look at the code ;). The mapping is needed for the AmigaOne/U-boot framebuffer to be able to access the ISA memory and I/O. Where and when can I savely remap (no 1:1 remapping) the ISA space so that the framebuffer survives the MMU initialization?
thanks!
Gerhard
--
GMX DSL-Flatrate 0,- Euro* - Überall, wo DSL verfügbar ist!
NEU: Jetzt bis zu 16.000 kBit/s! http://www.gmx.net/de/go/dsl
prev parent reply other threads:[~2006-10-25 7:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 20:27 Re: [Alsa-devel] RFC: dma_mmap_coherent() for powerpc/ppc architecture and ALSA? Gerhard Pircher
2006-06-29 9:27 ` Takashi Iwai
2006-06-29 21:15 ` Gerhard Pircher
2006-06-30 9:12 ` Takashi Iwai
2006-06-30 18:21 ` Gerhard Pircher
2006-10-19 13:24 ` [RFC] Porting AmigaOne platform code from ppc to powerpc Gerhard Pircher
2006-10-21 23:51 ` Benjamin Herrenschmidt
2006-10-23 18:57 ` Crash with highmem support enabled Gerhard Pircher
2006-10-25 5:34 ` Paul Mackerras
2006-10-25 7:45 ` Gerhard Pircher [this message]
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=20061025074514.236980@gmx.net \
--to=gerhard_pircher@gmx.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).