From b540f95a3e5c1ea18e3e55ec8cbbc2a35731095e Mon Sep 17 00:00:00 2001 From: Alexander Stein Date: Wed, 26 Oct 2011 09:58:45 +0200 Subject: [PATCH] --- yaml --- r: 270398 b: refs/heads/master c: 820bc19df20e1927054860513322742de5ebb6b3 h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/sound/alsa/HD-Audio.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index d6d557b49112..54d747bad573 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: cc667a72d471e79fd8e5e291ea115923cf44dca0 +refs/heads/master: 820bc19df20e1927054860513322742de5ebb6b3 diff --git a/trunk/Documentation/sound/alsa/HD-Audio.txt b/trunk/Documentation/sound/alsa/HD-Audio.txt index caa3ec655eac..03e2771ddeef 100644 --- a/trunk/Documentation/sound/alsa/HD-Audio.txt +++ b/trunk/Documentation/sound/alsa/HD-Audio.txt @@ -494,7 +494,7 @@ Also, the codec chip name can be rewritten via `[chip_name]` line. The hd-audio driver reads the file via request_firmware(). Thus, a patch file has to be located on the appropriate firmware path, typically, /lib/firmware. For example, when you pass the option -`patch=hda-init.fw`, the file /lib/firmware/hda-init-fw must be +`patch=hda-init.fw`, the file /lib/firmware/hda-init.fw must be present. The patch module option is specific to each card instance, and you