public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Stephen P. Becker" <geoman@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-core] Re: [gentoo-dev] Possible virtual/alsa change
Date: Mon, 24 Oct 2005 15:41:26 -0400	[thread overview]
Message-ID: <435D38E6.50200@gentoo.org> (raw)
In-Reply-To: <1130167272.9045.24.camel@cgianelloni.nuvox.net>

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?

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.

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.

-Steve
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-10-24 19:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-17 18:25 [gentoo-dev] Possible virtual/alsa change Chris Gianelloni
2005-10-17 18:42 ` Diego 'Flameeyes' Pettenò
2005-10-17 19:08   ` Jan Kundrát
2005-10-24 10:50     ` Shyam Mani
2005-10-24 13:11       ` Chris Gianelloni
2005-10-24 13:18         ` [gentoo-core] " Stephen P. Becker
2005-10-24 13:30           ` Chris Gianelloni
2005-10-24 13:56             ` Stephen P. Becker
2005-10-24 14:54               ` Chris Gianelloni
2005-10-24 15:03                 ` Stephen P. Becker
2005-10-24 15:21                   ` Chris Gianelloni
2005-10-24 19:41                     ` Stephen P. Becker [this message]
2005-10-24 19:25                       ` Ciaran McCreesh
2005-10-25  2:22                       ` Chris Gianelloni
2005-10-27 18:13                       ` John Mylchreest
2005-10-27 18:28                         ` Stephen P. Becker
2005-10-27 18:37                           ` John Mylchreest

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=435D38E6.50200@gentoo.org \
    --to=geoman@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox