Dear Frederik Kriewitz,
In message f67028d40908211627v31668e61k859d431f3ecc...@mail.gmail.com you
wrote:
Ok, is there a official naming convention for the include/configs/*.h
files and the *_config targets? Should they be grouped by CPU/SoC
and/or vendor (Makefile/MAKEALL)?
There is no
Peter Tyser wrote:
Hi Dirk,
On Fri, 2009-08-21 at 15:00 +0200, Dirk Behme wrote:
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
Hi Dirk,
My understanding is that the board/ layout should be /board/board
vendor or board name/ So even though the Frederik's board has a
TI OMAP3 cpu, he shouldn't put it in board/ti or board/omap3 since
neither TI nor OMAP3 made the DevKit8000.
...
For example, there are
Hi Dirk,
Well actually (I think) we agreed on doing the board/vendor scheme. For
example look at board/amcc - there are all the AMCC evalboards basically
each one with a different SoC. Turning this around into board/soc
would throw pieces all over the places, which is definitely not what we
Dear Detlev Zundel,
In message m24os18a3w@ohwell.denx.de you wrote:
That being said, I think it
would make sense to put the devkit8000 in either board/devkit8000/ or
board/embedinfo/devkit8000 now as that is the correct place for it.
Well, I just can't see what the advantage of
Dear Dirk Behme,
In message 4a8ec01f.7040...@googlemail.com you wrote:
I could add the opposite example:
A vendor == TI OMAP3 based board (e.g. Beagle) has no adhesion with
a vendor == TI DaVinci board.
I tend to interpret this as poor board support by that vendor, then.
A vendor who
On Fri, Aug 21, 2009 at 7:59 PM, Wolfgang Denkw...@denx.de wrote:
In message m24os18a3w@ohwell.denx.de you wrote:
That being said, I think it
would make sense to put the devkit8000 in either board/devkit8000/ or
board/embedinfo/devkit8000 now as that is the correct place for it.
7 matches
Mail list logo
