From: Lee Revell <rlrevell@joe-job.com>
To: James Courtier-Dutton <James@superbug.co.uk>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Creative Audigy 4
Date: Sat, 04 Dec 2004 16:43:51 -0500 [thread overview]
Message-ID: <1102196632.28776.43.camel@krustophenia.net> (raw)
In-Reply-To: <41B22DC8.2080704@superbug.co.uk>
On Sat, 2004-12-04 at 21:36 +0000, James Courtier-Dutton wrote:
> I found it.
> I quote:
Heh, I just posted the exact same info.
What do you think is the best long term solution? We can't expect every
user to add that sequence to modules.conf.
This seems like something the driver should do. After all, just because
you can set a register via /proc does not mean you should have to, if
it's something the driver should obviously do. I think this qualifies,
since this is necessary to get the port to work at all. Basic hardware
initialization should not be left to userspace.
Besides, the driver _knows_ whether the device is an Audigy 2 ZS,
whereas userspace would have to extract this from lspci or something.
Lee
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-04 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 21:15 Creative Audigy 4 James Courtier-Dutton
2004-12-04 21:20 ` Lee Revell
2004-12-04 21:36 ` James Courtier-Dutton
2004-12-04 21:43 ` Lee Revell [this message]
2004-12-04 22:06 ` James Courtier-Dutton
2004-12-09 15:00 ` Takashi Iwai
2004-12-04 21:36 ` Lee Revell
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=1102196632.28776.43.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=James@superbug.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
/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.