This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

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: ARM and interrupts

From: Toralf Lund <toralf at procaptura dot com>
To: Robert Schwebel <robert at schwebel dot de>
Cc: crossgcc <crossgcc at sources dot redhat dot com>
Date: Wed, 17 Mar 2004 17:17:49 +0100
Subject: Re: ARM and interrupts
References: <40583356.6060408@procaptura.com> <20040317154915.GI16437@pengutronix.de>

Robert Schwebel wrote:

On Wed, Mar 17, 2004 at 12:15:34PM +0100, Toralf Lund wrote:

I'm wondering about how to set up the interrupt vectors correctly on an ARM-9 setup w/o debug monitors. Has anyone else done this? Is there any kind of support for it in newlib? I mean, is the code that needs to be loaded at address 0 included anywhere? (That would not be the normal _start code, as far as I can tell.)

I'm not quite sure what you are talking about here; normally your Linux port handles all the interrupt request/release/masking stuff for you, so you don't have to deal with the vectors yourself.

I never said anything about Linux, did I?

I'm talking about an OS-less setup, using "stand-alone" newlib ;-)

Even if I wanted to run Linux, I'd probably have to set up the interrupt handling myself (in the Linux port), since we deal with custom hardware with special interrupt sources.

- Toralf


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com

References:
- ARM and interrupts
  - From: Toralf Lund
- Re: ARM and interrupts
  - From: Robert Schwebel

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