From: Harald Dunkel <harald.dunkel@t-online.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.24-rc7, intel audio: alsa doesn't say a beep
Date: Mon, 14 Jan 2008 21:46:58 +0100 [thread overview]
Message-ID: <478BCA42.1090503@t-online.de> (raw)
In-Reply-To: <s5h8x2u2cwf.wl%tiwai@suse.de>
Dear Takashi-san,
Takashi Iwai wrote:
>
> The "regression" was your original problem, no sound on rc7, which was
> fixed by reverting the patch. Now I'd like to know that my new patch
> doesn't break after reverting the broken patch.
>
Seems that there was some misunderstanding: I thought your patch
for sigmatel.c was supposed to fix the "missing sound" problem,
too.
> In short, try my patch on the latest Linus git tree. Check whether
> the sound still works.
>
It does.
rc7 plus the big "clean-up" patch for sigmatel.c plus hda_intel.c
taken from rc6 worked, too. Seems that I missed to mention it in a
previous EMail.
>
> It's simply a delay. Basically Ingo's patch changed msleep() to
> udelay() to reduce *unneeded* delays. The function waits until the
> all pending commands are processed. The delay is simply to reduce the
> system load. And, now, changing this delay causes a problem
> surprisingly.
>
I am glad to help, but could you please do me a favour? If I am
supposed to try some new version, then please create a complete(!)
patch using rc7 on kernel.org as the base, and send it as an
attachment using a unique filename. Very likely you have a much
better overview about the most recent kernel changes, but some
statements like "new patch" or "Ingo's patch" don't mean very much
to me. The "reverted" patch is a new patch, too, and AFAIK Ingo
reverted it, so maybe you can imagine that this is highly confusing.
>> AFAICS I did use the mm branch. The command to grab the sources was
>>
>> git-clone git://git.kernel.org/pub/scm/linux/kernel/git/perex/alsa.git mm
>>
>> Is this correct?
>
> No. You'd better to clone Linus git tree, then pull from alsa.git mm
> branch.
>
> % git-clone $LINUS/linux-2.6.git
> % cd linux-2.6
> % git-pull $ALSA/alsa.git mm
>
AFAICS there shouldn't be a difference to my one-liner, unless Linus'
and Alsa's git trees are out of sync. Is this correct? Sorry, I am
more familiar with ClearCase and Accurev than with Git.
Regards
Harri
next prev parent reply other threads:[~2008-01-14 20:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 19:53 2.6.24-rc7, intel audio: alsa doesn't say a beep Harald Dunkel
2008-01-08 7:24 ` Takashi Iwai
2008-01-08 10:10 ` Ingo Molnar
2008-01-08 17:01 ` Harald Dunkel
2008-01-08 17:43 ` Takashi Iwai
2008-01-09 6:03 ` Harald Dunkel
2008-01-09 7:31 ` Takashi Iwai
2008-01-09 20:10 ` Harald Dunkel
2008-01-10 13:30 ` Takashi Iwai
2008-01-10 22:02 ` Harald Dunkel
2008-01-11 6:49 ` Takashi Iwai
2008-01-11 21:55 ` Harald Dunkel
2008-01-13 11:17 ` Takashi Iwai
2008-01-14 20:46 ` Harald Dunkel [this message]
2008-01-15 10:07 ` Takashi Iwai
2008-01-12 9:41 ` Harald Dunkel
2008-01-12 17:11 ` Daniel Hazelton
2008-01-14 11:04 ` Takashi Iwai
2008-01-14 21:03 ` Daniel Hazelton
2008-01-15 10:08 ` Takashi Iwai
2008-01-15 19:00 ` Daniel Hazelton
2008-01-13 11:26 ` Takashi Iwai
2008-01-16 6:53 ` Harald Dunkel
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=478BCA42.1090503@t-online.de \
--to=harald.dunkel@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.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 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.