Difference between revisions of "Porting Raspbian"
Line 20: | Line 20: | ||
=== Device Template === | === Device Template === | ||
*a device template for the Pi so it's specific MD needs are recognized and implemented automatically, proper devices started, etc... | *a device template for the Pi so it's specific MD needs are recognized and implemented automatically, proper devices started, etc... | ||
− | + | *mac lookup: B8:27:EB:00:00:00 - B8:27:EB:FF:FF:FF Raspberry Pi Foundation | |
+ | ** /usr/pluto/bin/convert_mac B8:27:EB:00:00:00 = 202481585881088 | ||
+ | ** /usr/pluto/bin/convert_mac B8:27:EB:FF:FF:FF = 202481602658303 | ||
=== Booting - goal === | === Booting - goal === | ||
*diskless boot (nfs rootfs actually) | *diskless boot (nfs rootfs actually) |
Revision as of 06:11, 27 August 2012
This will attempt to highlight some of the requirements/process intended/followed for porting lmce to raspbian for use on the raspberry pi.
Contents
TODO
Builder
Many scripts are used to create a builder and perform a build.
- build a builder - based on an old create_builder.sh script - done
- creates raspbian build environment AND lucid i386 build environments (one script to build them all :P)
- source is shared between multiple chroot build environments
- database is shared between multiple chroot build environments (mysqld runs on host system)
- mysqld seg faults when run under static qemu in the armhf chroot, solution above
- Conf files need update - most of this is done, needs a little re-work
- builder.conf, raspbian.conf? (from ubuntu.conf/debian.conf)
- Build dependencies list needs updating. - ongoing, lots to remove probably, needs testing (laborious)
- build scripts need update - mostly done
- alter prepare-scripts to accomodate new distro, new flavor and new arch, where required - done
- alter build-scripts to accomodate new distro, new flavor and new arch, where required - done
- build-maindebs.sh - need to disable building some packages on RPi, namely game stuff and pre-built binary stuff (uirt, etc) - done
- attempt a build - working...
Creating Pi MD
Device Template
- a device template for the Pi so it's specific MD needs are recognized and implemented automatically, proper devices started, etc...
- mac lookup: B8:27:EB:00:00:00 - B8:27:EB:FF:FF:FF Raspberry Pi Foundation
- /usr/pluto/bin/convert_mac B8:27:EB:00:00:00 = 202481585881088
- /usr/pluto/bin/convert_mac B8:27:EB:FF:FF:FF = 202481602658303
Booting - goal
- diskless boot (nfs rootfs actually)
- using nfs for rootfs with kernel on an SD card IS possible: kernel is loaded by gpu prior to boot, video config and kernel are both on the SD card.
- need raspbian diskless image, disklesscreatetbz?, etc.
- NewMDInteractor/CreateDiskless likely need changes to support multi arch/multi distro, in conjunction with RaspberryPi as MD device template - needs investigation
- maybe not, as it isn't pxe the pnp system could detect the MAC and setup the DT and extract an debootstrapped image, could be all that is required
- boot scripts
- avwizard
- current avwizard uses X, raspi will not be, need alternate method
- initially simple and functional - whiptail initially
- graphics setup is performed by gpu prior to the kernel boot.
- method of setting/determining graphics mode - config.txt - changing resolution, anything really, requires reboot for gpu init
Install
- build a diskless image to untar similar to i386
- SD fat32 formatted with RPi boot files and MD initial config installed (can be done easily from a Windows PC or ...)
UI/Media
- qOrbiter on Pi
- qMediaPlayer on Pi?
- omxplayer player & streamer pair?
- as mpeg2 is now available on the RPi it is possible a streamer may not be required, at least initially
Other
- arm libs required for pre-compiled libraries (usb-uirt, external media identifier?/id-my-disc?, more?)
- mythtv frontend is too heavy for RPi, recordings will need to be natively played by omxplayer
DONE
New database data
Linuxmce uses the database at build time when creating deb packages for dependencies and later at install time to install those dependencies, add repositories to /etc/sources.list and so on. Since on every release some packages tend to change names or split/merge into others, updating the packages tables is time consuming and you need to do some install/fix cycles before figuring them all out.
Add Distro and Repositories
- update the 'Distro' table, add Raspbian: (then sqlCVS diff/get batch approved/sqlCVS udpate) - Done.
insert into Distro (Description, FK_OperatingSystem, Installer, SourceCode, Confirmed, InstallerURL ) values ('Raspbian Wheezy', 1, 'ConfirmDependencies_Debian.sh', 'src', 1, 'installDebian.php')
- update the 'RepositorySource' table, add the main raspbian repo and an lmce raspbian repo [2 entries]: (then sqlCVS diff/get batch approved/sqlCVS update) - Done.
insert into RepositorySource (FK_OperatingSystem, FK_Distro, FK_RepositoryType, Description, Define, Instructions) values ( 1, 19, 1, 'Raspbian', 'Raspbian', 'This package is part of Raspbian') insert into RepositorySource (FK_OperatingSystem, FK_Distro, FK_RepositoryType, Description, Instructions) values (1, 19, 1, 'Raspbian LinuxMCE addons', 'LinuxMCE packages for Raspbian')
- update the 'RepositorySource_URL' table, add the URLs for the 2 repositories above [2 entries]: (then sqlCVS diff/get batch approved/sqlCVS update) - Done.
insert into RepositorySource_URL (FK_RepositorySource, URL) values ( 22, 'deb http://archive.raspbian.org/raspbian') insert into RepositorySource_URL (FK_RepositorySource, URL) values ( 23, 'deb http://deb.linuxmce.org/raspbian')
Add Packages
For packages we are going to copy the entire bank of ubuntu and lmce packages for 1004 to raspbian wheezy entries, then we'll fix up individual package names afterwards.
- update the 'Package_Source' table, add all Packages from ubuntu lucid as a base, copy ubuntu repo packages and lmce repo packages: (then sqlCVS diff/approval/update) - Done.
insert into Package_Source (FK_Package, Name, FK_RepositorySource, Repository)select FK_Package, Name, "22", "wheezy main" from Package_Source join Package_Source_Compat on Package_Source.PK_Package_Source=Package_Source_Compat.FK_Package_Source where FK_Distro=18 and FK_RepositorySource IN ( 1, 2, 20) insert into Package_Source (FK_Package, Name, FK_RepositorySource, Repository)select FK_Package, Name, "23", "wheezy main" from Package_Source join Package_Source_Compat on Package_Source.PK_Package_Source=Package_Source_Compat.FK_Package_Source where FK_Distro=18 and FK_RepositorySource=21
- update the 'Package_Source_Compat' table, add OS and Distro for all Raspbian packages added in previous inserts: (then sqlCVS diff/approval/update) - Done
insert into Package_Source_Compat (FK_Package_Source, FK_OperatingSystem, FK_Distro) select PK_Package_Source, "1", "19" from Package_Source where FK_RepositorySource in (22,23)
- fix package names that are inconsistent between raspbian and ubuntu: (then sqlCVS diff/approval/update) - Initially Done, likely find more inconsistencies