From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brian Hutchinson Date: Thu, 21 Feb 2013 17:08:15 -0500 Subject: [U-Boot] [PATCH 05/10] am33xx: add ti814x specific register definitions In-Reply-To: <87ip5pk5qd.fsf@dell.be.48ers.dk> References: <1360766644-9901-1-git-send-email-mporter@ti.com> <1360766644-9901-6-git-send-email-mporter@ti.com> <87txpaofbi.fsf@dell.be.48ers.dk> <20130218151842.GC29026@bill-the-cat> <87ip5pk5qd.fsf@dell.be.48ers.dk> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de I need ti816x u-boot too! Maybe I can help too. Need 3.x kernel too but I guess that is for another list :) Regards, Brian On Feb 18, 2013 7:21 AM, "Peter Korsgaard" wrote: > > >>>>> "Tom" == Tom Rini writes: > > Hi, > > >> Quite some of the base addresses are similar, but I wonder if it > >> wouldn't be cleaner to simply have a hardware-am33xx.h / > >> hardware-ti814x.h instead of all these ifdef / elif? > > Tom> Since I suspect the things common from ti814x and am33xx are also common > Tom> to ti816x (which has been left as an exercise to whomever needs that > Tom> next), I think we can re-structure this into something like that, but > Tom> keeping the common parts within hardware.h still. > > FYI, I might very well be that guy as I've recently started work on a > ti816x based project. > > >> Argh! Couldn't we just swap the meaning of mmc1/mmc2 or would that be > >> too confusing? > > Tom> IMHO, that will lead to further confusion down the line. I talked with > Tom> Matt about this before and well, it's funky. > > Ok. > > -- > Bye, Peter Korsgaard > _______________________________________________ > U-Boot mailing list > U-Boot at lists.denx.de > http://lists.denx.de/mailman/listinfo/u-boot