|
2010-04-01
, 10:11
|
Posts: 999 |
Thanked: 1,117 times |
Joined on Dec 2009
@ earth?
|
#12
|
The Following User Says Thank You to johnel For This Useful Post: | ||
|
2010-04-01
, 10:26
|
Posts: 81 |
Thanked: 45 times |
Joined on Dec 2009
|
#13
|
Considering the rumors of some of the DRM implementation in Maemo 6/Harmattan, I'm not so sure. Seems like you were going have to choose between having a free open-hackable device and a semi-hackable device (e.g. no kernel modifications if you wanted to keep the access to DRM files).
The Following User Says Thank You to dov For This Useful Post: | ||
|
2010-04-01
, 11:38
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#14
|
The MeeGo Security framework (which is what was called Maemo 6 Security Framework) is highly configurable. It's up to the device vendor to define the level of openness of a device and it's up to the customers to buy a device with the desired levels of openness.
No matter what, MeeGo will fulfill the requirements of the licenses of the components integrated.
|
2010-04-01
, 11:53
|
|
Posts: 1,671 |
Thanked: 11,478 times |
Joined on Jun 2008
@ Warsaw, Poland
|
#15
|
As far as I understand there are 2 However if I wanted to create a custom image for the n900 I can do that but I would have to exclude the closed components.
Are the components seperate enough so I can build a custom image on the n900 and install the closed components too?
The Following 7 Users Say Thank You to Stskeeps For This Useful Post: | ||
|
2010-04-05
, 13:02
|
Posts: 345 |
Thanked: 467 times |
Joined on Nov 2007
@ Germany
|
#16
|
No matter what, MeeGo will fulfill the requirements of the licenses of the components integrated.
|
2010-04-05
, 13:07
|
Posts: 345 |
Thanked: 467 times |
Joined on Nov 2007
@ Germany
|
#17
|
|
2010-04-05
, 13:16
|
|
Posts: 2,355 |
Thanked: 5,249 times |
Joined on Jan 2009
@ Barcelona
|
#18
|
A “User Product” is either (1) a “consumer product”, which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, “normally used” refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
“Installation Information” for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
(of course some content becomes unavailable when one switch to its own kernel, for example DRM)
The Following User Says Thank You to javispedro For This Useful Post: | ||
|
2010-04-05
, 15:12
|
Posts: 345 |
Thanked: 467 times |
Joined on Nov 2007
@ Germany
|
#19
|
So, dunno. I don't think the GPLv3 will allow for operators to sell devices where you cannot enter "open mode" (would violate the first bold statement), but Nokia might be allowed to disallow the download & use of DRM'd apps and media in "open mode" (might be allowed as per the second bold statement).
The Following User Says Thank You to Master of Gizmo For This Useful Post: | ||
|
2010-04-05
, 16:11
|
|
Posts: 2,355 |
Thanked: 5,249 times |
Joined on Jan 2009
@ Barcelona
|
#20
|
Hightlight 2 imho has nothing to do with this. It imho only sais that nokia/intel do not have to provide any guarantee on the parts the hacker modified. Still as of highlight 1 they must not add artifical limitations to the part the hacker did not touch.
No matter what, MeeGo will fulfill the requirements of the licenses of the components integrated.
http://maemo.org/profile/view/qgil/ + http://qt-project.org