From: Ethan Benson <erbenson@alaska.net>
To: yaboot-devel@lists.penguinppc.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-mm1
Date: Mon, 20 Jun 2005 00:54:40 -0800 [thread overview]
Message-ID: <20050620085440.GT25980@plato.local.lan> (raw)
In-Reply-To: <1119250672.18247.94.camel@gaston>
[-- Attachment #1: Type: text/plain, Size: 1937 bytes --]
On Mon, Jun 20, 2005 at 04:57:51PM +1000, Benjamin Herrenschmidt wrote:
>
> On Sun, 2005-06-19 at 23:30 -0700, Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12/2.6.12-mm1/
> >
> >
> > - Someone broke /proc/device-tree on ppc64. It's being looked into.
>
> I did, the breakage is in 2.6.12, and no, it's not broken :)
>
> The problem is that the "ofpath" script that is part of the yaboot
> package has a stupid bug where for some reason, when booting from SCSI
> (or libata in this case), it decides to check wether there are any
> symlinks in /proc/device-tree, and if not, decides it's broken and
> aborts. It doesn't actually make any use of the symlinks that were there
> though (and they were useless and partially broken anyway, which is why
> I removed them).
this check was done because of BootX, which caused a broken and
unusable device-tree.
> So it's a bug in "ofpath", a bit annoying, but at the same time, you
> don't need to run it when changing kernels, so it's not too harmful.
>
> The fix is :
so long as BootX is no longer in use, yes.
> --- ofpath 2005-06-20 16:56:12.000000000 +1000
> +++ ofpath.patched 2005-06-20 16:57:00.000000000 +1000
> @@ -425,14 +425,6 @@
> {
> case "$DEVNODE" in
> sd*)
> - if ls -l /proc/device-tree | grep -q ^lr ; then
> - true
> - else
> - echo 1>&2 "$PRG: /proc/device-tree is broken. Do not use BootX to boot, use yaboot."
> - echo 1>&2 "$PRG: The yaboot HOWTO can be found here: http://www.alaska.net/~erbenson/doc"
> - return 1
> - fi
> -
> ## use common scsiinfo function to get info we need.
> scsiinfo || return 1
>
>
> --
> To UNSUBSCRIBE, email to minimalist@lists.penguinppc.org
> with a subject of "unsubscribe yaboot-devel". Trouble? Contact listmaster@lists.penguinppc.org
--
Ethan Benson
http://www.alaska.net/~erbenson/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2005-06-20 8:56 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 6:30 2.6.12-mm1 Andrew Morton
2005-06-20 6:57 ` 2.6.12-mm1 Benjamin Herrenschmidt
2005-06-20 8:54 ` Ethan Benson [this message]
2005-06-20 7:46 ` 2.6.12-mm1 Brice Goglin
2005-06-20 8:14 ` 2.6.12-mm1 Dominik Brodowski
2005-06-20 8:49 ` 2.6.12-mm1 Brice Goglin
[not found] ` <20050620085449.GA32330@isilmar.linta.de>
2005-06-20 13:11 ` 2.6.12-mm1 Brice Goglin
2005-06-22 23:34 ` 2.6.12-mm1 Rajesh Shah
2005-06-23 6:25 ` 2.6.12-mm1 Brice Goglin
2005-06-23 17:05 ` 2.6.12-mm1 Rajesh Shah
2005-06-23 18:09 ` 2.6.12-mm1 Brice Goglin
2005-06-23 20:32 ` 2.6.12-mm1 Rajesh Shah
2005-06-23 21:07 ` 2.6.12-mm1 Brice Goglin
2005-06-23 21:33 ` 2.6.12-mm1 Brice Goglin
2005-06-20 7:59 ` 2.6.12-mm1 Brice Goglin
2005-06-21 12:40 ` 2.6.12-mm1 Brice Goglin
2005-06-21 16:27 ` 2.6.12-mm1 Takashi Iwai
2005-06-21 16:32 ` 2.6.12-mm1 Takashi Iwai
2005-06-21 17:02 ` 2.6.12-mm1 Brice Goglin
2005-06-21 17:16 ` 2.6.12-mm1 Takashi Iwai
2005-06-21 19:39 ` 2.6.12-mm1 Brice Goglin
2005-06-22 10:10 ` 2.6.12-mm1 Takashi Iwai
2005-06-20 9:48 ` [patch] 2.6.12-mm1: saa7134-core.c compile error Adrian Bunk
2005-06-20 22:19 ` Michael Krufky
2005-06-20 11:36 ` [PATCH] bttv fix [was: 2.6.12-mm1] J.A. Magallon
2005-06-20 11:38 ` 2.6.12-mm1 J.A. Magallon
2005-06-20 16:36 ` 2.6.12-mm1 Jeff Garzik
2005-06-20 22:35 ` 2.6.12-mm1 J.A. Magallon
2005-06-20 12:32 ` [PATCH] Fix Reiser4 Dependencies Andrew James Wade
2005-06-20 18:26 ` Hans Reiser
2005-06-20 20:44 ` Andrew James Wade
2005-06-21 11:27 ` Edward Shishkin
2005-06-21 18:47 ` Hans Reiser
2005-06-21 19:26 ` Andrew James Wade
2005-06-22 8:56 ` Edward Shishkin
2005-06-22 8:39 ` Edward Shishkin
2005-06-20 13:14 ` 2.6.12-mm1 Andy Whitcroft
2005-06-21 22:55 ` 2.6.12-mm1 Greg KH
2005-06-22 9:23 ` 2.6.12-mm1 Andy Whitcroft
2005-06-22 10:04 ` 2.6.12-mm1 Ivan Kokshaysky
2005-06-20 13:21 ` 2.6.12-mm1: Kernel BUG at "fs/open.c":935 Rafael J. Wysocki
2005-06-20 13:54 ` Dipankar Sarma
2005-06-20 14:05 ` Rafael J. Wysocki
2005-06-20 17:38 ` 2.6.12-mm1: drivers/misc/ibmasm/ compile error Adrian Bunk
2005-06-20 20:24 ` Andrew Morton
2005-06-20 18:29 ` 2.6.12-mm1 Jean Delvare
2005-06-20 20:41 ` 2.6.12-mm1 Andrew Morton
2005-06-20 21:11 ` 2.6.12-mm1 Jean Delvare
2005-06-20 21:23 ` 2.6.12-mm1 Andrew Morton
2005-06-20 21:42 ` 2.6.12-mm1 Jean Delvare
2005-06-20 21:53 ` 2.6.12-mm1 Andrew Morton
2005-06-21 20:06 ` 2.6.12-mm1 Mauro Carvalho Chehab
2005-06-21 21:25 ` 2.6.12-mm1 Jean Delvare
2005-06-20 18:39 ` gregkh-usb-usb-isp116x-hcd-add.patch (was 2.6.12-mm1) Alexey Dobriyan
2005-06-20 22:15 ` 2.6.12-mm1 J.A. Magallon
2005-06-20 22:34 ` iptables bug (was: Re: 2.6.12-mm1) Andrew Morton
2005-06-20 23:39 ` iptables bug Patrick McHardy
2005-06-21 19:21 ` Stephen Jones
2005-06-22 1:52 ` Patrick McHardy
2005-06-21 22:09 ` [PATCH] more signed char cleanups in scripts J.A. Magallon
2005-06-21 22:18 ` Andrew Morton
2005-06-21 22:59 ` J.A. Magallon
2005-06-22 11:46 ` Paulo Marques
2005-06-22 0:05 ` Lee Revell
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=20050620085440.GT25980@plato.local.lan \
--to=erbenson@alaska.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yaboot-devel@lists.penguinppc.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