From mboxrd@z Thu Jan 1 00:00:00 1970 From: Albert ARIBAUD Date: Wed, 07 Mar 2012 10:37:28 +0100 Subject: [U-Boot] i.MX6: mx6qsabrelite: allow use with Freescale 2.6.38 kernels In-Reply-To: <20120304083919.6FE8E1275653@gemini.denx.de> References: <1330728909-12203-1-git-send-email-eric.nelson@boundarydevices.com> <20120302232545.464F212A7F30@gemini.denx.de> <4F51BBA9.4090608@googlemail.com> <20120303093826.C3054126F3B0@gemini.denx.de> <4F52015A.2080003@googlemail.com> <20120303133050.690AA82301@gemini.denx.de> <4F52C327.3080309@boundarydevices.com> <20120304083919.6FE8E1275653@gemini.denx.de> Message-ID: <4F572C58.6080400@aribaud.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Wolfgang, Le 04/03/2012 09:39, Wolfgang Denk a ?crit : > Dear Troy Kisky, > > In message<4F52C327.3080309@boundarydevices.com> you wrote: >> >>>> And which changes 'introduce forward incompatibilities', and what are >>>> these incompatibilities? >>> See the recent problems that occurred when RMK decided to "clean up" >>> the machids file. >>> >> Would you rather that I take RMK's cleaned up file, and undelete the >> machines that u-boot >> uses? That would be more simple than adding to the board's config file. >> I can delete all of the mach_is_xxx macros in mach-types while I'm at it. > > I think we had this discussion before (when RMK's changes hit us), and > it was decided not to do this. IIRC we decided not to do this. YRC. :) The retained strategy is to not fiddle with the Linux mach-type.h and to complement (and lampshade) any discrepancy between Linux and U-Boot support in the board config files. > I have never understood why this mach_types thingy was needed (other > rchitectures worked fine without it, or better), and now we are on the > edge of obsoleting it. So all efforts trying to maintain this file are > futile, and we would have to redo these for any updates of the file. > > I feel this is not a good investment of our time. Hopefully FDT will make mach-types obsolete, except for the rare boards which will want to keep support for it, at which point we'll decide to either maintain or own, reduced and mostly legacy, mach-type file, or to move mach-type declarations in the board's config files. > Best regards, > > Wolfgang Denk Amicalement, -- Albert.