Linked by Thom Holwerda on Sun 1st Oct 2006 10:34 UTC, submitted by Johan Berg
OpenBSD Theo wrote a letter at large to the open source community urging us to take a stand. In the letter Theo provides information on how to contact Intel and helpful hints on how to explain benefits of open documentation to any vendor.
Thread beginning with comment 167249
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Buy AMD Instead
by Dirge on Sun 1st Oct 2006 12:36 UTC in reply to "RE[2]: Buy AMD Instead"
Dirge
Member since:
2005-07-14

Sure but what stuff is that? I agree, a complete HCL would be helpful.

I did see these sites linked in the comments

http://vendorwatch.org/index.php?title=Main_Page

http://www.fsf.org/campaigns/hardware.html

Reply Parent Score: 2

RE[4]: Buy AMD Instead
by hackmykack on Sun 1st Oct 2006 12:44 in reply to "RE[3]: Buy AMD Instead"
hackmykack Member since:
2006-10-01

hey Dirge,

took a look at those links man ...

thats exactly what I mean ...

Every release of the kernel or bsd should have a listing of new hardware supported perfectly ... out of the box ....

The devs are in the best position to tell us this ...

Then I as an opensource user can vote with my feet.

Now wouldnt that be sooo much more useful ...

Reply Parent Score: 2

RE[5]: Buy AMD Instead
by Ookaze on Mon 2nd Oct 2006 15:17 in reply to "RE[4]: Buy AMD Instead"
Ookaze Member since:
2005-11-14

Every release of the kernel or bsd should have a listing of new hardware supported perfectly ... out of the box ....
The devs are in the best position to tell us this ...
Then I as an opensource user can vote with my feet.
Now wouldnt that be sooo much more useful ...


What you want is not possible and comes from the fact that you don't know what you're talking about.
I mean, marketing is designed so that you don't understand what you're talking about.
You see, there's a difference between a product with some name, and the chips inside it, for which drivers are written.
The kernel devs can know about those chips and write drivers for them. But they can't know every name of every products that use these chips.
And the IHV don't want you to know these relations chips-product either, as they can make you pay more for a functionality that is just a config option to check in the driver (but not accessible to the consumer).
Do you see the problem ?

Reply Parent Score: 2