[ECOS] FW: [ECOS] FW: [ECOS] ecos-discuss@ecos.sourceware.org

[ECOS] FW: [ECOS] FW: [ECOS] ecos-discuss@ecos.sourceware.org

[Yong Chen Tan]

> Date: Fri, 27 Jun 2008 11:01:38 +0200
> From: andrew@lunn.ch
> To: oricon776@hotmail.com
> CC: ecos-discuss@ecos.sourceware.org
> Subject: Re: [ECOS] FW: [ECOS] ecos-discuss@ecos.sourceware.org
>
>>> Do as Gary said here.... Enable the interrupt driver serial device
>>> driver and use /dev/ser0, or /dev/tty0 as appropriate.
>>>
>>> Andrew
>>>
>>> --
>>
>> Hi, i tried to enable the interrupt driver serial device but now the
>> serial keep giving me interrupt signals. How shall I go about
>> solving this problem?
>
> What problem?
>
> An interrupt driven serial device driver is expected to generate
> interrupt signals!
>
> Andrew
>
> --

Hi there, yes I know the serial device driver is giving me interrupts.. That brings back to my original problem, how is this going to help me solve the multithreading problem stuck at scanf()?


________________________________

Always-on security tools provide safer ways to connect and share anywhere. Find out more. Windows Live

_________________________________________________________________
Check out Barclays Premier League exclusive video clips here!
http://fc.sg.msn.com/index.aspx

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] FW: [ECOS] FW: [ECOS] ecos-discuss@ecos.sourceware.org

[Andrew Lunn]

> Hi there, yes I know the serial device driver is giving me
> interrupts.. That brings back to my original problem, how is this
> going to help me solve the multithreading problem stuck at scanf()?

Because when you use this interrupt driver serial device driver, your
scanf() will not block busy looping taking 100% of the CPU. It will
just go to sleep until there is an interrupt saying a character has
arrived. So your other threads get to use the CPU.

         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

RE: [ECOS] FW: [ECOS] FW: [ECOS] ecos-discuss@ecos.sourceware.org

[Yong Chen Tan]

> Date: Fri, 27 Jun 2008 17:23:18 +0200
> From: andrew@lunn.ch
> To: oricon776@hotmail.com
> CC: ecos-discuss@ecos.sourceware.org
> Subject: Re: [ECOS] FW: [ECOS] FW: [ECOS] ecos-discuss@ecos.sourceware.org
>
>> Hi there, yes I know the serial device driver is giving me
>> interrupts.. That brings back to my original problem, how is this
>> going to help me solve the multithreading problem stuck at scanf()?
>
> Because when you use this interrupt driver serial device driver, your
> scanf() will not block busy looping taking 100% of the CPU. It will
> just go to sleep until there is an interrupt saying a character has
> arrived. So your other threads get to use the CPU.
>
> Andrew

So this interrupt will give me interrupt whenever there is character sending out and in is it?
Because once I enable this serial drivers, the screen on my hyperterminal keeps displaying interrupt signals even though I never key in anything
My hyperterminal is to display my menu option for user to choose. Will that generates endless interrupts?
_________________________________________________________________
NEW! Get Windows Live FREE.
http://www.get.live.com/wl/all

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss