public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: daniel.neri@sigicom.se (Daniel Néri)
To: ecos-discuss@sources.redhat.com
Subject: [ECOS]  Re: Do any of the ARM LPCxxxx serial functions work?
Date: Mon, 24 Apr 2006 10:16:00 -0000	[thread overview]
Message-ID: <87wtdf6zzj.fsf@dual.hq.sigicom.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0604211608570.12142@pannier.canbike.ca>

Brett Delmage <Brett.Delmage@twobikes.ottawa.on.ca> writes:

> I wonder if anyone actually has interrupt-driven serial output
> working on any of the ARM Philips LPCxxxx based targets?
>
> I am not getting serial output to start. 
> The problem I see is in
> ser_16x5x.c pc_serial_start_xmit()

The "fix" mentioned in

  http://sourceware.org/ml/ecos-discuss/2005-05/msg00243.html

works for me on the LPC2292.


Regards,
-- 
Daniel Néri <daniel.neri@sigicom.se>
Sigicom AB, Stockholm, Sweden


-- 
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:[~2006-04-24 10:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-21 20:29 [ECOS] " Brett Delmage
2006-04-24 10:16 ` Daniel Néri [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=87wtdf6zzj.fsf@dual.hq.sigicom.net \
    --to=daniel.neri@sigicom.se \
    --cc=ecos-discuss@sources.redhat.com \
    /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).