Re: hda PCH id renamend to HDMI_1 after "id=HDMI index=-2" passed to the module, BUG?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ctirad Feřtr wrote:
>> "id=HDMI" says that the first device seen gets the ID "HDMI";
>> it _changes_ the ID.
>
> So if the either id and index parameters are given in the same time like:
> "modprobe snd-hda-intel id=HDMI index=-2"
> it says: "give the id "HDMI" to the first initialized device and do
> not use index 0 for it"?

Yes.

>> When there are multiple devices handled by the same driver, it is not
>> possible to choose which device gets handled by which parameter.
>
> Then I have a big problem, because I need to solve this without user
> interaction over a various PC configurations. Do you have any hint?

See "Writing udev rules" on <http://alsa.opensrc.org/Udev>
(but this works only on a fixed hardware configuration).


Regards,
Clemens

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user





[Index of Archives]     [ALSA Devel]     [Linux Audio Users]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]

  Powered by Linux