From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [PATCH] arm: make FORCE_MAX_ZONEORDER configurable for TI AM33XX Date: Mon, 8 Oct 2012 13:55:52 -0700 Message-ID: <20121008205552.GC13011@atomide.com> References: <1341325242-17638-1-git-send-email-yegorslists@googlemail.com> <20120924171858.GG28835@atomide.com> <20120924231619.GA28941@n2100.arm.linux.org.uk> <20120925003758.GP28835@atomide.com> <506165CA.7070406@visionsystems.de> <20120925081449.GF31374@n2100.arm.linux.org.uk> <50616B21.3070909@visionsystems.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from mho-04-ewr.mailhop.org ([204.13.248.74]:54117 "EHLO mho-02-ewr.mailhop.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753963Ab2JHUz6 (ORCPT ); Mon, 8 Oct 2012 16:55:58 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Dejan =?utf-8?Q?Ga=C4=8Dnik?= Cc: yegor_sub1@visionsystems.de, Russell King - ARM Linux , Yegor Yefremov , linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org * Dejan Ga=C4=8Dnik [120927 07:13]: >=20 > I and my colleagues have developed a brand new very enhanced board ha= ving > AM35xx CPU, 512MB DDR2, DVI, true dual Ethernet support (not using PR= USS), > CAN, SPI, I2C, 7 USBs, etc=E2=80=A6Board is already materialized and = operational. >=20 >=20 > According to our board we have create new machine type in the kernel > (version: linux-3.2-psp04.06.00.07.sdk) and all other required stuff = to > support our board, modify some things, like adding support for dual e= th, > etc. Our goal is to provide this new board to the market (let say wit= h > large quantity) and therefore I am wondering how to start or if it is= even > possible to transfer our kernel change the main stream of this distro= ? > During this kernel modification process we have been looking to not > changing anything in kernel, what could affect other machine types. =46or the mainline kernel, you should go with device tree based booting to start with, we are no longer adding new board-*.c files. For older distro kernels you need to maintain a separate board-*.c file until we have moved everything to use device tree and distros are using that kernel. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Mon, 8 Oct 2012 13:55:52 -0700 Subject: [PATCH] arm: make FORCE_MAX_ZONEORDER configurable for TI AM33XX In-Reply-To: References: <1341325242-17638-1-git-send-email-yegorslists@googlemail.com> <20120924171858.GG28835@atomide.com> <20120924231619.GA28941@n2100.arm.linux.org.uk> <20120925003758.GP28835@atomide.com> <506165CA.7070406@visionsystems.de> <20120925081449.GF31374@n2100.arm.linux.org.uk> <50616B21.3070909@visionsystems.de> Message-ID: <20121008205552.GC13011@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Dejan Ga?nik [120927 07:13]: > > I and my colleagues have developed a brand new very enhanced board having > AM35xx CPU, 512MB DDR2, DVI, true dual Ethernet support (not using PRUSS), > CAN, SPI, I2C, 7 USBs, etc?Board is already materialized and operational. > > > According to our board we have create new machine type in the kernel > (version: linux-3.2-psp04.06.00.07.sdk) and all other required stuff to > support our board, modify some things, like adding support for dual eth, > etc. Our goal is to provide this new board to the market (let say with > large quantity) and therefore I am wondering how to start or if it is even > possible to transfer our kernel change the main stream of this distro? > During this kernel modification process we have been looking to not > changing anything in kernel, what could affect other machine types. For the mainline kernel, you should go with device tree based booting to start with, we are no longer adding new board-*.c files. For older distro kernels you need to maintain a separate board-*.c file until we have moved everything to use device tree and distros are using that kernel. Regards, Tony