From: The Source <thesourcehim@gmail.com>
To: Daniel Mack <daniel@caiaq.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: usbaudio: Support for USB audio v2.0 devices
Date: Tue, 27 Apr 2010 21:27:15 +0400 [thread overview]
Message-ID: <4BD71E73.5020106@gmail.com> (raw)
In-Reply-To: <20100427154346.GH30801@buzzloop.caiaq.de>
27.04.2010 19:43, Daniel Mack пишет:
> On Tue, Apr 27, 2010 at 07:29:52PM +0400, The Source wrote:
>
>> 27.04.2010 18:07, Daniel Mack пишет:
>>
>>> On Tue, Apr 27, 2010 at 05:31:35PM +0400, The Source wrote:
>>>
>>>> Perhaps I should've posted my problem in this thread earlier. Here's the
>>>> summary:
>>>> Creative X-Fi Notebook stopped working after upgrading from 1.0.22.1 to
>>>> 1.0.23 (worked just fine before).
>>>> dmesg gives the following:
>>>>
>>>> usb 8-2: new full speed USB device using uhci_hcd and address 2
>>>> usb 8-2: New USB device found, idVendor=041e, idProduct=30d2
>>>> usb 8-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
>>>> usb 8-2: Product: SB X-Fi Notebook
>>>> usb 8-2: Manufacturer: Creative Technology Ltd
>>>> usb 8-2: configuration #1 chosen from 1 choice
>>>> input: Creative Technology Ltd SB X-Fi Notebook as
>>>> /devices/pci0000:00/0000:00:1d.2/usb8/8-2/8-2:1.3/input/input11
>>>> generic-usb 0003:041E:30D2.0002: input,hidraw1: USB HID v1.11 Device
>>>> [Creative Technology Ltd SB X-Fi Notebook] on usb-0000:00:1d.2-2/input3
>>>> input: Creative Technology Ltd SB X-Fi Notebook as
>>>> /devices/pci0000:00/0000:00:1d.2/usb8/8-2/8-2:1.4/input/input12
>>>> generic-usb 0003:041E:30D2.0003: input,hidraw2: USB HID v1.11 Keyboard
>>>> [Creative Technology Ltd SB X-Fi Notebook] on usb-0000:00:1d.2-2/input4
>>>> ALSA pcm.c:174: 2:1:1: endpoint lacks sample rate attribute bit, cannot
>>>> set.
>>>> ALSA pcm.c:174: 2:2:1: endpoint lacks sample rate attribute bit, cannot
>>>> set.
>>>>
>>> And you say this is a regression from earlier versions? Would you be
>>> able to bisect this problem?
>>>
>>> Daniel
>>>
>>>
>> Gladly, if you just tell me how :)
>>
> You would check out the latest mainline sources:
>
> $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> $ cd linux-2.6
>
> Then create a branch and merge the latest ALSA patches:
>
> $ git checkout -b alsa
> $ git pull git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git
>
> Then build and install the kernel and verify it still shows the error.
> Start the bisect and mark the current revision as 'bad':
>
> $ git bisect start
> $ git bisect bad
>
> Assuming that v2.6.34-rc5 (before the merge) still works, you would mark
> this as 'good':
>
> $ git bisect good v2.6.34-rc5
>
> git will now iterate you thru the changes and drop you off at chosen
> points. Just compile the tree you get, and tell git whether this is a
> good or bad one:
>
> $ git bisect good
> or
> $ git bisect bad
>
> Then recompile and test again After some steps, it will tell you which
> commit precisely broke it.
>
> HTH,
> Daniel
>
>
>
I'll try that. But is there any way to do this just with alsa and not
with entire kernel? Compiling kernel is a loooong process.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2010-04-27 17:27 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 16:28 usbaudio: Support for USB audio v2.0 devices Daniel Mack
2010-02-22 16:28 ` [PATCH 1/4] ALSA: usbaudio: parse USB descriptors with structs Daniel Mack
2010-02-22 16:28 ` [PATCH 2/4] ALSA: usbaudio: introduce new types for audio class v2 Daniel Mack
2010-02-22 16:28 ` [PATCH 3/4] ALSA: usbaudio: implement basic set of class v2.0 parser Daniel Mack
2010-02-22 16:28 ` [PATCH 4/4] ALSA: usbmixer: bail out early when parsing audio class v2 descriptors Daniel Mack
2010-02-22 17:40 ` usbaudio: Support for USB audio v2.0 devices Clemens Ladisch
2010-02-22 17:50 ` Daniel Mack
2010-03-02 9:13 ` adelias
2010-03-02 18:35 ` Daniel Mack
2010-04-27 13:23 ` adelias
2010-04-27 13:31 ` The Source
2010-04-27 14:07 ` Daniel Mack
2010-04-27 15:29 ` The Source
2010-04-27 15:43 ` Daniel Mack
2010-04-27 17:27 ` The Source [this message]
2010-04-27 17:33 ` Daniel Mack
2010-05-02 16:56 ` The Source
2010-05-03 20:55 ` Daniel Mack
2010-05-07 13:19 ` The Source
2010-05-07 13:22 ` Daniel Mack
2010-05-07 20:12 ` Daniel Mack
2010-05-07 21:32 ` The Source
2010-05-08 1:38 ` Daniel Mack
2010-05-08 7:26 ` The Source
2010-05-08 9:19 ` Daniel Mack
2010-05-08 9:24 ` [PATCH] ALSA: sound/usb: fix UAC1 regression Daniel Mack
2010-05-08 9:45 ` Takashi Iwai
2010-04-27 14:06 ` usbaudio: Support for USB audio v2.0 devices Daniel Mack
2010-05-03 12:49 ` adelias
2010-05-04 10:48 ` Daniel Mack
2010-05-18 7:07 ` adelias
2010-05-18 7:40 ` Daniel Mack
2010-05-18 8:32 ` adelias
2010-05-27 18:21 ` Daniel Mack
-- strict thread matches above, loose matches on Subject: below --
2010-02-22 22:49 Daniel Mack
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=4BD71E73.5020106@gmail.com \
--to=thesourcehim@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=daniel@caiaq.de \
/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;
as well as URLs for NNTP newsgroup(s).