From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: Can i submit B&N Nook Color generic kernel support patches? Date: Mon, 18 Apr 2011 15:25:57 +0300 Message-ID: <20110418122557.GM12272@atomide.com> References: <874o683jeo.fsf@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:21425 "EHLO mho-02-ewr.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752384Ab1DRMZ7 (ORCPT ); Mon, 18 Apr 2011 08:25:59 -0400 Content-Disposition: inline In-Reply-To: <874o683jeo.fsf@ti.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Kevin Hilman Cc: Abimanyu Gottumukkala , linux-omap@vger.kernel.org * Kevin Hilman [110408 17:27]: > Hello, > > Abimanyu Gottumukkala writes: > > > I am working on porting B&N Nook color source to generic kernel (non > > Android). Can i submit my ported code to omap-linux git? > > Absolutely! > > Support for new platforms is always welcome. This platform is based on > the OMAP36xx (3621 I think), so you might look at other 36xx-based > platforms (like Zoom3) as a starting point for your platform support. > > It will also be good to be familiar with the differences between a 3621 > and a 3630 and use OMAP features so any differences in the parts can be > determined at runtime (see omap_has_* in for example.) Adding support for new machines adds only a few tens of lines of code in most cases, so that should not be a problem from code consolidation point of view. Regards, Tony