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]

Re: #error " no RESET_ENTRY" ??

To: Grant Edwards <grante at visi dot com>
Subject: Re: [ECOS] #error " no RESET_ENTRY" ??
From: Jesper Skov <jskov at redhat dot com>
Date: Wed, 10 Jan 2001 18:06:32 +0100
Cc: Jesper Skov <jskov at redhat dot com>, ecos-discuss at sources dot redhat dot com
References: <20010109165157.A16129@visi.com><otpuhv969a.fsf@thinktwice.zoftcorp.dk><20010110093636.A23362@visi.com>

>>>>> "Grant" == Grant Edwards <grante@visi.com> writes:

>> After I complete my changes, IO will _always_ happen via the
>> virtual vector table. Your option will be to claim those vectors in
>> the RAM application (thus using serial IO routines in the
>> application) or leave them in the ROM monitor's control (using
>> serial IO routines in ROM/flash).

Grant> IOW, CYGSEM_HAL_VIRTUAL_VECTOR_DIAG will always be true, and
Grant> one controls which way things work with
Grant> CYGPRI_HAL_IMPLEMENTS_IF_SERVICES?

Yes, something like that. Except there'll be new options to increase
the configuration granularity.

Jesper

References:
- #error " no RESET_ENTRY" ??
  - From: Grant Edwards
- Re: #error " no RESET_ENTRY" ??
  - From: Jesper Skov
- Re: #error " no RESET_ENTRY" ??
  - From: Grant Edwards

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