On Wednesday 13 of February 2008 14:06:20 Takashi Iwai wrote:
> > This patch did not have any effect. (i haven't tested suspend-to-ram)
> >
> > alsa-info before powersaving (speaker silent, mixer says: Speaker=MM):
> > http://pastebin.ca/902330
> >
> > alsa-info after powersaving (speaker loud,
On Wednesday 13 of February 2008 11:59:58 Takashi Iwai wrote:
> > Now I just found that the new "Speaker" switch forgets it's value from
> > time to time, ie. it's muted, you go and have lunch, and when you get
> > back and start the music, it's unmuted. It is probably related to
> > aggressive
On Wednesday 13 of February 2008 11:59:58 Takashi Iwai wrote:
Now I just found that the new Speaker switch forgets it's value from
time to time, ie. it's muted, you go and have lunch, and when you get
back and start the music, it's unmuted. It is probably related to
aggressive hda-codec
On Wednesday 13 of February 2008 14:06:20 Takashi Iwai wrote:
This patch did not have any effect. (i haven't tested suspend-to-ram)
alsa-info before powersaving (speaker silent, mixer says: Speaker=MM):
http://pastebin.ca/902330
alsa-info after powersaving (speaker loud, mixer says:
On Tuesday 12 of February 2008 19:24:35 Matej Laitl wrote:
> > > Yes, this "slightly better" patch applied on top of your first patch
> > > against hda_codec.c did the trick, but with some side-effects:
> > > (...)
Now I just found that the new "Sp
Takashi Iwai wrote:
> Matej Laitl wrote:
> > Yes, this "slightly better" patch applied on top of your first patch
> > against hda_codec.c did the trick, but with some side-effects:
> > * the "Speaker" switch now mutes/unmutes speakers
> > * muti
Takashi Iwai wrote:
> Takashi Iwai wrote:
> > Matej Laitl wrote:
> > > With your patch, the sound in headphone-out is working again, but
> > > surprisingly the integrated loudspeakers stopped working! ;)
> > >
> > > Also, new on/of control ap
Takashi Iwai wrote:
> I wrote:
> > Thanks. It seems that your device has two headphone jacks according
> > to the BIOS setup, and this seems to be the problem.
> >
> > Could you show the kernel messages like "autoconfig: line_outs..." for
> > both cases? This appears when build with
Takashi Iwai wrote:
> Thanks. It seems that your device has two headphone jacks according
> to the BIOS setup, and this seems to be the problem.
>
> Could you show the kernel messages like "autoconfig: line_outs..." for
> both cases? This appears when build with CONFIG_SND_DEBUG=y.
Kernel with
Takashi Iwai wrote:
> Matej Laitl wrote:
> > after upgrading from 2.6.24 to 2.6.25-rc1, I lost headphone-out sound
> > output of my Intel HDA card - it is quiet no matter what the mixer
> > settings are.
> >
> > (...)
> >
> > The box is Fujitsu-Sieme
Takashi Iwai wrote:
Matej Laitl wrote:
after upgrading from 2.6.24 to 2.6.25-rc1, I lost headphone-out sound
output of my Intel HDA card - it is quiet no matter what the mixer
settings are.
(...)
The box is Fujitsu-Siemens Esprimo Mobile M9400 laptop.
Could you give the output
Takashi Iwai wrote:
Matej Laitl wrote:
Yes, this slightly better patch applied on top of your first patch
against hda_codec.c did the trick, but with some side-effects:
* the Speaker switch now mutes/unmutes speakers
* muting/unmuting Front channel now has zero effect (in 2.6.24 it had
On Tuesday 12 of February 2008 19:24:35 Matej Laitl wrote:
Yes, this slightly better patch applied on top of your first patch
against hda_codec.c did the trick, but with some side-effects:
(...)
Now I just found that the new Speaker switch forgets it's value from time to
time, ie. it's
Takashi Iwai wrote:
Takashi Iwai wrote:
Matej Laitl wrote:
With your patch, the sound in headphone-out is working again, but
surprisingly the integrated loudspeakers stopped working! ;)
Also, new on/of control appeared in alsamixer - Speaker, but unmuting
it (and unmuting all
Takashi Iwai wrote:
I wrote:
Thanks. It seems that your device has two headphone jacks according
to the BIOS setup, and this seems to be the problem.
Could you show the kernel messages like autoconfig: line_outs... for
both cases? This appears when build with CONFIG_SND_DEBUG=y.
And
Takashi Iwai wrote:
Thanks. It seems that your device has two headphone jacks according
to the BIOS setup, and this seems to be the problem.
Could you show the kernel messages like autoconfig: line_outs... for
both cases? This appears when build with CONFIG_SND_DEBUG=y.
Kernel with broken
a=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0
The box is Fujitsu-Siemens Esprimo Mobile M9400 laptop.
[1]
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=f889fa91ad47e6fcb530abf1184ca9f1473d3c72
Regards,
Matej Laitl
--
To unsubscribe from this list: sen
]: enable=0, dir=0, wake=0, sticky=0, data=0
The box is Fujitsu-Siemens Esprimo Mobile M9400 laptop.
[1]
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=f889fa91ad47e6fcb530abf1184ca9f1473d3c72
Regards,
Matej Laitl
--
To unsubscribe from this list: send the line
Alexey Starikovskiy wrote:
> ACPI: use select POWER_SUPPLY for AC, BATTERY and SBS
>
> From: Alexey Starikovskiy <[EMAIL PROTECTED]>
>
> POWER_SUPPLY is needed for AC, battery, and SBS sysfs support.
> Use 'select' instead of 'depends on', as it is will not be selected
> by anything else, leading
Alexey Starikovskiy wrote:
ACPI: use select POWER_SUPPLY for AC, BATTERY and SBS
From: Alexey Starikovskiy [EMAIL PROTECTED]
POWER_SUPPLY is needed for AC, battery, and SBS sysfs support.
Use 'select' instead of 'depends on', as it is will not be selected
by anything else, leading to
This little patch changes notation of unchangeable menuconfig items to always
reflect the current state of inclusion of a feature.
Signed-off-by: Matěj Laitl <[EMAIL PROTECTED]>
---
Hi again, Sam, Roman, Randy.
Instead of incorporating all changes into a single patch, I decided to split
things
This little patch changes notation of unchangeable menuconfig items to always
reflect the current state of inclusion of a feature.
Signed-off-by: Matěj Laitl [EMAIL PROTECTED]
---
Hi again, Sam, Roman, Randy.
Instead of incorporating all changes into a single patch, I decided to split
things
On Sunday 16 of September 2007 21:36:54 Roman Zippel wrote:
> On Sun, 16 Sep 2007, Matej Laitl wrote:
> > The v2 was maybe more intuitive, but had at least one flaw, where it claimed
> > the option was selected by another, while it was in fact only made
> > unchangeable b
On Sunday 16 of September 2007 20:41:10 Sam Ravnborg wrote:
> On Sat, Sep 15, 2007 at 08:04:10PM +0200, Matej Laitl wrote:
> > menuconfig currently represents options implied by another option ('select'
> > directive in Kconfig) by prefixing them with '---'. Unfortunately the sa
On Sunday 16 of September 2007 19:59:56 Roman Zippel wrote:
> Right now I prefer the previous version.
The v2 was maybe more intuitive, but had at least one flaw, where it claimed
the option was selected by another, while it was in fact only made
unchangeable by 'bool "Enable block layer" if
menuconfig currently represents options implied by another option ('select'
directive in Kconfig) by prefixing them with '---'. Unfortunately the same
notation is used for comments.
This patch changes notation of selected-by-another items by introducing new
representations for implied options:
menuconfig currently represents options implied by another option ('select'
directive in Kconfig) by prefixing them with '---'. Unfortunately the same
notation is used for comments.
This patch changes notation of selected-by-another items by introducing new
representations for implied options:
On Sunday 16 of September 2007 19:59:56 Roman Zippel wrote:
Right now I prefer the previous version.
The v2 was maybe more intuitive, but had at least one flaw, where it claimed
the option was selected by another, while it was in fact only made
unchangeable by 'bool Enable block layer if
On Sunday 16 of September 2007 20:41:10 Sam Ravnborg wrote:
On Sat, Sep 15, 2007 at 08:04:10PM +0200, Matej Laitl wrote:
menuconfig currently represents options implied by another option ('select'
directive in Kconfig) by prefixing them with '---'. Unfortunately the same
notation is used
On Sunday 16 of September 2007 21:36:54 Roman Zippel wrote:
On Sun, 16 Sep 2007, Matej Laitl wrote:
The v2 was maybe more intuitive, but had at least one flaw, where it claimed
the option was selected by another, while it was in fact only made
unchangeable by 'bool Enable block layer
On Saturday 15 of September 2007 20:38:14 you wrote:
> On Sep 15 2007 20:04, Matej Laitl wrote:
> >This patch changes notation of selected-by-another items by introducing 2
> > new representations for implied options:
> >{*} or {M} for options selected by another modulari
On Saturday 15 of September 2007 20:04:10 Matej Laitl wrote:
> menuconfig currently represents options implied by another option ('select'
> directive in Kconfig) by prefixing them with '---'. Unfortunately the same
> notation is used for comments.
>
> (...)
Oh please reply to my
menuconfig currently represents options implied by another option ('select'
directive in Kconfig) by prefixing them with '---'. Unfortunately the same
notation is used for comments.
This patch changes notation of selected-by-another items by introducing 2 new
representations for implied options:
From: Matěj Laitl <[EMAIL PROTECTED]>
This simple patch helps users reveal this config option and makes MSI Laptop
more coherent with other laptop extras found in misc devices.
(this option was hidden until user says y to BACKLIGHT_CLASS_DEVICE under
Graphics drivers)
When at it, convert space
From: Matěj Laitl [EMAIL PROTECTED]
This simple patch helps users reveal this config option and makes MSI Laptop
more coherent with other laptop extras found in misc devices.
(this option was hidden until user says y to BACKLIGHT_CLASS_DEVICE under
Graphics drivers)
When at it, convert space
menuconfig currently represents options implied by another option ('select'
directive in Kconfig) by prefixing them with '---'. Unfortunately the same
notation is used for comments.
This patch changes notation of selected-by-another items by introducing 2 new
representations for implied options:
On Saturday 15 of September 2007 20:04:10 Matej Laitl wrote:
menuconfig currently represents options implied by another option ('select'
directive in Kconfig) by prefixing them with '---'. Unfortunately the same
notation is used for comments.
(...)
Oh please reply to my address [EMAIL
On Saturday 15 of September 2007 20:38:14 you wrote:
On Sep 15 2007 20:04, Matej Laitl wrote:
This patch changes notation of selected-by-another items by introducing 2
new representations for implied options:
{*} or {M} for options selected by another modularized one, thus builtin
or module
menuconfig currently represents options implied by another option ('select'
directive in Kconfig) by prefixing them with '---'. Unfortunately the same
notation is used for comments. If the implied option is module capable,
user can still switch between Y and M, all without any feedback until she
menuconfig currently represents options implied by another option ('select'
directive in Kconfig) by prefixing them with '---'. Unfortunately the same
notation is used for comments. If the implied option is module capable,
user can still switch between Y and M, all without any feedback until she
40 matches
Mail list logo
