Re: [PATCH] [ALSA] Added new pin config for first gen macbook.
On 9/4/07, Takashi Iwai <[EMAIL PROTECTED]> wrote: > At Tue, 4 Sep 2007 09:12:32 +0530, > Abhijit Bhopatkar wrote: > > > > On 9/3/07, Ivan N. Zlatev <[EMAIL PROTECTED]> wrote: > > > On 9/3/07, Ivan N. Zlatev <[EMAIL PROTECTED]> wrote: > > > > On 9/3/07, Takashi Iwai <[EMAIL PROTECTED]> wrote: > > > > > At Mon, 3 Sep 2007 15:55:18 +0530, > OK, these are real problems. > > > I am willing to do whatever test you people want, though I do not know > Just to be sure, doesn't none of intel-mac-[1-5] model match with your > machine? If so, putting the pin-config back is the straightforward > solution indeed. > > Anyway, it'd be helpful if someone else can check the same MacBook > (1st generation, not Pro?) whether the problem is reproducible. To be precise its Macbook 1st Generation non pro. with subsystem id 0x106b0a00 Well a friend of mine has the same model and i tried things out on his machine. to my surprise :(, the original 2.6.23-rc5 is working fine on his machine. So on my machine we booted to windows and tested things out. The sound on my machine doesn't work in windows either, although its working in OSX. So sorry for all the noise its most likely a hardware problem after all. Although i am baffled as to why old pin config works on this particular broken hardware. I hope i didn't bug you too much, i appreciate your quick responses. Abhijit - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] [ALSA] Added new pin config for first gen macbook.
On 9/4/07, Takashi Iwai [EMAIL PROTECTED] wrote: At Tue, 4 Sep 2007 09:12:32 +0530, Abhijit Bhopatkar wrote: On 9/3/07, Ivan N. Zlatev [EMAIL PROTECTED] wrote: On 9/3/07, Ivan N. Zlatev [EMAIL PROTECTED] wrote: On 9/3/07, Takashi Iwai [EMAIL PROTECTED] wrote: At Mon, 3 Sep 2007 15:55:18 +0530, OK, these are real problems. I am willing to do whatever test you people want, though I do not know Just to be sure, doesn't none of intel-mac-[1-5] model match with your machine? If so, putting the pin-config back is the straightforward solution indeed. Anyway, it'd be helpful if someone else can check the same MacBook (1st generation, not Pro?) whether the problem is reproducible. To be precise its Macbook 1st Generation non pro. with subsystem id 0x106b0a00 Well a friend of mine has the same model and i tried things out on his machine. to my surprise :(, the original 2.6.23-rc5 is working fine on his machine. So on my machine we booted to windows and tested things out. The sound on my machine doesn't work in windows either, although its working in OSX. So sorry for all the noise its most likely a hardware problem after all. Although i am baffled as to why old pin config works on this particular broken hardware. I hope i didn't bug you too much, i appreciate your quick responses. Abhijit - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] [ALSA] Added new pin config for first gen macbook.
On 9/3/07, Ivan N. Zlatev <[EMAIL PROTECTED]> wrote: > On 9/3/07, Ivan N. Zlatev <[EMAIL PROTECTED]> wrote: > > On 9/3/07, Takashi Iwai <[EMAIL PROTECTED]> wrote: > > > At Mon, 3 Sep 2007 15:55:18 +0530, > > > Abhijit Bhopatkar wrote: > > > > > > > > commit 5d5d3bc3eddf2ad97b2cb090b92580e7fed6cee1 changed all > > > > pin configs for intel macs, but it breaks sound on > > > > Macbook first > > > > > > Please elaborate how does it break. "it breaks sound" is too > > > ambigious like the most popular bug reports "sound doesn't work" :) Apologies for the terse report, On my macbook with latest kernels 1. Alsamixer is showing only three controlls in total, Master PCM and Digital. 2. There is absolutely no output sound what so ever. 3. There is no capture sound being captured either. Reverting back the pin config to the one in previous kernels is working (although not perfect e.g. to enable input sound we need to toggle the capture device to mic and linein atlease once, no idea whats the deal with that) I am willing to do whatever test you people want, though I do not know where to look for more info at this point. So please feel free direct me to arrive at a better soultion or better info. Thanks Abhijit PS: lspci -v shows 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) Subsystem: Unknown device 8384:7680 Flags: us master, fast devsel, latency 0, IRQ 21 Memory at 9044 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Capabilities: [70] Express Unknown type IRQ 0 Let me know if you need output dump of other stuff. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[PATCH] [ALSA] Added new pin config for first gen macbook.
commit 5d5d3bc3eddf2ad97b2cb090b92580e7fed6cee1 changed all
pin configs for intel macs, but it breaks sound on
Macbook first generation.
Readded a known working pin config for first gen macbooks.
Signed-off-by: Abhijit Bhopatkar <[EMAIL PROTECTED]>
---
sound/pci/hda/patch_sigmatel.c | 10 +-
1 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/sound/pci/hda/patch_sigmatel.c b/sound/pci/hda/patch_sigmatel.c
index 3f25de7..a2b0422 100644
--- a/sound/pci/hda/patch_sigmatel.c
+++ b/sound/pci/hda/patch_sigmatel.c
@@ -585,6 +585,12 @@ static unsigned int intel_mac_v5_pin_configs[10] = {
0x40fc, 0x40fb,
};
+static unsigned int intel_macbook_first_gen_pin_configs[10] = {
+ 0x0321e230, 0x03a1e020, 0x9017e110, 0x01014010,
+ 0x01a19021, 0x0381e021, 0x1345e240, 0x13c5e22e,
+ 0x02a19320, 0x40fb,
+};
+
static unsigned int stac922x_dell_pin_configs[10] = {
0x0221121e, 0x408103ff, 0x02a1123e, 0x90100310,
0x408003f1, 0x0221122f, 0x03451340, 0x40c003f2,
@@ -603,7 +609,7 @@ static unsigned int *stac922x_brd_tbl[STAC_922X_MODELS] = {
[STAC_INTEL_MAC_V5] = intel_mac_v5_pin_configs,
/* for backward compitability */
[STAC_MACMINI] = intel_mac_v3_pin_configs,
- [STAC_MACBOOK] = intel_mac_v5_pin_configs,
+ [STAC_MACBOOK] = intel_macbook_first_gen_pin_configs,
[STAC_MACBOOK_PRO_V1] = intel_mac_v3_pin_configs,
[STAC_MACBOOK_PRO_V2] = intel_mac_v3_pin_configs,
[STAC_IMAC_INTEL] = intel_mac_v2_pin_configs,
@@ -2132,6 +2138,8 @@ static int patch_stac922x(struct hda_codec *codec)
spec->board_config = STAC_INTEL_MAC_V4;
break;
case 0x106b0a00:
+ spec->board_config = STAC_MACBOOK;
+ break;
case 0x106b2200:
spec->board_config = STAC_INTEL_MAC_V5;
break;
--
1.5.2.4
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH] [ALSA] Added new pin config for first gen macbook.
commit 5d5d3bc3eddf2ad97b2cb090b92580e7fed6cee1 changed all
pin configs for intel macs, but it breaks sound on
Macbook first generation.
Readded a known working pin config for first gen macbooks.
Signed-off-by: Abhijit Bhopatkar [EMAIL PROTECTED]
---
sound/pci/hda/patch_sigmatel.c | 10 +-
1 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/sound/pci/hda/patch_sigmatel.c b/sound/pci/hda/patch_sigmatel.c
index 3f25de7..a2b0422 100644
--- a/sound/pci/hda/patch_sigmatel.c
+++ b/sound/pci/hda/patch_sigmatel.c
@@ -585,6 +585,12 @@ static unsigned int intel_mac_v5_pin_configs[10] = {
0x40fc, 0x40fb,
};
+static unsigned int intel_macbook_first_gen_pin_configs[10] = {
+ 0x0321e230, 0x03a1e020, 0x9017e110, 0x01014010,
+ 0x01a19021, 0x0381e021, 0x1345e240, 0x13c5e22e,
+ 0x02a19320, 0x40fb,
+};
+
static unsigned int stac922x_dell_pin_configs[10] = {
0x0221121e, 0x408103ff, 0x02a1123e, 0x90100310,
0x408003f1, 0x0221122f, 0x03451340, 0x40c003f2,
@@ -603,7 +609,7 @@ static unsigned int *stac922x_brd_tbl[STAC_922X_MODELS] = {
[STAC_INTEL_MAC_V5] = intel_mac_v5_pin_configs,
/* for backward compitability */
[STAC_MACMINI] = intel_mac_v3_pin_configs,
- [STAC_MACBOOK] = intel_mac_v5_pin_configs,
+ [STAC_MACBOOK] = intel_macbook_first_gen_pin_configs,
[STAC_MACBOOK_PRO_V1] = intel_mac_v3_pin_configs,
[STAC_MACBOOK_PRO_V2] = intel_mac_v3_pin_configs,
[STAC_IMAC_INTEL] = intel_mac_v2_pin_configs,
@@ -2132,6 +2138,8 @@ static int patch_stac922x(struct hda_codec *codec)
spec-board_config = STAC_INTEL_MAC_V4;
break;
case 0x106b0a00:
+ spec-board_config = STAC_MACBOOK;
+ break;
case 0x106b2200:
spec-board_config = STAC_INTEL_MAC_V5;
break;
--
1.5.2.4
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] [ALSA] Added new pin config for first gen macbook.
On 9/3/07, Ivan N. Zlatev [EMAIL PROTECTED] wrote: On 9/3/07, Ivan N. Zlatev [EMAIL PROTECTED] wrote: On 9/3/07, Takashi Iwai [EMAIL PROTECTED] wrote: At Mon, 3 Sep 2007 15:55:18 +0530, Abhijit Bhopatkar wrote: commit 5d5d3bc3eddf2ad97b2cb090b92580e7fed6cee1 changed all pin configs for intel macs, but it breaks sound on Macbook first Please elaborate how does it break. it breaks sound is too ambigious like the most popular bug reports sound doesn't work :) Apologies for the terse report, On my macbook with latest kernels 1. Alsamixer is showing only three controlls in total, Master PCM and Digital. 2. There is absolutely no output sound what so ever. 3. There is no capture sound being captured either. Reverting back the pin config to the one in previous kernels is working (although not perfect e.g. to enable input sound we need to toggle the capture device to mic and linein atlease once, no idea whats the deal with that) I am willing to do whatever test you people want, though I do not know where to look for more info at this point. So please feel free direct me to arrive at a better soultion or better info. Thanks Abhijit PS: lspci -v shows 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) Subsystem: Unknown device 8384:7680 Flags: us master, fast devsel, latency 0, IRQ 21 Memory at 9044 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Capabilities: [70] Express Unknown type IRQ 0 Let me know if you need output dump of other stuff. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] [RFC] Throttle swappiness for interactive tasks
> I just wanted to know weather its worth going forward or we have > better reasons to discount any such direction? The reason that the wrong pages get swapped out sometimes could be due to a side effect of the way the swappiness policy is implemented. While the VM only reclaims page cache pages, it will still rotate through the anonymous pages on the LRU list, which effectively randomizes the order of those pages on the list. In my mind i find it fundamentally wrong to separate anon pages from page cache. It should rather be lot more dependent on which task accessed them last. Although it seems due to some twisted relationships bet anon pages and interactive tasks separating them improves it. Am i missing something here? I need to get back to benchmarking my patch to split the lists - anonymous and other swap backed pages on one set of pageout lists, filesystem backed pages on another list. Unfortunately my main desktop system at home depends on Xen, so it's not as easy to use that patch there :( Can you send me those patches please or point me to where i can find those? Abhijit - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] [RFC] Throttle swappiness for interactive tasks
I just wanted to know weather its worth going forward or we have better reasons to discount any such direction? The reason that the wrong pages get swapped out sometimes could be due to a side effect of the way the swappiness policy is implemented. While the VM only reclaims page cache pages, it will still rotate through the anonymous pages on the LRU list, which effectively randomizes the order of those pages on the list. In my mind i find it fundamentally wrong to separate anon pages from page cache. It should rather be lot more dependent on which task accessed them last. Although it seems due to some twisted relationships bet anon pages and interactive tasks separating them improves it. Am i missing something here? I need to get back to benchmarking my patch to split the lists - anonymous and other swap backed pages on one set of pageout lists, filesystem backed pages on another list. snip Unfortunately my main desktop system at home depends on Xen, so it's not as easy to use that patch there :( Can you send me those patches please or point me to where i can find those? Abhijit - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
