Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Bradley D. LaRonde" <brad@ltc.com>
To: "Florian Lohoff" <flo@rfc822.org>, <linux-mips@oss.sgi.com>
Subject: Re: [PATCH] /proc/cpuinfo endianess (autoconf dependencie)
Date: Thu, 13 Dec 2001 12:01:34 -0500	[thread overview]
Message-ID: <06c701c183f7$d23eb410$5601010a@prefect> (raw)
In-Reply-To: 20011213163953.GB23023@paradigm.rfc822.org

For autoconf?  Why need to ask the kernel?  Aren't there other very simple
ways of determining build endianness in userspace?

Regards,
Brad

----- Original Message -----
From: "Florian Lohoff" <flo@rfc822.org>
To: <linux-mips@oss.sgi.com>
Sent: Thursday, December 13, 2001 11:39 AM
Subject: [PATCH] /proc/cpuinfo endianess (autoconf dependencie)

Something like this should be needed for current kernel to make
autoconf happy ...

--- arch/mips/kernel/proc.c 2001/12/12 13:45:58 1.27.2.3
+++ arch/mips/kernel/proc.c 2001/12/13 17:39:19
@@ -51,6 +51,11 @@
  seq_printf(m, "BogoMIPS\t\t: %lu.%02lu\n",
                loops_per_jiffy / (500000/HZ),
                (loops_per_jiffy / (5000/HZ)) % 100);
+#ifdef __MIBSEB__
+ seq_printf(m, "byteorder\t\t: big endian\n");
+#else
+ seq_printf(m, "byteorder\t\t: little endian\n");
+#endif
  seq_printf(m, "wait instruction\t: %s\n", cpu_wait ? "yes" : "no");
  seq_printf(m, "microsecond timers\t: %s\n",
                (mips_cpu.options & MIPS_CPU_COUNTER) ? "yes" : "no");

WARNING: multiple messages have this Message-ID (diff)
From: "Bradley D. LaRonde" <brad@ltc.com>
To: Florian Lohoff <flo@rfc822.org>, linux-mips@oss.sgi.com
Subject: Re: [PATCH] /proc/cpuinfo endianess (autoconf dependencie)
Date: Thu, 13 Dec 2001 12:01:34 -0500	[thread overview]
Message-ID: <06c701c183f7$d23eb410$5601010a@prefect> (raw)
Message-ID: <20011213170134.06vbaHx8JJ4ymDB7WscVb9kE8H5ptPtxKfts7yRCG7M@z> (raw)
In-Reply-To: 20011213163953.GB23023@paradigm.rfc822.org

For autoconf?  Why need to ask the kernel?  Aren't there other very simple
ways of determining build endianness in userspace?

Regards,
Brad

----- Original Message -----
From: "Florian Lohoff" <flo@rfc822.org>
To: <linux-mips@oss.sgi.com>
Sent: Thursday, December 13, 2001 11:39 AM
Subject: [PATCH] /proc/cpuinfo endianess (autoconf dependencie)

Something like this should be needed for current kernel to make
autoconf happy ...

--- arch/mips/kernel/proc.c 2001/12/12 13:45:58 1.27.2.3
+++ arch/mips/kernel/proc.c 2001/12/13 17:39:19
@@ -51,6 +51,11 @@
  seq_printf(m, "BogoMIPS\t\t: %lu.%02lu\n",
                loops_per_jiffy / (500000/HZ),
                (loops_per_jiffy / (5000/HZ)) % 100);
+#ifdef __MIBSEB__
+ seq_printf(m, "byteorder\t\t: big endian\n");
+#else
+ seq_printf(m, "byteorder\t\t: little endian\n");
+#endif
  seq_printf(m, "wait instruction\t: %s\n", cpu_wait ? "yes" : "no");
  seq_printf(m, "microsecond timers\t: %s\n",
                (mips_cpu.options & MIPS_CPU_COUNTER) ? "yes" : "no");

  parent reply	other threads:[~2001-12-13 18:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-13 16:39 [PATCH] /proc/cpuinfo endianess (autoconf dependencie) Florian Lohoff
2001-12-13 16:56 ` Florian Lohoff
2001-12-13 17:01 ` Bradley D. LaRonde [this message]
2001-12-13 17:01   ` Bradley D. LaRonde
2001-12-13 17:04   ` Florian Lohoff
2001-12-13 17:13     ` Bradley D. LaRonde
2001-12-13 17:13       ` Bradley D. LaRonde
2001-12-13 17:05   ` Florian Lohoff

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='06c701c183f7$d23eb410$5601010a@prefect' \
    --to=brad@ltc.com \
    --cc=flo@rfc822.org \
    --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