From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Simek Subject: Re: microblaze syscall list Date: Fri, 02 May 2008 10:18:25 +0200 Message-ID: <481ACE51.80202@seznam.cz> References: <87a5b0800804220513t75690ceao938a288596b5ad0c@mail.gmail.com> <48151726.9000204@itee.uq.edu.au> <200804281431.26570.arnd@arndb.de> <200805012117.12991.arnd@arndb.de> <481AA8CC.10405@petalogix.com> Reply-To: monstr@seznam.cz Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <481AA8CC.10405@petalogix.com> Sender: linux-kernel-owner@vger.kernel.org To: John Williams Cc: Arnd Bergmann , Matthew Wilcox , Will Newton , Linux Kernel list , linux-arch@vger.kernel.org, git@xilinx.com, Stephen Neuendorffer , John Linn List-Id: linux-arch.vger.kernel.org Hi All, >>> How about this strategy then: >>> * Change all the data types and syscall numbers in the -for-2.6.27 >>> branch to only include the minimal set, and a modern ABI >>> * Add the old interfaces as an out-of-tree patch that adds source >>> level compatibility with the old libc, but does not modify any >>> of the new interfaces, so that a patched kernel can run all binaries >>> built for the upstream version. >>> * phase out the old source interface gradually, as all users update >>> their libc source code. >> >> >> Any news on this from the microblaze people? Have you made up your mind >> on what route you want to go? > > I think we're still digesting it. I need to sync up with Michal and the > Xilinx people. The libc and kernel API changes have to happen in > tandem, otherwise Michal can't properly test the kernel he's pushing. > > I am the defacto MicroBlaze uClibc and toolchain "builder" but somewhat > reluctantly - am trying to convince Xilnx to hand that over to someone > who is expert at it. > > Michal, John L, any thoughts? > > John I am convinced we need to change syscall table. I don't want to maintain old syscalls. It will be easier to test smaller amount of syscalls. I would like to talk about with you (John W) via Skype. (Can you send me private email where you have time?) I talked with Steve about this week. After that I will publish our proposed way. Michal From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.wifiinternet.cz ([89.31.47.1]:54189 "EHLO bor.wifiinternet.cz" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1757493AbYEBIqs (ORCPT ); Fri, 2 May 2008 04:46:48 -0400 Message-ID: <481ACE51.80202@seznam.cz> Date: Fri, 02 May 2008 10:18:25 +0200 From: Michal Simek Reply-To: monstr@seznam.cz MIME-Version: 1.0 Subject: Re: microblaze syscall list References: <87a5b0800804220513t75690ceao938a288596b5ad0c@mail.gmail.com> <48151726.9000204@itee.uq.edu.au> <200804281431.26570.arnd@arndb.de> <200805012117.12991.arnd@arndb.de> <481AA8CC.10405@petalogix.com> In-Reply-To: <481AA8CC.10405@petalogix.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-arch-owner@vger.kernel.org List-ID: To: John Williams Cc: Arnd Bergmann , Matthew Wilcox , Will Newton , Linux Kernel list , linux-arch@vger.kernel.org, git@xilinx.com, Stephen Neuendorffer , John Linn Message-ID: <20080502081825.x6uP7fldR4vsw5ezER6UkfbFmFoh8ZlD7YcsrwxmAWY@z> Hi All, >>> How about this strategy then: >>> * Change all the data types and syscall numbers in the -for-2.6.27 >>> branch to only include the minimal set, and a modern ABI >>> * Add the old interfaces as an out-of-tree patch that adds source >>> level compatibility with the old libc, but does not modify any >>> of the new interfaces, so that a patched kernel can run all binaries >>> built for the upstream version. >>> * phase out the old source interface gradually, as all users update >>> their libc source code. >> >> >> Any news on this from the microblaze people? Have you made up your mind >> on what route you want to go? > > I think we're still digesting it. I need to sync up with Michal and the > Xilinx people. The libc and kernel API changes have to happen in > tandem, otherwise Michal can't properly test the kernel he's pushing. > > I am the defacto MicroBlaze uClibc and toolchain "builder" but somewhat > reluctantly - am trying to convince Xilnx to hand that over to someone > who is expert at it. > > Michal, John L, any thoughts? > > John I am convinced we need to change syscall table. I don't want to maintain old syscalls. It will be easier to test smaller amount of syscalls. I would like to talk about with you (John W) via Skype. (Can you send me private email where you have time?) I talked with Steve about this week. After that I will publish our proposed way. Michal