linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Albrecht Dreß" <ad@mpifr-bonn.mpg.de>
To: "Michael K. Fleming" <mikef@praxis.etla.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: PCMCIA on a Pismo with pcmcia-cs-3.1.24
Date: Wed, 14 Feb 2001 12:02:36 +0100	[thread overview]
Message-ID: <3A8A65CC.87648220@mpifr-bonn.mpg.de> (raw)
In-Reply-To: Pine.LNX.4.21.0102130946440.32475-100000@praxis.etla.net


Hi Michael!

> > "Michael K. Fleming" wrote:
> > > I'm trying to get PCMCIA working on my Mac Powerbook Pismo, with kernel
> > > 2.2.18pre4-ben1 and pcmcia-cs-3.1.24 (no patches applied--as far as I can
> > > tell, none should be necessary...).  I'm primarily trying to get a
> >
> > This should be your problem... If you have a Pismo, you can not boot with BootX,
> > and in this case you have to patch your kernel. Did not check 2.2.18 yet (yeah,
> > my web page is outdated...), but I guess it is still necessary...
>
> I'm not booting with BootX--I'm booting with yaboot.

If you boot with BootX (which you *can* *not* use with the Pismo), OpenFirmware
takes care that the CardBus Bridge is initialised properly (but the kernel still
get a wrong number of pci busses on the Wallstreet/Lombard...). If you boot with
yaboot, some registers in the bridge contain bad values. I tried the stock
LinuxPPC 2.2.18 sources a few days ago, and they *still* need the patch. I did
not try the kernel-pmac rpm though, but if your box does not detect the IRQ,
there is no other solution than building a new kernel.

> What patches do I have to apply to my kernel?  Or do you mean patches to
> pcmcia-cs?

You just have to patch your kernel sources, as decsribed on my web page (see
http://www.mpifr-bonn.mpg.de/div/iri/Archiv/LinuxPPC/PCMCIA.html, just follow
the instructions in the section "Kernel Setup").

It *might* be possible for you to use the kernel-pcmcia-cs-2.2.18-4h.ppc.rpm
package. If it does not work, you should build your own pcmcia stuff. As pointed
out in the "PCMCIA/CardBus" section of the web page mentioned above, on the
Pismo you should use the stock package from sourceforge *without* any additional
patches. You *must* change the pcmcia config files afterwards, though.

Hth,

	Albrecht.

--

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

      reply	other threads:[~2001-02-14 11:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-11  2:01 PCMCIA on a Pismo with pcmcia-cs-3.1.24 Michael K. Fleming
2001-02-12  8:51 ` Albrecht Dre_
2001-02-12 11:08   ` Benjamin Herrenschmidt
2001-02-12 11:20     ` Albrecht Dreß
2001-02-13 17:50   ` Michael K. Fleming
2001-02-14 11:02     ` Albrecht Dreß [this message]

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=3A8A65CC.87648220@mpifr-bonn.mpg.de \
    --to=ad@mpifr-bonn.mpg.de \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mikef@praxis.etla.net \
    /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).