From: Chris Morrow <cmorrow@YottaYotta.com>
To: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] hal_copy_data and hal_zero_bss
Date: Mon, 15 Jan 2001 13:22:00 -0000 [thread overview]
Message-ID: <3A6369EB.E071860B@YottaYotta.com> (raw)
In-Reply-To: <ELEIIPIOKOBPDLLMNHKJAEBLCBAA.ppham@mit.edu>
The hal_copy_data() and hal_zero_bss() in the mips architecture
currently
do byte reads and writes. Is there any reason they shouldn't use the
memset() and memcpy() functions from infra?
--
Chris Morrow YottaYotta Inc.
email: cmorrow@yottayotta.com
phone: (780) 439 9000 ext 227
web: http://www.yottayotta.com
next prev parent reply other threads:[~2001-01-15 13:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-15 12:26 [ECOS] Header files in platform port Paul Pham
2001-01-15 13:22 ` Chris Morrow [this message]
2001-01-15 18:30 ` [ECOS] hal_copy_data and hal_zero_bss Jonathan Larmour
2001-02-25 18:05 ` Chris Morrow
2001-02-25 18:15 ` [ECOS] mips mmu setup Chris Morrow
2001-02-26 12:39 ` Jonathan Larmour
2001-02-26 15:22 ` [ECOS] hal_copy_data and hal_zero_bss Jonathan Larmour
2001-02-27 1:54 ` Chris Morrow
2001-02-27 10:25 ` Jonathan Larmour
2001-01-15 18:44 ` [ECOS] Header files in platform port Jonathan Larmour
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=3A6369EB.E071860B@YottaYotta.com \
--to=cmorrow@yottayotta.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).