From mboxrd@z Thu Jan 1 00:00:00 1970 From: Remco Poelstra Date: Tue, 17 Mar 2009 13:59:17 +0100 Subject: [U-Boot] Cleaning up new port In-Reply-To: <20090317121419.DD438832E8B7@gemini.denx.de> References: <49BF91D5.2030602@duran-audio.com> <20090317121419.DD438832E8B7@gemini.denx.de> Message-ID: <49BF9EA5.5040805@duran-audio.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Wolfgang Denk schreef: > In message <49BF91D5.2030602@duran-audio.com> you wrote: >> I've finished my port of U-boot 2008.10 to the LPC2468. I've based my >> port on code by Embedded Artists, which was based on U-boot 1.1.6. >> The LPC2468 is an ARM processor with build in peripherals, so I need to >> divide my code into LPC2468 generic part and a part for my board only >> (which is not to be published). I have however no clue on how to do > > Not pubslishing your code would be a stupid thing to do. Are you aware > how quickly out-of-mainline code rots? You are already two releases > behind against current mainline, and a lot of changes have already > been queued up in the "next" branch for the next release. I fully understand. The problem is that there is a special Ethernet PHY on the board which is under a NDA, so I cannot publish code surrounding it. I can publish the general part of the ethernet driver. > Try to forward port your stuff to the "next" branch (you will have to > do that to submit any patches), and then think again if it makes sense > for you to maintain an out-of-tree port. It doesn't. > >> that. What code should belong where? >> Is there any documentation on the exact code structure of U-boot? Is >> anyone here interested in LPC2468 support and willing to offer some help? > > Apply common sense. Then submit your patches. We will tell you if > they fit. Note that so far there is no LPC2468 support in U-Boot > mainline, so you must provide some complete working board port, or > there would be code which cannot even be compiled, and we don't allow > that. I see, I will provide a working example. Regards, Remco Poelstra