Task:Community firmware image distribution - Revision history

amigadave: wikify, categorize

2010-05-11T08:13:56Z

wikify, categorize

← Older revision		Revision as of 08:13, 11 May 2010
Line 1:		Line 1:
-	As part of the community efforts to backport Fremantle components (Mer), there have been discussions on how the community can provide	+	As part of the community efforts to backport Fremantle components ([[Mer]]), there have been discussions on how the community can provide firmware images containing proprietary contents (nokia software, hardware firmware blobs, 3rd party?, etc.) and distribute these.
-	firmware images containing proprietary contents (nokia software, hardware firmware blobs, 3rd party?, etc.) and distribute these.	+

	A proposal to deal with this problem could be to, allow/license/etc maemo.org, directed by the Maemo Community Council, elected by the Maemo Community, to do the following:		A proposal to deal with this problem could be to, allow/license/etc maemo.org, directed by the Maemo Community Council, elected by the Maemo Community, to do the following:
Line 10:		Line 9:
	The resulting firmware images would only be downloadable through providing a valid MAC address for a Nokia Internet Tablet product and agreeing to a license covering the user's use of the firmware image, just like tablets-dev.nokia.com.		The resulting firmware images would only be downloadable through providing a valid MAC address for a Nokia Internet Tablet product and agreeing to a license covering the user's use of the firmware image, just like tablets-dev.nokia.com.

-	The effect of this could be, through the maemo.org process, that the community could be able to remix the firmware images, backport	+	The effect of this could be, through the maemo.org process, that the community could be able to remix the firmware images, backport Fremantle components without having to directly deal with licensing and could make it possible to provide alternative distributions for the tablets without them sacrificing hardware interfaces, etc.
-	Fremantle components without having to directly deal with licensing and could make it possible to provide alternative distributions for	+
-	the tablets without them sacrificing hardware interfaces, etc.	+

	== First request: Distribution of initfs jffs2 (or other formats) image from maemo.org ==		== First request: Distribution of initfs jffs2 (or other formats) image from maemo.org ==

-	Of the closed source content in the Diablo initfs, we would like to be able to distribute (from maemo.org) to N800, N810 and N810WE users an initfs image containing the following bits (paths relative to initfs) under a scheme similar to above:	+	Of the closed source content in the Diablo initfs, we would like to be able to distribute (from maemo.org) to [[Nokia N800\|N800]], [[Nokia N810\|N810]] and N810WE users an initfs image containing the following bits (paths relative to initfs) under a scheme similar to above:

	Wi-Fi and connectivity related:		Wi-Fi and connectivity related:
Line 48:		Line 45:

	* [http://lists.maemo.org/pipermail/maemo-community/2008-December/002813.html Proposal for community firmware images] on maemo-community		* [http://lists.maemo.org/pipermail/maemo-community/2008-December/002813.html Proposal for community firmware images] on maemo-community
		+
		+	[[Category:Tasks]]

stskeeps: /* First request: Distribution of initfs jffs2 (or other formats) image from maemo.org */

2009-01-09T20:48:06Z

First request: Distribution of initfs jffs2 (or other formats) image from maemo.org

← Older revision		Revision as of 20:48, 9 January 2009
Line 37:		Line 37:
	Device state management:		Device state management:

-	* Any binaries and libraries that are needed to make DSME function and run.	+	* Any binaries and libraries that are needed to make DSME function and run (for basic functionality, backlight, wlan-cal, etc.)

	Various:		Various:

stskeeps: /* First request: Distribution of initfs jffs2 (or other formats) image from maemo.org */

2009-01-09T20:39:40Z

First request: Distribution of initfs jffs2 (or other formats) image from maemo.org

← Older revision		Revision as of 20:39, 9 January 2009
Line 16:		Line 16:
	== First request: Distribution of initfs jffs2 (or other formats) image from maemo.org ==		== First request: Distribution of initfs jffs2 (or other formats) image from maemo.org ==

-	Of the closed source content in the Diablo initfs, we would like to be able to distribute (from maemo.org) to N800, N810 and N810WE users a initfs image containing the following bits (paths relative to initfs) under a scheme similar to above:	+	Of the closed source content in the Diablo initfs, we would like to be able to distribute (from maemo.org) to N800, N810 and N810WE users an initfs image containing the following bits (paths relative to initfs) under a scheme similar to above:

	Wi-Fi and connectivity related:		Wi-Fi and connectivity related:

stskeeps: Adding information on initfs jffs distribution

2009-01-09T19:43:09Z

Adding information on initfs jffs distribution

← Older revision		Revision as of 19:43, 9 January 2009
Line 13:		Line 13:
	Fremantle components without having to directly deal with licensing and could make it possible to provide alternative distributions for		Fremantle components without having to directly deal with licensing and could make it possible to provide alternative distributions for
	the tablets without them sacrificing hardware interfaces, etc.		the tablets without them sacrificing hardware interfaces, etc.
		+
		+	== First request: Distribution of initfs jffs2 (or other formats) image from maemo.org ==
		+
		+	Of the closed source content in the Diablo initfs, we would like to be able to distribute (from maemo.org) to N800, N810 and N810WE users a initfs image containing the following bits (paths relative to initfs) under a scheme similar to above:
		+
		+	Wi-Fi and connectivity related:
		+
		+	* /lib/modules/2.6.21-omap1/umac.ko (Reason: Counterpart to cx3110x driver)
		+	* /usr/lib/hotplug/firmware/3826.arm (Reason: Firmware for STLC45xx)
		+	* /usr/sbin/wlan-cal (Reason: providing calibration data to cx3110x)
		+	* /usr/bin/bt-cal (Reason: calibration of bluetooth chip)
		+	* From outside initfs, stlc45xx-cal-0.1.2 , found at http://tablets-dev.nokia.com/d2.php (Reason: binary only initfs utility for providing calibration data to the new open source driver stlc45xx)
		+
		+	Battery handling:
		+
		+	* /usr/bin/bme_RX-34 (for proper handling of battery and charging)
		+	* /usr/bin/bme_RX-44 (as above)
		+
		+	RTC and alarm:
		+
		+	* /usr/bin/retutime (for alarm setting, time handling, etc)
		+
		+	Device state management:
		+
		+	* Any binaries and libraries that are needed to make DSME function and run.
		+
		+	Various:
		+
		+	* /usr/bin/cal-tool (for access to R&D flags, etc for purposes of system development)
		+
		+	We would also like clarification of the licensing of /linuxrc.

	== See also ==		== See also ==

	* [http://lists.maemo.org/pipermail/maemo-community/2008-December/002813.html Proposal for community firmware images] on maemo-community		* [http://lists.maemo.org/pipermail/maemo-community/2008-December/002813.html Proposal for community firmware images] on maemo-community

generalantilles at 21:47, 18 December 2008

2008-12-18T21:47:24Z

← Older revision		Revision as of 21:47, 18 December 2008
Line 14:		Line 14:
	the tablets without them sacrificing hardware interfaces, etc.		the tablets without them sacrificing hardware interfaces, etc.

-	~~Associated maemo-community thread~~ [http://lists.maemo.org/pipermail/maemo-community/2008-December/002813.html ~~here~~]	+	== See also ==
		+
		+	* [http://lists.maemo.org/pipermail/maemo-community/2008-December/002813.html Proposal for community firmware images] on maemo-community

stskeeps: Removed hard-wrap

2008-12-18T16:12:18Z

Removed hard-wrap

← Older revision		Revision as of 16:12, 18 December 2008
Line 1:		Line 1:
-	As part of the community efforts to backport Fremantle components	+	As part of the community efforts to backport Fremantle components (Mer), there have been discussions on how the community can provide
-	(Mer), there have been discussions on how the community can provide	+	firmware images containing proprietary contents (nokia software, hardware firmware blobs, 3rd party?, etc.) and distribute these.
-	firmware images containing proprietary contents (nokia software,	+
-	hardware firmware blobs, 3rd party?, etc.) and distribute these.	+

-	A proposal to deal with this problem could be to, allow/license/etc	+	A proposal to deal with this problem could be to, allow/license/etc maemo.org, directed by the Maemo Community Council, elected by the Maemo Community, to do the following:
-	maemo.org, directed by the Maemo Community Council, elected by the	+
-	Maemo Community, to do the following:	+

-	*On their servers construct, based on build scripts provided by	+	*On their servers construct, based on build scripts provided by community developers, firmware images (FIASCO images, jffs images, etc.) containing the proprietary contents.
-	community developers, firmware images (FIASCO images, jffs images,	+
-	etc.) containing the proprietary contents.	+

	*The resulting images will then be provided by the maemo.org servers.		*The resulting images will then be provided by the maemo.org servers.

-	The resulting firmware images would only be downloadable through	+	The resulting firmware images would only be downloadable through providing a valid MAC address for a Nokia Internet Tablet product and agreeing to a license covering the user's use of the firmware image, just like tablets-dev.nokia.com.
-	providing a valid MAC address for a Nokia Internet Tablet product and	+
-	agreeing to a license covering the user's use of the firmware image,	+
-	just like tablets-dev.nokia.com.	+

-	The effect of this could be, through the maemo.org process, that the	+	The effect of this could be, through the maemo.org process, that the community could be able to remix the firmware images, backport
-	community could be able to remix the firmware images, backport	+	Fremantle components without having to directly deal with licensing and could make it possible to provide alternative distributions for
-	Fremantle components without having to directly deal with licensing	+	the tablets without them sacrificing hardware interfaces, etc.
-	and could make it possible to provide alternative distributions for	+
-	the tablets without them sacrificing	+
-	hardware interfaces, etc.	+

	Associated maemo-community thread [http://lists.maemo.org/pipermail/maemo-community/2008-December/002813.html here]		Associated maemo-community thread [http://lists.maemo.org/pipermail/maemo-community/2008-December/002813.html here]

stskeeps: New page: As part of the community efforts to backport Fremantle components (Mer), there have been discussions on how the community can provide firmware images containing proprietary contents (n...

2008-12-18T12:51:31Z

New page: As part of the community efforts to backport Fremantle components (Mer), there have been discussions on how the community can provide firmware images containing proprietary contents (n...

New page

As part of the community efforts to backport Fremantle components
(Mer), there have been discussions on how the community can provide
firmware images containing proprietary contents (nokia software,
hardware firmware blobs, 3rd party?, etc.) and distribute these.

A proposal to deal with this problem could be to, allow/license/etc
maemo.org, directed by the Maemo Community Council, elected by the
Maemo Community, to do the following:

*On their servers construct, based on build scripts provided by
community developers, firmware images (FIASCO images, jffs images,
etc.) containing the proprietary contents.

*The resulting images will then be provided by the maemo.org servers.

The resulting firmware images would only be downloadable through
providing a valid MAC address for a Nokia Internet Tablet product and
agreeing to a license covering the user's use of the firmware image,
just like tablets-dev.nokia.com.

The effect of this could be, through the maemo.org process, that the
community could be able to remix the firmware images, backport
Fremantle components without having to directly deal with licensing
and could make it possible to provide alternative distributions for
the tablets without them sacrificing
hardware interfaces, etc.

Associated maemo-community thread [http://lists.maemo.org/pipermail/maemo-community/2008-December/002813.html here]