All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Hinds <dhinds@valinux.com>
To: "Theodore Y. Ts'o" <tytso@MIT.EDU>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	rgooch@ras.ucalgary.ca, jgarzik@mandrakesoft.mandrakesoft.com,
	linux-kernel@vger.kernel.org
Subject: Re: Serial cardbus code.... for testing, please.....
Date: Mon, 11 Dec 2000 13:14:54 -0800	[thread overview]
Message-ID: <20001211131454.B31098@valinux.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10012081319010.11626-100000@penguin.transmeta.com> <200012090541.AAA17863@tsx-prime.MIT.EDU>
In-Reply-To: <200012090541.AAA17863@tsx-prime.MIT.EDU>; from Theodore Y. Ts'o on Sat, Dec 09, 2000 at 12:41:24AM -0500

On Sat, Dec 09, 2000 at 12:41:24AM -0500, Theodore Y. Ts'o wrote:
> 
> There was is usual with these sorts of things, multiple problems I was
> dealing with.  The first was that I was trying to use cardmgr, and my
> pcmcia config file was still trying to load epic_cb.  Oops.  David, you
> might want to mention of this caveat in the README-2.4 file in the
> pcmcia-cs package.

I'm aware of the problem but I'm not actually sure what to present as
the appropriate solution yet; in the new scheme, cardmgr should just
ignore these cards and not load any module at all (as /sbin/hotplug 
should do that).  But I haven't decided how cardmgr will deduce that.

By the way, in my hands, PCMCIA serial cards do work ok with the 2.4
PCMCIA modules as of test12-pre7.  So I'm not sure what's going on in
Ted's situation, if the non-kernel PCMCIA is working: there should
not be much different for 16-bit cards.  I do seem to have some new
problems with Cardbus cards that I wasn't having with earlier 2.4
releases but I haven't made any attempt to figure that out yet.

-- Dave

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-12-11 21:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.3.96.1001003164737.31485F-100000@mandrakesoft.mandrakesoft.com>
     [not found] ` <200010032248.SAA23371@tsx-prime.MIT.EDU>
     [not found]   ` <200010040118.e941IuF00625@vindaloo.ras.ucalgary.ca>
2000-12-08 18:05     ` Serial cardbus code.... for testing, please tytso
2000-12-08 21:27       ` Linus Torvalds
2000-12-08 21:34         ` David Hinds
2000-12-09  5:41         ` Theodore Y. Ts'o
2000-12-09  7:41           ` Linus Torvalds
2000-12-09 16:13             ` Jeff Garzik
2000-12-10  8:22               ` Theodore Y. Ts'o
2000-12-10 16:26                 ` Jeff Garzik
2000-12-10  7:07             ` Theodore Y. Ts'o
2000-12-10 16:19               ` Linus Torvalds
2000-12-10 16:24                 ` Jeff Garzik
2000-12-10 16:33               ` Jeff Garzik
2000-12-10 18:32                 ` Alan Cox
2000-12-09  7:48           ` Linus Torvalds
2000-12-09 13:54           ` Jens Taprogge
2000-12-09 18:13             ` Linus Torvalds
2000-12-10  7:55               ` Theodore Y. Ts'o
2000-12-11  2:57               ` Chris Wedgwood
2000-12-11 21:14           ` David Hinds [this message]
2000-12-13 16:18       ` tytso
2000-12-14 21:25       ` tytso

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=20001211131454.B31098@valinux.com \
    --to=dhinds@valinux.com \
    --cc=jgarzik@mandrakesoft.mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgooch@ras.ucalgary.ca \
    --cc=torvalds@transmeta.com \
    --cc=tytso@MIT.EDU \
    /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.