From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Albrecht Dreß" <ad@mpifr-bonn.mpg.de>, linuxppc-dev@lists.linuxppc.org
Subject: Re: PCMCIA on a Pismo with pcmcia-cs-3.1.24
Date: Mon, 12 Feb 2001 12:08:49 +0100 [thread overview]
Message-ID: <19350107044033.16629@mailhost.mipsys.com> (raw)
In-Reply-To: <3A87A3F6.6A9CA4C7@mpifr-bonn.mpg.de>
>
>> 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/
next prev parent reply other threads:[~2001-02-12 11:08 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 [this message]
2001-02-12 11:20 ` Albrecht Dreß
2001-02-13 17:50 ` Michael K. Fleming
2001-02-14 11:02 ` Albrecht Dreß
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=19350107044033.16629@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=ad@mpifr-bonn.mpg.de \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).