linux-mips
[Top] [All Lists]

Re: how to include mips assembly in c code?

To: Matthew Dharm <mdharm@momenco.com>
Subject: Re: how to include mips assembly in c code?
From: ilya@theIlya.com
Date: Thu, 9 Oct 2003 14:47:06 -0700
Cc: durai <durai@isofttech.com>, mips <linux-mips@linux-mips.org>
In-reply-to: <20031009010539.B3375@momenco.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <007801c38e27$a1c81920$6b00a8c0@DURAI> <20031009010539.B3375@momenco.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4i
Here we go - whole six lines of code! What a terrible copyright infigement!

On Thu, Oct 09, 2003 at 01:05:39AM -0700, Matthew Dharm wrote:
> 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
> 
> 

Attachment: pgpoV0bpJsFS_.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>