From: Dominik Brodowski <linux@dominikbrodowski.net>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
"Robert P. J. Day" <rpjday@mindspring.com>,
linux-scsi@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: some PCMCIA SCSI drivers can be built *only* as modules
Date: Fri, 30 Mar 2007 16:48:11 -0400 [thread overview]
Message-ID: <20070330204811.GC11637@isilmar.linta.de> (raw)
In-Reply-To: <1174943213.3549.53.camel@mulgrave.il.steeleye.com>
On Mon, Mar 26, 2007 at 04:06:53PM -0500, James Bottomley wrote:
> On Mon, 2007-03-26 at 21:38 +0100, Christoph Hellwig wrote:
> > On Mon, Mar 26, 2007 at 03:35:47PM -0500, James Bottomley wrote:
> > > I agree the non-legacy (CardBus and beyond) ones can be built in. I
> > > thought the legacy 8 and 16 bit type I and II still had to be modular
> > > because they still need setting up.
> >
> > nope. While I don't have a pcmcia scsi card my 16 bit pcmcia wireless
> > cards work perfectly fine without any previous setup.
>
> OK ... I had the opposite experience ... A ZoomAir 802.11b card wasn't
> working because I'd accidentally config'd it non-modular. However, if
> Dominik confirms it's all supposed to work non-modular.
PCMCIA card drivers should (famous last words) work just fine if built as
modules. They may not be bound to devices, depending on the arch and
system, until userspace tools have run, but this is independent of modular
or built-in drivers. So a full ACK on this.
Thanks,
Dominik
prev parent reply other threads:[~2007-03-30 20:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0703250916090.22484@CPE00045a9c397f-CM001225dbafb6>
2007-03-26 13:27 ` some PCMCIA SCSI drivers can be built *only* as modules Stefan Richter
2007-03-26 20:02 ` Christoph Hellwig
2007-03-26 20:06 ` Robert P. J. Day
2007-03-26 20:31 ` Stefan Richter
2007-03-26 20:35 ` James Bottomley
2007-03-26 20:38 ` Christoph Hellwig
2007-03-26 21:06 ` James Bottomley
2007-03-30 20:48 ` Dominik Brodowski [this message]
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=20070330204811.GC11637@isilmar.linta.de \
--to=linux@dominikbrodowski.net \
--cc=James.Bottomley@SteelEye.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rpjday@mindspring.com \
--cc=stefanr@s5r6.in-berlin.de \
/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