public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: eCos discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] [Fwd: AT91SAM7S : cyg_io_write /dev/ser0]
Date: Thu, 06 Sep 2007 18:02:00 -0000	[thread overview]
Message-ID: <20070906180230.GL31456@lunn.ch> (raw)
In-Reply-To: <46E03E6E.1080409@jifvik.org>

On Thu, Sep 06, 2007 at 06:52:46PM +0100, Jonathan Larmour wrote:
> The attached mail was misaddressed....

> From: jc.caquet@kerlink.fr
> To: ecos-discuss-owner@ecos.sourceware.org
> Subject: AT91SAM7S : cyg_io_write /dev/ser0
> Date: Thu, 6 Sep 2007 18:58:50 +0200
> X-Spam-Status: No, score=4.3 required=5.0 tests=AWL,BAYES_99,
> 	MSGID_FROM_MTA_ID,NO_REAL_NAME autolearn=no version=3.0.4
> 
> Dear all,
> we use cyg_io_write on a serial device of AT91SAM7S board and when we try to
> send only 1 character cyg_io_write fails and returns -1 as a result code.
> Everything is OK as soon as we send more than 1 character, every character
> is always successfully output.
> Did anybody already face this problem??

AT91 is one of the two drivers which make use the block transfers in
the serial layer. So maybe you are seeing a bug in this code?

comment out the 

implements    CYGINT_IO_SERIAL_BLOCK_TRANSFER

in arm/at91/current/cdl/ser_arm_at91.cdl

and then do an 

ecosconfig tree ; make ;

so that it does not to block transfers. Do you still get the same
problem?

        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

  reply	other threads:[~2007-09-06 18:02 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 [this message]
2007-09-07  9:53   ` jc.caquet
     [not found]   ` <E1ITaXI-0005og-00@londo.lunn.ch>
2007-09-07 10:01     ` Andrew Lunn

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=20070906180230.GL31456@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).