This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Still confused by virtual vectors
- To: Jonathan Larmour <jlarmour at redhat dot com>
- Subject: Re: [ECOS] Still confused by virtual vectors
- From: Grant Edwards <grante at visi dot com>
- Date: Thu, 4 Oct 2001 15:08:20 -0500
- Cc: ecos-discuss at sources dot redhat dot com
- References: <20011003163242.A12778@visi.com> <3BBB998B.431448C3@redhat.com>
On Thu, Oct 04, 2001 at 12:04:43AM +0100, Jonathan Larmour wrote:
> Grant Edwards wrote:
> >
> > I'm trying to update my HAL to work with the current CVS
> > snapshot and to use virtual vectors the "right" way. I've read
> > and re-read porting/hal-calling-if.html, but I just don't get
> > it.
> >
> > I've looked at a couple different HAL implimentations and they
> > don't all seem to support virtual vectors (or lack thereof) can
> > somebody point me to a good HAL example?
>
> Most do though. Since you're on ARM, choosing another ARM target is good.
> How about the ebsa285 since it's well established. Look at hal_diag.c but
> ignore the "compatibility with older stubs" bits. And then hal_diag.h and
> plf_stub.h. edb7xxx is another option.
I've looked at those and configured my HAL to work with and
without virtual vector support.
But, I still can't figure out how to control that -- trying to
change CYG{INT|SEM}_HAL_VIRTUAL_VECTOR_SUPPORT in ecos.ecc
generates errors. When you've got a HAL that works either way,
how do you configure which way you want it to work?
--
Grant Edwards
grante@visi.com