From: Takashi Iwai Subject: Re: HDA Firmware file question Date: Thu, 17 Nov 2011 16:13:41 +0100 Message-ID: References: <4EC4D5DC.9090202@canonical.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id E661024142 for ; Thu, 17 Nov 2011 16:13:43 +0100 (CET) In-Reply-To: <4EC4D5DC.9090202@canonical.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: David Henningsson Cc: ALSA Development Mailing List List-Id: alsa-devel@alsa-project.org At Thu, 17 Nov 2011 10:37:32 +0100, David Henningsson wrote: > > Hi, > > As seen in the "Early Patching" section of the "More notes on HD-Audio > driver" document, you're supposed to activate it like this: > > options snd-hda-intel patch=on-board-patch,hdmi-patch > > But how do we know the order here? The pci bus is probed in parallel > (right?) so could this be racy, that on every other boot, the hdmi card > is probed first instead? IIRC, the probing order in the driver is serialized, so it doesn't vary, just depending on the PCI slots. In practice, I've never seen any order changes. > Also, since the patch file specifies a [codec] section, you could > actually use the same patch file for almost all cases. I guess the case > of having two card instances with the same codec at the same address is > pretty unusual, right? Right. You must specify the codec SSID, and this should be unique enough for identify each instance. thanks, Takashi