linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollis@amulet.co.jp>
To: Michael Lundkvist <ml@epact.se>
Cc: linuxppc-dev@lists.linuxppc.org, aeb@veritas.com
Subject: Re: Going from 2.2.12 to 2.2.17pre10
Date: Thu, 06 Jul 2000 22:54:33 +0900	[thread overview]
Message-ID: <39648F99.A06629CF@amulet.co.jp> (raw)
In-Reply-To: qphfa3ie20.fsf@erbium.epact.se


Michael Lundkvist wrote:

[snip]

> So it seems like the byte order is wrong. Does anyone know why this
> happens?
>
> Please don't tell me my 2.2.12 partitioned disk is wrong. :)

Something like that. This came up a while back (around 2.2.13 I think)
on the -workstation list. I didn't pay enough attention at the time, but
I think it switched from being always little-endian to being
native-endian. At least, I don't recall any x86 folks screaming about
it... ;)

I think without reformatting your only option is to use 'hda=swapdata'.

> Where do I go for the best LinuxPPC 2.4 kernel for MVME-boards? Is it
> fsmlabs Bitkeeper repository?

Probably. If that doesn't work shop around. ;)

-Hollis

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-07-06 13:54 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-06 13:27 Going from 2.2.12 to 2.2.17pre10 Michael Lundkvist
2000-07-06 13:54 ` Hollis Blanchard [this message]
2000-07-06 17:17 ` Gabriel Paubert
2000-07-06 17:32   ` Michael Lundkvist
2000-07-06 17:55     ` Gabriel Paubert
2000-07-06 22:23       ` Michael Lundkvist
2000-07-07  8:22         ` Gabriel Paubert
2000-07-07  8:55           ` Michael Lundkvist
2000-07-07  9:21             ` Gabriel Paubert
2000-07-07  9:47               ` Michael Lundkvist
2000-07-07 10:19                 ` Gabriel Paubert
2000-07-08  0:08                   ` Problem with de4x5 on an MVME-2400 Michael Lundkvist
2000-07-10 11:58                     ` Gabriel Paubert
2000-07-12 13:01                       ` Michael Lundkvist
2000-07-08 23:29     ` Going from 2.2.12 to 2.2.17pre10 Matt Porter
2000-07-09  6:12       ` Michael Lundkvist
2000-07-10  5:29         ` Matt Porter
2000-07-10 12:25           ` Gabriel Paubert
2000-07-11  5:57             ` Matt Porter
2000-07-11  9:37               ` Adrian Cox
2000-07-11 10:17                 ` Benjamin Herrenschmidt
2000-07-11 12:57                   ` Adrian Cox
2000-07-11 14:10                     ` Claus
2000-07-11 19:15                     ` Geert Uytterhoeven
2000-07-12 13:31                       ` Benjamin Herrenschmidt
2000-07-13 11:17                         ` Geert Uytterhoeven
2000-07-12  9:11                     ` Timothy A. Seufert
2000-07-12 14:16                 ` Matt Porter
2000-07-13 11:43                   ` Gabriel Paubert
2000-07-13 14:12                     ` Matt Porter
2000-07-12 12:52           ` Michael Lundkvist
2000-07-12 14:17             ` Matt Porter
2000-07-10 12:12       ` Gabriel Paubert
2000-07-11  6:12         ` Matt Porter
2000-07-11 10:48           ` Gabriel Paubert

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=39648F99.A06629CF@amulet.co.jp \
    --to=hollis@amulet.co.jp \
    --cc=aeb@veritas.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=ml@epact.se \
    /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;
as well as URLs for NNTP newsgroup(s).