Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
Note: You can take 10% off all Slashdot Deals with coupon code "slashdot10off." ×

Comment Exactly the same kind. (Score 3, Interesting) 35

Re the last paragraph. That is not entirely true, as Intel appear to be able to integrate new chipsets during the time they are released (but only to next tier manufacture) before the public can buy anything using it.

What kind of "peeing on it" has been done to the Intel drivers to get them integrated ?

Exactly the same kind. It's possible to do for anything, it just takes time.

The reason Intel is able to do this ahead of general release, when other vendors aren't, is that it does not lose them a competitive advantage.

First, there is no issue of another manufacturer producing "pin and register compatible devices", and undercutting Intel, because Intel's graphics are integrated into the CPU; you'd have to build an entire Intel compatible CPU as well, and you'd have to do it competitively in terms of price point.

Second, no one really wants to emulate Intel Integrated Graphics in silicon, since there's really no advantage to doing so, since the chips have inferior performance relative to the competition.

So there's really nothing lost by Intel pre-announcing all of the information needed to make a driver, or even publishing source code for the driver, since doing so will sell more Intel chips, not less. For other GPU vendors, this is simply not the case, and there's no economic value in such pre-disclosure.

Comment The whole posting is disengenuous. (Score 3, Insightful) 35

The whole posting is disengenuous.

"the R9 Fury isn't yet in good shape on the open-source driver"

The card won't be changing to fix this; the driver will have to change to accommodate the card; therefore it is more correct to say "The Open Source driver is not yet in good shape on the R9 Fury". In other words, it's not the hardware's fault that the driver doesn't support it yet.

"AMD's open-source developers haven't yet found the time to implement power management / re-clocking support"

The power management model in Linux is Linux's responsibility, not AMD's. The authors of the Open Source driver are accountable *only* for writing callbacks for the device power management component, and populating the structure. It's my understanding that Linux lacks a uniform model for use by all graphics drivers, in this regard. his is a Linux issue, not an AMD issue.

Also:

In general, in a hardware world, you either NDA people, or the Open Source is going to lag the closed source, period. This is because openly manipulating code related to an unreleased hardware product in a publicly accessible source repository, instead of a privately held repository, is tantamount to preannouncing your hardware to competitors. You might as well have the CEO call a press conference, and then shoot themselves in the head in public.

Open Source projects have a secondary problem in that, even if the driver source was developed entirely by engineers within AMD, and released the same day as the hardware was made available, the Open Source projects aren't going to be happy just integrating the code as is. They will insist on peeing on it to make it smell like themselves, just as cats do with new furniture, and this will take time. You can either have closed source, or you can have it integrated later than the release date, but you can not have both.

Comment Re:I can tell you how the story ends (Score 1) 148

After the app is released, people will flock to the cab app during peak hours because of the cheaper pricing.

That is already happening in cities like San Francisco and New York (without the app).

Taxi cabs simply do not have the extra capacity during peak hours. In New York, a famous black neurosurgeon can't seem to catch a cab, but as a white person in SF, I can't even seem to catch a cab either when I really need one (and as it turns out, I tend to need one during peak hours when everyone else wants one).

The Medaillon system assumes the demand is constant 24 hours a day 7 days a week. It does not increase the number of drivers during peak hours, and at the same time, it forces drivers to work during off-peak hours when nobody needs them to try to recoup the already very high sunk cost of the Medaillon.

You scratch my tape, and I'll scratch yours.

Working...