Kernel 2.6.11 SERIAL_PORT_DFNS broken in MPC8540_ADS
Ahh, this is because we dont build the boot code for 85xx. Since the=20 only bootloader I'm aware of is u-boot, we do the following:
$ make uImage
- kumar
Quoted 10 lines · Clemens Koller
Hello, Kumar,
I guess you are the right person to help me with the MPC85xx devices
and platforms.
Maybe you remember that I use a MPC8540 on the Board from Microsys. (www.microsys.de).The Problem: 2.6.11 (as well as 2.6.11-rc4) breaks due to a
missingSERIAL_PORT_DFNSformpc8540_adsin ns16550:
Quoted 8 lines
root@ecam:/share/kernel/linux$ make =A0=A0 CHK=A0=A0=A0=A0 include/linux/version.h make[1]: `arch/ppc/kernel/asm-offsets.s' is up to date. =A0=A0 CHK=A0=A0=A0=A0 include/linux/compile.h =A0=A0 CHK=A0=A0=A0=A0 usr/initramfs_list make[1]: `arch/ppc/boot/images/uImage' is up to date. =A0=A0 CC=A0=A0=A0=A0=A0 arch/ppc/boot/common/ns16550.o arch/ppc/boot/common/ns16550.c:20: error: `SERIAL_PORT_DFNS' =
undeclared
Quoted 46 lines
here (not in a function)
arch/ppc/boot/common/ns16550.c:20: error: initializer element is not
constant
arch/ppc/boot/common/ns16550.c:20: error: (near initialization for `rs_table[0]')
make[2]: *** [arch/ppc/boot/common/ns16550.o] Error 1 make[1]: *** [arch/ppc/boot/common] Error 2
make: *** [zImage] Error 2Well, I see that you try to get rid of the mess... but I still
didn't understand all your changes and the different flavors of the platforms. (Uses the SBC8560 non-std. serial ports on external interrupts? But all the others are 'normal'MPC85xx_DUARTtypes?)
STD_SERIAL_PORT_DFNSare also missing... so, how can I tell that
I want to use the same as I did in 2.6.10? Can I useSTD_UART_OP?
Or is it deprecated to use an extra define if I don't have any
special non std. hardware.What is the best way for me to integrate my board (which will be used
in another system with some more PCI devices not part of the Microsys platform) into your platform / device structures?Currently, only minor changes were necessary to get 2.6.10 mpc8540ads
working with my board. I needed to change only
the PHY addresses (ids) on the FECs)
and the PCI Interrupt routing (IDSEL -> IRQ ABCD)
as they are wired up slightly different.Best greets,
Clemens Koller
_______________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Str. 45/1
81379 Muenchen
Germanyhttp://www.anagramm.de
Phone: +49-89-741518-50
Fax: +49-89-741518-19