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: Fri, 07 May 2010 17:19:24 +0400 [thread overview]
Message-ID: <4BE4135C.80009@gmail.com> (raw)
In-Reply-To: <20100503205558.GM30801@buzzloop.caiaq.de>
04.05.2010 00:55, Daniel Mack пишет:
> On Sun, May 02, 2010 at 08:56:18PM +0400, The Source wrote:
>
>> 27.04.2010 21:33, Daniel Mack пишет:
>>
>>> On Tue, Apr 27, 2010 at 09:27:15PM +0400, The Source wrote:
>>>
>>>> 27.04.2010 19:43, Daniel Mack пишет:
>>>>
>>>>> 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.
>>>>
>>> The description above won't touch much things outside the ALSA tree
>>> during the bisect, so it shouldn't take long to compile.
>>>
>>> Thanks for helping,
>>> Daniel
>>>
>>>
>>>
>> I'm sorry, but after 2 or 3 steps (of ~10) I got kernel that doesn't
>> even boot properly (2.6.34-rc4, something with sata is broken) so I
>> can't test my card with this kernel. Should I mark current version
>> as bad and continue or something else can be done?
>>
> Hmm, so you say you can't boot a vanilla (unmodified) 2.6.34-rc4? Is
> your problem fixed in the current git HEAD? The bisect procedure I
> described shouldn't touch anything else than sound code, so SATA should
> be unaffected. Anyway, you can skip unbootable or uncompilable versions
> with
>
> $ git bisect skip
>
> HTH,
> Daniel
>
>
>
Bisect results:
23caaf19b11eda7054348452e1618d4512a86907 is the first bad commit
commit 23caaf19b11eda7054348452e1618d4512a86907
Author: Daniel Mack <daniel@caiaq.de>
Date: Thu Mar 11 21:13:25 2010 +0100
ALSA: usb-mixer: Add support for Audio Class v2.0
USB Audio Class v2.0 compliant devices have different descriptors and a
different way of setting/getting min/max/res/cur properties. This patch
adds support for them.
Signed-off-by: Daniel Mack <daniel@caiaq.de>
Cc: Clemens Ladisch <clemens@ladisch.de>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
:040000 040000 db0691095b20f0872c9042e6498ce40693d69241
7cd9e29352fd45e50968b4a17891d1c3225aaba9 M include
:040000 040000 981c7c69fc8695281929677ebccf3bdae5ef41de
c5bec5c3954278601ec4b29226f4671333262f04 M sound
_______________________________________________
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-05-07 13:19 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
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 [this message]
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=4BE4135C.80009@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).