linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Hinds <dhinds@sonic.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: simple question
Date: Thu, 31 Jul 2003 19:14:57 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-105967921612965@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-105967562908251@msgid-missing>

On Thu, Jul 31, 2003 at 01:53:05PM -0400, Zyman, Andy wrote:
> Hello,
> I'm trying to figure out why my SMC wireless card is not working.

What model card, specifically?

> 1. Cardbus cards are not handled by PCMCIA package ( kernel 2.4.18-14,
> pcmcia 3.1.31 )

Cardbus cards are not managed by the kernel PCMCIA subsystem.  Some of
their setup is done by the PCMCIA subsystem, but then they are handed
off to the hotplug system.

> 2. At the same time pcmcia is needed to be in the memory for hotplug
> events to be recognized by kernel.

Err not exactly.  The PCMCIA subsystem is needed to handle setup of
the CardBus bridge device.  The hotplug subsystem is a separate and
independent part of the kernel, and generates hotplug events.  Both
are needed for a Cardbus card to be set up properly.

> 3. Cardbus network cards ( ethernet and wireless ) trigger the pci.agent
> with ethX parameter and <REGISTER> event.
> 	this basically calls ifup ethX 
> 	
> Now why it calls ETHx, not wlan interface?

Most wireless drivers call their devices ETHx too.  The "ifup" will be
for whatever the device is actually named.

Perhaps you should describe your problem more specifically (i.e., show
all relevant system log messages), then we can decide if this is the
appropriate forum for your question.

-- Dave


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  reply	other threads:[~2003-07-31 19:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-31 17:53 simple question Zyman, Andy
2003-07-31 19:14 ` David Hinds [this message]
2003-07-31 20:41 ` Zyman, Andy
2003-07-31 20:59 ` David Hinds
2003-07-31 21:26 ` Joshua Schmidlkofer
  -- strict thread matches above, loose matches on Subject: below --
2006-02-19  0:12 Niv
2006-02-19  0:44 ` Greg KH
2006-02-19  2:19 ` Mark Rosenstand
2006-02-19  2:26 ` Niv

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=marc-linux-hotplug-105967921612965@msgid-missing \
    --to=dhinds@sonic.net \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).