From: Matthew Dharm <mdharm@momenco.com>
To: durai <durai@isofttech.com>
Cc: mips <linux-mips@linux-mips.org>
Subject: Re: how to include mips assembly in c code?
Date: Thu, 9 Oct 2003 01:05:39 -0700 [thread overview]
Message-ID: <20031009010539.B3375@momenco.com> (raw)
In-Reply-To: <007801c38e27$a1c81920$6b00a8c0@DURAI>; from durai@isofttech.com on Thu, Oct 09, 2003 at 11:08:56AM +0530
I feel compelled to point out that the source file you are quoting looks
suspiciously like it came from VxWorks, which means it is likely copyright
Wind River Systems. Using their code without permission would be illegal.
Matt
On Thu, Oct 09, 2003 at 11:08:56AM +0530, durai wrote:
> hello,
> I am having the following assembly code and i wanted to call this function from a c code.
> can anybody tell me how to include this code in a c program?
>
> /******************************************************************************
> *
> * sysWbFlush - flush the write buffer
> *
> * This routine flushes the write buffers, making certain all
> * subsequent memory writes have occurred. It is used during critical periods
> * only, e.g., after memory-mapped I/O register access.
> *
> * RETURNS: N/A
>
> * sysWbFlush (void)
>
> */
> .ent sysWbFlush
> sysWbFlush:
> li t0, K1BASE /* load uncached address */
> lw t0, 0(t0) /* read in order to flush */
> j ra /* return to caller */
> .end sysWbFlush
>
>
> regards
> durai
--
Matthew Dharm Work: mdharm@momenco.com
Senior Software Designer, Momentum Computer
next prev parent reply other threads:[~2003-10-09 8:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 5:38 how to include mips assembly in c code? durai
2003-10-09 7:54 ` Ralf Baechle
2003-10-09 8:05 ` Matthew Dharm [this message]
2003-10-09 21:47 ` ilya
2003-10-09 22:09 ` Wolfgang Denk
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=20031009010539.B3375@momenco.com \
--to=mdharm@momenco.com \
--cc=durai@isofttech.com \
--cc=linux-mips@linux-mips.org \
/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