linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Compiling cardbus devices monolithic doesn't work?
Date: Mon, 18 Aug 2003 15:34:37 -0400	[thread overview]
Message-ID: <200308181534.37586.rob@landley.net> (raw)
In-Reply-To: <20030818084411.A26743@flint.arm.linux.org.uk>

Ahem, second attempt:

On Monday 18 August 2003 03:44, Russell King wrote:

> You still need to use cardmgr to bind the driver to the device.
> It seems to work for me here on SA11x0 platforms, and I'm not aware
> of it breaking at any point in the 2.5 series.
>
> While it is true that Cardbus devices plugged into cardbus slots do
> not need cardmgr, PCMCIA devices still do.

The hotplug scripts from RH9 are there and seem happy, I thought cardmgr was 
called from them.  (The same setup works in 2.4.21, albeit with modules 
enabled.  I should compile a monolithic 2.4 kernel and see what it does...)

> > (P.S.  And while I'm at it, what's the relationship between orinoco_cs,
> > orinoco, and hermes?  The /proc/modules dependency tree thing says
> > they're using each other in a chain.  Probably true, just a bit odd, I
> > thought. Couldn't figure out which driver I needed, compiled all three,
> > and it loaded ALL of them.  Can't complain, the card works under 2.4. 
> > This is just a random "huh?")
>
> IIRC hermes provides the low level interface to the device, orinoco
> provides the interface between it and the network stack, and orinoco_cs
> provides a bridge between the PCMCIA subsystem and orinoco.

Now I'm confused.  I thought the _cs on the end was short for "cardbus"...

Rob

  parent reply	other threads:[~2003-08-18 19:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-18  1:58 Compiling cardbus devices monolithic doesn't work? Rob Landley
2003-08-18  7:44 ` Russell King
2003-08-18 19:31   ` Rob Landley
2003-08-18 19:34   ` Rob Landley [this message]
2003-08-18 19:43     ` Randy.Dunlap

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=200308181534.37586.rob@landley.net \
    --to=rob@landley.net \
    --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).