Re: Non-working snd-pcsp

[Stas Sergeev <stsp@xxxxxxxx>]

Hello.

Jan Engelhardt wrote:
> Previously, with Stas's standalone patch, one was able to switch
> between (a) no speaker (b) beep/pcspkr (c) beep/pcspkr and
> PCM/snd-pcsp, all by means of modprobe/rmmod.
But now you can get any such combination
by the use of alsamixer only.

> Except if snd-pcsp itself contains beep code, and that would
> be sort of redundant when it is already in pcspkr.
It is redundant only if you _intend_
to use both drivers. But its usually
a bad idea to have multiple drivers
serving the single device simultaneously.
The other way of thinking about it,
is that you simply use a new driver
instead of an old one. The new one
does everything the old one did and
more. Since they can't be built together,
the redundancy is then only in a source
code.
I am not saying it is an ideal solution.
It is not, but for only a single reason -
people who need only beeps, may not
want to have the entire sound subsystem
loaded. So they want pcspkr to be at
least built. But getting these drivers
back together again, suddenly became
very problematic...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/