All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: Wakko Warner <wakko@animx.eu.org>, linux-kernel@vger.kernel.org
Subject: Re: Bug in pcmcia-core
Date: Tue, 21 Jun 2005 11:43:14 -0400	[thread overview]
Message-ID: <1119368594.19357.22.camel@mindpipe> (raw)
In-Reply-To: <42B27D51.4040407@superbug.demon.co.uk>

On Fri, 2005-06-17 at 08:35 +0100, James Courtier-Dutton wrote:
> > 
> > I thought drivers for the cardbus cards were the same as standard PCI cards. 
> > I know that as far as networking goes, the same driver runs a cardbus 3com
> > 3c575 and the pci 3c905.  Same with netgear's cardbus FA510 and PCI FA310.
> > 
> > I'm not a kernel developer, but this is what I've understood.
> > 
> 
> That is also what I thought. But I think that the cardbus 3com 3c575
> uses memory for io and not ioports. I think the problem is related to
> the use of ioports on an cardbus card.

Any update on this?  Is the PCMCIA layer really unmaintained?  Are we
hosed?

A quick grep of the subjects in my LKML folder for "PCMCIA" is certainly
not encouraging.  I see lots of questions along the lines of "did ANYONE
EVER get this to work?" with no replies...

Lee


  reply	other threads:[~2005-06-21 15:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-16 22:37 Bug in pcmcia-core James Courtier-Dutton
2005-06-17  1:48 ` Wakko Warner
2005-06-17  7:35   ` James Courtier-Dutton
2005-06-21 15:43     ` Lee Revell [this message]
2005-06-21 16:53       ` Dominik Brodowski
2005-06-21 17:44         ` Lee Revell
2005-06-21 18:03           ` James Courtier-Dutton
2005-07-11 21:00             ` Lee Revell
2005-07-11 21:08 ` Adam Belay
2005-08-13 22:31   ` James Courtier-Dutton
  -- strict thread matches above, loose matches on Subject: below --
2005-06-16 14:55 James Courtier-Dutton

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=1119368594.19357.22.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=James@superbug.demon.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wakko@animx.eu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.