mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kay Sievers" <kay.sievers@vrfy.org>
To: greg@enjellic.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: PCMCIA serial_cs driver binding problems.
Date: Fri, 23 Nov 2007 09:40:47 +0100	[thread overview]
Message-ID: <3ae72650711230040t421af579xa92208ecbf20a0e2@mail.gmail.com> (raw)
In-Reply-To: <200711201408.lAKE8WMp001714@wind.enjellic.com>

On Nov 20, 2007 3:08 PM,  <greg@enjellic.com> wrote:
> I'm working to sort out what appear to be issues with binding of the
> serial_cs driver to a PCMCIA wireless card (Zoom).
>
> Card works perfectly in recent 2.6.2[23] kernels if cardmgr is running
> and PCMCIA_IOCTL support is in the kernel.  The serial_cs driver
> fails, however, to bind in a pure hotplug configuration.  The hotplug
> scripts detect card insertion and load the serial_cs module but the
> driver doesn't bind to the device.
>
> The slot number (0.0 or 1.0) appears in the /sys/bus/pcmcia/devices
> directory after card insertion.  The serial_cs directory also presents
> in the /sys/bus/pcmcia/drivers directory secondary to module load.
>
> I've tried to manually echo the device number (0.0 or 1.0) into the
> /sys/bus/pcmcia/drivers/serial_cs/bind pseudo-file but nothing
> happens.  The device number is present as a binding if cardmgr frobs
> things with the pcmcia_ioctl bind commands.

Did you enable this?
  echo -n 1 > /sys/devices/pci0000:00/0000:00:1e.0/0000:15:00.0/0.0/allow_func_id_match

You can watch "udevmonitor --kernel" while doing this, to get the path and
see what events the kernel creates.

Distros usually set it automatically by udev:
  ACTION=="add", SUBSYSTEM=="pcmcia", ENV{MODALIAS}=="?*",
ATTR{allow_func_id_match}="1"

Kay

  reply	other threads:[~2007-11-23  8:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-20 14:08 greg
2007-11-23  8:40 ` Kay Sievers [this message]
2007-11-26 16:26 greg

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=3ae72650711230040t421af579xa92208ecbf20a0e2@mail.gmail.com \
    --to=kay.sievers@vrfy.org \
    --cc=greg@enjellic.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®