From: Jesper Skov <jskov@redhat.com>
To: "Jurica Baricevic" <jura@INTESIS.hr>
Cc: "Ecos" <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] Stand-alone application working from RAM
Date: Thu, 20 Jul 2000 09:00:00 -0000 [thread overview]
Message-ID: <otlmywbxlf.fsf@thinktwice.zoftcorp.dk> (raw)
In-Reply-To: <002801bff259$d0cefb20$6b00a8c0@JURA>
>>>>> "Jurica" == Jurica Baricevic <jura@INTESIS.hr> writes:
Jurica> Thank you for the code - it helped me a lot since I didn't
Jurica> have to write it by myself :-). Only thing I had to modify is
Jurica> destination address of 'other_vector' because my MIPS R3041
Jurica> has general exception vector at 0x80000080. Nevertheless, I
Jurica> am worried about using cached kernel segment in
Jurica> 'hal_memc_init' because cache is not yet initialized
Jurica> ('hal_cache_init' is called latter).
Good point. The code should be moved to hal_mon_init.
Jesper
prev parent reply other threads:[~2000-07-20 9:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-19 9:29 Jurica Baricevic
2000-07-19 23:48 ` Jesper Skov
2000-07-20 7:52 ` Jurica Baricevic
2000-07-20 9:00 ` Jesper Skov [this message]
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=otlmywbxlf.fsf@thinktwice.zoftcorp.dk \
--to=jskov@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=jura@INTESIS.hr \
/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).