From: "H . J . Lu" <hjl@lucon.org>
To: Jun Sun <jsun@mvista.com>
Cc: Dan Aizenstros <dan@quicklogic.com>,
Hanks Li <hli@quicklogic.com>,
linux-mips@oss.sgi.com
Subject: Re: Big endian problem
Date: Fri, 12 Oct 2001 22:54:33 -0700 [thread overview]
Message-ID: <20011012225433.A10523@lucon.org> (raw)
In-Reply-To: <20011012173552.B3689@mvista.com>; from jsun@mvista.com on Fri, Oct 12, 2001 at 05:35:52PM -0700
On Fri, Oct 12, 2001 at 05:35:52PM -0700, Jun Sun wrote:
> On Fri, Oct 12, 2001 at 04:13:50PM -0400, Dan Aizenstros wrote:
> > Hello Jun,
> >
> > The file is the common time.c from linux/arch/mips/kernel as you
> > can see from the third to last line of Hanshi's email. The tools
> > he is using are from H. J. Lu's RedHat 7.1 RPMs on the oss.sgi.com
> > ftp site. The file compiles just fine with the little endian version
> > of the same tools from the same place.
> >
> > Hanshi and I will look at the USECS_PER_JIFFY_FRAC macro. Thanks for
> > the pointer.
> >
> > -- Dan A.
> >
>
> It is indeed a strange problem as it only shows up in BE tools.
> Some tool gurus want to look into it?
>
> Meanwhile the following patch seems to fix it (and a couple of other
> time.c files)
>
> Jun
This is what I sent out in July.
H.J.
----
From hjl@lucon.org Tue Jul 24 13:25:34 2001
Date: Tue, 24 Jul 2001 13:25:34 -0700
From: "H . J . Lu" <hjl@lucon.org>
To: Marc Karasek <marc_karasek@ivivity.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: GCC and Modules
Message-ID: <20010724132534.A25416@lucon.org>
References: <25369470B6F0D41194820002B328BDD27D2E@ATLOPS> <20010724085544.A20610@lucon.org> <995995907.1331.5.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <995995907.1331.5.camel@localhost.localdomain>; from marc_karasek@ivivity.com on Tue, Jul 24, 2001 at 01:31:41PM -0400
Status: RO
Content-Length: 954
Lines: 29
On Tue, Jul 24, 2001 at 01:31:41PM -0400, Marc Karasek wrote:
> The way to see this bug is just try to compile the MIPS kernel (either
> 2.4.1 or 2.4.3) as follows:
>
> 1) make distclean
> 2) copy linux/arch/mips/defconfig-malta linux/.config
> 3) make oldconfig
> 4) make menuconfig
> 5) change the endianess from little to big
> 6) make dep
> 7) make zImage
>
That is a kernel bug. The code only works on littl endian by accident
Here is a patch.
H.J.
--- arch/mips/mips-boards/generic/time.c.int64 Tue Jul 24 13:21:21 2001
+++ arch/mips/mips-boards/generic/time.c Tue Jul 24 13:22:02 2001
@@ -275,7 +275,7 @@ void __init time_init(void)
/* This is for machines which generate the exact clock. */
#define USECS_PER_JIFFY (1000000/HZ)
-#define USECS_PER_JIFFY_FRAC (0x100000000*1000000/HZ&0xffffffff)
+#define USECS_PER_JIFFY_FRAC ((long) (0x100000000*1000000/HZ&0xffffffff))
/* Cycle counter value at the previous timer interrupt.. */
WARNING: multiple messages have this Message-ID (diff)
From: "H . J . Lu" <hjl@lucon.org>
To: Jun Sun <jsun@mvista.com>
Cc: Dan Aizenstros <dan@quicklogic.com>,
Hanks Li <hli@quicklogic.com>,
linux-mips@oss.sgi.com
Subject: Re: Big endian problem
Date: Fri, 12 Oct 2001 22:54:33 -0700 [thread overview]
Message-ID: <20011012225433.A10523@lucon.org> (raw)
Message-ID: <20011013055433.uaU3UjcfxBk_16rGKFFI_tD_cQzXc4KorF3_qn0-spU@z> (raw)
In-Reply-To: <20011012173552.B3689@mvista.com>; from jsun@mvista.com on Fri, Oct 12, 2001 at 05:35:52PM -0700
On Fri, Oct 12, 2001 at 05:35:52PM -0700, Jun Sun wrote:
> On Fri, Oct 12, 2001 at 04:13:50PM -0400, Dan Aizenstros wrote:
> > Hello Jun,
> >
> > The file is the common time.c from linux/arch/mips/kernel as you
> > can see from the third to last line of Hanshi's email. The tools
> > he is using are from H. J. Lu's RedHat 7.1 RPMs on the oss.sgi.com
> > ftp site. The file compiles just fine with the little endian version
> > of the same tools from the same place.
> >
> > Hanshi and I will look at the USECS_PER_JIFFY_FRAC macro. Thanks for
> > the pointer.
> >
> > -- Dan A.
> >
>
> It is indeed a strange problem as it only shows up in BE tools.
> Some tool gurus want to look into it?
>
> Meanwhile the following patch seems to fix it (and a couple of other
> time.c files)
>
> Jun
This is what I sent out in July.
H.J.
----
next prev parent reply other threads:[~2001-10-13 5:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-12 16:26 Big endian problem Hanks Li
2001-10-12 16:26 ` Hanks Li
2001-10-12 17:45 ` Ralf Baechle
2001-10-12 17:47 ` Jun Sun
2001-10-12 20:13 ` Dan Aizenstros
2001-10-13 0:35 ` Jun Sun
2001-10-13 0:55 ` Thiemo Seufer
2001-10-13 5:54 ` H . J . Lu [this message]
2001-10-13 5:54 ` H . J . Lu
2001-10-13 21:02 ` MySQL Yoshi-K
2001-10-13 21:02 ` MySQL Yoshi-K
2001-10-14 16:30 ` MySQL H . J . Lu
2001-10-14 21:01 ` MySQL Ralf Baechle
2001-10-15 5:46 ` MySQL H . J . Lu
2001-10-16 14:28 ` IDE DMA mode in Big endian for mips Hanks Li
2001-10-16 14:28 ` Hanks Li
2001-10-16 17:30 ` Jun Sun
2001-10-17 2:38 ` Atsushi Nemoto
2001-10-17 5:48 ` Geert Uytterhoeven
2001-10-17 9:33 ` Gleb O. Raiko
2001-10-17 11:43 ` Atsushi Nemoto
2001-10-18 2:18 ` Atsushi Nemoto
2001-10-18 5:54 ` Geert Uytterhoeven
2001-10-18 10:33 ` Gleb O. Raiko
2001-10-17 17:52 ` Hanks Li
2001-10-17 17:52 ` Hanks Li
2001-10-19 9:54 ` Atsushi Nemoto
2001-10-21 16:50 ` Alan Cox
2001-10-21 16:50 ` Alan Cox
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=20011012225433.A10523@lucon.org \
--to=hjl@lucon.org \
--cc=dan@quicklogic.com \
--cc=hli@quicklogic.com \
--cc=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
/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