From: Gary Thomas <gthomas@cygnus.co.uk>
To: Grant Edwards <grante@visi.com>
Cc: ecos <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] ARM vectors.S question
Date: Wed, 27 Oct 1999 07:09:00 -0000 [thread overview]
Message-ID: <XFMail.991027081717.gthomas@cygnus.co.uk> (raw)
In-Reply-To: <19991027090116.B14874@visi.com>
On 27-Oct-99 Grant Edwards wrote:
>> Firstly, you should consider working from the public CVS repository. This
>> has the latest stuff in it, including much work that lets items such as
>> this be specified in platform specific files, not directly in "vectors.S".
>
> OK, I'll take a look at the CVS tree -- having to modify what were
> supposed to be platform-independant files made me think that I was
> headed in the wrong direction. Are there semi-stable CVS snapshots,
> or is a guy pretty much rolling the dice when using sources from the
> CVS tree?
>
The public version of the CVS tree is updated from our working CVS about
once a week. We try to keep the CVS tree in a constant working state since
we have so much parallel development (the *!@# really flies when the tree
gets broken :-) If you grab it today, you'll have a good version that
shouldn't be more than a few days old.
>> I'll try and provide help/guidance with whatever changes you need.
>> Note that there are other places than "vectors.S" that expect low memory
>> to be writeable so vectors can be updated. Unless you can take the
>> "remap" route, there will be other considerations.
>
> Thanks. That's a very useful tip. I should be able to go either way:
> remapping ROM/RAM in startup code or having ROM vectors go through
> RAM. Initially I was thinking of sticking with the ROM vectors, but
> it sounds like remapping might be a better idea.
>
Absolutely, remapping is the best [lowest cost/risk] way to do this.
>> > I must say that the ARM load/store instructions are about the coolest
>> > I've seen since the PDP-11.
>>
>> I shudder to think what you've been working with...
>
> Mostly the usual crop of embedded architectures (8086, 8051, 68HC11,
> 68332) and the TI TMS32C320 DSP for a while [it was wierd having
> sizeof (everyting) == 1].
>
Yeuch!
Let me (via the list) know if you have questions or problems.
next prev parent reply other threads:[~1999-10-27 7:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-26 13:44 Grant Edwards
1999-10-26 15:05 ` Gary Thomas
1999-10-26 18:42 ` Grant Edwards
1999-10-27 4:00 ` Hugo Tyson
1999-10-27 5:14 ` Gary Thomas
1999-10-27 7:01 ` Grant Edwards
1999-10-27 7:09 ` Gary Thomas [this message]
1999-10-27 1:04 ` Dan Hovang
2013-10-12 14:54 [ECOS] ARM Vectors.S Question Michael Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=XFMail.991027081717.gthomas@cygnus.co.uk \
--to=gthomas@cygnus.co.uk \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=grante@visi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).