This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: question about "VIRTUAL_VECTOR_SUPPORT"
- To: Tony Ko <nhko at gctsemi dot com>
- Subject: Re: [ECOS] question about "VIRTUAL_VECTOR_SUPPORT"
- From: Jonathan Larmour <jlarmour at redhat dot com>
- Date: Thu, 13 Sep 2001 19:18:48 +0100
- Cc: ecos-discuss at sources dot redhat dot com
- Organization: Red Hat UK Ltd.
- References: <9860C773D04D834D83FD6FAD00A61E9311B722@gctsemi.gctsemi.com>
Tony Ko wrote:
>
> hi.
> look at the satement below,
> "Enable use of virtual vector calling interface. Virtual vector support
> allows
> the HAL to let the ROM monitor handle certain operations."
>
> does this satement mean " when exception occurs while ecos running,
> the exception can be processed by REDBOOT" ?
> I think ROM monitor is same with REDBOOT in this case.
> If so, some exception can be processed REDBOOT exception handler even
> while eCos running, right?
I'm not quite clear on what you are asking here. But yes the application
will hand over certain operations to RedBoot using virtual vectors.
But in most cases when it comes to processor exceptions, a RAM-loaded eCos
app will not take over the processor exception vectors in the first place -
but that's not related to *virtual* vectors.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine