Live data from Hacker News

Apple limits daisychaining of non-Apple displays in OS X

apple.stackexchange.com

31–40 of 59 posts

Re: Apple limits daisychaining of non-Apple displays in OS X

#31
post #8

Earlier quoted context omitted.

It's also a 2560x1440 screen sold for $999. An upgrade with their latest 5K display is overdue.

I just recently bought a couple of Dell U2515H monitors (and will probably buy another), and, given you can buy three of them for the cost of one of Apple's Thunderbolt displays, they really are a great deal - same resolution, higher PPI, more adjustable and rotatable, and they're matte. My Apple Thunderbolt display has from day one had some light leakage in the lower right corner, and the ethernet port stopped worki…

I got an U2515H at work last week (for use with my MBP) and am amazed at the effect it's had on my working patterns in such a short space of time. Simply being able to have documentation, browser and editor open at once and not feel 'cramped' is amazing.

Re: Apple limits daisychaining of non-Apple displays in OS X

#32

Apple has the right to claim that using unsupported hardware is...well....unsupported. However, it sounds like they nerfed the driver which makes it a non standards complaint driver. This is a problem and Apple needs to be called out on it. At the very least, they could face sanctions or a trademark lawsuit from the display port standards group for using the logo with non compliant products. At the worst, a hefty fin…

They're compliant with DP 1.1. The DP association doesn't require 1.2 be supported, although Apple really ought to. There's really not that much substance to the OP's hand waving here except for the fact that it's disappointing that there is driver support for the same hardware in Windows.

Re: Apple limits daisychaining of non-Apple displays in OS X

#33

I really hope Apple reads that feedback form. Safari on iOS has a broken Content Security Policy for the font-src (namely 'self' isn't working) and I am getting flooded with false reports. When I google it I only find an unanswered post on Stackoverflow: http://stackoverflow.com/questions/29417735/content-security... Do so few people use content security policy? How did this go unnoticed for so long?

If you want Apple to fix issues report them through Radar: http://bugreporter.apple.com

They do get triaged by the engineering teams.

Re: Apple limits daisychaining of non-Apple displays in OS X

#35

"This question has been asked before and already has an answer." This is the single MOST ANNOYING thing about stack exchange. WHERE was this question asked before? How about a link to the original question? Hello?

To be fair to Stack Exchange, that's a behavior that's been around forever; at least since USENET. It is very annoying, though.

Re: Apple limits daisychaining of non-Apple displays in OS X

#36

"This question has been asked before and already has an answer." This is the single MOST ANNOYING thing about stack exchange. WHERE was this question asked before? How about a link to the original question? Hello?

The yellow box above the question does give a link to the previous answer. Is that what you're talking about?

EDIT: also, more annoying is-

"I want to do this. How do it do it?"

"No, don't do that. Do this other thing instead."

Re: Apple limits daisychaining of non-Apple displays in OS X

#37

"This question has been asked before and already has an answer." This is the single MOST ANNOYING thing about stack exchange. WHERE was this question asked before? How about a link to the original question? Hello?

The worst is when you ask something that is subtly different enough that it really isn't the same question anymore, and then they shut you down anyway. Perhaps to somebody with expert-level knowledge, it might be the same, but for someone trying to learn something new, subtle differences can be huge.

Re: Apple limits daisychaining of non-Apple displays in OS X

#38
post #30
post #19

Earlier quoted context omitted.

This is the correct answer. You can't blame Apple for not supporting a feature they never claimed to support. I don't think there's malicious intent here, rather a lack of demand or awareness.

I can easilty blame Apple for locking out functionality that underlying hardware supports though. Especially when it's essentially functionality handled by the hardware layer and drivers not written by Apple at all.

There's a big difference between "locking out support" and "not doing extra work to support a feature we don't need."

Should I blame Microsoft for not supplying all software ever written with Windows? After all, my PC is just a Turing machine, so by not providing me with all the software ever written, they're locking out functionality the underlying hardware supports.

Re: Apple limits daisychaining of non-Apple displays in OS X

#39

This is pretty simple. Apple does not, and never did, support DisplayPort daisy chaining. The confusion lies in the fact that Apple does support Thunderbolt monitor daisy chaining, and Thunderbolt uses the same port as mini-DisplayPort. That the hardware can support it is irrelevant. Apple hardware can do lots of things that Apple doesn't support or claim their hardware can do. Call it malevance on Apple's part if yo…

I'm confused though. If they support MST[0], how did they rip out daisychaining specifically? I don't understand MST well enough to see how a computer connected to one large monitor with two MST regions would be different than two monitors daisy chained using MST.

It really does look like Apple specifically has disabled it because there isn't an apple product that supports it, but that may be due to my own ignorance of MST.

[0]: https://support.apple.com/en-us/HT202856

Re: Apple limits daisychaining of non-Apple displays in OS X

#40
post #36

"This question has been asked before and already has an answer." This is the single MOST ANNOYING thing about stack exchange. WHERE was this question asked before? How about a link to the original question? Hello?

The yellow box above the question does give a link to the previous answer. Is that what you're talking about? EDIT: also, more annoying is- "I want to do this. How do it do it?" "No, don't do that. Do this other thing instead."

[deleted]
Post reply on HN