From: John Linn <John.Linn@xilinx.com>
To: <microblaze-uclinux@itee.uq.edu.au>, <linux-kernel@vger.kernel.org>
Cc: <john.williams@petalogix.com>, <michal.simek@petalogix.com>
Subject: RE: [microblaze-uclinux] Microblaze MMU v2
Date: Fri, 29 May 2009 08:39:04 -0600 [thread overview]
Message-ID: <20090529143906.570B082804F@mail59-va3.bigfish.com> (raw)
In-Reply-To: <1243406874-3917-1-git-send-email-monstr@monstr.eu>
Acked-by: John Linn <john.linn@xilinx.com>
Looks like great progress,
John
> -----Original Message-----
> From: owner-microblaze-uclinux@lists.itee.uq.edu.au
[mailto:owner-microblaze-
> uclinux@lists.itee.uq.edu.au] On Behalf Of Michal Simek
> Sent: Wednesday, May 27, 2009 12:47 AM
> To: linux-kernel@vger.kernel.org
> Cc: john.williams@petalogix.com; microblaze-uclinux@itee.uq.edu.au;
michal.simek@petalogix.com
> Subject: [microblaze-uclinux] Microblaze MMU v2
>
> Hi All,
>
> This is bunch of patches for Microblaze MMU kernel support version 2.
> There is one problem(not functional) with uaccess.h which I know about
and I would like
> to fix it till rc2 with Arnd's new generic patches which I hope will
be there.
>
> All changes are available at
git://git.monstr.eu/linux-2.6-microblaze.git
> next branch.
>
> Version 1 is available at mmu_v1 branch.
>
> Changes in version 2.
> I added all reported problems - mmu_v1 branch contains separate
commits for that
> I fixed problems with stat.h and fcntl.h - there are prepared for Arnd
generic version.
>
> Thanks for your time and review.
>
> I believe that this is the last version for review in LKML.
>
> Thanks for your ACK,
> Michal
>
>
>
>
>
>
> ___________________________
> microblaze-uclinux mailing list
> microblaze-uclinux@itee.uq.edu.au
> Project Home Page :
http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive :
http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
>
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
next prev parent reply other threads:[~2009-05-29 14:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 6:47 Microblaze MMU v2 Michal Simek
2009-05-27 6:47 ` [PATCH 01/29] microblaze_mmu_v2: Add mmu_defconfig Michal Simek
2009-05-27 6:47 ` [PATCH 02/29] microblaze_mmu_v2: MMU update for startup code Michal Simek
2009-05-27 6:47 ` [PATCH 03/29] microblaze_mmu_v2: Alocate TLB for early console Michal Simek
2009-05-27 6:47 ` [PATCH 04/29] microblaze_mmu_v2: TLB low level code Michal Simek
2009-05-27 6:47 ` [PATCH 05/29] microblaze_mmu_v2: MMU initialization Michal Simek
2009-05-27 6:47 ` [PATCH 06/29] microblaze_mmu_v2: mmu.h update Michal Simek
2009-05-27 6:47 ` [PATCH 07/29] microblaze_mmu_v2: Page fault handling high level - fault.c Michal Simek
2009-05-27 6:47 ` [PATCH 08/29] microblaze_mmu_v2: Context handling - mmu_context.c/h Michal Simek
2009-05-27 6:47 ` [PATCH 09/29] microblaze_mmu_v2: Page table - ioremap - pgtable.c/h, section update Michal Simek
2009-05-27 6:47 ` [PATCH 10/29] microblaze_mmu_v2: io.h MMU update Michal Simek
2009-05-27 6:47 ` [PATCH 11/29] microblaze_mmu_v2: pgalloc.h and page.h Michal Simek
2009-05-27 6:47 ` [PATCH 12/29] microblaze_mmu_v2: Update process creation for MMU Michal Simek
2009-05-27 6:47 ` [PATCH 13/29] microblaze_mmu_v2: Update tlb.h and tlbflush.h Michal Simek
2009-05-27 6:47 ` [PATCH 14/29] microblaze_mmu_v2: MMU asm offset update Michal Simek
2009-05-27 6:47 ` [PATCH 15/29] microblaze_mmu_v2: Add CURRENT_TASK for entry.S Michal Simek
2009-05-27 6:47 ` [PATCH 16/29] microblaze_mmu_v2: entry.S, entry.h Michal Simek
2009-05-27 6:47 ` [PATCH 17/29] microblaze_mmu_v2: Update exception handling - MMU exception Michal Simek
2009-05-27 6:47 ` [PATCH 18/29] microblaze_mmu_v2: uaccess MMU update Michal Simek
2009-05-27 6:47 ` [PATCH 19/29] microblaze_mmu_v2: Add MMU related exceptions handling Michal Simek
2009-05-27 6:47 ` [PATCH 20/29] microblaze_mmu_v2: Update linker script for MMU Michal Simek
2009-05-27 6:47 ` [PATCH 21/29] microblaze_mmu_v2: Enable fork syscall for MMU and add fork as vfork for noMMU Michal Simek
2009-05-27 6:47 ` [PATCH 22/29] microblaze_mmu_v2: Traps MMU update Michal Simek
2009-05-27 6:47 ` [PATCH 23/29] microblaze_mmu_v2: Update signal returning address Michal Simek
2009-05-27 6:47 ` [PATCH 24/29] microblaze_mmu_v2: Update cacheflush.h Michal Simek
2009-05-27 6:47 ` [PATCH 25/29] microblaze_mmu_v2: Update dma.h for MMU Michal Simek
2009-05-27 6:47 ` [PATCH 26/29] microblaze_mmu_v2: Elf update Michal Simek
2009-05-27 6:47 ` [PATCH 27/29] microblaze_mmu_v2: stat.h MMU update Michal Simek
2009-05-27 6:47 ` [PATCH 28/29] microblaze_mmu_v2: Kconfig update Michal Simek
2009-05-27 6:47 ` [PATCH 29/29] microblaze_mmu_v2: Makefiles Michal Simek
2009-05-27 11:08 ` [PATCH 08/29] microblaze_mmu_v2: Context handling - mmu_context.c/h Arnd Bergmann
2009-05-27 11:59 ` Michal Simek
2009-05-29 14:39 ` John Linn [this message]
2009-06-11 8:46 ` Microblaze MMU v2 John Williams
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=20090529143906.570B082804F@mail59-va3.bigfish.com \
--to=john.linn@xilinx.com \
--cc=john.williams@petalogix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@petalogix.com \
--cc=microblaze-uclinux@itee.uq.edu.au \
/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