From: Andrew Lunn <andrew@lunn.ch>
To: jc.caquet@kerlink.fr
Cc: 'eCos discussion' <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] [Fwd: AT91SAM7S : cyg_io_write /dev/ser0]
Date: Fri, 07 Sep 2007 10:01:00 -0000 [thread overview]
Message-ID: <20070907100130.GL32192@lunn.ch> (raw)
In-Reply-To: <E1ITaXI-0005og-00@londo.lunn.ch>
> OK, when doing so I get the following result when building ecos library :
>
> packages/devs/serial/arm/at91/current/src/at91_serial.c:506: structure has
> no member named `data_xmt_req'
> packages/devs/serial/arm/at91/current/src/at91_serial.c: In function
> `at91_serial_DSR':
> packages/devs/serial/arm/at91/current/src/at91_serial.c:613: structure has
> no member named `data_rcv_req'
> /packages/devs/serial/arm/at91/current/src/at91_serial.c:624: structure has
> no member named `data_rcv_done'
> packages/devs/serial/arm/at91/current/src/at91_serial.c:647: structure has
> no member named `data_xmt_done'
> packages/devs/serial/arm/at91/current/src/at91_serial.c:652: structure has
> no member named `data_xmt_req'
>
> When CYGINT_IO_SERIAL_BLOCK_TRANSFER is not defined "_data_rcv_req,
> _data_rcv_done, _data_xmt_req, _data_xmt_done" are excluded from structure
> definition in serial.h.
> Do you think that some #if defined CYGINT_IO_SERIAL_BLOCK_TRANSFER are
> missing in at91_serial.c ?
It looks like it :-(
This is something to fix later.
I guess you will have to single step through the code and work out
what is happening....
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
prev parent reply other threads:[~2007-09-07 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 17:53 Jonathan Larmour
2007-09-06 18:02 ` Andrew Lunn
2007-09-07 9:53 ` jc.caquet
[not found] ` <E1ITaXI-0005og-00@londo.lunn.ch>
2007-09-07 10:01 ` Andrew Lunn [this message]
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=20070907100130.GL32192@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=jc.caquet@kerlink.fr \
/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).