From: Peter Tyser Date: Thu, 15 Apr 2010 17:44:22 -0500 Subject: [U-Boot] [STATUS] Heads-up: Reorganize directory structure In-Reply-To: <20100415175845.GA2680@morgana.gnudd.com> References: <1271347099.6519.18.camel@localhost.localdomain> <20100415152247.3891BEEE8D9@gemini.denx.de> <20100413092323.44D8719F60@gemini.denx.de> <4BC6BAD2.8040908@monstr.eu> <20100415075232.77202EEE8D8@gemini.denx.de> <1271343853.6519.6.camel@localhost.localdomain> <20100415153127.GA628@morgana.gnudd.com> <20100415175845.GA2680@morgana.gnudd.com> Message-ID: <1271371462.6519.298.camel@localhost.localdomain> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Alessandro, > > How does putting boards in their appropriate CPU directory make > > your coding any easier? > > Because if all boars with the same SoC are in the same directory they > can share source files. But boards don't need to be in the same directory to share the same source files. You could pull out common code to arch/arm/cpu/* or arch/arm/lib right now if you wanted, but that is the case whether the board directories were in board/... or arch/.... > In my example, st/nhk8815 and calao/usb-s8815 > had several files replicated -- so Wolfgang rejected the patch. But > in a vendor-based structure I won't merge in a single board dir boards > from two different vendors. Same will happen for dave/zefeer where a > lot is in commong with edb93xx. Could you give a specific example of how you'd like to final directory/file structure to look like? eg where would the code common to the nhk8815 and usb-s8815 be located? What would the file(s) be named? And how would the issue of vendors like Freescale which support multiple architectures and share code between them be supported? > thanks for your patience Likewise:) Peter