LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
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: Fri, 11 Jan 2008 22:55:28 +0100	[thread overview]
Message-ID: <4787E5D0.7000405@t-online.de> (raw)
In-Reply-To: <s5hprw8g8m7.wl%tiwai@suse.de>

Takashi Iwai wrote:
> At Thu, 10 Jan 2008 23:02:53 +0100,
> Harald Dunkel wrote:
>> Takashi Iwai wrote:
>>> Hm...  Just to be sure, try the patch below.  It's a clean up patch
>>> that I'd like to apply later.
>>>
>> Sorry, no sound.
> 
> OK, but I'd like to know whether this makes no regression to rc6.
> Could you check?
> 

"Regression" sounds like a test suite to me, verifying that the
old problems didn't come back. Maybe you could send me a pointer?

Of course I didn't try that much yet. The kernel booted as expected,
I saw XWindow running, the mouse pointer was moving, etc. There was
just no sound, as before with rc7.

> Also, what exactly did you test?  "No sound" means that no sound from
> the headphone / line-out or from the speaker?
> 

Speaker and first headphone are the same on this laptop. If I plugin
the headphone, then the tiny speakers are disconnected. But for the
last tests no headphone was plugged in.

I tested it by running gnome-alsamixer. I tried to switch off and
on the mute buttons, change the volume and other sliders, etc.

> One interesting test would be to increase the value of udelay() in the
> reverted patch.  What happens if it's set to 500?
> 

I will try tomorrow. What exactly is this delay good for?

>>> The perex/alsa.git mm branch on kernel.org has many fixes.  Could you
>>> give it a try, too?
>>>
>> This version seems to work. But AFAICS it just reverts hda_intel.c back
>> to rc6 again, so this is no surprise.
> 
> Use mm branch.  The main branch is just an old Linus tree.
> 

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?


Regards

Harri


  reply	other threads:[~2008-01-11 21:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07 19:53 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 [this message]
2008-01-13 11:17                     ` Takashi Iwai
2008-01-14 20:46                       ` Harald Dunkel
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=4787E5D0.7000405@t-online.de \
    --to=harald.dunkel@t-online.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.de \
    --subject='Re: 2.6.24-rc7, intel audio: alsa doesn'\''t say a beep' \
    /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

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).