From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from down.free-electrons.com ([37.187.137.238] helo=mail.free-electrons.com) by bombadil.infradead.org with esmtp (Exim 4.80.1 #2 (Red Hat Linux)) id 1aunWY-0004W5-16 for linux-mtd@lists.infradead.org; Mon, 25 Apr 2016 20:54:31 +0000 Date: Mon, 25 Apr 2016 22:53:57 +0200 From: Boris Brezillon To: Tom Rini Cc: Scott Wood , Scott Wood , Marek Vasut , Thomas Petazzoni , Richard Weinberger , u-boot@lists.denx.de, "linux-sunxi@googlegroups.com" , "linux-mtd@lists.infradead.org" , Alexander Kaplan , Brian Norris Subject: Re: [U-Boot] Porting Linux's MTD/NAND changes into U-Boot Message-ID: <20160425225357.7bb6338d@bbrezillon> In-Reply-To: <20160425173646.GM3732@bill-the-cat> References: <20160425164314.15c3fc94@bbrezillon> <20160425173646.GM3732@bill-the-cat> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 25 Apr 2016 13:36:46 -0400 Tom Rini wrote: > On Mon, Apr 25, 2016 at 04:43:14PM +0200, Boris Brezillon wrote: > > > Hi Scott, > > > > I've recently contributed a lot of MTD/NAND related patches (and intend > > to continue doing so). Some of them are transversal changes touching the > > MTD and NAND framework internals, which implies patching all NAND > > drivers along with the core changes. > > > > All those changes are required to properly handle modern NANDs (MLC/TLC > > NANDs), and I need them to add proper NAND support to the sunxi > > platform (and more particularly to the C.H.I.P from NextThing Co.). > > > > So my question is, how should I port those changes to U-Boot? I see > > that your doing "synchronization commits", but in my case this mean > > including a bunch of driver specific changes into this "sync commit". > > > > I think it's also worth mentioning that I plan to heavily rework the > > Linux NAND framework to improve NAND performances on modern NAND > > controllers and clarify the NAND chip / NAND controller concepts, and > > other people are also working on merging the BBT code of the NAND and > > OneNAND framework. Which unfortunately means that we're not done porting > > invasive changes to U-Boot :-/. > > > > Any advice is welcome. > > I suppose my first suggestion would be to sync the kernel back into > U-Boot more frequently. With our bi-monthly release cycle it shouldn't > be too hard to pick a window to grab the current kernel release and > bring it over. I think the more stuff we let build up prior to syncing > the harder it will be. > Okay, so this means I should be the one back-porting Linux changes into U-Boot? I was planning on porting my current work on the sunxi NAND driver (including all the core dependencies) and submitting it to U-Boot, but honestly, I don't see how I can keep things in sync in the long run. From my experience, porting things to U-Boot is never as easy at it seems, and I don't think I'll have the time to maintain that by myself. Scott, what's your policy regarding Linux -> U-Boot syncs? Can I expect some help from your side? -- Boris Brezillon, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com