Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Rafael Espíndola" <rafael.espindola@gmail.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Fwd: [PATCH] sound working on the macbook pro
Date: Mon, 19 Feb 2007 12:52:32 +0100	[thread overview]
Message-ID: <s5hps8674an.wl%tiwai@suse.de> (raw)
In-Reply-To: <564d96fb0702180924y32118e7esf81e5ec2514d3af9@mail.gmail.com>

At Sun, 18 Feb 2007 17:24:37 +0000,
=?UTF-8?Q?Rafael_Esp=C3=ADndola?= wrote:
> 
> ---------- Forwarded message ----------
> From: Rafael Espíndola <rafael.espindola@gmail.com>
> Date: Feb 18, 2007 5:06 PM
> Subject: [PATCH] sound working on the macbook pro
> To: alsa-devel@alsa-project.org
> 
> 
> The problem with the pin config of the macbook pro is that it has no
> line outs. Because of this, snd_hda_parse_pin_def_config tries to hack
> the speaker into being a line out. This hack makes the subsequent
> setup fail.

How (and what) does it fail exactly?


> The attached patch does the followig:
> 1) install the correct pin config (extracted from macos)
> 2) removes the hack from snd_hda_parse_pin_def_config
> 3) stac92xx_parse_auto_config no longuer aborts if line_outs == 0
> 
> item 2 might cause some problems for parts of the system that expect
> this hack. IMHO, we should try to fix these problems and remove the
> hack. It is very confusing to see an Speaker appearing as a line out!

I'm sure that this would break many other devices.  So, the patch is
unacceptable as it is, unfortunately.

The line_outs are actually primary outputs, not exactly "line-out".
You can find pretty many codes that refer to this as the primary
output.


Takashi

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  parent reply	other threads:[~2007-02-19 11:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-18 17:06 [PATCH] sound working on the macbook pro Rafael Espíndola
     [not found] ` <564d96fb0702180924y32118e7esf81e5ec2514d3af9@mail.gmail.com>
2007-02-19 11:52   ` Takashi Iwai [this message]
2007-02-20  9:40     ` Fwd: " Rafael Espíndola
2007-02-20 12:05       ` Takashi Iwai
2007-02-20 20:05         ` Rafael Espíndola
2007-02-22 15:46           ` Takashi Iwai
2007-02-22 20:01             ` Rafael Espíndola
2007-02-23 14:32               ` Takashi Iwai
     [not found]                 ` <564d96fb0702262134t438dd480t45c83e556f315e2e@mail.gmail.com>
2007-03-07 23:01                   ` Takashi Iwai
2007-03-10  5:57                     ` Rafael Espíndola
2007-03-12 15:00                       ` Takashi Iwai
2007-03-13  7:14                         ` Rafael Espíndola
2007-03-13  9:41                           ` Takashi Iwai

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=s5hps8674an.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=rafael.espindola@gmail.com \
    /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