linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* PCMCIA on a Pismo with pcmcia-cs-3.1.24
@ 2001-02-11  2:01 Michael K. Fleming
  2001-02-12  8:51 ` Albrecht Dre_
  0 siblings, 1 reply; 6+ messages in thread
From: Michael K. Fleming @ 2001-02-11  2:01 UTC (permalink / raw)
  To: linuxppc-dev


Hi--

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
WaveLAN card to work.

I've carefully read the notes at:

http://www.mpifr-bonn.mpg.de/div/iri/Archiv/LinuxPPC/PCMCIA.html

and followed what seemed currently relevant.

The problem seems to be that the i82365 driver cannot properly allocate
the interrupt assigned to the device.  The problem I'm having seems to be
identical to one that Uwe Steinmann reported a few weeks ago on this
mailing list.  I've read the followups to that email, but did not find any
solutions.

The relevant portions of my kernel log, /etc/pcmcia/config.opts, and lspci
are attached below.

Any hints or pointers would be greatly appreciated.

Mike Fleming
mikef@praxis.etla.net

-------------------------
dmesg
-------------------------

Linux PCMCIA Card Services 3.1.24
  kernel build: 2.2.18pre4-ben1 #6 Sat Feb 10 13:56:41 PST 2001
  options:  [pci] [cardbus]
Intel PCIC probe:
  TI 1211 rev 00 PCI-to-CardBus at slot 00:1a, mem 0x80080000
    host opts [0]: [serial pci & irq] [pci irq 58] [lat 16/32] [bus 1/1]
    PCI irq 58 test failed
    *NO* card interrupts, polling interval = 1000 ms

When I insert a WaveLAN card:

wvlan_cs: WaveLAN/IEEE PCMCIA driver v1.0.6
wvlan_cs: (c) Andreas Neuhaus <andy@fasta.fh-dortmund.de>
wvlan_cs: RequestIRQ: Resource in use

-------------------------
/etc/pcmcia/config.opts:
-------------------------

include memory 0x90000000-0x9003ffff
include port 0x1000-0x1fff

-------------------------
Output of lspci:
-------------------------

00:1a.0 CardBus bridge: Texas Instruments PCI1211
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
	Latency: 16, cache line size 08
	Interrupt: pin A routed to IRQ 58
	Region 0: Memory at 80080000 (32-bit, non-prefetchable)
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
	I/O window 1: 00000000-00000003
	BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+
PostWrite+
	16-bit legacy interface ports at 0001
-------------------------


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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: PCMCIA on a Pismo with pcmcia-cs-3.1.24
  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-13 17:50   ` Michael K. Fleming
  0 siblings, 2 replies; 6+ messages in thread
From: Albrecht Dre_ @ 2001-02-12  8:51 UTC (permalink / raw)
  To: Michael K. Fleming; +Cc: linuxppc-dev


"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...

Hope this helps, Albrecht.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[snip]
>     PCI irq 58 test failed

This leads to a complete failure of the pcmcia package...

> include memory 0x90000000-0x9003ffff
> include port 0x1000-0x1fff

Looks fine.

>         Bus: primary=00, secondary=01, subordinate=01, sec-latency=32

These entries look suspicious, and they do not work for sure with our pismos.

--

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: PCMCIA on a Pismo with pcmcia-cs-3.1.24
  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
  1 sibling, 1 reply; 6+ messages in thread
From: Benjamin Herrenschmidt @ 2001-02-12 11:08 UTC (permalink / raw)
  To: Albrecht Dreß, linuxppc-dev


>
>>         Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
>
>These entries look suspicious, and they do not work for sure with our pismos.

These are correct for a 2.2 kernel. 2.4 will have something like
primary=01, secondary=02, ...

Ben.


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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: PCMCIA on a Pismo with pcmcia-cs-3.1.24
  2001-02-12 11:08   ` Benjamin Herrenschmidt
@ 2001-02-12 11:20     ` Albrecht Dreß
  0 siblings, 0 replies; 6+ messages in thread
From: Albrecht Dreß @ 2001-02-12 11:20 UTC (permalink / raw)
  To: Benjamin Herrenschmidt; +Cc: linuxppc-dev


Benjamin Herrenschmidt wrote:
> >>         Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
> >
> >These entries look suspicious, and they do not work for sure with our pismos.
>
> These are correct for a 2.2 kernel. 2.4 will have something like
> primary=01, secondary=02, ...

The working config on the Lombard is

00:13.0 CardBus bridge: Texas Instruments PCI1211
	[...]
        Bus: primary=00, secondary=01, subordinate=04, sec-latency=176

and on the Pismo

00:1a.0 CardBus bridge: Texas Instruments PCI1211
	[...]
        Bus: primary=00, secondary=01, subordinate=04, sec-latency=32

These are the same bus settings as with MacOS, but I must admit that I do not
know exactly what they are for... The default values with the unpatched kernel
if booting with yaboot do not work at all, at least with the 2.2.x series.

Albrecht.

--

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: PCMCIA on a Pismo with pcmcia-cs-3.1.24
  2001-02-12  8:51 ` Albrecht Dre_
  2001-02-12 11:08   ` Benjamin Herrenschmidt
@ 2001-02-13 17:50   ` Michael K. Fleming
  2001-02-14 11:02     ` Albrecht Dreß
  1 sibling, 1 reply; 6+ messages in thread
From: Michael K. Fleming @ 2001-02-13 17:50 UTC (permalink / raw)
  To: Albrecht Dreß; +Cc: linuxppc-dev


Albrecht--

I'm confused:

> "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.

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

Mike


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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: PCMCIA on a Pismo with pcmcia-cs-3.1.24
  2001-02-13 17:50   ` Michael K. Fleming
@ 2001-02-14 11:02     ` Albrecht Dreß
  0 siblings, 0 replies; 6+ messages in thread
From: Albrecht Dreß @ 2001-02-14 11:02 UTC (permalink / raw)
  To: Michael K. Fleming; +Cc: linuxppc-dev


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/

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2001-02-14 11:02 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).