From: "Roman Mashak" <mrv@tusur.ru>
To: <Saugata.Chatterjee@taec.toshiba.com>, <linux-mips@linux-mips.org>
Subject: Re: Yamon compiling and linking
Date: Wed, 18 Aug 2004 14:53:18 +0900 [thread overview]
Message-ID: <002701c484e7$af440980$1422bdd3@roman> (raw)
In-Reply-To: OFBBD37EA1.A7922B89-ON88256EF3.005D0F89-88256EF3.005D49DB@taec.com
Hello, Saugata.Chatterjee@taec.toshiba.com!
You wrote to "Roman Mashak" <mrv@tusur.ru> on Tue, 17 Aug 2004
09:58:57 -0700:
SC> Reset code (reset.S) IS compiled and linked (at bfc00000 like it should
SC> be), and pretty early on in there YAMON detects endianness and jumps to
the
SC> location of the appropriate endian image. Dump the output of make to a
log
SC> file and look for the compilation of reset.S.
I have already investigated the 'makefile' and 'make' dump - and I've found
that reset code is compiled only in one case - when I compile both LE and BE
images.
Yes, I'm using AMD modified code and perhaps this is the reason, but their
support didn't answer yet.
Anyway - thank you for spending time for me.
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: Saugata.Chatterjee@taec.toshiba.com, linux-mips@linux-mips.org
Subject: Re: Yamon compiling and linking
Date: Wed, 18 Aug 2004 14:53:18 +0900 [thread overview]
Message-ID: <002701c484e7$af440980$1422bdd3@roman> (raw)
Message-ID: <20040818055318.yRRklCJu0ggX8U7KIHH975LHHEOCSbJtmDO1SVtEJwI@z> (raw)
In-Reply-To: OFBBD37EA1.A7922B89-ON88256EF3.005D0F89-88256EF3.005D49DB@taec.com
Hello, Saugata.Chatterjee@taec.toshiba.com!
You wrote to "Roman Mashak" <mrv@tusur.ru> on Tue, 17 Aug 2004
09:58:57 -0700:
SC> Reset code (reset.S) IS compiled and linked (at bfc00000 like it should
SC> be), and pretty early on in there YAMON detects endianness and jumps to
the
SC> location of the appropriate endian image. Dump the output of make to a
log
SC> file and look for the compilation of reset.S.
I have already investigated the 'makefile' and 'make' dump - and I've found
that reset code is compiled only in one case - when I compile both LE and BE
images.
Yes, I'm using AMD modified code and perhaps this is the reason, but their
support didn't answer yet.
Anyway - thank you for spending time for me.
With best regards, Roman Mashak. E-mail: mrv@tusur.ru
next prev parent reply other threads:[~2004-08-18 5:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 16:58 Yamon compiling and linking Saugata.Chatterjee
2004-08-18 5:53 ` Roman Mashak [this message]
2004-08-18 5:53 ` Roman Mashak
-- strict thread matches above, loose matches on Subject: below --
2004-08-17 1:57 Roman Mashak
2004-08-17 1:57 ` Roman Mashak
2004-08-17 10:45 ` Chris Dearman
2004-08-18 5:50 ` Roman Mashak
2004-08-18 5:50 ` 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='002701c484e7$af440980$1422bdd3@roman' \
--to=mrv@tusur.ru \
--cc=Saugata.Chatterjee@taec.toshiba.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