public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Scott Moore" <smoore@powerfile.com>
To: "Ecos-Discuss" <ecos-discuss@ecos.sourceware.org>,
		"Steve Gaskill" <sgaskill@powerfile.com>
Subject: [ECOS] Question on serial ports
Date: Thu, 13 Sep 2007 20:32:00 -0000	[thread overview]
Message-ID: <BC0348D2176B4C4EA0CBB50AEFDBD9670B5E6719@MI8NYCMAIL14.Mi8.com> (raw)
In-Reply-To: <006a01c7f63e$3d31d630$b7958290$@net>

 
Hi, I am working with a Keil MCB2300 board. I had a question on serial port
implementations.

Our installation was derived from the ARM/MCB2100 board which comes with
ECOS, using the lpc2xxx structures.

Included with the standard build is the diagnostic port haldiag, which is
layered as ttydiag. The hal for the board includes code to access both
ports, 0 and 1 on the board. However, the code does not appear to support
more than a single port at the device level. The code does not appear
to support interrupts, and uses the SERIAL_CHANNEL macro as opposed to
the SERIAL_CHANNEL_USING_INTERRUPTS macro. Basically it appears that
this installation was only designed to support a single diagnostics
serial port which doubles as a GDB access port.

under /packages/devs/serial, there is a directory for arm/lpc2xxx, but
it contains the single file arm_lpc2xxx_ser.inl, which appears to just
contain the headers for a possible driver. The functions defined in this
file don't appear to go anywhere, for example "pc_serial_init", etc.

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?

Thank you,

Scott Moore
Powerfile

---
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

  reply	other threads:[~2007-09-13 20:32 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 ` Scott Moore [this message]
2007-09-13 21:03   ` [ECOS] Question on serial ports Andrew Lunn
2007-09-13 21:12     ` Scott Moore
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=BC0348D2176B4C4EA0CBB50AEFDBD9670B5E6719@MI8NYCMAIL14.Mi8.com \
    --to=smoore@powerfile.com \
    --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).