U-Boot source tree for PM9G45 v1.2, PM9263 and PM9261
-----------------------------------------------------
Release: 03.09.2010

1. Get the U-Boot
	
	A. from denx.de

	$ git clone git://git.denx.de/u-boot.git u-boot
	
	B. from Ronetix download site

	$ wget http://download.ronetix.info/boards/linux/u-boot/u-boot-2010.06/u-boot-v2010.06.tar.bz2
	$ tar xjf u-boot-v2010.06.tar.bz2 -C u-boot


2. Apply the porvided patches

	$ wget http://download.ronetix.info/boards/linux/u-boot/u-boot-2010.06/0001-pm9g45-add-LCD.patch
	$ wget http://download.ronetix.info/boards/linux/u-boot/u-boot-2010.06/0002-DS2401-provides-48-bits-serial-number-using-Dallas-1.patch
	$ wget http://download.ronetix.info/boards/linux/u-boot/u-boot-2010.06/0003-PM9G45-uses-DS2401-to-set-the-MAC-address-of-the-Eth.patch
	$ wget http://download.ronetix.info/boards/linux/u-boot/u-boot-2010.06/0004-PM9263-uses-DS2401-to-set-the-MAC-address-of-the-Eth.patch
	$ wget http://download.ronetix.info/boards/linux/u-boot/u-boot-2010.06/0005-PM9261-uses-DS2401-to-set-the-MAC-address-of-the-Eth.patch
	$ cd u-boot
	$ patch -p1 < ../*.patch
	
2a. Apply this patch if you have a PM9263 with 128MB SDRAM
	$ wget http://download.ronetix.info/boards/linux/u-boot/u-boot-2010.06/0006-PM9263-SDRAM-128MB.patch
	$ patch -p1 < ../0006-PM9263-SDRAM-128MB.patch

3. Configure and build

	A. For pm9g45

		$ make pm9g45_config

	B. For pm9263

		$ make pm9263_config

	C. For pm9261

		$ make pm9261_config

	The common part for all boards:

		$ export USE_PRIVATE_LIBGCC=yes
		$ export CROSS_COMPILE=/usr/cross/arm-linux-4.3.3/bin/arm-linux-
		$ make



4. Look at manual/README files on how to build and program U-Boot with more details


5. There are and pre-built images

	pm9g45_v1.2_u-boot.bin
	pm9263_u-boot.bin
	pm9261_u-boot.bin

Note:
	If the board comes without DS2401 SN chip then
	to use the network in U-boot you should do this:

		U-Boot> setenv ethaddr "02:01:02:03:04:05"

	Remember to put MAC address valid for production.

Note: Unique file identification

	The name of the files should be descriptive and easy to remember and use.
	Sometimes their names are not enough to distinguish files, so file SHA256 
	message digest(check sum) will be used to identify them,
	in some cases the UUID(universally unique identifier) could be used.
	Check md5sum.txt and sha256sum.txt.