From: "Daniel Lidsten" <Daniel.Lidsten@combitechsystems.com>
To: "Gary D. Thomas" <gary.thomas@mind.be>
Cc: "eCos Discussion" <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] Problem with serial setup
Date: Tue, 13 May 2003 09:30:00 -0000 [thread overview]
Message-ID: <004B1D7A5257174C9044A1B7BD0E60EDA65D05@ratatosk.combitechsystems.com> (raw)
Hi,
> > I am trying to use the same serial port for both printf and
> > diag_printf but there seem to be some problem. Is there
> someone that
> > use the same port for both an interrupt driven serial driver and a
> > diag version at the same time?
> >
>
> Yes, I have done this successfully on the PowerPC (QUICC)
> hardware that you are using. Be sure and get up-to-date
> sources, as I fixed a bug in the HAL/QUICC serial serial
> drivers about a month ago.
I now have two serial channels (diag and printf) working on the same HW
port but when i want to change the diag to use SMC2 instead of SMC1 then
i hang in the quicc_smc1.c putc function because a BD flag indicates
busy:
while (bd->ctrl & QUICC_BD_CTL_Ready)
The only change i have done in ConfigTool is to change the "Diagnostic
Serial Port" from 0 to 1. Is there any other location that i need to
change to make this work?
Regards, Daniel
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next reply other threads:[~2003-05-13 9:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 9:30 Daniel Lidsten [this message]
2003-05-13 13:09 ` Gary D. Thomas
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 13:21 Daniel Lidsten
2003-05-13 13:27 ` Gary D. Thomas
2003-04-27 15:31 Daniel Lidsten
2003-05-01 2:03 ` Jonathan Larmour
2003-04-27 12:40 Daniel Lidsten
2003-04-27 14:39 ` Gary D. Thomas
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=004B1D7A5257174C9044A1B7BD0E60EDA65D05@ratatosk.combitechsystems.com \
--to=daniel.lidsten@combitechsystems.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=gary.thomas@mind.be \
/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).