public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Rutger Nijlunsing <rutger@nospam•com>
To: Kim Phillips <kim.phillips@freescale•com>
Cc: linuxppc-dev@ozlabs•org, Paul Mackerras <paulus@samba•org>
Subject: Re: [PATCH] Re: 2.6.22-git hangs during PCMCIA on PowerBook G3 in 0.0 seconds
Date: Sat, 28 Jul 2007 00:11:31 +0200	[thread overview]
Message-ID: <20070727221131.GA18273@nospam.com> (raw)
In-Reply-To: <20070726162921.a60c76ae.kim.phillips@freescale.com>

> Kim
> 
> p.s. should the stable team be notified to fix 2.6.22 for
> Lombard-nvram-style machines?

Logically, yes. 

Practically it does not matter that much it seems. I've got the
feeling the Lombard-users-group-size is about one person which is
going to drop to zero if he doesn't get any further in being able to
use _any_ PCMCIA card in his machine ;-)

For example, PCMCIA (non-cardbus) does not work on Lombard since
~2.6.12 (2 years old bug instantly crashing the kernel!) according to
own experiences, Google and own git-bisecting down to 2.6.13,
compiling and running different kernels. 2.6.12 appears to require the
'old-style' PCMCIA tools, which I do not have installed and is
therefore impossible for me to test.

Links:
  2.6.12 works with PCMCIA on Lombard:
    http://www.mascanc.net/~vieri/gnumela.html
  2.6.13 dead
    (checked with git)
  2.6.15 dead (Lombard PCMCIA problems in FC5):
    http://forums.fedoraforum.org/archive/index.php/t-110657.html
  2.6.18 dead, 2.6.12 works:
    http://lists.infradead.org/pipermail/linux-pcmcia/2006-October/004051.html
  2.6.19 dead (own bug report):
    http://ozlabs.org/pipermail/linuxppc-dev/2006-November/028617.html
  2.6.20 dead:
    http://lists.infradead.org/pipermail/linux-pcmcia/2007-April/004500.html
  2.6.22 dead (own bug report #2):
    http://ozlabs.org/pipermail/linuxppc-dev/2007-July/039863.html

The initial reason to bisect to the now-reverting patch was to get a
working Lombard. I'd like to get this working or to help out in any
way, but I don't know how to proceed...

-- 
Rutger Nijlunsing ---------------------------------- eludias ed dse.nl
never attribute to a conspiracy which can be explained by incompetence
----------------------------------------------------------------------

  parent reply	other threads:[~2007-07-27 22:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-21 19:21 2.6.22-git hangs during boot on PowerBook G3 in 0.0 seconds Rutger Nijlunsing
2007-07-21 21:28 ` [PATCH] " Rutger Nijlunsing
2007-07-23 22:27   ` Kim Phillips
2007-07-23 23:55     ` Benjamin Herrenschmidt
2007-07-24 23:59       ` Kim Phillips
2007-07-25  2:07         ` Benjamin Herrenschmidt
2007-07-26  3:31         ` Paul Mackerras
2007-07-26  3:42         ` Paul Mackerras
2007-07-26 21:29           ` Kim Phillips
2007-07-26 21:53             ` Benjamin Herrenschmidt
2007-07-27 22:11             ` Rutger Nijlunsing [this message]
2007-07-27 22:26               ` [PATCH] Re: 2.6.22-git hangs during PCMCIA " Benjamin Herrenschmidt
2007-07-27 23:29                 ` Kim Phillips

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=20070727221131.GA18273@nospam.com \
    --to=rutger@nospam$(echo .)com \
    --cc=kim.phillips@freescale$(echo .)com \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=linuxppc-dev@tux$(echo .)tmfweb.nl \
    --cc=paulus@samba$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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