From: Wakko Warner <wakko@animx.eu.org>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bug in pcmcia-core
Date: Thu, 16 Jun 2005 21:48:20 -0400 [thread overview]
Message-ID: <20050617014820.GA15045@animx.eu.org> (raw)
In-Reply-To: <42B1FF2A.2080608@superbug.demon.co.uk>
James Courtier-Dutton wrote:
> I am trying to write a Linux ALSA driver for the Creative Audigy 2 NX
> Notebook PCMCIA card.
> This is a cardbus card, that uses ioports.
> When it is inserted into the laptop, the entry appears in "lspci -vv "
> showing ioports used by the card.
> As soon as my driver uses "outb()" to anything in the address range
> shown in "lspci -vv" , the PC hangs.
>
> I can only conclude from this that ioport resources are not being
> allocated correctly to the PCMCIA card.
>
> Can anybody help me track this down. If someone could tell me which
> PCMCIA and PCI registers should be set for it to work, I could then find
> out which pcmcia registers have not been set correctly, and fix the bug.
>
> It seems that the PCMCIA specification is not open and free, so I cannot
> refer to it in order to fix this myself.
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.
--
Lab tests show that use of micro$oft causes cancer in lab animals
next prev parent reply other threads:[~2005-06-17 1:31 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 [this message]
2005-06-17 7:35 ` James Courtier-Dutton
2005-06-21 15:43 ` Lee Revell
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=20050617014820.GA15045@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=James@superbug.demon.co.uk \
--cc=linux-kernel@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