Re: [Mactel-linux-users] contacting apple/ati

[Nicolas B. <ni...@bo...>]

Hi,

Sheer El-Showk wrote:
> Hi All,
> 
> A recent post on Michael Larabel's blog suggests that linux users are
> taking an incorrect approach by pestering companies like AMD/ATI
> directly about poor linux support of their drivers.
> 
> http://www.michaellarabel.com/index.php?k=blog&i=121
> 
> Rather, Michael suggests we should contact the OEM's (such as Apple,
> Dell, etc...) and ask them to have better linux support on their
> products and point out particular problems with e.g. ATI drivers so
> that they will have some impetus to pressure ATI.  I'm not sure how
> pliable apple will be but it can't hurt to try.  It would be good to
> point out in such messages that Apple makes a lot of its money in
> hardware and there are many people who want to use Apple hardware but
> to run multiple OSes.
> 
> Also, another large issue with the MB and MBP is SMC support in linux.
>  I'm not sure if this is  for want of specifications or for want of
> someone to just implement a good driver.  If its the former then we
> should also ask apple to release these or perhaps even help develop a
> driver.

Forget about them developing a driver, I think it's asking WAY to much
(and actually the applesmc driver we have has more features exposed to
the user than the one in OS X (you need third party apps to get fan
control for example))... The specs would be interesting though.

> I strongly suggest that any affected Apple hardware product owner go to:
> 
> http://www.apple.com/feedback/
> 
> and post a polite and detailed comment regarding what issues we'd like
> resolved.

I'll try to post something there, but don't expect too much.

A small real life experience I have on another project, slightly
off-subject, just to give you any idea how vendors react, and react
differently.

I'm developing a tool to control desktop monitors parameters
(brightness, contrast, etc...) without having to touch the monitor
controls on it (everything is done through the VGA/DVI cable, using a
protocol called DDC/CI).

I reverse-engineered the protocol, as VESA asks to pay for it, no real
problem there. The thing is that for every monitor the project wants to
support, we need to create a database file, identifying which "number"
in the DDC/CI protocol controls which feature (brightness, contrast,
etc, etc...). Most of these numbers are standard (standard I had to
guess..), but some are manufacturer/monitor specific.

I contacted NEC/Mitubishi, Samsung and Fujitsu/Siemens, using their
support site:
 - The person responsible of writing the Windows/Mac tools for
NEC/Mitubishi contacted me a few days afterwards, and every time I have
a report of a monitor non-supported, I can contact him to fill the
controls that I don't know about. He also gave me some hints about the
general development of the application, really, really, nice.
 - Fujitsu/Siemens sent me the DDC/CI spec sheets of all their monitors
(they had only a few DDC/CI-capable monitors at that time). Perfect.
 - Samsung never replied (I tried to contact them twice. In fact, they
replied once, asking me to contact my local importer... What???).

The funny thing in the story is that NEC/Mitubishi and Fujitsu/Siemens
monitors are perfectly usable under Linux, without that tool, I mean,
you use the old-style "mechanical" way, i.e. you press your buttons in
front of your monitor and you adjust the settings.
On the other hand, Samsung has a few monitors with just an ON/OFF button
in front, no brightness/contrast or anything. They rely completely on
the Windows/Mac applications to control these parameters, so, without my
tools, these monitors are useless under Linux: you need to reboot on
Windows to change your parameters.

Conclusion: The company that takes the most advantage of having DDC/CI
support on Linux doesn't give us any support. While some others, who,
honestly, don't really need it (software control is more convenient, but
not more than just "more convenient" if you have buttons in front of
your monitor), support us actively.

Strange world, isn't it?

Best regards,

Nicolas