From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ecos-discuss-return-38764-listarch-ecos-discuss=sources.redhat.com@ecos.sourceware.org>
Received: (qmail 3016 invoked by alias); 13 Sep 2007 21:03:58 -0000
Received: (qmail 3006 invoked by uid 22791); 13 Sep 2007 21:03:58 -0000
X-Spam-Check-By: sourceware.org
Received: from londo.lunn.ch (HELO londo.lunn.ch) (80.238.139.98)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 13 Sep 2007 21:03:52 +0000
Received: from lunn by londo.lunn.ch with local (Exim 3.36 #1 (Debian)) 	id 1IVvqg-0006Q5-00; Thu, 13 Sep 2007 23:03:42 +0200
Date: Thu, 13 Sep 2007 21:03:00 -0000
From: Andrew Lunn <andrew@lunn.ch>
To: Scott Moore <smoore@powerfile.com>
Cc: Ecos-Discuss <ecos-discuss@ecos.sourceware.org>, 	Steve Gaskill <sgaskill@powerfile.com>
Message-ID: <20070913210342.GD16874@lunn.ch>
Mail-Followup-To: Scott Moore <smoore@powerfile.com>, 	Ecos-Discuss <ecos-discuss@ecos.sourceware.org>, 	Steve Gaskill <sgaskill@powerfile.com>
References: <006a01c7f63e$3d31d630$b7958290$@net> <BC0348D2176B4C4EA0CBB50AEFDBD9670B5E6719@MI8NYCMAIL14.Mi8.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BC0348D2176B4C4EA0CBB50AEFDBD9670B5E6719@MI8NYCMAIL14.Mi8.com>
User-Agent: Mutt/1.5.16 (2007-06-11)
X-IsSubscribed: yes
Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <ecos-discuss.ecos.sourceware.org>
List-Subscribe: <mailto:ecos-discuss-subscribe@ecos.sourceware.org>
List-Archive: <http://ecos.sourceware.org/ml/ecos-discuss/>
List-Post: <mailto:ecos-discuss@ecos.sourceware.org>
List-Help: <mailto:ecos-discuss-help@ecos.sourceware.org>, <http://ecos.sourceware.org/ml/#faqs>
Sender: ecos-discuss-owner@ecos.sourceware.org
Subject: Re: [ECOS] Question on serial ports
X-SW-Source: 2007-09/txt/msg00082.txt.bz2

> 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