Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Roman Mashak" <mrv@tusur.ru>
To: "Chris Dearman" <chris@mips.com>, <linux-mips@linux-mips.org>
Subject: Re: Yamon compiling and linking
Date: Wed, 18 Aug 2004 14:50:41 +0900	[thread overview]
Message-ID: <002601c484e7$4ea38e70$1422bdd3@roman> (raw)
In-Reply-To: 4121E1DF.9020801@mips.com

Hello, Chris!
You wrote to "Roman Mashak" <mrv@tusur.ru> on Tue, 17 Aug 2004 11:45:51
+0100:

 CD>    I think you are using modified YAMON sources... I can tell you how
 CD> the build process works for the distributed version of YAMON:

   Sorry, i didn't mention that  I'm using YAMON source code supplied with
AMD Alchemy  AU1550 dev. board. But I've already sent my questions to AMD
support, and didn't get reply for 3 days, that's why I asked here.
 CD>    Invoking make in the  yamon/bin directory build two YAMON images
 CD> (one big-endian & one little-endian) in the EB & EL subdirectories.  In
    Yes, absolutely correct
 CD> addition some endianess independent reset code (reset.o) is built in
 CD> yamon/bin. These three images are combined together to make a single
 CD> yamon-02.xx.rec image that can run in either endianess.
    In my case - NOT. So, if I invoke 'make srec_el' to build little-endian
only image I get only LE image located in the bin/EL directory and nothing
in the upper directory.
 CD>    If you're only interested in running little-endian you should be
 CD> able to simply combine the reset-02.xx.rec and EL/yamon-02.xx_el.rec
 CD> images.
    So, I have to compile reset code seperately and combine it with LE
according to your device.

With best regards, Roman Mashak.  E-mail: mrv@tusur.ru

WARNING: multiple messages have this Message-ID (diff)
From: "Roman Mashak" <mrv@tusur.ru>
To: Chris Dearman <chris@mips.com>, linux-mips@linux-mips.org
Subject: Re: Yamon compiling and linking
Date: Wed, 18 Aug 2004 14:50:41 +0900	[thread overview]
Message-ID: <002601c484e7$4ea38e70$1422bdd3@roman> (raw)
Message-ID: <20040818055041.J82JpojnzexdsMdRUP4piGbxfGX1nTHdbEyAXS3MHcA@z> (raw)
In-Reply-To: 4121E1DF.9020801@mips.com

Hello, Chris!
You wrote to "Roman Mashak" <mrv@tusur.ru> on Tue, 17 Aug 2004 11:45:51
+0100:

 CD>    I think you are using modified YAMON sources... I can tell you how
 CD> the build process works for the distributed version of YAMON:

   Sorry, i didn't mention that  I'm using YAMON source code supplied with
AMD Alchemy  AU1550 dev. board. But I've already sent my questions to AMD
support, and didn't get reply for 3 days, that's why I asked here.
 CD>    Invoking make in the  yamon/bin directory build two YAMON images
 CD> (one big-endian & one little-endian) in the EB & EL subdirectories.  In
    Yes, absolutely correct
 CD> addition some endianess independent reset code (reset.o) is built in
 CD> yamon/bin. These three images are combined together to make a single
 CD> yamon-02.xx.rec image that can run in either endianess.
    In my case - NOT. So, if I invoke 'make srec_el' to build little-endian
only image I get only LE image located in the bin/EL directory and nothing
in the upper directory.
 CD>    If you're only interested in running little-endian you should be
 CD> able to simply combine the reset-02.xx.rec and EL/yamon-02.xx_el.rec
 CD> images.
    So, I have to compile reset code seperately and combine it with LE
according to your device.

With best regards, Roman Mashak.  E-mail: mrv@tusur.ru

  reply	other threads:[~2004-08-18  5:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-17  1:57 Yamon compiling and linking Roman Mashak
2004-08-17  1:57 ` Roman Mashak
2004-08-17 10:45 ` Chris Dearman
2004-08-18  5:50   ` Roman Mashak [this message]
2004-08-18  5:50     ` Roman Mashak
  -- strict thread matches above, loose matches on Subject: below --
2004-08-17 16:58 Saugata.Chatterjee
2004-08-18  5:53 ` Roman Mashak
2004-08-18  5:53   ` Roman Mashak

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='002601c484e7$4ea38e70$1422bdd3@roman' \
    --to=mrv@tusur.ru \
    --cc=chris@mips.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