linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@transmeta.com>
To: tytso@mit.edu
Cc: rgooch@ras.ucalgary.ca, jgarzik@mandrakesoft.mandrakesoft.com,
	dhinds@valinux.com, linux-kernel@vger.kernel.org
Subject: Re: Serial cardbus code.... for testing, please.....
Date: Fri, 8 Dec 2000 13:27:51 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.10.10012081319010.11626-100000@penguin.transmeta.com> (raw)
In-Reply-To: <200012081805.eB8I5AT08790@snap.thunk.org>


I didn't have time to do more than just quickly apply the patch and leave
in a hurry, but my Vaio certainly recognized the serial port on the combo
cardbus card I have with this patch. Everything looked fine - I got a
message saying it found a 16450 on ttyS4 when I plugged the card in.

Ted, I have the in-kernel pcmcia on both Toves VAIO 505VE, and on both the
VAIO picturebooks I have (Pentium/MMX 266 and crusoe-600), and I saw the
serial chip on the first try with your patch. I'm surprised you seem to
have so many problems. All the thin-and-light VAIO's have very similar
electronics (the big power-VAIO's are different, but you said you had a
505VX, right?).

Why are you using "epic_cb"? That's almost certainly not going to work
with the in-kernel cardbus driver. Use the standard epic100 PCI driver, it
should work directly. No need to mess with any modules, or anything like
that. You don't even need cardmgr - the device just shows up. Same thing
with the serial card - remove all traces of serial_cb.

(Of course, I use tulip instead of epic100, so maybe there's an epic
driver bug, but it's definitely hotplug-aware).

			Linus

-
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/

  reply	other threads:[~2000-12-08 21:59 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 [this message]
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
2000-12-14 21:25       ` tytso
2000-12-13 16:18     ` 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=Pine.LNX.4.10.10012081319010.11626-100000@penguin.transmeta.com \
    --to=torvalds@transmeta.com \
    --cc=dhinds@valinux.com \
    --cc=jgarzik@mandrakesoft.mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgooch@ras.ucalgary.ca \
    --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 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).