Binary Drivers
Quoted 6 lines · David Schwartz
If I bought the car from the manufacturer, it also must
include any rights the manufacturer might have to the car's use. That includes using the car to violate emission control measures. If I didn't buy the right to use the car that way (insofar as that right was owned by the car manufacturer), I didn't buy the whole care -- just *some* of the rights to use it.
just to be dense - what makes you think that the car manufacturer has
any legal right to violate emission control measures? What an utter nonsense (sorry).
So, lets stop the stupid car comparisons. They are no being funny any
more.
Martin
------------------------------------------------------
Martin Knoblauch
email: k n o b i AT knobisoft DOT de www: http://www.knobisoft.de
Quoted 9 lines · Martin Knoblauch
Quoted 6 lines · David Schwartz
If I bought the car from the manufacturer, it also must
include any rights the manufacturer might have to the car's use. That includes using the car to violate emission control measures. If I didn't buy the right to use the car that way (insofar as that right was owned by the car manufacturer), I didn't buy the whole care -- just *some* of the rights to use it.
Quoted 6 lines
just to be dense - what makes you think that the car manufacturer has
any legal right to violate emission control measures? What an utter nonsense (sorry).So, lets stop the stupid car comparisons. They are no being funny any
more.
Let's summarize the current situation:
1) Hardware vendors don't have to tell us how to program their products, as long as they provide some way to use it (i.e. binary blob driver).
2) Hardware vendors don't want to tell us how to program their products, because they think this information is their secret sauce (or maybe their competitor's secret sauce).
3) Hardware vendors don't tell us how to program their products, because they know about (1) and they believe (2).
4) We need products with datasheets because of our development model.
5) We want products with capabilities that these vendors advertise.
6) Products that satisfy both (4) and (5) are often scarce or non-existent.
So far, the suggestions I've seen to resolve the above conflict fall into three categories:
a) Force vendors to provide datasheets.
b) Entice vendors to provide datasheets.
c) Reverse engineer the hardware and write our own datasheets.
Solution (a) involves denial of point (1), mostly through the use of analogy and allegory. Alternatively, one can try to change the law through government channels.
Solution (b) requires market pressure, charity, or visionary management. We can't exert enough market pressure currently to make much difference. Charity sometimes gives us datasheets for old hardware. Visionary management is the future.
Solution (c) is what we do now, with varying degrees of success. A good example is the R300 support in the radeon DRM module.
Did I miss anything?
Quoted 16 lines · --- James C Georgas
Quoted 10 lines · Martin Knoblauch
Quoted 6 lines · David Schwartz
If I bought the car from the manufacturer, it also must
include any rights the manufacturer might have to the car's use. That includes using the car to violate emission control measures. If I didn't buy the right to use the car that way (insofar as that right was owned by the car manufacturer), I didn't buy the whole care -- just *some* of the rights to use it.just to be dense - what makes you think that the car manufacturer
has
Quoted 4 lines
any legal right to violate emission control measures? What an utter nonsense (sorry).
So, lets stop the stupid car comparisons. They are no being funny
Quoted 9 lines
any
Quoted 1 line
more.
Let's summarize the current situation:
1) Hardware vendors don't have to tell us how to program their products, as long as they provide some way to use it (i.e. binary blob driver).
Correct, as far as I can tell.
Quoted 4 lines
2) Hardware vendors don't want to tell us how to program their products, because they think this information is their secret sauce (or maybe their competitor's secret sauce).
- or they are ashamed to show the world what kind of crap they sell
- or they have lost (never had) the documentation themselves. I tend
to no believe this
Quoted 3 lines
3) Hardware vendors don't tell us how to program their products, because they know about (1) and they believe (2).
- or they are just ignorant
Quoted 2 lines
4) We need products with datasheets because of our development model.
- correct
Quoted 2 lines
5) We want products with capabilities that these vendors advertise.
we want open-spec products that meet the performance of the high-end
closed-spec products
Quoted 3 lines
6) Products that satisfy both (4) and (5) are often scarce or non-existent.
unfortunatelly
Quoted 6 lines
So far, the suggestions I've seen to resolve the above conflict fall into three categories:
a) Force vendors to provide datasheets.
Quoted 8 lines
b) Entice vendors to provide datasheets.
c) Reverse engineer the hardware and write our own datasheets.
Solution (a) involves denial of point (1), mostly through the use of analogy and allegory. Alternatively, one can try to change the law through government channels.
good luck
Quoted 7 lines
Solution (b) requires market pressure, charity, or visionary management.
We can't exert enough market pressure currently to make much difference.
Charity sometimes gives us datasheets for old hardware. Visionary management is the future.
- Old hardware is not interesting in most markets
- Visionary mamangement is rare
Quoted 3 lines
Solution (c) is what we do now, with varying degrees of success. A good example is the R300 support in the radeon DRM module.
But the R300 does not meet 5)
Cheers
Martin
------------------------------------------------------
Martin Knoblauch
email: k n o b i AT knobisoft DOT de www: http://www.knobisoft.de
James C Georgas <[email protected]> wrote:
[...]
Quoted 3 lines
Let's summarize the current situation:
1) Hardware vendors don't have to tell us how to program their products, as long as they provide some way to use it (i.e. binary blob driver).
No. They have absolutely no obligation to tell you anything. If they sell you a card with a binary driver that /only/ works with, say, Minix, it is up to you to buy it or not.
Quoted 3 lines
2) Hardware vendors don't want to tell us how to program their products, because they think this information is their secret sauce (or maybe their competitor's secret sauce).
And lots of other reasons, including that with detailed specs you might be able to continue using the same card for 3 or 5 years, when they'd love to sell you a replacement next year... Creating, vetting and maintaining specs is /hard/ work, and costs money. If it won't bring a measurable increase in income, why do it?
Quoted 2 lines
3) Hardware vendors don't tell us how to program their products, because they know about (1) and they believe (2).
The law says (1), and they know (2) for a fact.
Quoted 1 line
4) We need products with datasheets because of our development model.
Yep.
Quoted 1 line
5) We want products with capabilities that these vendors advertise.
Yep.
Quoted 2 lines
6) Products that satisfy both (4) and (5) are often scarce or non-existent.
Just too bad.
Quoted 4 lines
So far, the suggestions I've seen to resolve the above conflict fall into three categories:
a) Force vendors to provide datasheets.
How?
Quoted 1 line
b) Entice vendors to provide datasheets.
How?
Quoted 1 line
c) Reverse engineer the hardware and write our own datasheets.
Not always legal...
Quoted 2 lines
Solution (a) involves denial of point (1), mostly through the use of analogy and allegory.
These are big companies, who deal in hard realities and cold cash. Poetry won't get you anywhere.
Quoted 2 lines
Alternatively, one can try to change the law
through government channels.
Won't happen before open source is so prevalent that the point has long become moot.
Quoted 1 line
Solution (b) requires market pressure,
Will happen once open source has a large enough slice of a lucrative pie. I.e., it is happening today with "server class" machines.
Quoted 1 line
charity,
A company is bound /by law/ to make as much profit as possible. Whoever wants to go this route might spend some time as a neighbor to the Enron et al folks.
Quoted 1 line
or visionary management.
This cuts both ways... visionary management made small companies big, and huge companies dissappear from the face of the earth.
Quoted 1 line
We can't exert enough market pressure currently to make much difference.
OK.
Quoted 1 line
Charity sometimes gives us datasheets for old hardware.
OK.
Quoted 2 lines
Visionary
management is the future.
Don't they tell that all aspiring MBAs...
Quoted 2 lines
Solution (c) is what we do now, with varying degrees of success. A good example is the R300 support in the radeon DRM module.
And others.
And this is not the only avenue persued, not by far. Some developers are chummy with the engineers behind the devices they support, and get some help that way. There are people who convinced their companies to let them work on Linux drivers on their own time (with access to the people in the know and datasheets, one would presume), others have gone so far as to be able to work part-time on Linux drivers. Some companies have hired developers under NDA to develop drivers, others have given out datasheets (and access to sample hardware) under NDA (or just "don't give this out too freely") to interested developers. Then there are others (IBM comes to mind) where the company itself is officially developing drivers for their hardware. Sure, most of the more backstage deals you won't ever hear about, and for some of the other cases you might have absolutely no interest. Fact is, Linux has /by far/ the best hardware support of all operating systems out there. You only notice the (small) minority of devices that don't work (yet). Sure, it is mostly in the latest glitter where support is currently lacking, and this distorts the perspective quite a bit.
Signature · 4 lines
Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 2654431 Universidad Tecnica Federico Santa Maria +56 32 2654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 2797513
Do we have a right to reverse engineer hardware, or they are protected by patents or something similar that would prevent you from publishing results adn/or drivers (open source).
Are there any restrictions in how you obtain information - signal analyser, disassembly of windows driver, etc.
Rok Markovic
Quoted 3 lines · Rok Markovic
Do we have a right to reverse engineer hardware, or they are protected by patents or something similar that would prevent you from publishing results adn/or drivers (open source).
This is a pretty good resource:
http://www.chillingeffects.org/reverse/faq.cgi
Yes, there are probably patents covering this hardware stuff.. and that's why we have all those open source companies that have given their patents to an entity that promises to sue in retalitation if they try to use their patents against open source. So let's not worry about patents ok? They'd be screwed more than us if they try to use them.
Quoted 3 lines
Are there any restrictions in how you obtain information - signal analyser, disassembly of windows driver, etc.
Not as far as I am aware. Obviously if you were to disassemble a windows driver, add a wrapper and reassemble, that would be copying.. but if you are trying to figure out how something works by reverse engineering a windows driver then that's ok. At least it is where I live (Australia) because we have laws that allow us to ignore license restrictions that say "thou shalt not reverse engineer" for most interesting purposes. Maybe you have similar laws where you live. Maybe not.
Hope that helps,
Trent
Quoted 5 lines
Do we have a right to reverse engineer hardware, or they are protected by patents or something similar that would prevent you from publishing results
adn/or drivers (open source).
As I understand the issues, you have the right to reverse engineer hardware except where the DMCA applies. I don't see any way a patent or similar could prevent you from publishing results. Again, the DMCA might.
Quoted 3 lines
Are there any restrictions in how you obtain information - signal analyser,
disassembly of windows driver, etc.
There are a few things that might be able to impose such a restriction on you. If none of these apply, I think you should be okay: Any EULA, shrink-wrap, or click-through type agreement that might apply to the software (whether the driver, OS, analyzer, or whatever). Also, any actual agreement you entered into.
Patents don't provide any ability to keep things secret. Copyright doesn't apply to a creative work you made yourself, even if it describes the creative work of another in *functional* detail.
IANAL, and I might have missed something. IMO, the DMCA or a driver EULA are the only things you really need to worry about. It's hard to see how the DMCA would apply if we're not talking about some kind of content protection scheme.
DS
Quoted 1 line · David Schwartz
Patents don't provide any ability to keep things secret. Copyright doesn't apply to a creative work you made yourself, even if it describes the creative work of another in *functional* detail.
in fact, to get a Patent you are required to explain the invention in sufficant detail for somone 'normally skilled' in the field to be able to duplicate it. the Patent protection is a reward for _not_ keeping thing secret and publicising the details.
at least in that's how it's supposed to work.
David Lang
Combined responses:
Quoted 10 lines
Quoted 6 lines
If I bought the car from the manufacturer, it also must include any rights the manufacturer might have to the car's use. That includes using the car to violate emission control measures. If I didn't buy the right to use the car that way (insofar as that right was owned by the car manufacturer), I didn't buy the whole care -- just *some* of the rights to use it.
just to be dense - what makes you think that the car manufacturer has
any legal right to violate emission control measures? What an utter nonsense (sorry).
That's why I said "insofar as that right was owned by the car manufacturer". The example of emission control measures wasn't mine. I'm responding to a silly hypothetical.
Quoted 2 lines
So, lets stop the stupid car comparisons. They are no being funny any more.
They were never intended to be funny. They only become stupid when people deliberately pointed out the cases where the examples differ from the case we're realling interested in. I agree that examples involving cases where there are specific laws (such as emissions control) are silly.
The point is that any rights the manufacturer may have had to the car should have been sold along with the car, otherwise it's not a normal free and clear sale. A normal free and clear sale includes all rights to the item sold, except those specific laws allows the manufacturer to retain.
All the issues about whether the manufacturer has the right to break the law or whether the manufacturer has to help you break the law are not in any way relevant to the hardware issue we were discussion. Someone brought them up just to sidetrack the analogies.
That's a very good way to make an analogy seem irrelevent, but it's cheating. So long as you stick to the issues that relate, the analogy is nearly perfect. See, for examlek, James C. Georgas post.
--
Quoted 3 lines
Solution (a) involves denial of point (1), mostly through the use of analogy and allegory. Alternatively, one can try to change the law through government channels.
One doesn't need to change the law, just enforce it.
I simply do not accept the argument that it is lawful for a manufacturer to sell a physical object in a normal free and clear sale and then refuse to disclose the knowledge necessary to use it. (And by that I mean necessary to use it any reasonable way, not just the way the manufacturer intended it to be used.)
This same issue has been pressed in other areas and I think it's time it be pressed with graphics cards.
DS
David Schwartz <[email protected]> wrote:
[..]
.
Quoted 4 lines
The point is that any rights the manufacturer may have had to the car should have been sold along with the car, otherwise it's not a normal free and clear sale. A normal free and clear sale includes all rights to the item sold, except those specific laws allows the manufacturer to retain.
This is complete nonsense. The car manufacturer can very well agree with you to sell you the right to only drive the car on weekdays, and rent it off on weekends. Nothing forces them to sell "all rights they have on the car".
[...]
Quoted 3 lines
I simply do not accept the argument that it is lawful for a manufacturer to sell a physical object in a normal free and clear sale and then refuse to disclose the knowledge necessary to use it.
Ask a lawyer about this, don't impose your wacky legal theories on us.
Quoted 3 lines
(And by that I mean necessary to
use it any reasonable way, not just the way the manufacturer intended it to be used.)
Define "reasonable way". The manufacturer could very well define it as "use the XYZ graphics card on Windows XP service pack 2", as it was designed specifically for that environment. Everything else (use on Linux, for example) is then "unreasonable use", and need not be supported at all.
Quoted 1 line
This same issue has been pressed in other areas
Examples?
Quoted 2 lines
and I think it's time it be
pressed with graphics cards.
Signature · 4 lines
Dr. Horst H. von Brand User #22616 counter.li.org Departamento de Informatica Fono: +56 32 2654431 Universidad Tecnica Federico Santa Maria +56 32 2654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 2797513