This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: RedBoot and interrupts
- From: Mark Salter <msalter at redhat dot com>
- To: grante at visi dot com
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Wed, 12 Feb 2003 16:41:20 -0500 (EST)
- Subject: Re: [ECOS] RedBoot and interrupts
- References: <20030212150016.A16942@visi.com>
>>>>> Grant Edwards writes:
> I've got an Intel IXP425 eval board that runs RedBoot. The 425
> has two built-in Ethernet interfaces, but RedBoot will only use
> a third EEPRO-100 PCI board. Upon investigating the use of the
> two onboard Ethernet interfaces, it seems it is not practical
> to operate the built-in Ethernet controlelrs in polled mode.
> What sort of problems are to be expected if an Ethernet driver
> uses interrupts under RedBoot?
There will be problems with the gdb stub. The stub relies on
interrupts being turned off by the master enable in the CPSR.
If you needed interrupts for the stub comm channel, then that
enable in the CPSR would need to allow interrupts. This would
also allow interrupts used by the program being debugged. This
could complicate the debugging because gdb assumes that the
program being debug is completely stopped when say a breakpoint
is hit. It would also prevent you from being able to debug
interrupt handlers.
I think it best to use the eepro board or to use polling with
the builtin ports.
--Mark
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss