This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Help with Interrupt driven Serial ports in EB40A
- From: "Gary Thomas" <gary at mlbassoc dot com>
- To: "Giri Raja" <giri_amf at yahoo dot com>
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Fri, 2 Apr 2004 23:02:25 -0700 (MST)
- Subject: Re: [ECOS] Help with Interrupt driven Serial ports in EB40A
- References: <20040402164443.30344.qmail@web41711.mail.yahoo.com>
Giri Raja said:
> Hi,
> I'm trying to write a small application, which
> would accept data from /dev/ttyS0 and convey it via a
> GDB session from /dev/ttyS1.
> I want the reception of data from /dev/ttyS0 to be
> interrupt driven. Should I then create a interrupt
> using cyg_drv_interrupt_create with the USART0
> interrupt vector? And should I also create my own ISR
> and DSR, then use the device handle to read and wirte?
> I'm confused because I saw an implementation of the
> serial drivers' ISR and DSR implementation in
> at91_serial.c located under
> ecos/packages/devs/serial/arm/at91/current/src
>
> Shall I just ignore it and just include
> <cyg/hal/drv_api.h> .
Why not just use the standard, interrupt driven, drivers?
It's easy to configure eCos to have one port available using
this driver and the other to use only debug I/O (e.g. GDB).
>
> Your response would be very helpful.
>
> Thank you in advance.
>
> Giri.
>
> p.s: This is a repost, I'm desperately seeking for
> help. Thank you for your patience.
This is a *voluntary* mailing list - folks answer if and when
they have the time and/or knowledge you seek. If you are
truly desperate, this is not the correct vehicle to use.
In that case, you'd be better off contracting for proper,
professional assistance.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss