[U-Boot] [PATCH v3] Adding support for DevKit8000
Dirk Behme
dirk.behme at googlemail.com
Fri Aug 21 15:00:33 CEST 2009
Frederik Kriewitz wrote:
> Jean-Christophe asked me to move it out of the omap3 "vendor" directory:
>
> On 10:55 Thu 20 Aug , Frederik Kriewitz wrote:
>> On Thu, Aug 20, 2009 at 12:19 AM, Jean-Christophe
>> PLAGNIOL-VILLARD<plagnioj at jcrosoft.com> wrote:
>>>> board/omap3/devkit8000/Makefile | 52 +++++
>>>> board/omap3/devkit8000/config.mk | 35 ++++
>>>> board/omap3/devkit8000/devkit8000.c | 124 ++++++++++++
>>>> board/omap3/devkit8000/devkit8000.h | 373 +++++++++++++++++++++++++++++++++++
>>> no need board are allow in board/omap3
>>> please create your own vendor dirent or just put it in board/
>> What do you mean with that?
> board/devkit8000/devkit8000.h
> or board/embedinfo/devkit8000/devkit8000.h
>
> I'm confused, where am I supposed to use omap3 and where not?
Yes, sometimes it can be confusing ;)
From earlier discussions I understood that Jean-Christophe doesn't like
board/omap3/
I'm not totally sure what he actually wants, but I think something like
board/ti/omap3
board/ti/omap2
board/ti/omap1
board/ti/davinci
etc. (e.g. like board/atmel).
While I don't care what we use, like with other discussions we should
do it consistent. That is, having already x boards in omap3 and now
adding the next board somewhere else isn't ok. As long as we don't
have the new directory layout, new boards should use the old one. If
we want an other directory layout, we should *first* move all existing
boards to the other directory (ideally doing this directly in git).
*Then* new patches can and have to use this new layout.
Conclusion: Until we don't have an other directory layout, I'm fine
with board/omap3/devkit8000
Best regards
Dirk
More information about the U-Boot
mailing list