On Mon, May 02, 2016 at 11:11:31AM -0400, Lyude Paul wrote:
> I gave a short try at fixing MST audio, but it definitely looks like it's
> going
> to require quite a bit of troubleshooting and a few more patches :(.
>
> Since I can't find an immediate fix to actually make MST audio work I'm
> tot
I gave a short try at fixing MST audio, but it definitely looks like it's going
to require quite a bit of troubleshooting and a few more patches :(.
Since I can't find an immediate fix to actually make MST audio work I'm totally
in favor of reverting the MST audio support for the time being
On Th
On Thu, 28 Apr 2016, Ville Syrjälä wrote:
> On Thu, Apr 28, 2016 at 09:17:00AM +0300, Jani Nikula wrote:
>> On Wed, 27 Apr 2016, Lyude wrote:
>> > For MST encoders, the encoder struct is stored in the intel_dp_mst
>> > struct, not a intel_digital_port struct.
>> >
>> > This fixes issues with ho
On Thu, Apr 28, 2016 at 09:17:00AM +0300, Jani Nikula wrote:
> On Wed, 27 Apr 2016, Lyude wrote:
> > For MST encoders, the encoder struct is stored in the intel_dp_mst
> > struct, not a intel_digital_port struct.
> >
> > This fixes issues with hotplugging MST displays that support MST audio,
> > w
On Wed, 27 Apr 2016, Lyude wrote:
> For MST encoders, the encoder struct is stored in the intel_dp_mst
> struct, not a intel_digital_port struct.
>
> This fixes issues with hotplugging MST displays that support MST audio,
> where hotplugging had a surprisingly good chance of accidentally
> overwri
For MST encoders, the encoder struct is stored in the intel_dp_mst
struct, not a intel_digital_port struct.
This fixes issues with hotplugging MST displays that support MST audio,
where hotplugging had a surprisingly good chance of accidentally
overwriting other parts of the kernel leading to seem
