mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Lee Revell <rlrevell@joe-job.com>
Cc: James Courtier-Dutton <James@superbug.demon.co.uk>,
	Wakko Warner <wakko@animx.eu.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Bug in pcmcia-core
Date: Tue, 21 Jun 2005 18:53:03 +0200	[thread overview]
Message-ID: <20050621165303.GA14487@isilmar.linta.de> (raw)
In-Reply-To: <1119368594.19357.22.camel@mindpipe>

Hi,

On Tue, Jun 21, 2005 at 11:43:14AM -0400, Lee Revell wrote:
> 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?

Check the linux-pcmcia list, check -mm and you'll see that the PCMCIA layer
is in the process of being updated.

> 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...

Well, some of them are handled in the background, some are simply unsolvable
(no real reason for hardware to behave the way it does, no driver support,
extremely strange setups, ...), some bugs are caused elsewhere (e.g., in
current -mm, PCI makes life difficult for PCMCIA), and some bugs are not
handled at all because the few developers taking care of PCMCIA do have too
few time. So, some help in maintaining PCMCIA is much appreciated.

	Dominik

  reply	other threads:[~2005-06-21 16:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-16 22:37 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
2005-06-21 16:53       ` Dominik Brodowski [this message]
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=20050621165303.GA14487@isilmar.linta.de \
    --to=linux@dominikbrodowski.net \
    --cc=James@superbug.demon.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome