linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Narayan Desai <desai@mcs.anl.gov>
Cc: Russell King <rmk@arm.linux.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: weird pcmcia problem
Date: Tue, 19 Aug 2003 00:47:00 -0400	[thread overview]
Message-ID: <200308190447.h7J4l0Vq004410@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 18 Aug 2003 19:34:59 CDT." <87u18efpsc.fsf@mcs.anl.gov>

[-- Attachment #1: Type: text/plain, Size: 1900 bytes --]

On Mon, 18 Aug 2003 19:34:59 CDT, Narayan Desai <desai@mcs.anl.gov>  said:
> Running 2.6.0-test3 (both with and without your recent yenta socket
> patches) pcmcia cards present during boot don't show up until they are
> removed and reinserted. Once reinserted, they work fine. This only
> seems to occur if yenta_socket is build into the kernel; if support is
> modular, cards appear to be recognized properly at boot time. I am
> running on a thinkpad t21.  Let me know if I can help with this
> problem in any way...  thanks

Same issue on 2.6.0-test3-mm2 on a Dell Latitude C840 with a TrueMobile 1150
wireless (uses orinoco_cs driver) - card is recognized at boot, and somewhat
configured:

Aug 18 11:16:52 turing-police kernel: eth1: Station identity 001f:0001:0008:000a
Aug 18 11:16:53 turing-police kernel: eth1: Looks like a Lucent/Agere firmware version 8.10
Aug 18 11:16:53 turing-police kernel: eth1: Ad-hoc demo mode supported
Aug 18 11:16:53 turing-police kernel: eth1: IEEE standard IBSS ad-hoc mode supported
Aug 18 11:16:53 turing-police kernel: eth1: WEP supported, 104-bit key
Aug 18 11:16:53 turing-police kernel: eth1: MAC address 00:02:2D:5C:11:48
Aug 18 11:16:53 turing-police kernel: eth1: Station name "HERMES I"
Aug 18 11:16:53 turing-police kernel: eth1: ready
Aug 18 11:16:53 turing-police kernel: eth1: index 0x01: Vcc 3.3, irq 11, io 0x0100-0x013f

but it takes a 'cardctl eject 2;cardctl insert 2' to actually finish the job
and get things started (actually popping the card out not required, and not
possible, it's a built-in). Relevant .config:

CONFIG_YENTA=y
CONFIG_HERMES=y
# CONFIG_PLX_HERMES is not set
# CONFIG_TMD_HERMES is not set
CONFIG_PCI_HERMES=y
CONFIG_PCMCIA_HERMES=y

I'm wondering if this is a cardmgr/hotplug bug - if they can't insmod the Yenta
support, they don't realize that it could already be onboard so they don't even
try to start the cards?


[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  parent reply	other threads:[~2003-08-19  4:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-19  0:34 weird pcmcia problem Narayan Desai
2003-08-19  1:11 ` Jamie Lokier
2003-08-19  4:47 ` Valdis.Kletnieks [this message]
     [not found]   ` <200308191816.h7JIGNBC002405@turing-police.cc.vt.edu>
2003-08-19 18:19     ` Russell King
2003-08-19 19:22       ` Valdis.Kletnieks
2003-08-19  8:34 ` Russell King
2003-08-19 19:12   ` Sven Dowideit
2003-08-19 11:45 ` Russell King
2003-08-19 13:46   ` Henrik Persson
2003-08-19 14:19   ` Narayan Desai
2003-08-19 23:35   ` Sven Dowideit
2003-08-19 23:46   ` Sven Dowideit

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=200308190447.h7J4l0Vq004410@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=desai@mcs.anl.gov \
    --cc=linux-kernel@vger.kernel.org \
    --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 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).