This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Interrupts ? oops !

From: Jonathan Larmour <jifl at eCosCentric dot com>
To: Matthieu dot GIRARDIN at fr dot thalesgroup dot com
Cc: ecos-discuss at sources dot redhat dot com
Date: Tue, 02 Sep 2003 03:17:23 +0100
Subject: Re: [ECOS] Interrupts ? oops !
References: <66CE949D18BCB249ABE8D9AF48C4F1CE94B180@helios.gnv.tcc.thomson-csf.com>

Matthieu.GIRARDIN@fr.thalesgroup.com wrote:

Oooups Sorry !
I forgot to include my code source in the previous e-mail.

____________________________________

Hello world !

A question from a newbie on the eCos interrupts system :

You can see just under a very little source code in order to test eCos
interrupts on my Linux (Synthetic Target).
1) Is it correct ? I believe and it compiled without any problem.
2) Can I launch next an interrupt to the eCos process under Linux with a
"kill -s 1 ecos_pid" whee ecos_pid is the pid of this process eCos ?
3) Can I use any signal Linux for this application ? What are the eCos
vectors ?

I think you'll get a better understanding from reading hal/synth/arch/current/src/synth_intr.c. SIGHUP (signal #1) is blocked there. There isn't meant to be a way to receive signals like that. But you could manually unblock SIGHUP using cyg_hal_sys_sigprocmask I guess.

Jifl
--
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine


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

References:
- Interrupts ? oops !
  - From: Matthieu . GIRARDIN

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]