From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] Adding support for DevKit8000
Date: Fri, 21 Aug 2009 15:00:33 +0200 [thread overview]
Message-ID: <4A8E9A71.7010103@googlemail.com> (raw)
In-Reply-To: <f67028d40908201137p509226f1vb3bd200e6f2203e9@mail.gmail.com>
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@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
next prev parent reply other threads:[~2009-08-21 13:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 16:47 [U-Boot] [PATCH v3] Adding support for DevKit8000 Frederik Kriewitz
2009-08-20 17:02 ` Peter Tyser
2009-08-20 17:28 ` Dirk Behme
2009-08-20 18:37 ` Frederik Kriewitz
2009-08-20 20:20 ` Jean-Christophe PLAGNIOL-VILLARD
2009-08-21 13:00 ` Dirk Behme [this message]
2009-08-21 14:34 ` Peter Tyser
2009-08-21 15:08 ` [U-Boot] Rules for board/* directory, was: " Dirk Behme
2009-08-21 15:22 ` Detlev Zundel
2009-08-21 15:41 ` Dirk Behme
2009-08-21 16:04 ` Detlev Zundel
2009-08-21 18:07 ` Wolfgang Denk
2009-08-21 17:59 ` Wolfgang Denk
2009-08-21 23:27 ` Frederik Kriewitz
2009-08-22 8:14 ` Wolfgang Denk
2009-08-21 15:28 ` Peter Tyser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A8E9A71.7010103@googlemail.com \
--to=dirk.behme@googlemail.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox