lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 13 Feb 2019 16:42:19 +0100
From:   Paul Menzel <pmenzel+alsa-devel@...gen.mpg.de>
To:     Takashi Iwai <tiwai@...e.de>
Cc:     alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: snd_hda_codec_hdmi: `hdaudio hdaudioC0D2: Unable to bind the
 codec`

Dear Takashi,


On 02/13/19 16:12, Takashi Iwai wrote:
> On Wed, 13 Feb 2019 15:58:44 +0100,
> Paul Menzel wrote:
>>
>>> Why the i915 driver gets initialized *so late*?
>>
>> Maybe, because it’s built as a module?
>>
>> ```
>> $ grep I915 /boot/config-4.20.8.mx64.245 
>> CONFIG_DRM_I915=m
>> # CONFIG_DRM_I915_ALPHA_SUPPORT is not set
>> CONFIG_DRM_I915_CAPTURE_ERROR=y
>> CONFIG_DRM_I915_COMPRESS_ERROR=y
>> CONFIG_DRM_I915_USERPTR=y
>> # CONFIG_DRM_I915_GVT is not set
>> CONFIG_SND_HDA_I915=y
>> ```
> 
> That explains.  You built the HD-audio as built-in while the graphics
> as module.  This makes the binding impossible at the time of sound
> driver initialization.
> 
> If you build the graphics driver as a module, built the sound driver
> also as a module.

Can this be enforced by the Kconfig configuration? If not, should the
warning/error message be extended with this hint?


Kind regards,

Paul


Download attachment "smime.p7s" of type "application/pkcs7-signature" (5174 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ