On Mon, 2005-10-24 at 15:41 -0400, Stephen P. Becker wrote:
> Chris Gianelloni wrote:
> > On Mon, 2005-10-24 at 11:03 -0400, Stephen P. Becker wrote:
> > 
> >>>What would be your recommendation on how to handle this for mips, then?
> >>>Make the virtual alsa-driver?
> >>
> >>This wouldn't work, as none of our alsa drivers are actually provided by 
> >>alsa-driver.
> > 
> > 
> > OK.  How does it work now, then?
> > 
> > ...and please provide me with any information that you think I might
> > need or even a suggestion on what you want.  This having to email back
> > and forth is tiresome.
> > 
> 
> If you are so concerned with getting this issue hammered out without 
> more than one email, you should have just pinged one of us on irc. 
> What's wrong with having an ongoing discussion on a mailing list where 
> anybody might be able to chip in to the conversation?

My point was really that if you know pertinent information, why make
someone ask for it over and over again.

> Currently, we have two machines with alsa drivers (only one of which 
> *really* works, but that is beside the point), and the working driver is 
> applied to our mips-sources-2.6.* ebuilds along with the patchset for 
> octane.  However, this information is pretty irrelevent from my point of 
> view.  The real problems are that A) alsa-driver doesn't contain any 
> mips drivers, B) 2.4 kernel sources do not contain the alsa drivers 
> while 2.6 do, and C) that mips-sources included both 2.4 and 2.6. 
> Therefore, we really do not have anything generic that can be changed to 
> the default virtual for us without being broken (until such time as we 
> can finally get rid of 2.4).  I don't have a solution at this point in 
> time either...I'm just saying how things are.

This is exactly the kind of information that I was looking for when I
asked.  Thank you.

As I understand it, the only working ALSA driver that you have it part
of mips-sources.  It would make sense to me for that to be the default
virtual, as it would work for at least some people, versus the current
situation where it works for none.

> Unfortunately, we don't have any member of the mips team that really 
> does much with sound (where did that Indy go to anyway?), so I'm not 
> sure any of us are going to be able to give you a satisfying answer or 
> solution.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux