All of lore.kernel.org
 help / color / mirror / Atom feed
From: The Source <thesourcehim@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: X-Fi notebook support
Date: Tue, 12 Jan 2010 19:52:34 +0300	[thread overview]
Message-ID: <4B4CA8D2.30303@gmail.com> (raw)
In-Reply-To: <4B4C1EA7.3060305@gmail.com>

12.01.2010 10:03, The Source пишет:
> 30.12.2009 21:25, The Source пишет:
>> 30.12.2009 19:22, The Source пишет:
>>> 30.12.2009 10:39, The Source пишет:
>>>> Hello. I have some info on that card, but not much. I have 
>>>> discovered that this card is detected connected via USB rather than 
>>>> PCI-E (the slot is ExpressCard). snd_ctxfi uses PCI interfaces 
>>>> right? Can X-Fi support be also added to snd_usb_audio? Or can 
>>>> snd_ctxfi support USB?
>>>>
>>>> lsusb -v output on that card is attached (sorry for duplicate mail, 
>>>> forgot to attach it first time). I now have this card and willing 
>>>> to help to test (or perhaps create) proper driver.
>>> Additional info. The card is partially recognized - Analog Stereo 
>>> Input device is available. But sadly no output.
>>> Also I tested the card in Virtual Box (WinXP 64 guest) and even 
>>> without creative drivers the card is recognized as USB Audio Device 
>>> and works fine. So it seems it's usb audio compliant. I hope this is 
>>> helpful.
>> Hmm, it looks like Input working is the result of my addition to 
>> alsa-kernel/usb/usbquirks.h
>> Recording from mic now works (on very low volume though)
>>
>> /* Creative X-Fi Notebook */
>> {
>>     .match_flags = USB_DEVICE_ID_MATCH_VENDOR | 
>> USB_DEVICE_ID_MATCH_PRODUCT,
>>     .idVendor = 0x041e,
>>     .idProduct = 0x30d2,
>>     .bInterfaceClass = USB_CLASS_AUDIO,
>>     .driver_info = (unsigned long) & (const struct 
>> snd_usb_audio_quirk) {
>>         .vendor_name = "Creative Labs",
>>         .product_name = "X-Fi Notebook",
>>         .ifnum = QUIRK_NO_INTERFACE
>>     }
>> },
>>
>> I tested some other quirk values but nothing else works at all. As 
>> for output - alsamixer actually shows it and allows to change it's 
>> volume, but channel number is not available. For example speaker-test 
>> says 'Error setting hwparams: Invalid argument" and aplay says 
>> "Channel number is not available" on any channel number.
>> alsa-info output is attached.
>> I ask for any help from experienced alsa developer (snd_usb_audio 
>> specifically).
>
> I found out that 6 is the only valid number for channels. Sound is 
> played fine when channels is set to 6. Other values like 2 result in 
> 'invalid argument'
Latest test results: if the card is plugged before system starts, 
everything is fine. All output devices is seen by everyone including 
pulseaudio. No such luck if the card is hotplugged. I wonder why?
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2010-01-12 16:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-30  7:39 X-Fi notebook support The Source
2009-12-30 16:22 ` The Source
2009-12-30 18:25   ` The Source
2010-01-12  7:03     ` The Source
2010-01-12 16:52       ` The Source [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-12-30  7:37 The Source

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=4B4CA8D2.30303@gmail.com \
    --to=thesourcehim@gmail.com \
    --cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.