On Tue, Aug 25, 2009 at 8:25 AM, Stefan Roese wrote:
> On Tuesday 25 August 2009 07:54:57 Frederik Kriewitz wrote:
>> >> include/configs/devkit8000.h | 307 +
>> >> include/configs/omap3_devkit8000.h | 307 +++
On Tue, Aug 25, 2009 at 7:25 AM, Jean-Christophe
PLAGNIOL-VILLARD wrote:
> On 20:31 Mon 24 Aug , Frederik Kriewitz wrote:
>> This patch adds support for the DevKit8000 board.
>>
>>
>>
>> MAINTAINERS|4 +
>> MAKEALL
This patch adds support for the DevKit8000 board.
Signed-off-by: Frederik Kriewitz
---
mach-types.h needs to be synced (MACH_TYPE_DEVKIT8000)
Changelog:
v6:
added changelog
v5:
moved files from board/timll/devkit8000 to board/devkit8000
added omap3_ config file prefix
renamed README.timll
This patch adds support for the DevKit8000 board.
Signed-off-by: Frederik Kriewitz
---
mach-types.h needs to be synced (MACH_TYPE_DEVKIT8000)
---
---
MAINTAINERS|4 +
MAKEALL|1 +
Makefile |3 +
board
On Sun, Aug 23, 2009 at 6:02 PM, Dirk Behme wrote:
> Frederik Kriewitz wrote:
>>
>> This patch adds support for the DevKit8000 board.
>>
>> Signed-off-by: Frederik Kriewitz
>> ---
>> mach-types.h needs to be synced (MACH_TYPE_DEVKIT8000)
>> ---
&
This patch adds support for the DevKit8000 board.
Signed-off-by: Frederik Kriewitz
---
mach-types.h needs to be synced (MACH_TYPE_DEVKIT8000)
---
MAINTAINERS |4 +
MAKEALL |1 +
Makefile|3 +
board/timll
On Fri, Aug 21, 2009 at 7:59 PM, Wolfgang Denk wrote:
> In message 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 s
u, Aug 20, 2009 at 7:02 PM, Peter Tyser wrote:
> Hi Frederik,
> I had some minor aesthetic nitpicks. I'd change the title to "Add
> support for the DevKit8000 board".
Ok, I'll fix them.
Jean-Christophe asked me to move it out of the omap3 "vendor" d
This patch adds support for the DevKit8000 board.
Signed-off-by: Frederik Kriewitz
---
mach-types.h needs to be synced (MACH_TYPE_DEVKIT8000)
---
MAINTAINERS |4 +
MAKEALL |1 +
Makefile |3 +
board/devkit8000/Makefile
On Thu, Aug 20, 2009 at 12:19 AM, Jean-Christophe
PLAGNIOL-VILLARD wrote:
>> board/omap3/devkit8000/Makefile | 52 +
>> board/omap3/devkit8000/config.mk| 35
>> board/omap3/devkit8000/devkit8000.c | 124
>> board/omap3/devkit8000/devkit8000.h | 373
>> +
I'll fix that.
On Thu, Aug 20, 2009 at 12:19 AM, Jean-Christophe
PLAGNIOL-VILLARD wrote:
>> +void reset_phy(void)
>> +{
>> + eth_init(gd->bd);
>> +}
> NACK
> the net need to be init only when you use it
The kernel will try to use the already (temporally) programmed MAC address.
I always init
This patch adds support for the DevKit8000 board.
Signed-off-by: Frederik Kriewitz
---
mach-types.h needs to be synced (MACH_TYPE_DEVKIT8000)
---
MAINTAINERS |4 +
Makefile|3 +
board/omap3/devkit8000/Makefile | 52 +
board
On Mon, Aug 17, 2009 at 5:21 PM, Dirk Behme wrote:
> With the OMAP DIE_ID thread we know what you are doing here. But do we want
> to have this really in mainline? It looks to me like a workaround for broken
> hardware (that is, having no proper MAC address configured)? Or do I miss
> anything?
I'
Thank you for reviewing my patch.
I've fixed the issues and will submit it again once Jean-Christophe
updated the mach-types.h.
On Mon, Aug 17, 2009 at 11:50 AM, Wolfgang Denk wrote:
>> +#define CONFIG_SYS_MAX_FLASH_SECT 520 /* max number of sectors on */
>> +
This patch adds support for the DevKit8000 board.
Signed-off-by: Frederik Kriewitz
---
Makefile|3 +
board/omap3/devkit8000/Makefile | 51 +
board/omap3/devkit8000/config.mk| 34 +++
board/omap3/devkit8000/devkit8000.c | 117 +++
board
Hello,
I noticed that enabling CONFIG_CMDLINE_EDITING breaks CONFIG_SYS_CBSIZE.
Once CONFIG_CMDLINE_EDITING is enabled, it's not possible to enter
more than 256 characters (CONFIG_SYS_CBSIZE is ignored).
Probably related to
#define MAX_CMDBUF_SIZE 256
in common/main.c
I guess replacing M
On Sat, Aug 15, 2009 at 6:12 PM, Jean-Christophe
PLAGNIOL-VILLARD wrote:
>> I intent to use some bytes of the die id as MAC address. So I'm
>> interested in the bytes which change often.
> for private mac address or public?
>
> for public you may need to remember that you are supposed to trac all o
On Sat, Aug 15, 2009 at 4:35 PM, Jean-Christophe
PLAGNIOL-VILLARD wrote:
> Honnesty it's not really important the order except you have a special need
> it's really a personnal preference
I intent to use some bytes of the die id as MAC address. So I'm
interested in the bytes which change often.
__
I'm a bit confused about the u-boot code which reads the OMAP die id.
>From the OMAP TRM:
CONTROL.CONTROL_DIE_ID[127:0]
Address: 0x4830A218
Size: 128
u-boot code:
http://gitorious.org/u-boot-omap3/mainline/blobs/master/cpu/arm_cortexa8/omap3/sys_info.c#line44
result: Die ID #: 04ba0054 0020
19 matches
Mail list logo
