From: Arnd Bergmann <arnd@arndb.de>
To: monstr@monstr.eu
Subject: Re: [PATCH 29/30] microblaze_mmu_v1: stat.h MMU update
Date: Thu, 30 Apr 2009 16:40:32 +0200
User-Agent: KMail/1.9.9
Cc: Christoph Hellwig <hch@infradead.org>, linux-kernel@vger.kernel.org,
       john.williams@petalogix.com
References: <1240821139-7247-23-git-send-email-monstr@monstr.eu> <200904301553.47556.arnd@arndb.de> <49F9B13C.3060008@monstr.eu>
In-Reply-To: <49F9B13C.3060008@monstr.eu>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200904301640.32769.arnd@arndb.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1482
Lines: 30

On Thursday 30 April 2009, Michal Simek wrote:

> 2. header cleanup -> some of them is pain because I have to recompile toolchain
> that's should be a big deal but after recompilation kernel, user apps I am getting some problems.

Yes, I understand that you have a circular dependency there, but fixing
the ABI can only become harder with time, as more people start using
the current kernel/toolchain combination.

> 3. syscall cleanup -> we still have old libc and I can't simple remove ancient syscalls

I had hoped that the way I set __ARCH_WANT_SYSCALL_* in the microblaze
unistd.h would provide an easy way to migrate, because this still defines
almost all traditional system calls (I haven't double-checked if some more
are currently used on microblaze, but they would be easy to add).
This means that as a first step, rebuilding the tool chain (as above) should
be sufficient and not require source-level changes to libc. From that point,
you can remove the remaining __ARCH_WANT_SYSCALL_* defintions one by one,
and change the libc accordingly.

I could also try building uclibc with the generic headers if I find the
time. Which version do you use, just upstream or do you have a private
libc tree with more changes?

	Arnd <><
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/