From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Adam Belay <ambx1@neo.rr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bug in pcmcia-core
Date: Sat, 13 Aug 2005 23:31:41 +0100 [thread overview]
Message-ID: <42FE74CD.4040108@superbug.demon.co.uk> (raw)
In-Reply-To: <20050711210834.GA4898@neo.rr.com>
Adam Belay wrote:
> On Thu, Jun 16, 2005 at 11:37:30PM +0100, James Courtier-Dutton wrote:
>
>>Hi,
>>
>>I have tried conacting the mailing list for the PCMCIA subsystem in
>>Linux, but no-one seems to respond.
>>
>>PCMCIA SUBSYSTEM
>>L: http://lists.infradead.org/mailman/listinfo/linux-pcmcia
>>S: Unmaintained
>>
>>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.
>
>
> It's possible.
>
>
>>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.
>>
>>Can anybody help me?
>>
>>James
>
>
> Please provide more information. /proc/ioports, lspci -vv, the ranges
> assigned to your driver, and your driver code if it's available. I'll try
> to look into the problem.
>
> Thanks,
> Adam
>
>
Please see bug#5057. I have placed all the information there.
http://bugzilla.kernel.org/show_bug.cgi?id=5057
James
next prev parent reply other threads:[~2005-08-13 22: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
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 [this message]
-- 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=42FE74CD.4040108@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=ambx1@neo.rr.com \
--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;
as well as URLs for NNTP newsgroup(s).