This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Porting ecos to a custom board.
- From: Andrew Lunn <andrew at lunn dot ch>
- To: Asim Jamshed <asim dot jamshed at gmail dot com>
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Mon, 30 Jan 2006 12:06:57 +0100
- Subject: Re: [ECOS] Porting ecos to a custom board.
- References: <ef0b5f230601300258u1291018fq7eed7672189b9a9c@mail.gmail.com>
On Mon, Jan 30, 2006 at 03:58:52PM +0500, Asim Jamshed wrote:
> Hi,
>
> I have a custom MIPS324kc board on which I am porting eCos. Right now,
> I am stuck in the serial device driver(16550) porting process. I
> followed the way in which the source code for Atlas MIPS324kc board is
> placed in the directories but I am still not sure why the serial
> device driver source code is placed in
> packages/hal/mips/atlas/v_2.0/src/ and
> packages/devs/serial/mips/atlas/v2_0/src/ directories separately. Any
> form of assistance is appreciated. Is there any good guide I should
> follow. Thanks,
eCos has two serial device drivers for each board. The one in the hal
directory is a very simple polled IO, real time unfrendly, version
which is used for debugging. All diag_printf() output uses this driver
and also communcation to gdb.
The driver in dev/serial is a full driver, interupt driver, flow
control etc. This is a high performance, real time friendly driver.
You must have a HAL serial driver, but the full serial driver is
optional and you only need it if your application wants to make use of
the serial ports.
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