From: "Scott Moore" <smoore@powerfile.com>
To: "Andrew Lunn" <andrew@lunn.ch>
Cc: "Ecos-Discuss" <ecos-discuss@ecos.sourceware.org>,
"Steve Gaskill" <sgaskill@powerfile.com>
Subject: RE: [ECOS] Question on serial ports
Date: Thu, 13 Sep 2007 21:12:00 -0000 [thread overview]
Message-ID: <BC0348D2176B4C4EA0CBB50AEFDBD9670B5E67E4@MI8NYCMAIL14.Mi8.com> (raw)
In-Reply-To: <20070913210342.GD16874@lunn.ch>
Thank you.
-----Original Message-----
From: Andrew Lunn [mailto:andrew@lunn.ch]
Sent: Thursday, September 13, 2007 2:04 PM
To: Scott Moore
Cc: Ecos-Discuss; Steve Gaskill
Subject: Re: [ECOS] Question on serial ports
> 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
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.762 / Virus Database: 510 - Release Date: 9/13/2004
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.762 / Virus Database: 510 - Release Date: 9/13/2004
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2007-09-13 21:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 19:40 [ECOS] dOUG lEE'S MALLOC Rick Davis
2007-09-13 20:32 ` [ECOS] Question on serial ports Scott Moore
2007-09-13 21:03 ` Andrew Lunn
2007-09-13 21:12 ` Scott Moore [this message]
2007-09-14 21:05 ` Scott Moore
2007-09-14 21:13 ` Andrew Lunn
2007-09-14 21:40 ` Scott Moore
2007-09-13 20:59 ` [ECOS] dOUG lEE'S MALLOC Andrew Lunn
2007-09-27 0:21 ` [ECOS] Doug Lea's malloc Rick Davis
2007-09-27 7:38 ` Johan Cederbom
2007-09-27 11:54 ` Rick Davis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BC0348D2176B4C4EA0CBB50AEFDBD9670B5E67E4@MI8NYCMAIL14.Mi8.com \
--to=smoore@powerfile.com \
--cc=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=sgaskill@powerfile.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).