Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Rick Wright <riwright@vt.edu>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: emu10k1 multichannel issue/observation
Date: Sun, 30 Oct 2005 19:50:26 -0500	[thread overview]
Message-ID: <1130719826.32101.2.camel@mindpipe> (raw)
In-Reply-To: <43656175.3040303@vt.edu>

On Sun, 2005-10-30 at 19:12 -0500, Rick Wright wrote:
> 
> Lee Revell wrote: 
> > On Fri, 2005-10-28 at 21:09 -0400, Rick Wright wrote:
> >   
> > > My questions are:
> > > 1) Was there an early version(s) of this card where the side channels
> > > aren't supported by the ALSA driver?
> > >     
> > 
> > Possible.
> > 
> >   
> > > 2) Could this be made to work?
> > >     
> > 
> > Yes.
> > 
> >   
> > > 3) If so, what info is needed and who needs it?
> > >     
> > 
> > Please provide lspci output for the new card (working side channels) and
> > the old one (non working side channels).
> > 
> >   
> Attached are the outputs of lspci for both working/non-working side
> channel machines.
> 
> These machines are basically clones and the Audigy2 card is in the
> same PCI slot in both machines.
> 

Sorry I should have been more specific.  I need 
"lspci -vn | grep -A1 0401" output for both machines.

Lee




-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information

  reply	other threads:[~2005-10-31  0:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <434E7646.3000507@poeticstudios.com>
     [not found] ` <5bdc1c8b0510221502v28a2cbe0ybfe049be2f34e186@mail.gmail.com>
     [not found]   ` <200510230053.44479.Martin.Wohlleben@gmx.de>
     [not found]     ` <5bdc1c8b0510221655r4d28430fr7b80f5403d8daaa4@mail.gmail.com>
     [not found]       ` <435AF023.70903@woh.rr.com>
     [not found]         ` <5bdc1c8b0510221957s278a28a7n8ead2de1e0760cf6@mail.gmail.com>
     [not found]           ` <435B74E9.20308@woh.rr.com>
     [not found]             ` <20051023180312.GA4544@mobilat.informatik.uni-bremen.de>
     [not found]               ` <5bdc1c8b0510231123h5ed64b38nd178ce9dfcb13f87@mail.gmail.com>
     [not found]                 ` <1130097599.11980.54.camel@mindpipe>
     [not found]                   ` <5bdc1c8b0510231318j4e9db7b0x1106e9b240329249@mail.gmail.com>
     [not found]                     ` <435CFC95.6000703@vt.edu>
     [not found]                       ` <1130170444.16563.22.camel@mindpipe>
2005-10-29  1:09                         ` emu10k1 multichannel issue/observation Rick Wright
2005-10-29  2:27                           ` Lee Revell
2005-10-31  0:12                             ` Rick Wright
2005-10-31  0:50                               ` Lee Revell [this message]
2005-10-31 16:03                                 ` Rick Wright
2005-11-05 19:24                                   ` Lee Revell
2005-11-07 14:54                                     ` Takashi Iwai
2005-11-07 18:19                                     ` Rick Wright

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=1130719826.32101.2.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=riwright@vt.edu \
    /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