Skip to contentSkip to conversation

U-boot-1.3.2-rc2 Error when Building with CONFIG_FIT and CONFIG_LOGBUFFER

U-Boot-Users Grant Erickson 2 participants 2 messages May 2, 2008 – May 5, 2008 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): C440A98E.EF7D%[email protected]

#1 lore raw

I am attempting to use CONFIG_FIT in u-boot-1.3.3-rc2 on the AMCC Kilauea board and, when used in conjunction with CONFIG_LOGBUFFER get the following compilation errors in common/cmd_bootm.c:

cmd_bootm.c: In function 'fit_check_kernel':
cmd_bootm.c:438: error: 'kbd' undeclared (first use in this function) cmd_bootm.c:438: error: (Each undeclared identifier is reported only once cmd_bootm.c:438: error: for each function it appears in.) cmd_bootm.c:440: error: 'initrd_high' undeclared (first use in this function)
cmd_bootm.c:440: error: 'LOGBUFF_LEN' undeclared (first use in this function)
cmd_bootm.c:440: error: 'LOGBUFF_OVERHEAD' undeclared (first use in this function)

Are these known/expected errors? Looking at the source, it seems like this got patched into the wrong place or is missing part of the patch.

Regards,

Grant Erickson

#2 lore raw
Quoted 15 lines · Grant Erickson

I am attempting to use CONFIG_FIT in u-boot-1.3.3-rc2 on the AMCC Kilauea board and, when used in conjunction with CONFIG_LOGBUFFER get the following compilation errors in common/cmd_bootm.c:

cmd_bootm.c: In function 'fit_check_kernel':
cmd_bootm.c:438: error: 'kbd' undeclared (first use in this function) cmd_bootm.c:438: error: (Each undeclared identifier is reported only once cmd_bootm.c:438: error: for each function it appears in.) cmd_bootm.c:440: error: 'initrd_high' undeclared (first use in this function)
cmd_bootm.c:440: error: 'LOGBUFF_LEN' undeclared (first use in this function)
cmd_bootm.c:440: error: 'LOGBUFF_OVERHEAD' undeclared (first use in this function)

Quoted 2 lines

Are these known/expected errors? Looking at the source, it seems like this got patched into the wrong place or is missing part of the patch.

Hello Grant,

This seems to be a bug, we're looking into it and will get back with more details/fix in a day of two.

Regards,
Bartlomiej