From: Jun Sun <jsun@mvista.com>
To: Adeel Malik <AdeelM@avaznet.com>
Cc: linux-mips@linux-mips.org, jsun@mvista.com
Subject: Re: YAMON Source code modification
Date: Thu, 9 Oct 2003 11:01:54 -0700 [thread overview]
Message-ID: <20031009110154.B17781@mvista.com> (raw)
In-Reply-To: <10C6C1971DA00C4BB87AC0206E3CA38264F05F@1aurora.enabtech>; from AdeelM@avaznet.com on Thu, Oct 09, 2003 at 03:46:19PM +0500
On Thu, Oct 09, 2003 at 03:46:19PM +0500, Adeel Malik wrote:
> We want to port and 'run' YAMON to our own MIPS-based Development Board. Can
> someone tell me what changes are necessary in the YAMON source code so that
> it works on our board ?.
> Regards,
> ADEEL MALIK,
>
Actually is YAMON code freely available? Can someone from MIPS confirm
that and perhaps point to the downloading place?
Many people have asked me about this in the past ...
Jun
next prev parent reply other threads:[~2003-10-09 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 10:46 YAMON Source code modification Adeel Malik
2003-10-09 18:01 ` Jun Sun [this message]
2003-10-09 18:50 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2003-10-09 18:38 Mitchell, Earl
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=20031009110154.B17781@mvista.com \
--to=jsun@mvista.com \
--cc=AdeelM@avaznet.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