public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Belay <ambx1@neo.rr.com>
To: Jaroslav Kysela <perex@perex.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [alsa, pnp] more on opl3sa2 (fwd)
Date: Thu, 30 Jan 2003 22:24:01 +0000	[thread overview]
Message-ID: <20030130222401.GH2246@neo.rr.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0301300940090.1445-100000@pnote.perex-int.cz>

Hi Jaroslav,

How does this sound...

What if we make pnp card services match against all pnp cards and allow more
than one card driver to use the same card.  This can be accomplished if we detach
the card portion from the driver model and use driver_attach.  If you feel it is
necessary, we could also add an optional card id to the pnp_device_id structure.
As for the pnpbios, I disagree with putting it under one card.  If the pnpbios
contains two opl3sa2 sound cards then only one will be matched and therefore it
is a bad idea to represent the pnpbios as a card.  When ACPI is introduced, both
pnpbios and ACPI will be cardless protocols.  Therefore I think it is best to 
use the pnp_driver structure instead of the pnpc_driver structure in the
opl3sa2 ALSA driver.

Any aditional comments?

Regards,
Adam

  reply	other threads:[~2003-01-31  3:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0301271534210.2937-100000@pnote.perex-int.cz>
2003-01-29 22:12 ` [alsa, pnp] more on opl3sa2 (fwd) Adam Belay
2003-01-30  8:45   ` Jaroslav Kysela
2003-01-30 22:24     ` Adam Belay [this message]
2003-02-03 14:15       ` Jaroslav Kysela
2003-02-05 22:01         ` Adam Belay
2003-02-09 17:55           ` Jaroslav Kysela

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=20030130222401.GH2246@neo.rr.com \
    --to=ambx1@neo.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    /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