From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jerry Van Baren Date: Fri, 25 May 2007 13:33:49 -0400 Subject: [U-Boot-Users] Imminent u-boot-fdt pull request In-Reply-To: <20070525121339.189729bb.kim.phillips@freescale.com> References: <46526C2E.3070100@gmail.com> <20070524222612.381a3587.kim.phillips@freescale.com> <4656AC13.2010300@grandegger.com> <20070525105833.3d1dbd0e.kim.phillips@freescale.com> <4657152D.7030606@smiths-aerospace.com> <20070525121339.189729bb.kim.phillips@freescale.com> Message-ID: <46571DFD.7080407@smiths-aerospace.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Kim Phillips wrote: > On Fri, 25 May 2007 12:56:13 -0400 > Jerry Van Baren wrote: [snip] > please do not ask Wolfgang to pull patches to files in mpc83xx and > related directories (cpu.c, board configs, etc.) from your tree; they > should go through the mpc83xx tree from now on. > > Kim In retrospect, that was impolite and I apologize for the crossover. :-( The 83xx changes were necessary to make the bootm using libfdt work (I have a 8360 board). If I don't push the necessary changes through u-boot-fdt, u-boot-fdt will be impossible to use until you add the necessary changes in the 83xx repo (and possibly vice versa). In addition, Wolfgang would have to coordinate his pulls into the main repo or it would break. The cross coupling is unfortunate, but we have to have one example of a CPU/board and libfdt coupled in order to test the libfdt changes. I would prefer to fix the problems noted (which really are not as bad as they look IMHO) to make one CPU+board+libfdt example work and push those changes to Wolfgang via the u-boot-fdt repo. If you are opposed to this, I can back out the 83xx changes and push just libfdt stuff to Wolfgang and supply you with the set of 83xx patches which you can push through your repo, but it will tough for others to use/test since they will get only half a picture from each repo. Best regards, gvb