From: Andrey Panin <pazke@orbita1.ru>
To: Petr Kulhavy <brain@artax.karlin.mff.cuni.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problems with GUS PnP: ad1848, pnp
Date: Thu, 20 Dec 2001 17:57:53 +0300 [thread overview]
Message-ID: <20011220175753.A277@pazke.ipt> (raw)
In-Reply-To: <20011220104657.A195@pazke.ipt> <Pine.LNX.3.96.1011219111521.11868A-100000@artax.karlin.mff.cuni.cz>
In-Reply-To: <Pine.LNX.3.96.1011219111521.11868A-100000@artax.karlin.mff.cuni.cz>; from brain@artax.karlin.mff.cuni.cz on Wed, Dec 19, 2001 at 11:25:22AM +0100
[-- Attachment #1: Type: text/plain, Size: 920 bytes --]
On Wed, Dec 19, 2001 at 11:25:22AM +0100, Petr Kulhavy wrote:
> On Thu, 20 Dec 2001, Andrey Panin wrote:
>
> > First, don't mix isapnptools and kernel level ISAPNP support.
>
> Why? Both should set card parameters, shouldn't they? And when one sets
> parameters, the second should be able to read them (and read the same
> values).
They both touch hardware at the same time and ISA PnP handling isn't simple.
>
> > Second, send a copy of /proc/isapnp to lkml, may be we can add isapnp
> > support for your card.
>
> OK. But how do I learn if my card is supported or not?
IIRC, Gravis Ultrasound PnP listed as supported in Hardware Compatibility
HOWTO, but it can lack ISA PnP configuration support. So send us a copy
of /proc/isapnp anyway :))
--
Andrey Panin | Embedded systems software engineer
pazke@orbita1.ru | PGP key: http://www.orbita1.ru/~pazke/AndreyPanin.asc
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-12-19 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011220104657.A195@pazke.ipt>
2001-12-19 10:25 ` Problems with GUS PnP: ad1848, pnp Petr Kulhavy
2001-12-20 14:57 ` Andrey Panin [this message]
2001-12-20 19:25 ` brain
2001-12-22 9:32 ` Andrey Panin
2001-12-22 0:14 ` brain
2001-12-18 22:13 brain
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=20011220175753.A277@pazke.ipt \
--to=pazke@orbita1.ru \
--cc=brain@artax.karlin.mff.cuni.cz \
--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 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.