Mer/Status/SmartQ5 - Revision history

imported_>amigadave: {{Mer}}

2010-09-22T10:56:26Z

← Older revision		Revision as of 10:56, 22 September 2010
Line 1:		Line 1:
			{{Mer}}

	For general SmartQ tips, see [[../SmartQ \| tips for SmartQ]].		For general SmartQ tips, see [[../SmartQ \| tips for SmartQ]].

Line 269:		Line 271:
	* Hardware buttons support		* Hardware buttons support
	* [[/XAA\|XAA]]		* [[/XAA\|XAA]]

	~~[[Category:Mer]]~~

2010-02-01T21:24:39Z

← Older revision		Revision as of 21:24, 1 February 2010
Line 1:		Line 1:
			For general SmartQ tips, see [[../SmartQ \| tips for SmartQ]].

	Notes on SmartQ 5 MID:		Notes on SmartQ 5 MID:

2009-07-18T15:33:28Z

link to XAA

2009-07-18T15:30:00Z

Mer/Hardware/SmartQ5 moved to Mer/Status/SmartQ5: keep all the /Status HW together

← Older revision	Revision as of 15:30, 18 July 2009
(No difference)

2009-06-04T16:25:20Z

Hardware support

2009-06-04T15:50:03Z

← Older revision		Revision as of 15:50, 4 June 2009
Line 250:		Line 250:

	Offset in NAND is meant as offset from 16/8mb end offset in blocks (512 byte blocks). If offset is 0, it is not meant to be in the NAND image (qi doesn't make any sense there, nor rootfs, etc)		Offset in NAND is meant as offset from 16/8mb end offset in blocks (512 byte blocks). If offset is 0, it is not meant to be in the NAND image (qi doesn't make any sense there, nor rootfs, etc)


			== Hardware support ==

			* Power management
			** Bluetooth
			** USB otg / Host
			** WiFi (on/off, PSM)
			** Backlight control + dimming/turn off
			* SD slot automounting
			* Open source upgrade tool and initramfs
			* Updated u-boot
			* Audio: Headphone / loudspeaker switch
			* TV out
			* Microphone?

2009-05-25T13:28:32Z

Boot process

← Older revision		Revision as of 13:28, 25 May 2009
Line 208:		Line 208:
	This is where qi is placed, maximum 16 blocks size, zero out the remaining 2/1027 blocks		This is where qi is placed, maximum 16 blocks size, zero out the remaining 2/1027 blocks

	Qi will then (see /qi/src/cpu/s3c6410/start_qi.c) try to locate a SmartQ firmware image (see genimage for format, or same file, struct FirmHead on ~~16384~~ blocks before the end, or ~~32768~~ blocks before the end, and load u-boot from the firmware image.		Qi will then (see /qi/src/cpu/s3c6410/start_qi.c) try to locate a SmartQ firmware image (see genimage for format, or same file, struct FirmHead on 32768 blocks before the end, or 16384 blocks before the end, and load u-boot from the firmware image.

	If this fails it will load u-boot from 512+18 blocks before the end, maximum size 512 blocks.		If this fails it will load u-boot from 512+18 blocks before the end, maximum size 512 blocks.

2009-05-22T11:26:03Z

Firmware image format

← Older revision		Revision as of 11:26, 22 May 2009
Line 232:		Line 232:
	<pre>		<pre>
	typedef struct _firmware_fileheader {		typedef struct _firmware_fileheader {
	uint32_t magic; // '~~2009~~'		uint32_t magic; // '2\0\09'= 0x32 0x00 0x00 0x39
	uint32_t check_sum; // for 8 ~ .fh_size		uint32_t check_sum; // for 8 ~ .fh_size
	uint32_t fh_size;		uint32_t fh_size;

2009-05-22T11:25:23Z

Firmware image format

← Older revision		Revision as of 11:25, 22 May 2009
Line 239:		Line 239:
	char vendor[32]; // XXX: uint32_t vendor_string_len; char vendor_string[]		char vendor[32]; // XXX: uint32_t vendor_string_len; char vendor_string[]
	//uint32_t nand_off_end1=16M/512, nand_off_end2=8M/512; // offset from INAND END(BLOCKS)		//uint32_t nand_off_end1=16M/512, nand_off_end2=8M/512; // offset from INAND END(BLOCKS)
	uint32_t component_count /* = 4*/;		uint32_t component_count /* = 5*/;
	struct {		struct {
	struct {		struct {
	uint32_t offset, size;		uint32_t offset, size; /* nand offset in blocks, sizes and file offset in bytes */
	} file, nand;		} file, nand;
	uint32_t check_sum;		uint32_t check_sum;

2009-05-18T17:06:33Z

Firmware image format

← Older revision		Revision as of 17:06, 18 May 2009
Line 249:		Line 249:
	</pre>		</pre>

	Offset in NAND is meant as offset from 16/8mb end offset in blocks (512 byte blocks)		Offset in NAND is meant as offset from 16/8mb end offset in blocks (512 byte blocks). If offset is 0, it is not meant to be in the NAND image (qi doesn't make any sense there, nor rootfs, etc)