On 21 Jun, Paul Tomlin wrote:
> Guys,
> I am getting the impression that the new code Brent put
> together works for many people but still not for Brent.
> Ironic (if its true).
Well, I guess better this way than it working for me and nobody else :-)
Seriously, I would like to hear some reports from people with DBRIs;
what works; what doesn't...
> I was wondering about the problem with the output volume.
> Is this something which needs to be changed in the driver?
> Does the DBRI not work normally with mixers (aumix) because
> of HW design or unimplemented features of the driver.
aumix doesn't work because of the way sparcaudio is designed. It's
completely seperate from the normal Linux sound code, and is designed
to mimic SunOS/Solaris audio ioctl's, to allow things like realaudio to
be run in emulation mode. Since aumix uses Linux sound ioctl's, it
doesn't work with the DBRI or any other sparcaudio device.
I don't have any plans to fix this, because I'm not too thrilled with
this design, and don't plan to put any more effort into the sparcaudio
midlevel (the device-independant part). The device drivers themselves
would be useful for integration into the standard Linux sound drivers,
which could then be augmented to recognize Sun ioctl's. This would
allow aumix to work with DBRI, as well as allowing (for example) a
soundblaster card to be plugged into a PCI-bus SPARC and run realaudio
in emulation.
I have no plans to do any of this any time soon. In the meantime, you
can:
1) modify aumix to use the Sun ioctls if invoked with an appropriate
option, or
2) find some existing tool that adjusts volume on a SunOS system, or
3) use the yet-to-be-implemented module option that lets you set the
volume at load time
> Ditto for the Type 5 volume keys. I have looked at some code
> for the Sun kb's and there are definitions for the keys. But
> without a great deal more knowledge (on my part) I am unlikely
> to be able to help too much.
Good question. I suspect that with an appropriate aumix, X windows
could be convinced to recognize the keys and adjust the volume. I
don't know of any generic way to grab three keys off the keyboard and
direct them to some arbitrary application, though. I guess some
special code could be put in the kernel to grab those keys and call
volume adjusting routines in sparcaudio. Comments?
> The last question, promise, is SMP support. How complicated
> are the changes to the driver required to make it SMP safe,
> and how high up the list is this.
It's definately on the list, but higher is getting the code running
stable on a single CPU. The ISDN side, in particular, is still just
too easy to crash. I'll probably end up putting a spinlock in the
DBRI's driver structure, and just have all the code wait on it before
starting to change things. Something more clever could be designed,
but I don't think it'll be neccessary.
--
-bwb
Brent Baccala
[EMAIL PROTECTED]
-------------------------------------------------------------------------
To receive periodic news about what's happening at freesoft.org, send
email to "[EMAIL PROTECTED]", with "SUBSCRIBE" as the message, i.e:
echo SUBSCRIBE | mail [EMAIL PROTECTED]
-------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of the message to [EMAIL PROTECTED]
