Linux for ml310

DISCUSSION Grant Likely 1 participant 1 message Jan 9, 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): [email protected]

Grant Likely

author

2008-01-09 16:48 UTC #1 lore raw

always CC the mailing list when replying.

Quoted 11 lines · Joachim Meyer

arch/ppc/boot/common/ns16550.c:21: error: `XPAR_UARTNS550_0_CLOCK_FREQ_HZ' undeclared here (not in a function) arch/ppc/boot/common/ns16550.c:21: error: initializer element is not constant arch/ppc/boot/common/ns16550.c:21: error: (near initialization for rs_table[0].baud_base') arch/ppc/boot/common/ns16550.c:21: error: XPAR_INTC_0_UARTNS550_0_VEC_ID' undeclared here (not in a function) arch/ppc/boot/common/ns16550.c:21: error: initializer element is not constant arch/ppc/boot/common/ns16550.c:21: error: (near initialization for rs_table[0].irq') arch/ppc/boot/common/ns16550.c:21: error: XPAR_UARTNS550_0_BASEADDR' undeclared here (not in a function) arch/ppc/boot/common/ns16550.c:21: error: initializer element is not constant arch/ppc/boot/common/ns16550.c:21: error: (near initialization for rs_table[0].iomem_base') arch/ppc/boot/common/ns16550.c:21: error: initializer element is not constant arch/ppc/boot/common/ns16550.c:21: error: (near initialization for rs_table[0]'

You're xparameters_ml300.h file does not define XPAR_UARTNS550_0_CLOCK_FREQ_HZ', XPAR_INTC_0_UARTNS550_0_VEC_ID' and `XPAR_UARTNS550_0_BASEADDR'.

You'll need to look in your xparams file, find out what the real #defines are for the uart and add fixups to xparameter.h so ns16550 can find them.

You're almost there! :-)

Signature · 2 lines

Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.