From: Eliot Blennerhassett <linux@audioscience.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: asihpi - hwdep
Date: Sat, 23 Feb 2008 20:41:48 +1300 [thread overview]
Message-ID: <200802232041.48913.linux@audioscience.com> (raw)
In-Reply-To: <75b66ecd0802221652s6dd2a56fye01616b5e17c93aa@mail.gmail.com>
Thanks Lee,
On Saturday 23 February 2008 13:52:13 Lee Revell wrote:
> On Fri, Feb 22, 2008 at 4:10 PM, Eliot Blennerhassett
>
> <linux@audioscience.com> wrote:
>I just don't know enough
> > about how to start on hwdep implementation.
>
> Please take a look at snd_emu10k1_fx8010_ioctl in
> alsa-kernel/pci/emu10k1/emufx.c for examples of hwdep ioctl usage.
that wasn't too hard. I have implemented stubs just to see how it fits
together.
It doesn't do quite what I want. The existing HPI ioctl has one device file
for the driver, whether one or sixteen cards are installed, and its name
doesn't change depending on the card index. (I.e. userspace accesses the
whole (HPI) audio subsystem through the one /dev/asihpi)
ALSA makes one device file per card, and the file name depends on the card
index. Is there any way I can make a single device for the driver that has
an unchanging name (preferably /dev/asihpi)
regards
--
--
Eliot Blennerhassett
www.audioscience.com
next prev parent reply other threads:[~2008-02-23 7:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 23:26 asihpi - how much further? Eliot Blennerhassett
2008-02-22 17:14 ` Takashi Iwai
2008-02-22 21:10 ` Eliot Blennerhassett
2008-02-23 0:52 ` Lee Revell
2008-02-23 7:41 ` Eliot Blennerhassett [this message]
2008-02-23 10:46 ` asihpi - hwdep Takashi Iwai
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=200802232041.48913.linux@audioscience.com \
--to=linux@audioscience.com \
--cc=alsa-devel@alsa-project.org \
--cc=rlrevell@joe-job.com \
--cc=tiwai@suse.de \
/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.