This is the mail archive of the
ecos-discuss@sourceware.cygnus.com
mailing list for the eCos project.
Re: block transfer functions..
- To: "Jesper Skov" <jskov at redhat dot com>
- Subject: Re: [ECOS] block transfer functions..
- From: "Dave Airlie" <airlied at parthus dot com>
- Date: 3 Jul 2000 14:32:23 +0100
- Cc: ecos-discuss at sourceware dot cygnus dot com
Well I've used the attached patch as a cheat,
the reason I don't want to add CDL is that the driver is part of a
separate build process, that uses a completed eCos build, i.e. I build
eCos once and then just link my driver against it, I don't want to make
any changes to eCos outside of the CVS tree/public releases so that I can
just point people to the CVS tree...
Dave.
On 3 Jul 2000, Jesper Skov wrote:
> >>>>> "Dave" == Dave Airlie <airlied@parthus.com> writes:
>
> Dave> Hi, I've got a driver that I'm building separate to eCos and
> Dave> linking with a pre-built eCos image, however I want to use the
> Dave> SERIAL_BLOCK_TRANSFER, but I don't want to add CDL and stuff for
> Dave> my driver to eCos, but the .ecc doesn't let me say to include
> Dave> the files it just says
>
> Dave> cdl_interface CYGINT_IO_SERIAL_BLOCK_TRANSFER { # This value
> Dave> cannot be modified here. # Current_value: 0 };
>
> Dave> Where can I modify it without adding my driver to eCos and
> Dave> adding CDL?
>
> You can't.
>
> Out of interest, why don't you just write the CDL? It'll be a
> two-second job copying it from some other driver and renaming option +
> adding the implements CYGINT_IO_SERIAL_BLOCK_TRANSFER line.
>
> Jesper
>
--
David Airlie, Software Engineer, Parthus Technologies plc.,
Mary Rosse Centre, National Tech Park, Limerick, Ireland.
t: +353-61-508116 / f: +353-61-508101 / David.Airlie@parthus.com
--- io_serial.cdl.old Mon Jul 3 12:50:48 2000
+++ io_serial.cdl Mon Jul 3 12:50:55 2000
@@ -71,8 +71,9 @@
semantics from blocking to non-blocking."
}
- cdl_interface CYGINT_IO_SERIAL_BLOCK_TRANSFER {
+ cdl_option CYGINT_IO_SERIAL_BLOCK_TRANSFER {
display "Driver requires block transfer callback functions"
+ default_value 0
description "
Some low-level drivers can be optimized to transfer blocks
of data instead of a single character at a time. These usually