public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jesper Skov <jskov@redhat.com>
To: "jeremy" <chienyul@home.com>
Cc: <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] HAL register write problem
Date: Mon, 22 Jan 2001 00:40:00 -0000	[thread overview]
Message-ID: <otn1ckt1x5.fsf@thinktwice.zoftcorp.dk> (raw)
In-Reply-To: <003e01c0828f$42da2260$7c6509c0@viatech.com>

>>>>> "jeremy" == jeremy  <chienyul@home.com> writes:

jeremy> template. One has kernal the other doesn't.  Do I need to add
jeremy> any package when compiling stub in order to use 16-bit and
jeremy> 32-bit HAL_WRITE ?  Thanks a lot!!

No. The HAL IO macros are just memory writes. If you have a JEENI,
can't you single step through the assembly to see what happens?

Jesper

  reply	other threads:[~2001-01-22  0:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-18 14:07 jeremy
2001-01-18 15:11 ` Gary Thomas
2001-01-18 19:04 ` Jonathan Larmour
2001-01-19  8:33 ` Grant Edwards
2001-01-19 19:37   ` jeremy
2001-01-22  0:40     ` Jesper Skov [this message]
2001-01-23 16:16 jeremy
2001-01-24  7:18 ` Grant Edwards

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=otn1ckt1x5.fsf@thinktwice.zoftcorp.dk \
    --to=jskov@redhat.com \
    --cc=chienyul@home.com \
    --cc=ecos-discuss@sourceware.cygnus.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).