public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "wangwei" <wangw@start.com.cn>
To: <ecos-discuss@sources.redhat.com>
Subject: [ECOS] Fw: [ECOS] select err in ecos application
Date: Sun, 08 Jul 2001 18:31:00 -0000	[thread overview]
Message-ID: <003c01c10815$ec9e0940$592da8c0@start.com.cn> (raw)

and I had notice the changelog of kernel in cvs:

        * src/common/thread.cxx (Cyg_Thread::Cyg_Thread): Initialize
         wakeup_count

Does this change has some relative with this problem?

Best regard

                                           wangwei
----- Original Message -----
From: "wangwei" <wangw@start.com.cn>
To: <ecos-discuss@sources.redhat.com>
Sent: Sunday, July 08, 2001 4:55 PM
Subject: [ECOS] select err in ecos application


> Hi all:
>
> I'm making a application in ecos , which will drive 8 serial ports and
> tcp/ip.
> I use function "select" in my program .To improve speed , I use ISR of
> serial port
> to receive data , not DSR. So the functon "cyg_selwakeup" is called in ISR
.
>
> It runs normally at begining .   A while later, the thread of application
is
> blocked,
> maybe in select function and the program cann't get any data of serial
port
> from then on.
>
> At that time ,the ISR of serial port is still working perfectly.
> In gdb , I use another thread to break in, and use command "info thread"
to
> look at the state of all thread , the thread of serial application is
ready
> .But it doesn't work really.
>
> By the way , I had use the function "cyg_drv_isr_lock" instead of
> "cyg_drv_dsr_lock" in function "serial_read".
>
> Who can give me some advice .
> Thanks.
>

             reply	other threads:[~2001-07-08 18:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-08 18:31 wangwei [this message]
2001-07-09 15:12 ` Jonathan Larmour

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='003c01c10815$ec9e0940$592da8c0@start.com.cn' \
    --to=wangw@start.com.cn \
    --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).