This post has been thanked 2 times. |
|
||||
Wirelessly posted (Opera/9.80 (Windows Mobile; Opera Mini/5.1.21594/23.333; U; en) Presto/2.5.25 Version/10.54)
Quote:
|
This post has been thanked 1 times. |
|
||||
Wirelessly posted (Vogue: Mozilla/5.0 (Linux; U; Android 2.2.1; en-us; MSM Build/FRX03) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1)
Quote:
it should be just a simple tar command... I will post what I'm using later tonight. Just thought I would see if you guys know what's going on.
__________________
|
This post has been thanked 1 times. |
|
||||
Re: NAND Boot Testing - 01-07: Panel power on/off fixes
Sorry vfellas .. at a rooftop ripped drunk... I won't be able to look into anything till tomottow.
|
This post has been thanked 4 times. |
|
||||
Re: NAND Boot Testing - 01-07: Panel power on/off fixes
Well, this is going better than I expected. Unless someone tells me otherwise, I'm modifying the new bootenv/tinboot for the following:
1) Full NAND only (at least initially until it is stable) 2) Rhodium support only (taking out detection of other phones) 3) build.prop is now responsible for setting lcd density (currently 240 in FRX04 and makes our cmdline is redundant...) 4) Incorporating stinebd's OTA update.zip method 5) Froyo libs moved into system (see note below) I've learned that you can't bind mount onto an initrd, so you have to use links and copy the data that way. Unfortunately, this poses a problem for our method of copying hw lib files based on the build type. For now, I am going to cook the libs into the system. This means we need to cook the libs and stuff into system for each build type (i.e. froyo, gingerbread, cynogen, etc.) that you want to try. Here's the code I'm talking about: Code:
RCSCRIPT="" RCCONFIG="" echo "Checking for build type..." if [ -f /system/hero.build ] ; then echo "Hero build detected" RCSCRIPT="hero" RCCONFIG="hero" ln /data/app_s /system/app elif [ -f /system/eclairhero.build ] ; then echo "HERO 2.1 BUILD DETECTED -- ECLAIR" RCSCRIPT="eclairhero" RCCONFIG="eclairhero" mount --bind /lib/eclair/hw /system/lib/hw elif [ -f /system/eclair.build ] ; then echo "Eclair build detected" RCSCRIPT="eclair" RCCONFIG="eclair" mount --bind /lib/eclair/hw /system/lib/hw elif [ -f /system/froyo.build ] ; then echo "Froyo build detected" RCSCRIPT="froyo" RCCONFIG="froyo" ln -s /lib/froyo/hw /system/lib/hw # vold: Fix sdcard device location for CDMA boards (thanks paalsteek) if [ -d /sys/devices/platform/msm_sdcc.3 ]; then /bin/sed -i -e 's:/devices/platform/msm_sdcc\.2:/devices/platform/msm_sdcc.3:g' /etc/vold.fstab fi elif [ -f /system/gingerbread.build ] ; then echo "Gingerbread build detected" RCSCRIPT="gingerbread" RCCONFIG="gingerbread" ln -s /lib/froyo/hw /system/lib/hw # vold: Fix sdcard device location for CDMA boards (thanks paalsteek) if [ -d /sys/devices/platform/msm_sdcc.3 ]; then /bin/sed -i -e 's:/devices/platform/msm_sdcc\.2:/devices/platform/msm_sdcc.3:g' /etc/vold.fstab fi elif [ -f /system/tattoo.build ] ; then echo "Tattoo build detected" RCSCRIPT="tattoo" RCCONFIG="tattoo" elif [ -f /system/donut.build ] ; then echo "Donut build detected" RCSCRIPT="donut" RCCONFIG="donut" mount --bind /lib/donut/hw /system/lib/hw elif [ -d /system/lib/donut ] ; then echo "Donut build detected" RCSCRIPT="donut" RCCONFIG="donut" elif [ -f /system/xrom.build ] ; then echo "xROM build detected" RCSCRIPT="xrom" RCCONFIG="xrom" elif [ -f /system/rogers.build ] ; then echo "Rogers build detected" RCSCRIPT="rogers" RCCONFIG="rogers" elif [ -f /system/cyanogen.build ] ; then echo "cyanogen experimental detected.....eating donuts" RCSCRIPT="cyanogen" RCCONFIG="cyanogen" elif [ -f /system/custom.build ] ; then echo "Custom init.rc detected" cp /system/sysinit.rc /build.cfg/init.sysinit.rc RCCONFIG="hero" RCSCRIPT="sysinit" else echo "Unknown Android build. Assuming Ion variant" RCSCRIPT="ion" RCCONFIG="ion" # for the fake sensors library mount /lib/hw /system/lib/hw -o loop chmod 666 /dev/input/event0 fi echo "using /init.$RCSCRIPT.rc as init.rc" echo "using $card/conf/$RCCONFIG.user.conf" cp "/init.cfg/init.$RCSCRIPT.rc" /etc/init.rc Last edited by natemcnutty; 02-04-2011 at 04:02 AM. |
This post has been thanked 3 times. |
|
||||
Re: NAND Boot Testing - 01-07: Panel power on/off fixes
Great work Nate.
For the LCDDENSITY this line of code won't work anymore? Code:
LCDDENSITY=`/bin/grep -o "lcd.density=.*" /proc/cmdline | /bin/sed -e "s/.*lcd.density=//g" -e "s/ .*//g"` if [ "$LCDDENSITY" != "" ] ; then echo "ro.sf.lcd_density=$LCDDENSITY" >> /etc/default.prop echo Setting ro.sf.lcd_density=$LCDDENSITY fi And how did you make your initramfs? |
|
||||
Re: NAND Boot Testing - 01-07: Panel power on/off fixes
Quote:
Code:
bhe@HP-dv3500-bhe:/tmp/test/initrd-kaiser/initrd/bin$ ls -ali total 2544 549794 drwxr-xr-x 2 bhe bhe 12288 2011-02-04 15:40 . 549793 drwxr-xr-x 4 bhe bhe 4096 2011-02-04 15:40 .. 549796 lrwxrwxrwx 1 bhe bhe 7 2011-02-04 15:40 [ -> busybox 549797 lrwxrwxrwx 1 bhe bhe 7 2011-02-04 15:40 [[ -> busybox 549798 -rwxr-xr-x 1 bhe bhe 117460 2011-02-04 15:40 adbd 549799 lrwxrwxrwx 1 bhe bhe 7 2011-02-04 15:40 addgroup -> busybox 549800 lrwxrwxrwx 1 bhe bhe 7 2011-02-04 15:40 adduser -> busybox 549801 lrwxrwxrwx 1 bhe bhe 7 2011-02-04 15:40 adjtimex -> busybox 549802 lrwxrwxrwx 1 bhe bhe 7 2011-02-04 15:40 ar -> busybox 549803 lrwxrwxrwx 1 bhe bhe 7 2011-02-04 15:40 arp -> busybox 549804 lrwxrwxrwx 1 bhe bhe 7 2011-02-04 15:40 arping -> busybox 549805 lrwxrwxrwx 1 bhe bhe 7 2011-02-04 15:40 ash -> busybox 549806 lrwxrwxrwx 1 bhe bhe 7 2011-02-04 15:40 awk -> busybox 549807 lrwxrwxrwx 1 bhe bhe 7 2011-02-04 15:40 basename -> busybox 549808 lrwxrwxrwx 1 bhe bhe 7 2011-02-04 15:40 bbconfig -> busybox 549809 lrwxrwxrwx 1 bhe bhe 7 2011-02-04 15:40 bunzip2 -> busybox 549810 -rwxr-xr-x 1 bhe bhe 1530860 2011-02-04 15:40 busybox 549811 lrwxrwxrwx 1 bhe bhe 7 2011-02-04 15:40 bzcat -> busybox You could download it here as tar.gz to start test building : Tree for initrd-kaiser in android-initrd-kaiser - Gitorious |
This post has been thanked 1 times. |
|
||||
Re: NAND Boot Testing - 01-07: Panel power on/off fixes
Quote:
Quote:
|
|
||||
Re: NAND Boot Testing - 01-07: Panel power on/off fixes
Quote:
The other phones are so far behind nand its good if we wipe em out .. Lets face it. Each build from now on will most likely need tweaking so moving the libs so we dont need to mount bind isnt a bad idea. Plus once the cookers get their hands on our precious code, bam they will release builds like wild fire. It will be up to them to move the modules to the right place. An alternative is to create a thin slice to hold the modules so we can mount bind them that way. But a new partition just for modules? i dunno if thats a good idea. What about the rc files ? having a directory dedicated to just rc files like the haret rootfs limits us to builds. So we should just do the same as vogue (and every other build) and have the rc in the build itself. i got so drunk last night and i had to call in sick. So im doing some small changes here and there to help out, but it sounds like you got it all under control. I'll have to commit the links for bin directly instead of the binaries and any patches you want to tinboot itself, let me know. Also i'm uploading the frx04 now.. i'll post a link later. Edit: Forgot about the screen calibration. ideas ?. Last edited by [ACL]; 02-04-2011 at 02:20 PM. |
This post has been thanked 2 times. |
|
|
|