From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764530AbYEFJDf (ORCPT ); Tue, 6 May 2008 05:03:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1761500AbYEFIvd (ORCPT ); Tue, 6 May 2008 04:51:33 -0400 Received: from smtp1.wifiinternet.cz ([89.31.47.1]:51612 "EHLO bor.wifiinternet.cz" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1756489AbYEFIuu (ORCPT ); Tue, 6 May 2008 04:50:50 -0400 Message-ID: <48201C23.1040609@seznam.cz> Date: Tue, 06 May 2008 10:51:47 +0200 From: Michal Simek Reply-To: monstr@seznam.cz User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: John Williams CC: linux-kernel@vger.kernel.org, arnd@arndb.de, linux-arch@vger.kernel.org, stephen.neuendorffer@xilinx.com, John.Linn@xilinx.com, matthew@wil.cx, will.newton@gmail.com, drepper@redhat.com, microblaze-uclinux@itee.uq.edu.au, grant.likely@secretlab.ca, Michal Simek Subject: Re: [PATCH 02/56] microblaze_v2: Makefiles for Microblaze cpu References: <1209901305-6404-1-git-send-email-monstr@seznam.cz> <1209952030.5798.32.camel@localhost> In-Reply-To: <1209952030.5798.32.camel@localhost> Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi John, >> --- /dev/null >> +++ b/arch/microblaze/Makefile >> @@ -0,0 +1,63 @@ >> +UTS_SYSNAME = -DUTS_SYSNAME=\"uClinux\" >> + >> +# What CPU vesion are we building for, and crack it open >> +# as major.minor.rev >> +CPU_VER=$(subst ",,$(CONFIG_XILINX_MICROBLAZE0_HW_VER) ) >> +CPU_MAJOR=$(shell echo $(CPU_VER) | cut -d '.' -f 1) >> +CPU_MINOR=$(shell echo $(CPU_VER) | cut -d '.' -f 2) >> +CPU_REV=$(shell echo $(CPU_VER) | cut -d '.' -f 3) > > No doubt there's some cleaner shell-fu to do this but I'm not > complaining as I'm responsible for the original yucky version! I think you told me that toolchain can use this flags. This is not pain for now. I'll add to my future plans. >> --- /dev/null >> +++ b/arch/microblaze/platform/Makefile >> @@ -0,0 +1,3 @@ >> +# >> +# Makefile for arch/microblaze/platform directory >> +# > > How about a single > > obj-$(CONFIG_PLATFORM_GENERIC) += generic/ > > to show how platform-specific setup code can be added (even though > there's none in the default generic target)? We'll add this to Microblaze readme file. Chapter: how to add platform specific files. M