From: Albert Herranz <albert_herranz@yahoo.es>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC PATCH v2 08/11] powerpc: gamecube/wii: early debugging using usbgecko
Date: Mon, 30 Nov 2009 06:50:53 +0100 [thread overview]
Message-ID: <4B135D3D.9030006@yahoo.es> (raw)
In-Reply-To: <1259536695.2076.40.camel@pasglop>
Benjamin Herrenschmidt wrote:
> On Sat, 2009-11-28 at 21:43 +0100, Albert Herranz wrote:
>> + * Prepare again the same BAT for MMU_init.
>> + * This allows udbg I/O to continue working after the MMU is
>> + * turned on for real.
>> + *
>> + * We are assuming here that exi_io_base is identity mapped.
>> + */
>> + addr = ((unsigned long)exi_io_base) & 0xffff0000;
>> + setbat(1, addr, addr, 128*1024, PAGE_KERNEL_NCG);
>
> How do you prevent that from overlapping otherwise valid kernel
> mappings ?
>
ug_udbg_init() is called from ppc_md.init_early.
It doesn't overlap any valid kernel mappings because exi_io_base is hardcoded to an i/o region not used yet by the kernel.
See udbg_early_grab_exi_io_base().
The setbat just prepares again, exactly in the same way, the same BAT that we got setup by setup_usbgecko_bat in head_32.S.
_start
__start
> early_init
> mmu_off
# mmu off
> clear_bats
> flush_tlbs
> initial_bats
> setup_usbgecko_bat <--- BAT1 setup here
> call_setup_cpu
> init_idle_6xx
! relocate_kernel
! turn_on_mmu
# mmu on
! start_here
> machine_init
>> udbg_early_init
>>> udbg_init_usbgecko <--- BAT1 prepared again here for after MMU_init
>> early_init_devtree
> __save_cpu_setup
> MMU_init
# mmu off
> load_up_mmu
# mmu on
! start_kernel
> You need to allocate the virtual space. For a debug thing like that, you
> could use the fixmap. In fact, I think we should create a fixmap entry
> or two always available for use by early debug.
>
Or give us back ppc_md.setup_io_mappings :)
> Cheers,
> Ben.
>
Thanks,
Albert
next prev parent reply other threads:[~2009-11-30 5:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-28 20:43 [RFC PATCH v2 00/11] powerpc: nintendo gamecube support Albert Herranz
2009-11-28 20:43 ` [RFC PATCH v2 01/11] powerpc: gamecube/wii: usbgecko bootwrapper console support Albert Herranz
2009-12-01 18:28 ` Segher Boessenkool
2009-11-28 20:43 ` [RFC PATCH v2 02/11] powerpc: gamecube: device tree Albert Herranz
2009-12-01 18:29 ` Segher Boessenkool
2009-11-28 20:43 ` [RFC PATCH v2 03/11] powerpc: gamecube: bootwrapper bits Albert Herranz
2009-12-01 18:31 ` Segher Boessenkool
2009-11-28 20:43 ` [RFC PATCH v2 04/11] powerpc: gamecube/wii: introduce GAMECUBE_COMMON Albert Herranz
2009-11-28 20:43 ` [RFC PATCH v2 05/11] powerpc: gamecube/wii: declare as non-coherent platforms Albert Herranz
2009-11-28 20:43 ` [RFC PATCH v2 06/11] powerpc: gamecube/wii: do not include PCI support Albert Herranz
2009-11-28 20:43 ` [RFC PATCH v2 07/11] powerpc: gamecube/wii: udbg support for usbgecko Albert Herranz
2009-12-01 18:33 ` Segher Boessenkool
2009-11-28 20:43 ` [RFC PATCH v2 08/11] powerpc: gamecube/wii: early debugging using usbgecko Albert Herranz
2009-11-29 23:18 ` Benjamin Herrenschmidt
2009-11-30 5:50 ` Albert Herranz [this message]
2009-11-30 6:14 ` Benjamin Herrenschmidt
2009-11-30 6:28 ` Albert Herranz
2009-11-30 6:42 ` Benjamin Herrenschmidt
2009-11-30 6:15 ` Albert Herranz
2009-11-28 20:43 ` [RFC PATCH v2 09/11] powerpc: gamecube/wii: flipper interrupt controller support Albert Herranz
2009-11-29 23:21 ` Benjamin Herrenschmidt
2009-12-01 18:35 ` Segher Boessenkool
2009-12-01 19:48 ` Albert Herranz
2009-12-02 20:56 ` Benjamin Herrenschmidt
2009-12-02 23:29 ` Albert Herranz
2009-11-28 20:43 ` [RFC PATCH v2 10/11] powerpc: gamecube: platform support Albert Herranz
2009-11-28 20:43 ` [RFC PATCH v2 11/11] powerpc: gamecube: default config Albert Herranz
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=4B135D3D.9030006@yahoo.es \
--to=albert_herranz@yahoo.es \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.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).