Re: [ECOS] Question on serial ports

[Andrew Lunn <andrew at lunn dot ch>]

> The questions are:
> 
> 1. Does this indeed indicate that a full (not diagnostic) serial port
> implementation was never completed for the MCB2100 board?
> 
> 2. What was the purpose of the directory 
> ../packages/devs/serial/arm/lpc2xxx/..? Was this just a placeholder for
> where a device might go?

Take a look at the targets which use this:

target p2106 {
        alias { "Olimex evaluation board LPC-P2106" p2106 }
        packages { CYGPKG_HAL_ARM
                   CYGPKG_HAL_ARM_LPC2XXX
                   CYGPKG_HAL_ARM_LPC2XXX_P2106
                   CYGPKG_IO_SERIAL_GENERIC_16X5X
                   CYGPKG_IO_SERIAL_ARM_LPC2XXX
                   CYGPKG_DEVICES_WATCHDOG_ARM_LPC2XXX
        }
        description "
        The p2106 target provides the packages needed to run eCos on the
        LPC-P2106 evaluation board from Olimex."
}

target lpcmt {
        alias { "Olimex evaluation board LPC-LPCMT" lpcmt }
        packages { CYGPKG_HAL_ARM
                   CYGPKG_HAL_ARM_LPC2XXX
                   CYGPKG_HAL_ARM_LPC2XXX_LPCMT
                   CYGPKG_IO_SERIAL_GENERIC_16X5X
                   CYGPKG_IO_SERIAL_ARM_LPC2XXX
                   CYGPKG_DEVICES_WATCHDOG_ARM_LPC2XXX
        }
        description "
        The lpcmt target provides the packages needed to run eCos on the
        LPC-LPCMT evaluation board from Olimex."
}

Looking at this suggests that the LPC2XXX serial driver is just what
is needed to make the generic 16x5x serial driver work on LPC
targets. Take a closer look at one of the these targets and all should
become clear...

       Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss