public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Bob Picco" <bob.picco@hp.com>
To: hpa@zytor.com
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, bob.picco@hp.com
Subject: [PATCH] klibc
Date: Thu, 1 Jun 2006 15:47:51 -0400	[thread overview]
Message-ID: <20060601194751.GD17809@localhost> (raw)

This change enabled me to boot on OpenPower 710. Otherwise klibc's statfs is 
built for 32 bit and not for 64 bit. The failure was in kinit when
calling run_init. run_init would attempt to validate ramfs and
failed calling statfs of "/".


Signed-off-by: Bob Picco <bob.picco@hp.com>

 usr/include/sys/vfs.h |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

Index: linux-2.6.17-rc5-mm2/usr/include/sys/vfs.h
===================================================================
--- linux-2.6.17-rc5-mm2.orig/usr/include/sys/vfs.h	2006-06-01 14:51:11.000000000 -0400
+++ linux-2.6.17-rc5-mm2/usr/include/sys/vfs.h	2006-06-01 14:52:20.000000000 -0400
@@ -13,7 +13,8 @@
 /* struct statfs64 -- there seems to be two standards -
    one for 32 and one for 64 bits, and they're incompatible... */
 
-#if !defined(__x86_64__) && !defined(__ia64__) && !defined(__sparc_v9__)
+#if !defined(__x86_64__) && !defined(__ia64__) && !defined(__sparc_v9__) && \
+	!defined(__powerpc64__)
 
 struct statfs {
 	uint32_t f_type;


             reply	other threads:[~2006-06-01 19:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-01 19:47 Bob Picco [this message]
2006-06-01 20:06 ` [PATCH] klibc Brian F. G. Bidulock
2006-06-01 20:23   ` H. Peter Anvin
2006-06-02  8:14     ` maximilian attems
2006-06-03 22:26       ` H. Peter Anvin
2006-06-04  6:30         ` David Miller
2006-06-04 17:42           ` H. Peter Anvin

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=20060601194751.GD17809@localhost \
    --to=bob.picco@hp.com \
    --cc=akpm@osdl.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.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