Linked by Thom Holwerda on Tue 9th Nov 2010 22:24 UTC, submitted by koki
Thread beginning with comment 449443
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
More News »
Sponsored Links



Member since:
2005-07-22
This loadable microcode is now new.
I was writing loadable microcode for VAX & PDP-11 Computers in the early 1980's.
In my simplistic view (waiting for incoming missiles) if you have the hardware and it requires loadable firmware/microcode to run then how you load it is immaterial, i.e. it don't matter if it loaded from Windows or Linux or unix or Fred's Toy O/S.
Again in my simplistic view, if you have legally purchased said H/W then it is not complete until you load the F/W.
What does matter to me is that said firmware is binary identical to that shipped by the H/W manufacturer. If you start messing with their original then sorry, you have messed up.
IN my view if you write your own code and release it under the GPL then that's fine as well. Just don't break into the manufacturers blob. Leave it alone and IMHO (IANAL etc) you should be fine legally.
If H/W makers decide to insist that the F/W can only be loaded into the device from a certain O/S then I think they are open to lawsuits but given the totally broken & messed up morass that is the US legals system I wouldn't be surprised if such suits failed.