From: Faux Pas III <fauxpas@temp123.org>
To: linux-kernel@vger.kernel.org
Subject: Weird PCMCIA behavior
Date: Sun, 18 Nov 2001 18:06:56 -0500 [thread overview]
Message-ID: <20011118180656.A18252@temp123.org> (raw)
Note: this is the same laptop mentioned above in the Maestro 2E
thread above, so the same weird-ass power behavior applies here.
When on AC power, everything is dandy with PCMCIA. When on
battery power, PCMCIA device detection fails, emanating a lower
than normal pitched beep, followed by an even lower beep.
However, if the apm module is inserted, this makes it behave
properly, but ONLY if the apm module was compiled with 'Make
CPU idle calls when idle'. Yeah, I know it's ucked fup.
Some possibly relevant details:
2.4.{14,15-pre{3,5}}
pcmcia-cs-3.1.29
lspci -vv:
00:0b.0 CardBus bridge: Toshiba America Info Systems ToPIC97 (rev 05)
Subsystem: Toshiba America Info Systems: Unknown device 0001
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin A routed to IRQ 11
Region 0: Memory at 10000000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=00, secondary=14, subordinate=14, sec-latency=0
Memory window 0: 10400000-107ff000 (prefetchable)
Memory window 1: 10800000-10bff000
I/O window 0: 00004000-000040ff
I/O window 1: 00004400-000044ff
BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt+ PostWrite+
16-bit legacy interface ports at 0001
--
Josh Litherland (fauxpas@temp123.org)
next reply other threads:[~2001-11-18 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-18 23:06 Faux Pas III [this message]
2001-11-18 23:21 ` Weird PCMCIA behavior Jeff Garzik
2001-11-18 23:29 ` Faux Pas III
2001-11-18 23:44 ` Jeff Garzik
2001-11-19 11:26 ` christophe barbé
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=20011118180656.A18252@temp123.org \
--to=fauxpas@temp123.org \
--cc=linux-kernel@vger.kernel.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