From: Jussi Laako <jlaako@pp.htv.fi>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Per Jessen <per.jessen@enidan.com>,
linux-kernel@vger.kernel.org, linux-laptop@vger.kernel.org
Subject: Re: PCMCIA control I82365 stops working with 2.4.4
Date: Sat, 04 Aug 2001 01:54:23 +0300 [thread overview]
Message-ID: <3B6B2B9F.1CFC220A@pp.htv.fi> (raw)
In-Reply-To: <3B5D8A0A002D181A@mta2n.bluewin.ch> <20010801114105.A26615@flint.arm.linux.org.uk> <3B68557B.7816FE4B@pp.htv.fi> <20010801202409.A27667@flint.arm.linux.org.uk>
Russell King wrote:
>
> Hmm, I'm not an x86 expert, so I'll have to leave you here. What I do
> know is that yenta is for PCI-based PCMCIA controllers with CardBus
> support. i82365 is for ISA PCMCIA controllers only.
The machine has CardBus (at least CB-logo beside slots). It's Toshiba
Satellite 300CDS.
- Jussi Laako
--- 8< ---
00:00.0 Host bridge: Toshiba America Info Systems 601 (rev 2c)
00:04.0 VGA compatible controller: Chips and Technologies F65555 HiQVPro
(rev c6)
00:0b.0 USB Controller: NEC Corporation USB (rev 02)
00:11.0 Communication controller: Toshiba America Info Systems FIR Port (rev
21)
00:13.0 CardBus bridge: Toshiba America Info Systems ToPIC97 (rev 20)
00:13.1 CardBus bridge: Toshiba America Info Systems ToPIC97 (rev 20)
--- 8< ---
--
PGP key fingerprint: 161D 6FED 6A92 39E2 EB5B 39DD A4DE 63EB C216 1E4B
Available at PGP keyservers
next prev parent reply other threads:[~2001-08-03 22:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 10:40 PCMCIA control I82365 stops working with 2.4.4 Per Jessen
2001-08-01 10:41 ` Russell King
2001-08-01 19:16 ` Jussi Laako
2001-08-01 19:24 ` Russell King
2001-08-03 22:54 ` Jussi Laako [this message]
2001-08-06 11:39 ` Jamie Lokier
2001-08-01 19:42 ` bvermeul
2001-08-03 23:03 ` Jussi Laako
2001-08-04 9:25 ` bvermeul
2001-08-05 18:36 ` Jussi Laako
2001-08-05 18:59 ` bvermeul
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=3B6B2B9F.1CFC220A@pp.htv.fi \
--to=jlaako@pp.htv.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-laptop@vger.kernel.org \
--cc=per.jessen@enidan.com \
--cc=rmk@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.