From: Piet Delaney <pdelaney@tensilica.com>
To: linux-kernel@vger.kernel.org
Cc: Johannes Weiner <jw@emlix.com>, Cord Seele <cs@emlix.com>,
Oskar Schirmer <os@emlix.com>, Daniel Gloeckner <dg@emlix.com>,
Piet Delaney <piet@tensilica.com>,
Marc Gauthier <marc@tensilica.com>,
Maxim Grigoriev <maxim@tensilica.com>,
Dan Nicolaescu <dann@tensilica.com>,
Chris Zankel <chris@zankel.net>,
Bill Huffman <huffman@tensilica.com>,
Ross Morley <ross@tensilica.com>
Subject: Re: [patch 0/8] xtensa: s6000 & s6105
Date: Wed, 11 Mar 2009 17:44:45 -0700 [thread overview]
Message-ID: <49B85AFD.1050200@tensilica.com> (raw)
In-Reply-To: <E1Lh1cN-0005rH-9t@cmpxchg.org>
Johannes Weiner wrote:
> Hi,
>
> here is the core series of our s6000 port.
>
> First comes the nommu patch. Right now we use CONFIG_MMU for
> everything that separates the S6000 from existing ports, memorywise.
> This is a lot easier and can still be broken up by newer ports when
> they have requirements with finer granularity. Furthermore, we have
> only this one nommu box here, so we couldn't test an MMU architecture
> and therefor not say for sure we didn't break anything ;)
Perhaps you have a pointer to a git repository with your changes
that I can clone from.
I can make sure the LX60 and LX200 didn't break. We have a
number of bug fixes and new support for SMP and a new MMU
that we expect to ready for prime time soon. I'd prefer to
use git to test your changes and doing the merge.
How about I add accounts for you, Oskar, and Daniel and
we use the repo(s) as a staging site to test each other's changes
before passing them upstream to Christian and Linus.
It you don't have an external Git repository you could just
ftp a copy and we can add it easily.
-piet
>
> Then comes the core variant stuff. We are the first variant that
> needs to ship code files, so there is a prereq patch that allows that.
>
> The inclusion of the GPIO driver is a bit arbitrary. It was the only
> one left after stripping out all real peripheral support because we
> initially used GPIO in platform_setup(). I send it now to have an
> example on variant-specific code and conceptual improvements can then
> be excercised on it.
>
> The platform patch is fairly trivial. One more requirement is that
> our platform can define the kernel text offset. We can not use a
> fixed virtual address (nommu, remember? ;)) but have to provide a
> physical one that is within bounds of our actual RAM.
>
> The diffstat looks a bit overwhelming, but note that most of it is the
> defconfig, the tensilica core definitions and address definitions
> where the core has registers mapped.
>
> Hannes
>
> arch/xtensa/Kconfig | 15 +
> arch/xtensa/Makefile | 5 +
> arch/xtensa/configs/s6105_defconfig | 530 ++++++++++++++++++++
> arch/xtensa/include/asm/cacheflush.h | 10 +-
> arch/xtensa/include/asm/dma.h | 3 +-
> arch/xtensa/include/asm/gpio.h | 56 ++
> arch/xtensa/include/asm/io.h | 9 +-
> arch/xtensa/include/asm/irq.h | 7 +
> arch/xtensa/include/asm/mmu.h | 5 +
> arch/xtensa/include/asm/mmu_context.h | 5 +
> arch/xtensa/include/asm/nommu.h | 3 +
> arch/xtensa/include/asm/nommu_context.h | 25 +
> arch/xtensa/include/asm/page.h | 9 +-
> arch/xtensa/include/asm/pgtable.h | 13 +-
> arch/xtensa/include/asm/processor.h | 6 +
> arch/xtensa/kernel/entry.S | 3 +-
> arch/xtensa/kernel/head.S | 3 +-
> arch/xtensa/kernel/irq.c | 14 +
> arch/xtensa/kernel/setup.c | 7 +
> arch/xtensa/kernel/traps.c | 2 +
> arch/xtensa/kernel/vectors.S | 4 +
> arch/xtensa/kernel/vmlinux.lds.S | 3 +
> arch/xtensa/mm/Makefile | 3 +-
> arch/xtensa/mm/init.c | 62 +---
> arch/xtensa/mm/misc.S | 2 +
> arch/xtensa/mm/mmu.c | 70 +++
> arch/xtensa/platforms/s6105/Makefile | 3 +
> arch/xtensa/platforms/s6105/device.c | 67 +++
> .../xtensa/platforms/s6105/include/platform/gpio.h | 27 +
> .../platforms/s6105/include/platform/hardware.h | 11 +
> .../platforms/s6105/include/platform/serial.h | 8 +
> arch/xtensa/platforms/s6105/setup.c | 61 +++
> arch/xtensa/variants/dc232b/Makefile | 1 +
> arch/xtensa/variants/fsf/Makefile | 1 +
> arch/xtensa/variants/s6000/Makefile | 3 +
> arch/xtensa/variants/s6000/gpio.c | 71 +++
> arch/xtensa/variants/s6000/include/variant/core.h | 431 ++++++++++++++++
> .../variants/s6000/include/variant/hardware.h | 259 ++++++++++
> arch/xtensa/variants/s6000/include/variant/irq.h | 9 +
> .../variants/s6000/include/variant/tie-asm.h | 304 +++++++++++
> arch/xtensa/variants/s6000/include/variant/tie.h | 191 +++++++
> arch/xtensa/variants/s6000/irq.c | 74 +++
> 42 files changed, 2320 insertions(+), 75 deletions(-)
>
next prev parent reply other threads:[~2009-03-12 0:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 13:03 [patch 0/8] xtensa: s6000 & s6105 Johannes Weiner
2009-03-12 0:44 ` Piet Delaney [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-10 13:11 Johannes Weiner
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=49B85AFD.1050200@tensilica.com \
--to=pdelaney@tensilica.com \
--cc=chris@zankel.net \
--cc=cs@emlix.com \
--cc=dann@tensilica.com \
--cc=dg@emlix.com \
--cc=huffman@tensilica.com \
--cc=jw@emlix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@tensilica.com \
--cc=maxim@tensilica.com \
--cc=os@emlix.com \
--cc=piet@tensilica.com \
--cc=ross@tensilica.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