Database Develop

Android on HTC S730 Wings

Hello All,
I would like to run Android on my HTC S730.
Tried to run the Kaiser optimised kernel as the hardware is somewhat similar.
I am using haret.exe and the kernel does start running, however there is nothing shown on the screen and the process gets stuck always at the same point.
The only proof of it running is that there is a dmesg file created on the SD.
I will put the contents of the file and the default.txt in a separate post.
Any idea what to change, I am hoping that by playing with the kernel parameters it would be possible to get further ahead.
Thanks and all the best,

dmesg on HTC S730
[ 0.000000] Linux version 2.6.25-01025-g3c90f25 ([email protected]) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #4505 PREEMPT Fri Mar 26 13:36:25 NZDT 2010
[ 0.000000] CPU: ARMv6-compatible processor [4107b364] revision 4 (ARMv6TEJ), cr=00c5387f
[ 0.000000] Machine: HTC Kaiser
[ 0.000000] Ignoring unrecognised tag 0x00000000
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] On node 0 totalpages: 24576
[ 0.000000] DMA zone: 208 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 24368 pages, LIFO batch:3
[ 0.000000] Normal zone: 0 pages used for memmap
[ 0.000000] Movable zone: 0 pages used for memmap
[ 0.000000] CPU0: D VIPT write-back cache
[ 0.000000] CPU0: I cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets
[ 0.000000] CPU0: D cache: 32768 bytes, associativity 4, 32 byte lines, 256 sets
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 24368
[ 0.000000] Kernel command line: ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend board-kaiser-keypad.atttilt=0
[ 0.000000] Unknown boot option `ppp.nostart=0': ignoring
[ 0.000000] PID hash table entries: 512 (order: 9, 2048 bytes)
[ 0.000000] Console: colour dummy device 80x30
[ 0.000040] console [tty0] enabled
[ 0.000941] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.001693] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.013030] Memory: 56MB 40MB = 96MB total
[ 0.013130] Memory: 91964KB available (2772K code, 1263K data, 120K init)
[ 0.014561] Calibrating delay loop... 383.38 BogoMIPS (lpj=1916928)
[ 0.230795] Mount-cache hash table entries: 512
[ 0.232220] CPU: Testing write buffer coherency: ok
[ 0.235221] net_namespace: 440 bytes
[ 0.237593] NET: Registered protocol family 16
[ 0.239481] set gpio 21 wakeup 40000000
[ 0.249781] msm_i2c_probe
[ 0.249945] msm_i2c_probe: clk_ctl 35d, 100000 Hz
[ 0.280248] Bluetooth: Core ver 2.11
[ 0.281433] NET: Registered protocol family 31
[ 0.281560] Bluetooth: HCI device and connection manager initialized
[ 0.281651] Bluetooth: HCI socket layer initialized
[ 0.284658] NET: Registered protocol family 2
[ 0.290096] Switched to high resolution mode on CPU 0
[ 0.370686] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.372900] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.373320] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.373571] TCP: Hash tables configured (established 4096 bind 4096)
[ 0.373651] TCP reno registered
[ 0.401651] Unpacking initramfs... done
[ 0.944525] Freeing initrd memory: 1193K
[ 0.945080] kaiser i2c touch screen
[ 0.945691] input: kaiser-ts as /devices/virtual/input/input0
[ 0.945821] No IRQF_TRIGGER set_type function for IRQ 190 (kaisergpio)
[ 0.946703] msm7200: Copying audio table 0 to fd000
[ 0.946838] msm7200: Copying audio table 1 to fd080
[ 0.946908] msm7200: Copying audio table 2 to fd100
[ 0.946975] msm7200: Copying audio table 3 to fd180
[ 0.947040] msm7200: Copying audio table 4 to fd200
[ 0.947103] msm7200: Copying audio table 5 to fd280
[ 0.947166] msm7200: Copying audio table 6 to fd300
[ 0.947231] msm7200: Copying audio table 7 to fd380
[ 0.947295] msm7200: Copying audio table 8 to fd400
[ 0.947360] msm7200: Copying audio table 9 to fd480
[ 0.947423] msm7200: Copying audio table 10 to fd500
[ 0.947488] msm7200: Copying audio table 11 to fd580
[ 0.947553] msm7200: Copying audio table 12 to fd600
[ 0.947618] msm7200: Copying audio table 13 to fd680
[ 0.947683] msm7200: Copying audio table 14 to fd700
[ 0.947748] msm7200: Copying audio table 15 to fd780
[ 0.947813] msm7200: Copying audio table 16 to fd800
[ 0.947878] msm7200: Copying audio table 17 to fd880
[ 0.947943] msm7200: Copying audio table 18 to fd900
[ 0.948008] msm7200: Copying audio table 19 to fd980
[ 0.948073] msm7200: Copying audio table 20 to fda00
[ 0.948138] msm7200: Copying audio table 21 to fda80
[ 0.948203] msm7200: Copying audio table 22 to fdb00
[ 0.948268] msm7200: Copying audio table 23 to fdb80
[ 0.949003] Registered led device: lcd-backlight
[ 0.949365] Registered led device: button-backlight
[ 0.949645] Registered led device: keyboard-backlight
[ 0.949893] Registered led device: green
[ 0.950305] Registered led device: red
[ 0.950586] Registered led device: amber
[ 0.950865] Registered led device: blue
[ 0.951123] Registered led device: wifi
[ 0.951373] Registered led device: gps
[ 0.956066] titan ts_init
[ 0.956570] Modem Status:
[ 0.956731] <SM 00000929 00010929>
[ 1.002071] input: kaiser_kbd as /devices/virtual/input/input1
[ 1.002481] DS-2746 Probe
[ 1.002815] Initialise htc_rfkill for Bluetooth
[ 1.002911] Bluetooth 0
[ 1.021578] clk_get grp_clk
[ 1.021721] clk_get imem_clk
[ 1.021836] hw3d: 0 init
[ 1.022263] PMEM:hw3d a0000000 100000 at c7000000
[ 1.022533] clk_get acpu_clk
[ 1.025585] ashmem: initialized
[ 1.027053] squashfs: version 3.4 (2008/08/26) Phillip Lougher
[ 1.027365] yaffs Mar 4 2010 10:36:01 Installing.
[ 1.028015] io scheduler noop registered (default)
[ 1.028100] io scheduler deadline registered
[ 1.029040] logger: created 64K log 'log_main'
[ 1.029360] logger: created 256K log 'log_events'
[ 1.029671] logger: created 64K log 'log_radio'
[ 1.029850] ram_console: got buffer at e0000, size 20000
[ 1.030160] ram_console: no valid data in buffer (sig = 0xffffffff)
[ 1.030340] console [ram-1] enabled
[ 1.035103] pmem: 1 init
[ 1.035678] PMEMmem 16800000 800000 at c8000000
[ 1.036055] pmem_adsp: 0 init
[ 1.036710] PMEMmem_adsp 17000000 800000 at c9000000
[ 1.037163] pmem_gpu0: 0 init
[ 1.038060] PMEMmem_gpu0 100000 700000 at c7800000
[ 1.038440] pmem_gpu1: 0 init
[ 1.039093] PMEMmem_gpu1 17800000 800000 at ca000000
[ 1.039496] pmem_camera: 1 init
[ 1.040400] PMEMmem_camera 17800000 800000 at cb000000
[ 1.041256] clk_get mdp_clk
[ 1.041916] mddi_pmdh: init() base=0xe000b000 irq=16
[ 1.042035] clk_get pmdh_clk
[ 1.042400] mddi_pmdh: unsupported version 0x19
[ 1.042628] mddi cmd send rtd: int 23a000, stat 808063, rtd val d
[ 1.042941] mddi_pmdh: publish: mddi_c_0000_0000
[ 1.043973] vsync on gpio 97 now 0
[ 1.044100] mddi_pmdh: mddi_add_panel(c040ccf0, c0312628)
[ 1.044176] mddi_pmdh: publish: mddi_panel
[ 1.044580] msmfb_probe() installing 240 x 320 panel
[ 1.050000] fus
[ 1.050000] fake_vsync_int for update
[ 1.050000] mddi0_panel_power(1) type=0
[ 1.050788] Console: switching to colour frame buffer device 40x29
[ 1.100915] set gpio 20 wakeup 40000000
[ 1.105701] No IRQF_TRIGGER set_type function for IRQ 186 (kaisergpio)
[ 1.110223] No IRQF_TRIGGER set_type function for IRQ 187 (kaisergpio)
[ 1.115476] No IRQF_TRIGGER set_type function for IRQ 188 (kaisergpio)
[ 1.121208] clk_get uart1dm_clk
[ 1.123966] clk_set_rate 34:1843200
[ 1.126686] msm_serial_hs.0: ttyMSM0 at MMIO 0xa0200000 (irq = 45) is a MSM HS UART
[ 1.133160] loop: module loaded
[ 1.140258] PPP generic driver version 2.4.2
[ 1.146556] PPP Deflate Compression module registered
[ 1.150061] PPP BSD Compression module registered
[ 1.162623] allocated dma buffer at ffc7b000, dma_addr 15cc1000
[ 1.168583] read CFG0 = aad400c0, CFG1 = 4747c
[ 1.170165] CFG0 = a8d408c0, CFG1 = 4745c
[ 1.180156] CFG0: cw/page=3 ud_sz=516 ecc_sz=10 spare_sz=1 num_addr_cycles=5
[ 1.185925] NAND_READ_ID = 15c1aaec
[ 1.188931] status: e03020
[ 1.190050] nandid: 15c1aaec maker ec device aa
[ 1.195780] CFG0: cw/page=3 ud_sz=512 ecc_sz=10 spare_sz=5
[ 1.200223] DEV_CMD1: f00f3000
[ 1.203695] <6>NAND_EBI2_ECC_BUF_CFG: 0
[ 1.210138] flash_id: 15c1aaec size 5580ba2c10000000
[ 1.220481] usb_probe() io=c7106000, irq=15, dma=ffc7c000(15cc6000)
[ 1.226401] clk_get usb_hs_clk
[ 1.229231] clk_get usb_hs_pclk
[ 1.230726] usb_function_register() 'adb'
[ 1.236900] usb_function_register() 'usb_mass_storage'
[ 1.240070] msm_hsusb: functions bound. starting.
[ 1.250306] usb_mass_storage usb_mass_storage: Number of LUNs=1
[ 1.256563] hsusb: IDLE -> ONLINE
[ 1.259478] hsusb: reset controller c5cc5c00
[ 1.285320] usb: notify offline
[ 1.288195] hsusb: ONLINE -> OFFLINE
[ 1.290870] usb_ether_setup()
[ 1.295711] usb_function_register() 'ether'
[ 1.360338] GPIO Event Driver
[ 1.363418] MSM RTC init
[ 1.366105] RTC probe
[ 1.369483] msm_rtc msm_rtc.0: rtc core: registered msm_rtc as rtc0
[ 1.370275] MSM RTC started
[ 1.373880] s5k3c1fx: probe
[ 1.380523] Bluetooth: HCI UART driver ver 2.2
[ 1.385413] Bluetooth: HCI H4 protocol initialized
[ 1.390095] Bluetooth: HCILL protocol initialized
[ 1.395555] clk_get sdc1_pclk
[ 1.398186] clk_get_rate 20:66000000
[ 1.400210] clk_get sdc1_clk
[ 1.403218] clk_set_rate 19:144000
[ 1.407681] set sd clock - 0 1
[ 1.513335] clk_get_rate 19:144000
[ 1.516431] mmc0: Qualcomm MSM SDCC at 0x00000000e1000000 irq 24,0 dma 8
[ 1.520215] mmc0: 4 bit data mode enabled
[ 1.525160] mmc0: MMC clock 144000 -> 32000000 Hz, PCLK 66000000 Hz
[ 1.530045] mmc0: Slot eject status = 1
[ 1.535388] mmc0: Power save feature enable = 1
[ 1.540081] mmc0: DM non-cached buffer at ffc7e000, dma_addr 0x15cdd000
[ 1.545468] mmc0: DM cmd busaddr 0x15cdd000, cmdptr busaddr 0x15cdd300
[ 1.550468] clk_get sdc2_pclk
[ 1.553311] clk_get_rate 22:66000000
[ 1.556043] clk_get sdc2_clk
[ 1.560068] clk_set_rate 21:144000
[ 1.564816] set sd clock - 0 1
[ 1.670560] clk_get_rate 21:144000
[ 1.674050] mmc1: Qualcomm MSM SDCC at 0x00000000e1001000 irq 26,0 dma 8
[ 1.679563] mmc1: 4 bit data mode enabled
[ 1.680385] mmc1: MMC clock 144000 -> 32000000 Hz, PCLK 66000000 Hz
[ 1.690193] mmc1: Slot eject status = 0
[ 1.695496] mmc1: Power save feature enable = 1
[ 1.700093] mmc1: DM non-cached buffer at ffc7f000, dma_addr 0x15ce0000
[ 1.705535] mmc1: DM cmd busaddr 0x15ce0000, cmdptr busaddr 0x15ce0300
[ 1.710370] mmc1: Polling status mode enabled
[ 1.720261] nf_conntrack version 0.5.0 (2048 buckets, 8192 max)
[ 1.732728] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 1.739298] ClusterIP Version 0.8 loaded successfully
[ 1.740293] arp_tables: (C) 2002 David S. Miller
[ 1.750320] TCP cubic registered
[ 1.753566] NET: Registered protocol family 1
[ 1.760316] NET: Registered protocol family 17
[ 1.766313] Bluetooth: L2CAP ver 2.9
[ 1.770183] Bluetooth: L2CAP socket layer initialized
[ 1.776468] Bluetooth: SCO (Voice Link) ver 0.6
[ 1.780045] Bluetooth: SCO socket layer initialized
[ 1.786118] Bluetooth: RFCOMM socket layer initialized
[ 1.790150] Bluetooth: RFCOMM TTY layer initialized
[ 1.800348] Bluetooth: RFCOMM ver 1.9
[ 1.803741] Bluetooth: BNEP (Ethernet Emulation) ver 1.2
[ 1.809265] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 1.811738] msm_rtc msm_rtc.0: setting system clock to 2007-11-13 21:10:55 UTC (1194988255)
[ 1.820211] Freeing init memory: 120K
[ 2.119216] mmc1: Command timeout
[ 2.120000] mmc1: Command timeout
[ 2.120000] mmc1: Command timeout
[ 2.120000] mmc1: Command timeout
[ 2.120000] SD Init
[ 2.148356] mmc_sd_init_card: Delay 250 ms
[ 2.409845] clk_set_rate 21:25000000
[ 2.412045] set sd clock - 0 1
[ 2.517448] mmc1: host does not support reading read-only switch. assuming write-enable.
[ 2.520031] SD Init Retry
[ 2.522411] mmc1: new SD card at address b7b8
[ 2.531265] mmcblk0: mmc1:b7b8 SU02G 1985024KiB
[ 2.536631] mmcblk0: p1

default.txt kernel parameters HTC S730 Android
#alloctest 0x2000
set RAMSIZE 0x04000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage-26-03-10
set initrd initrd.gz
#
# The following kernel parameters are useful
# ppp.nostart - Set ppp.nostart=1 to disable starting the ppp connection on boot
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 1, use 1 for best power savings
# board-htckaiser.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Sony 2=Topoly 3=Topoly (probably just the same as 2)
# lcd.density - Defaults to 160, 128 shows more on screen
#
set cmdline "ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend board-kaiser-keypad.atttilt=0"
boot

Hello.
You really think it's possible to run Android on the Wings?
Good luck then!
Happily waiting your progress on this!

correct me if i'm wrong be doesn't android need touchscreen ?

Not the original android. Like the one from google's test device

[DEV][Kernel] Updated Archos Kernel

Hi!
I've done some work to merge the kernel code from archos into the current one from p-android-omap-3.0, omapzoom git one.
I looked for the base version and I assumed, that this one 45ee6d7c8ae96ca60cb73821414927c1118bbdf8
Date: Wed Jan 18 16:28:16 2012 +0200
was the best. It has only 250~ files changed (~130 where for pvr) compared to the one from omapzoom.
So I took these version and merged the archos kernel into a new branch. After that I made a fast forward and merged (most of) the archos specific changes into the current head.
After some troubles and with the help of scholbert with the serial output cable, I was able get a booting kernel which starts the base system including adb daemon.
Currently some thins are not working yet:
Ducati Binary from archos doesn't load.
I really don't know how to build a new one which fits our device.
I tried the tutorial at http://omappedia.org/wiki/RPMsg_BIOS_Sources
but with no luck. The test_omx_sysm3.xem3 is build but the test_omx_appm3.xem3 is missing. So it is not possible to generate an own ducati-m3.bin file.
PVR libraries are not starting
I took the pvr from the branch android-omap-tuna-3.0 but I'm was not able to test further the SGX drivers.
If some one would like to try it just copy the pvr directory into drivers/gpu/ folder and adapt Makefile and KConfig.
Battery is not working yet
I saw a post on another devices here:
[ROM/KERNEL] UNOFFICIAL CM10 + 3.x Kernel for Kindle Fire [08/17 ALPHA
Maybe we can learn something from Hashcode...
If someone is interested in, my repository is located at:
https://github.com/Quallenauge/kernel-archosg9

Cool stuff!
Hi Quallenauge,
well done, impressive work so far!!
I did a similar attempt to get an idea of the Archos specific stuff compared to the omapzoom kernels.
To get it very close to the essentials, i used the 3.0 Beta branch which is also 3.0.8 kernel version.
I made an old school diff between this branch and the Archos stock one and even stripped off some parts (e.g. documentation & default configs).
Though the patch is quite big, there're much less files affected.
Most of them are not even required for the Gen9 series to work.
By looking into the file you may get a good overview, where most of the work had been done.
My intention was to port this to an even newer kernel code.
Should be possible, but we also have to keep track of the changes in the kernel APIs.
Anyway here's my patch. Maybe it helps to get some of the bugs fixed
Cheers,
scholbert

scholbert said:
I did a similar attempt to get an idea of the Archos specific stuff compared to the omapzoom kernels.
To get it very close to the essentials, i used the 3.0 Beta branch which is also 3.0.8 kernel version.
I made an old school diff between this branch and the Archos stock one and even stripped off some parts (e.g. documentation & default configs).
Click to expand...
Click to collapse
I really appreciate it and I know how much effort this is. I also need some attempts. (Again: Thanks for the tip with the USB serial cable).
My intention was to port this to an even newer kernel code.
Should be possible, but we also have to keep track of the changes in the kernel APIs.
Click to expand...
Click to collapse
Yes, but most of the api changes are not affected by the archos changes.
Currently the version 3.0.31+ is within my repository. I expect major API changes in 3.1, 3.2, .3.X..kernels.
My target is to drive JellyBean with hw acceleration (3d and video) on the Archos G9.
Anyway here's my patch. Maybe it helps to get some of the bugs fixed
Click to expand...
Click to collapse
Thanks (!!!), this will be an good reference book in case of errors. :good:
What could be the next steps?
archos-memory.c has to be rewritten to mach the non-static memory definitions. No need to difference between 512MB/1Gbyte Models because this is done by the latest kernel changes.
I've done that yesterday quick&dirty and it works....sort off. No tiler map but the ducati tablet binary seems to be loading.
Get the graphic drivers working: Source should be taken from here. git.omapzoom.org
I've taken the kernel source from android-omap-tuna-3.0 but these are version 1.8. (Git provides 1.9).
Would someone jump on the bandwagon?

Quallenauge said:
Would someone jump on the bandwagon?
Click to expand...
Click to collapse
I'm in, I'm in, where do I sign! :laugh:
This is the sort of thing I've been looking at for a while. I've had a few failed experiments while poking around with trying to update the goldfish kernel but i'm still getting my head round it all and I still have more questions than answers. Definitely on the wrong side of noob on this subject but we've all got to start somewhere .
Have you got 3.0.31+ booting?
Fantastic Work Everyone!

trevd said:
I'm in, I'm in, where do I sign! :laugh:
Click to expand...
Click to collapse
=) Now you are signed automatically
Others can also signed in if they:
Installed GIT
Installed an IDE, for me it is Eclipse with CDT and E-Git extension, I used this tutorial for setup a kernel project: http://friendlyarm-in-tunisia.blogspot.de/2011/01/configuring-building-and-debugging.html
Installed a toolchain (You can use the guide on: http://forum.xda-developers.com/showpost.php?p=27427105&postcount=8)
Knows how to build a kernel, e.g.:
Code:
export ARCH=arm
export CROSS_COMPILE=<PATH>linaro-toolchain-prebuild/android-toolchain-eabi/bin/arm-linux-androideabi- make
make menuconfig
make
trevd said:
...I still have more questions than answers. Definitely on the wrong side of noob on this subject but we've all got to start somewhere .
Click to expand...
Click to collapse
Just ask the questions. Maybe my repo is a good start.
trevd said:
Have you got 3.0.31+ booting?
Click to expand...
Click to collapse
Yes it is booting. The userspace does have some problems. (no sgx init, some crashes).
Okay, let's start:
I attached a patch (which as to be applied to the HEAD-Version of my kernel repository), which uses the dynamic memory allocation which was introduced for a few months. So there's no need to use the archos memory definitions.
At first I wanted to use the init method of android-display.c, but later I have realized that archos used a completly another structure which means high adaption efforts :-/ So I used my quick&dirty approach which seems to work.
Also included in the patch is are the drivers for PVR 1.8. I know there are a new version 1.9 is out, but I wanted to see if this version is also usable (for the start). I also had updated these binaries within the rom, so that kernel drivers and user space libraries are matching.
The current state is the following:
Graphics drivers are not correctly loaded. I get
Code:
D/libEGL ( 2780): loaded /system/lib/egl/libEGL_POWERVR_SGX540_120.so
D/libEGL ( 2780): loaded /system/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
D/libEGL ( 2780): loaded /system/lib/egl/libGLESv2_POWERVR_SGX540_120.so
W/libEGL ( 2780): eglInitialize(0x1) failed (EGL_BAD_ALLOC)
I/cat ( 610): <6>[ 411.734649] PVR_K:(Error): BridgedDispatchKM: Driver initialisation not completed yet. [4807, drivers/gpu/pvr/bridged_pvr_bridge.c]
and I don't know why (see logcat.txt.gz). Maybe I had forgotten to reserve some SGX memory or else... I don't know :-/
Also yesterday I encountered some troubles at cold boot. Then the rpmsg driver seems to crash! I was able to get the kernel messages over the USB<-Serial->USB cable. See capture.txt:
Code:
[ 12.263916] rproc_da_to_pa: rproc_da_to_pa: matched mem entry no. 0
[ 12.264038] omap-rproc omap-rproc.1: da 0x8054b034 pa 0xb384b034 len 0x56ac
[ 12.264343] omap-rproc omap-rproc.1: section: type 2 da 0x805546e0 len 0x200
[ 12.264495] rproc_da_to_pa: rproc_da_to_pa: matched mem entry no. 0
[ 12.264617] omap-rproc omap-rproc.1: da 0x805546e0 pa 0xb38546e0 len 0x200
[ 12.264831] omap-rproc omap-rproc.1: section: type 2 da 0x9f0e0000 len 0x102f8
[ 12.264984] rproc_da_to_pa: rproc_da_to_pa: matched mem entry no. 0
[ 12.265106] omap-rproc omap-rproc.1: da 0x9f0e0000 pa 0xb2be0000 len 0x102f8
[ 12.336425] omap-rproc omap-rproc.1: remote processor ipu is now up
[ 12.806274] ------------[ cut here ]------------
[ 12.811889] WARNING: at arch/arm/mach-omap2/omap_l3_noc.c:135 l3_interrupt_handler+0x280/0x3b4()
[ 12.822387] CUSTOM SRESP error with SOURCE:L4CFG
[ 12.828002] Modules linked in:
[ 12.831878] Backtrace:
[ 12.835144] [<c0087a14>] (dump_backtrace+0x0/0x138) from [<c068cb18>] (dump_stack+0x20/0x24)
[ 12.845214] r7:00000087 r6:c00acd4c r5:00000009 r4:e92f1ba0
[ 12.852691] [<c068caf8>] (dump_stack+0x0/0x24) from [<c00d6410>] (warn_slowpath_common+0x64/0x7c)
[ 12.863372] [<c00d63ac>] (warn_slowpath_common+0x0/0x7c) from [<c00d64e4>] (warn_slowpath_fmt+0x40/0x48)
[ 12.874694] r8:00080003 r7:00000448 r6:f8000000 r5:c007d000 r4:c07c779a
[ 12.883209] r3:00000009
[ 12.886749] [<c00d64a4>] (warn_slowpath_fmt+0x0/0x48) from [<c00acd4c>] (l3_interrupt_handler+0x280/0x3b4)
[ 12.898315] r3:c07c779a r2:c07c7741
[ 12.903015] [<c00acacc>] (l3_interrupt_handler+0x0/0x3b4) from [<c01240b8>] (handle_irq_event_percpu+0xcc/0x2c4)
[ 12.915222] [<c0123fec>] (handle_irq_event_percpu+0x0/0x2c4) from [<c01242fc>] (handle_irq_event+0x4c/0x6c)
[ 12.926910] [<c01242b0>] (handle_irq_event+0x0/0x6c) from [<c0126c60>] (handle_fasteoi_irq+0xf4/0x144)
[ 12.938049] r6:c0883b8c r5:c007d000 r4:c0883b40 r3:00000000
[ 12.945556] [<c0126b6c>] (handle_fasteoi_irq+0x0/0x144) from [<c0123934>] (generic_handle_irq+0x30/0x40)
[ 12.956848] r6:0000002a r5:e92f0000 r4:0000002a r3:c0126b6c
[ 12.964385] [<c0123904>] (generic_handle_irq+0x0/0x40) from [<c007d3cc>] (asm_do_IRQ+0xac/0xe0)
[ 12.974792] r4:c007d000 r3:0000019a
[ 12.979492] [<c007d320>] (asm_do_IRQ+0x0/0xe0) from [<c0083108>] (__irq_svc+0x48/0xe0)
[ 12.989013] Exception stack(0xe92f1cc0 to 0xe92f1d08)
[ 12.995117] 1cc0: 00000000 c0947fe0 00000000 00000000 c007d000 00000282 c12bc040 c007bf80
[ 13.004943] 1ce0: e92f0000 e92f0000 3f77dfbc e92f1d5c c00ddc5c e92f1d08 c00de3d4 c00ddcdc
[ 13.014770] 1d00: 40000113 ffffffff
[ 13.019104] [<c00ddc44>] (__do_softirq+0x0/0x2a0) from [<c00de3d4>] (irq_exit+0x64/0xb8)
[ 13.028839] [<c00de370>] (irq_exit+0x0/0xb8) from [<c0088f64>] (ipi_timer+0x58/0x68)
[ 13.038116] r4:c007b040 r3:00000000
[ 13.042877] [<c0088f0c>] (ipi_timer+0x0/0x68) from [<c007d478>] (do_local_timer+0x78/0x9c)
[ 13.052764] r6:c0892ba8 r5:c007d000 r4:e92f0000 r3:0000055e
[ 13.060302] [<c007d400>] (do_local_timer+0x0/0x9c) from [<c0083108>] (__irq_svc+0x48/0xe0)
[ 13.070251] Exception stack(0xe92f1dc0 to 0xe92f1e08)
[ 13.076385] 1dc0: c089e1d8 c007d000 c08f0cb8 c08f0cb8 00000047 e92f0000 00000001 00000003
[ 13.086273] 1de0: 00000003 60000113 c0927bc6 e92f1eac c00d701c e92f1e08 c00d72e8 c00d7960
[ 13.096099] 1e00: 60000113 ffffffff
[ 13.100433] [<c00d74a4>] (vprintk+0x0/0x590) from [<c068d240>] (printk+0x2c/0x34)
[ 13.109497] [<c068d214>] (printk+0x0/0x34) from [<c04d3ae4>] (thermal_lookup_temp+0x3c/0xa8)
[ 13.119659] r3:e91b9b40 r2:c083c278 r1:c06c352c r0:c083c1ae
[ 13.127227] [<c04d3aa8>] (thermal_lookup_temp+0x0/0xa8) from [<c04d4050>] (hotspot_temp_to_sensor_temp+0x24/0x88)
[ 13.139556] r5:c0aa67ac r4:000061a8
[ 13.144256] [<c04d402c>] (hotspot_temp_to_sensor_temp+0x0/0x88) from [<c04d417c>] (average_cpu_sensor_delayed_work_fn+0xc8/0x130)
[ 13.158203] r4:e91b9b40 r3:e91b9b40
[ 13.162933] [<c04d40b4>] (average_cpu_sensor_delayed_work_fn+0x0/0x130) from [<c00f26bc>] (process_one_work+0x26c/0x46c)
[ 13.176025] r7:c12c0600 r6:c12bc5c0 r5:e91b9b78 r4:e922cb40
[ 13.183563] [<c00f2450>] (process_one_work+0x0/0x46c) from [<c00f2cb8>] (worker_thread+0x210/0x34c)
[ 13.194488] [<c00f2aa8>] (worker_thread+0x0/0x34c) from [<c00f7564>] (kthread+0x9c/0xa8)
[ 13.204223] [<c00f74c8>] (kthread+0x0/0xa8) from [<c00da788>] (do_exit+0x0/0x6fc)
[ 13.213256] r6:c00da788 r5:c00f74c8 r4:e941feb0
[ 13.219360] ---[ end trace 66050ce957e8cabb ]---
[ 13.225006] Master 0x44 DucatiM3
[ 13.229156] L4CFG OPCODE 0x00000002
...
It would be really cool, if we can squash these issues away...

Hi Quallenauge,
i'm sorry but i guess time is lacking to join development on a certain level.
Apart from that i prepare for holiday these days.
Anyway, just some advice... or maybe just a guess.
I had a short look into the patch you made and also looked at the omapzoom repository of your reference kernel.
As you already stated the complete pvr directory is missing in this kernel code.
I have not found out yet, why it had been removed (obviously this is an Android kernel).
Anyway apart from this driver directory there might be some essential parts missing in this code (e.g. internal kernel API stuff).
If you want to step to a higher kernel base, why not use this one:
https://android.googlesource.com/kernel/omap/+/refs/heads/android-omap-panda-3.0/#
You may try to use it as a base (3.0.31 as well) and again implement the archos specific stuff.
This way you might get less trouble to get the pvr part working, i guess.
Might be better than hunting for the tuna implementation, because Pandaboard in fact is very close to our tablet's design.
So i even wonder, if it would be possible some day to use the panda resources as a base to build
the Android OS (e.g. framework) for the Gen 9 as well.
As stated this is more a guess...
Good luck,
scholbert

scholbert said:
Hi Quallenauge,
i'm sorry but i guess time is lacking to join development on a certain level.
Apart from that i prepare for holiday these days.
Click to expand...
Click to collapse
No problem, we have all private things to do .
So i even wonder, if it would be possible some day to use the panda resources as a base to build
the Android OS (e.g. framework) for the Gen 9 as well.
Click to expand...
Click to collapse
For me, I will stuck at the kernel from omapzoom, because activly maintained display for the LCD display.
I guess the changes are not so big compared to the panda board kernel.
(And I also wan't this kind of merging not again, yet).
But others are invited to try it out.
It seems to be not complicated to replace the pvr driver tree with another implementation. From my point of view, it is equal to copy the files into that directory and adapt makefiles/Kconfig files.
Currently I look at the issues that I have with cold boot. Hopefully I get an solution.... Currently I have no idea

Disclaimer: I've built and modified kernels for my android phone a couple of times, but those have only been minor modifications, nothing at all on this scale, so please ignore my comments if they are too noobish.
Anyway, regarding the pvr issues: I found this: https://groups.google.com/forum/#!msg/android-building/feACaqANrAs/NPgF5gbHjSwJ apparently some guy had similar experiences with the panda board when mixing versions for different things. JBQ is then referring to this commit: https://android.googlesource.com/kernel/omap.git/+/52f476403350050beb0dff135a55c06c9e7a82a9 have you seen this already?
I'd love to get my hands dirty, but I think I'll start slowly, much left to learn

ergoen said:
Disclaimer: I've built and modified kernels for my android phone a couple of times, but those have only been minor modifications, nothing at all on this scale, so please ignore my comments if they are too noobish.
Anyway, regarding the pvr issues: I found this: https://groups.google.com/forum/#!msg/android-building/feACaqANrAs/NPgF5gbHjSwJ apparently some guy had similar experiences with the panda board when mixing versions for different things. JBQ is then referring to this commit: https://android.googlesource.com/kernel/omap.git/+/52f476403350050beb0dff135a55c06c9e7a82a9 have you seen this already?
I'd love to get my hands dirty, but I think I'll start slowly, much left to learn
Click to expand...
Click to collapse
Hi!
I made some progress about the pvr issue. I splitted the initialization routines of archos and where able to use the android-display.c routines to get a running graphics system.
I've managed the kernel to boot up. Graphics drivers (1.9) are loaded (A80S model only) - (yeah!!) and they are working.
Battery loading is working!
Current ducati firmaware is loading!
Sound is not working anymore...I have to adapt the archos specific changes.
If you give it a try just use the kernel and image provided at my shared4 account:
http://www.4shared.com/folder/jJrxHmKb/30_online.html
If you want to start, just checkout my kernel repository and compile the kernel.
Note that the pvr driver has to build as module.
Just use my config also in my shared4s folder to build a kernel. Note, that I adapted only my A80S device for this.
If you want to adapt the other devices you're welcome to do so. I will give some hints what should be done.
(It may a good start to get knowledge about how things work together).
Also I builded up my rom using different sources, cyanogenmod and omapzoom to get the extened omap support.
You can download my manifest at my shared4s folder and download all sources. (Don't forget to use my github device/vendor repository).
Then you must apply the patch (also at the shared4s folder) at framework/base to add the needed include files.
After building you get the system folder as usual. HWComposer seems not to work. Strange, that when I delete them
from the rom, it uses a default one - I didn't know that... But at least graphics starts.
I don't know why this isn't working. I will look further.
Also the next manual step is needed: Make a symlink from /system/vendor/lib/hw/gralloc.omap4460.so to /system/vendor/lib/hw/gralloc.archos.so.
I think trevd can give some more instructions...I'm not really available atm.
Just checkout this forum from time to time.

Thanks!
I will check out the kernel sources and try to make proper changes (I have the 101s). Unfortunately I do not have a good enough computer to build the whole rom (I've tries building cyanogenmod before and it takes aaaaages), but the image on your 4shared page includes every necessary change, right?

ergoen said:
Thanks!
I will check out the kernel sources and try to make proper changes (I have the 101s). Unfortunately I do not have a good enough computer to build the whole rom (I've tries building cyanogenmod before and it takes aaaaages), but the image on your 4shared page includes every necessary change, right?
Click to expand...
Click to collapse
It is a snapshot. At least it boots up and the Android GUI is starting up... .
I wanted to build the optimized hwcomposer from the omapzoom repository,
but when I start surfaceflinger, the display became black. So this is the next step when I continue hacking on this.
Maybe it would be also good, to use the ICS release and test this kernel with that.

EDIT : Possible useful documentation, after a quick goolge into the problem described below
http://www.mjmwired.net/kernel/Documentation/arm/OMAP/DSS
I suppose it might be an idea to RTFM that comes in every kernel tree.... Often forget about it because google's so easy just to type in a search term but hours can be lost!!
Hi Folks,
I'm going to have an hack on this tonight..... There was a time when I was in the club on Saturday's but a quiet night in with linux kernel is how I get my kick now-a-days, :laugh: anyway I digress.
Quallenauge said:
I wanted to build the optimized hwcomposer from the omapzoom repository, but when I start surfaceflinger, the display became black. So this is the next step when I continue hacking on this.
Click to expand...
Click to collapse
strace at the ready then ...... Currently on the A101S I've had to disable watchdog_daemon because It could not find the battery path, there may be a slight difference there from the A80's
My surface flinger doesn't want to start because /dev/graphics/fb0 doesn't exist which is slightly confusing in the least, Is ( should ) this device be created by a kernel level code and setup in [device drivers]/[graphics .. ]/[Framebuffer Devices] or whatever the path is in menuconfig . From what I understand it is??? I was getting framebuffer and gralloc not a typewriter , which is a message i've seen before when trying to force in drivers of other devices, but I've stripped it all back to just load the android Open GL Drivers and that is what strace currently reveals....
I'll keep hacking on it, maybe something will click in my brain because it's still blowing my mind a bit...... I think I've got kernel fear, I'll get over it though! :good:
---------- Post added at 11:31 PM ---------- Previous post was at 10:49 PM ----------
Hmmm, Well it's pretty self explantory why I've not got an fb device, the question is why ? Highlighted line is missing from my 3.0.31 bring up
Code:
--------- beginning of /dev/log/main
I/cat ( 418): <6>[ 0.000000] Initializing cgroup subsys cpu
I/cat ( 418): <5>[ 0.000000] Linux version 3.0.8+ ([email protected]) (gcc version 4.4.1 (GCC) ) #4 SMP PREEMPT Thu Jun 7 16:12:27 CEST 2012
I/cat ( 418): <4>[ 0.000000] CPU: ARMv7 Processor [411fc093] revision 3 (ARMv7), cr=10c5387f
I/cat ( 418): <4>[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
I/cat ( 418): <4>[ 0.000000] Machine: ARCHOS A101S board
I/cat ( 418): <6>[ 0.000000] fixup_archos: [email protected] from bootloader.
I/cat ( 418): <4>[ 0.000000] fixup_archos: [mem=512M init=/linuxrc debug omapdss.debug=0 omapfb.debug=0]
I/cat ( 418): <6>[ 0.000000] Product Name: A101S
I/cat ( 418): <6>[ 0.000000] DDR type elpida
[B][SIZE="4"]I/cat ( 418): <6>[ 0.000000] Reserving 8388608 bytes SDRAM for VRAM[/SIZE][/B]
I/cat ( 418): <4>[ 0.000000] Memory policy: ECC disabled, Data cache writealloc
I/cat ( 418): <6>[ 0.000000] OMAP4430 ES2.3
I/cat ( 418): <6>[ 0.000000] SRAM: Mapped pa 0x40300000 to va 0xfe400000 size: 0xd000
I/cat ( 418): <7>[ 0.000000] On node 0 totalpages: 114432
I/cat ( 418): <7>[ 0.000000] free_area_init_node: node 0, pgdat c07eda40, node_mem_map c0977000
I/cat ( 418): <7>[ 0.000000] Normal zone: 1024 pages used for memmap
I/cat ( 418): <7>[ 0.000000] Normal zone: 0 pages reserved
I/cat ( 418): <7>[ 0.000000] Normal zone: 113408 pages, LIFO batch:31
I/cat ( 418): <6>[ 0.000000] PERCPU: Embedded 7 pages/cpu @c0d7d000 s7072 r8192 d13408 u32768
I/cat ( 418): <7>[ 0.000000] pcpu-alloc: s7072 r8192 d13408 u32768 alloc=8*4096
I/cat ( 418): <7>[ 0.000000] pcpu-alloc: [0] 0 [0] 1
I/cat ( 418): <4>[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 113408
I/cat ( 418): <5>[ 0.000000] Kernel command line: mem=512M init=/linuxrc debug omapdss.debug=0 omapfb.debug=0
I/cat ( 418): <6>[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
I/cat ( 418): <6>[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
I/cat ( 418): <6>[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
I/cat ( 418): <6>[ 0.000000] Memory: 446MB 1MB = 447MB total
I/cat ( 418): <5>[ 0.000000] Memory: 442284k/442284k available, 82004k reserved, 0K highmem
I/cat ( 418): <5>[ 0.000000] Virtual kernel memory layout:
I/cat ( 418): <5>[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
I/cat ( 418): <5>[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
I/cat ( 418): <5>[ 0.000000] DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
I/cat ( 418): <5>[ 0.000000] vmalloc : 0xe0800000 - 0xf8000000 ( 376 MB)
I/cat ( 418): <5>[ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
I/cat ( 418): <5>[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
I/cat ( 418): <5>[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
I/cat ( 418): <5>[ 0.000000] .init : 0xc0008000 - 0xc005a000 ( 328 kB)
I/cat ( 418): <5>[ 0.000000] .text : 0xc005a000 - 0xc0778000 (7288 kB)
I/cat ( 418): <5>[ 0.000000] .data : 0xc0778000 - 0xc07ee5a0 ( 474 kB)
I/cat ( 418): <5>[ 0.000000] .bss : 0xc07ee5c4 - 0xc09768c8 (1569 kB)
I/cat ( 418): <6>[ 0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
I/cat ( 418): <6>[ 0.000000] Preemptible hierarchical RCU implementation.
Code:
--------- beginning of /dev/log/main
I/cat ( 601): <6>[ 0.000000] Initializing cgroup subsys cpu
I/cat ( 601): <5>[ 0.000000] Linux version 3.0.31+ ([email protected]) (gcc version 4.7.1 20120531 (prerelease) (Linaro GCC 4.7-2012.06-1~dev) ) #186 SMP PREEMPT Mon Sep 17 21:23:15 CEST 2012
I/cat ( 601): <7>[ 0.000000] CPU: ARMv7 Processor [411fc093] revision 3 (ARMv7), cr=10c5387d
I/cat ( 601): <7>[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
I/cat ( 601): <7>[ 0.000000] Machine: ARCHOS A101S board
I/cat ( 601): <6>[ 0.000000] fixup_archos: [email protected] from bootloader.
I/cat ( 601): <7>[ 0.000000] fixup_archos: [mem=512M console=ttyO2,115200n8 init=/linuxrc debug omapdss.debug=0 omapfb.debug=0]
I/cat ( 601): <6>[ 0.000000] Product Name: A101S
I/cat ( 601): <3>[ 0.000000] Perform archos reserve...
I/cat ( 601): <3>[ 0.000000] Found 1 memory banks with total size: 536870912
I/cat ( 601): <3>[ 0.000000] Perform omap_ion_init()
I/cat ( 601): <6>[ 0.000000] omap4_total_ram_size = 0x20000000
I/cat ( 601): <6>[ 0.000000] omap4_smc_size = 0x300000
I/cat ( 601): <6>[ 0.000000] omap4_ion_heap_secure_input_size = 0x0
I/cat ( 601): <6>[ 0.000000] omap4_ion_heap_secure_output_wfdhdcp_size = 0x0
I/cat ( 601): <6>[ 0.000000] omap4_ducati_heap_size = 0x5300000
I/cat ( 601): <6>[ 0.000000] omap4_ion_heap_tiler_mem_size = 0x0
I/cat ( 601): <6>[ 0.000000] omap4_ion_heap_nonsec_tiler_mem_size = 0x0
I/cat ( 601): <6>[ 0.000000] omap4_smc_addr = 0x9fd00000
I/cat ( 601): <6>[ 0.000000] omap4_ion_heap_secure_input_addr = 0x9fd00000
I/cat ( 601): <6>[ 0.000000] omap4_ion_heap_secure_output_wfdhdcp_addr = 0x9fd00000
I/cat ( 601): <6>[ 0.000000] omap4_ducati_heap_addr = 0x9aa00000
I/cat ( 601): <6>[ 0.000000] omap4_ion_heap_tiler_mem_addr = 0x9aa00000
I/cat ( 601): <6>[ 0.000000] omap4_ion_heap_nonsec_tiler_mem_addr = 0x9aa00000
I/cat ( 601): <6>[ 0.000000] omap_ion_init: secure_input id=2 [9fd00000-9fd00000] size=0
I/cat ( 601): <6>[ 0.000000] omap_ion_init: secure_output_wfdhdcp id=5 [9fd00000-9fd00000] size=0
I/cat ( 601): <6>[ 0.000000] omap_ion_init: tiler id=1 [9aa00000-9aa00000] size=0
I/cat ( 601): <6>[ 0.000000] omap_ion_init: nonsecure_tiler id=3 [9aa00000-9aa00000] size=0
I/cat ( 601): <6>[ 0.000000] omap_ion_init: system id=0 [0-0] size=0
I/cat ( 601): <6>[ 0.000000] omap_ion_init: tiler_reservation id=4 [0-0] size=0
I/cat ( 601): <6>[ 0.000000] DDR type elpida
I/cat ( 601): <3>[ 0.000000] omap_ipu_set_static_mempool(start=0x9aa00000, size=0x5300000)
I/cat ( 601): <7>[ 0.000000] Memory policy: ECC disabled, Data cache writealloc
I/cat ( 601): <6>[ 0.000000] OMAP4430 ES2.3
I/cat ( 601): <6>[ 0.000000] SRAM: Mapped pa 0x40300000 to va 0xfe400000 size: 0xd000
I/cat ( 601): <7>[ 0.000000] On node 0 totalpages: 108544
I/cat ( 601): <7>[ 0.000000] free_area_init_node: node 0, pgdat c085aea0, node_mem_map c0b71000
I/cat ( 601): <7>[ 0.000000] Normal zone: 1024 pages used for memmap
I/cat ( 601): <7>[ 0.000000] Normal zone: 0 pages reserved
I/cat ( 601): <7>[ 0.000000] Normal zone: 107520 pages, LIFO batch:31
I/cat ( 601): <6>[ 0.000000] PERCPU: Embedded 7 pages/cpu @c0f77000 s7328 r8192 d13152 u32768
I/cat ( 601): <7>[ 0.000000] pcpu-alloc: s7328 r8192 d13152 u32768 alloc=8*4096
I/cat ( 601): <7>[ 0.000000] pcpu-alloc: [0] 0 [0] 1
I/cat ( 601): <7>[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 107520
I/cat ( 601): <5>[ 0.000000] Kernel command line: mem=512M console=ttyO2,115200n8 init=/linuxrc debug omapdss.debug=0 omapfb.debug=0
I/cat ( 601): <6>[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
I/cat ( 601): <6>[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
I/cat ( 601): <6>[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
I/cat ( 601): <6>[ 0.000000] Memory: 256MB 168MB = 424MB total
I/cat ( 601): <5>[ 0.000000] Memory: 416684k/416684k available, 107604k reserved, 0K highmem
I/cat ( 601): <5>[ 0.000000] Virtual kernel memory layout:
I/cat ( 601): <5>[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
I/cat ( 601): <5>[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
I/cat ( 601): <5>[ 0.000000] DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
I/cat ( 601): <5>[ 0.000000] vmalloc : 0xe0800000 - 0xf8000000 ( 376 MB)
I/cat ( 601): <5>[ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)
I/cat ( 601): <5>[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
I/cat ( 601): <5>[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
I/cat ( 601): <5>[ 0.000000] .init : 0xc0008000 - 0xc007c000 ( 464 kB)
I/cat ( 601): <5>[ 0.000000] .text : 0xc007c000 - 0xc082d000 (7876 kB)
I/cat ( 601): <5>[ 0.000000] .data : 0xc082e000 - 0xc085ccc0 ( 188 kB)
I/cat ( 601): <5>[ 0.000000] .bss : 0xc09f5e60 - 0xc0b70c48 (1516 kB)
I/cat ( 601): <6>[ 0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
I/cat ( 601): <6>[ 0.000000] Preemptible hierarchical RCU implementation.
I/cat ( 601): <6>[ 0.000000] NR_IRQS:410
I/cat ( 601): <4>[ 0.000000] omap_hwmod: dpll_mpu_m2_ck: missing clockdomain for dpll_mpu_m2_ck.
I/cat ( 601): <6>[ 0.000000] OMAP clockevent source: GPTIMER1 at 32768 Hz
I/cat ( 601): <6>[ 0.000000] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms
I/cat ( 601): <6>[ 0.000061] Calibrating delay loop... 1990.38 BogoMIPS (lpj=7774208)
I/cat ( 601): <6>[ 0.070312] pid_max: default: 32768 minimum: 301
I/cat ( 601): <6>[ 0.070709] Mount-cache hash table entries: 512
I/cat ( 601): <6>[ 0.071807] Initializing cgroup subsys debug
I/cat ( 601): <6>[ 0.071838] Initializing cgroup subsys cpuacct
I/cat ( 601): <6>[ 0.071899] Initializing cgroup subsys freezer
I/cat ( 601): <6>[ 0.071990] CPU: Testing write buffer coherency: ok
---------- Post added 30th September 2012 at 12:26 AM ---------- Previous post was 29th September 2012 at 11:31 PM ----------
More brain dump..... could well be usefulhttp://omappedia.org/wiki/Android_How-tos#KERNEL_CONFIG
http://omappedia.org/wiki/Android_How-tos#KERNEL_CONFIG

Hi trevd!
For the surfaceflinger thing, you must implement the changes I made in the board specific files.
Just have a look at the end of the file, there should be a struct which contains a function pointer to a reserve function.
I have changed this reference to a board specific function, which also initializes the graphic subsystem.
If it suceed, you should get the framebuffer special files which are provided by the omapfb driver.
For the twl charger logic, I have no clue why it doesn't work. Does it work with the kernel which I have uploaded to 4shared?

Quallenauge said:
Hi trevd!
For the surfaceflinger thing, you must implement the changes I made in the board specific files.
Just have a look at the end of the file, there should be a struct which contains a function pointer to a reserve function.
I have changed this reference to a board specific function, which also initializes the graphic subsystem.
If it suceed, you should get the framebuffer special files which are provided by the omapfb driver.
For the twl charger logic, I have no clue why it doesn't work. Does it work with the kernel which I have uploaded to 4shared?
Click to expand...
Click to collapse
Thanks Quallenauge, Is that board specific file in arch/arm or do they live in some like drivers/video/omapfb ( i'll have a look around anyway and can't remember exact paths off the top of my head ) . For twl , I was using your kernel from 4shared... I'm not too bothered though as I think it's more in the watching daemon and I turned that off in the init.archos.rc. I still get battery change reports reported by my hotplug kernel monitor, which although not written for the purpose has become very useful.

trevd said:
Thanks Quallenauge, Is that board specific file in arch/arm or do they live in some like drivers/video/omapfb ( i'll have a look around anyway and can't remember exact paths off the top of my head ) .
Click to expand...
Click to collapse
It is in arch/arm/... board.*.80S.c file.

progress at Archos...
Hi!
Quallenauge said:
It is in arch/arm/... board.*.80S.c file.
Click to expand...
Click to collapse
Great work so far... so i'm back from holiday.
Seen this already:
https://gitorious.org/archos/archos-gpl-gen9-kernel-ics/trees/linux-ics-3.0.21
It's not 3.0.31 but intersting that G10 upgrades hit the G9 as well :laugh:
EDIT:
Just had a look inside the new "unofficial" firmware file which leaked at archos...
Guess what... included are latest graphics driver [email protected]
Should play nice with JB
Cheers,
scholbert

Hi Folks
I've just given my self a lesson in board bring up on omap arm devices and I'm making progress with the A101S board.
It creates the framebuffer in /dev/graphics/ and shows the boot animation although i've still got an issue with surfaceflinger and gralloc and framebuffer not being typewriter when I try to use the pvr drivers. I presume it something to do with the issue below which happens pretty early in the boot.
Code:
omapfb_calc_addr:892
Backtrace:
[<c008690c>] (dump_backtrace+0x0/0x138) from [<c0650164>] (dump_stack+0x20/0x24)
r7:c0a4f764 r6:d9b9a000 r5:00000000 r4:d931ce90
[<c0650144>] (dump_stack+0x0/0x24) from [<c0322e6c>] (omapfb_setup_overlay+0x158/0x4b8)
[<c0322d14>] (omapfb_setup_overlay+0x0/0x4b8) from [<c03236a0>] (omapfb_apply_changes+0x4d4/0x5c8)
[<c03231cc>] (omapfb_apply_changes+0x0/0x5c8) from [<c03240f4>] (omapfb_probe+0x960/0xda0)
[<c0323794>] (omapfb_probe+0x0/0xda0) from [<c03624f8>] (platform_drv_probe+0x24/0x28)
[<c03624d4>] (platform_drv_probe+0x0/0x28) from [<c0360f00>] (driver_probe_device+0xdc/0x1c8)
[<c0360e24>] (driver_probe_device+0x0/0x1c8) from [<c0361064>] (__driver_attach+0x78/0x9c)
r6:c087e350 r5:c0872d9c r4:c0872d68 r3:00000000
[<c0360fec>] (__driver_attach+0x0/0x9c) from [<c035fb5c>] (bus_for_each_dev+0x58/0xa0)
r6:c0360fec r5:c087e350 r4:00000000 r3:00000000
[<c035fb04>] (bus_for_each_dev+0x0/0xa0) from [<c0360b14>] (driver_attach+0x2c/0x34)
r6:c0880748 r5:d928d0c0 r4:c087e350
[<c0360ae8>] (driver_attach+0x0/0x34) from [<c0360698>] (bus_add_driver+0x138/0x2d8)
[<c0360560>] (bus_add_driver+0x0/0x2d8) from [<c03616cc>] (driver_register+0xd4/0x160)
[<c03615f8>] (driver_register+0x0/0x160) from [<c03629a0>] (platform_driver_register+0x80/0x9c)
[<c0362920>] (platform_driver_register+0x0/0x9c) from [<c0032644>] (omapfb_init+0x40/0x70)
r5:c004d778 r4:c004d7b0
[<c0032604>] (omapfb_init+0x0/0x70) from [<c007c768>] (do_one_initcall+0xb4/0x1b0)
[<c007c6b4>] (do_one_initcall+0x0/0x1b0) from [<c0008b64>] (kernel_init+0xb0/0x16c)
[<c0008ab4>] (kernel_init+0x0/0x16c) from [<c00d99a8>] (do_exit+0x0/0x6fc)
r6:c00d99a8 r5:c0008ab4 r4:00000000 r3:00000000
data_start_v=0xe2000000
rotation_type=0
cannot apply mgr(lcd) on inactive device
omapfb omapfb: failed to apply dispc config
cannot apply mgr(tv) on inactive device
omapfb omapfb: failed to apply dispc config
cannot apply mgr(lcd2) on inactive device
omapfb omapfb: failed to apply dispc config
omapdss DPI: Could not find exact pixel clock. Requested 68930 kHz, got 68929 kHz
panel_enable [wxga10]
I've got myself a Linaro JellyBean to boot all the way on the new kernel as that allows you to disable hardware rendering on the launcher
scholbert said:
It's not 3.0.31 but intersting that G10 upgrades hit the G9 as well
EDIT:
Just had a look inside the new "unofficial" firmware file which leaked at archos...
Guess what... included are latest graphics driver [email protected]
Should play nice with JB
Cheers,
scholbert
Click to expand...
Click to collapse
I'm just having a look at that firmware myself, some very interesting changes...... /system/lib/modules contains the pvrsrvkm_sgx540_120.ko and omaplfb_sgx540_120.ko, I'm just going to play around with some jellybean builds and see if I can get the drivers playing ball.
I assume if archos have created a new kernel in preparation for a JellyBean Rom on either the G10 or G9 then that would make this work kind of redundant for now?

trevd said:
I've got myself a Linaro JellyBean to boot all the way on the new kernel as that allows you to disable hardware rendering on the launcher
Click to expand...
Click to collapse
Great work... so you took the Pandaboard files or built your own?
trevd said:
I'm just having a look at that firmware myself, some very interesting changes...... /system/lib/modules contains the pvrsrvkm_sgx540_120.ko and omaplfb_sgx540_120.ko, I'm just going to play around with some jellybean builds and see if I can get the drivers playing ball.
Click to expand...
Click to collapse
Yeah i also wondered about that.
If you look at the 3.0.21 the known pvr part is missing now.
Guess the whole graphics stuff is changing for new releases, but i'm not a Ducati specialist
trevd said:
I assume if archos have created a new kernel in preparation for a JellyBean Rom on either the G10 or G9 then that would make this work kind of redundant for now?
Click to expand...
Click to collapse
Might get redundant, but don't forget the education :laugh:
Anyway you always give nice information to the community!
Keep on your great work.
Cheers,
scholbert

scholbert said:
Great work... so you took the Pandaboard files or built your own?
Click to expand...
Click to collapse
I acquired this book [ Embedded Android ] and decided to started from scratch, I've been using the Blaze and Panda as references.
I've made some major changes to the archos firmware/images which I will document very soon for everyone as I think we can bring the Archos Roms into line with the rest of Android.
scholbert said:
Yeah i also wondered about that.
If you look at the 3.0.21 the known pvr part is missing now.
Guess the whole graphics stuff is changing for new releases, but i'm not a Ducati specialist
Click to expand...
Click to collapse
I built myself a 3.0.21 kernel this morning and created myself a 4.0.24 rooted firmware ( I presume this number is related to the Gen10 ). The pvr/omaplfb kernel objects do get installed on boot although I still have not located exactly where that is happening. I'm still a little confused by how all this graphics stuff fits together and I seem to be going round in a segfault circle when trying to use the 3.0.21 drivers on a JellyBean Rom. I probably just need to add more method to my madness as I'm probably just repeating things I've already attempted.
I think I may go back to working on the 3.0.31 kernel if I don't make any headway
@Quallenauge : Have you got pvr drivers working on your 3.0.31 Kernel? What Is the "Secret Sauce" I need to Add?
scholbert said:
Might get redundant, but don't forget the education :laugh:
Click to expand...
Click to collapse
It's certainly an education and I think this is worth carrying on with as It it means we can keep the device up to date long after archos has stopped supporting it.
scholbert said:
Anyway you always give nice information to the community!
Keep on your great work.
Click to expand...
Click to collapse
And yourself, Although much of the H/W stuff is over my head at the moment, I'll understand one day :laugh:
Slightly off topic, I was wondering if you had looked into extracting the public keys from Gen10 F/W , It was something I made a naive attempt to do but I got lost in a sea of Hex! :silly:

trevd said:
I acquired this book [ Embedded Android ] and decided to started from scratch, I've been using the Blaze and Panda as references.
I've made some major changes to the archos firmware/images which I will document very soon for everyone as I think we can bring the Archos Roms into line with the rest of Android.
Click to expand...
Click to collapse
Cool, that's great... that's the way i like.
Interesting book as well. Few year ago i purchased "building embedded linux systems" from O'Reilly.
Good basics here, but little old skool in the meantime :angel:
Back on track... started digging around in the project files of the more open platforms in the meantime,
but unfortunately time is lacking to produce some useful output. So it's great you do!!!
trevd said:
I built myself a 3.0.21 kernel this morning and created myself a 4.0.24 rooted firmware ( I presume this number is related to the Gen10 ). The pvr/omaplfb kernel objects do get installed on boot although I still have not located exactly where that is happening. I'm still a little confused by how all this graphics stuff fits together and I seem to be going round in a segfault circle when trying to use the 3.0.21 drivers on a JellyBean Rom. I probably just need to add more method to my madness as I'm probably just repeating things I've already attempted.
Click to expand...
Click to collapse
I must admit, i got no clue right now...
trevd said:
I think I may go back to working on the 3.0.31 kernel if I don't make any headway
Click to expand...
Click to collapse
Always follow the path of least resistance
... at least first.
trevd said:
It's certainly an education and I think this is worth carrying on with as It it means we can keep the device up to date long after archos has stopped supporting it.
Click to expand...
Click to collapse
That'll be really great achievement.
trevd said:
And yourself, Although much of the H/W stuff is over my head at the moment, I'll understand one day :laugh:
Click to expand...
Click to collapse
Thanks alot... but no active hacks for some time now :highfive:
trevd said:
Slightly off topic, I was wondering if you had looked into extracting the public keys from Gen10 F/W , It was something I made a naive attempt to do but I got lost in a sea of Hex! :silly:
Click to expand...
Click to collapse
I would extract them, but in fact i'll need a dump of the first blocks of a Gen10 device. Maybe we should ask cajl for help...
You can't extract the keys from the firmware file because you'll need the key first to extract the bootloader out of the firmware file
We need to dd if=/dev/block/mmcblk0 of=/mnt/sdcard/first-64k.bin bs=512 count=128 or similar from a real device...
Best regards,
scholbert

[Q] Old kernel on new bootloader?

Has anyone else tried?
I backed up ICS boot.img and system.img before upgrading and then restore after flashing V20A.kdz but it doesn't boot. Just stays at the non-animated LG logo.

arararagi said:
Has anyone else tried?
I backed up ICS boot.img and system.img before upgrading and then restore after flashing V20A.kdz but it doesn't boot. Just stays at the non-animated LG logo.
Click to expand...
Click to collapse
Did you tried install Windows7 and after change the "windows" folder for the one from XP?
Doesn't make sense, right?

RuedasLocas said:
Did you tried install Windows7 and after change the "windows" folder for the one from XP?
Doesn't make sense, right?
Click to expand...
Click to collapse
It works if I also restore the MBR from XP.

arararagi said:
It works if I also restore the MBR from XP.
Click to expand...
Click to collapse
Here you don's have that "if"... sorry

Found this in another thread
gordon0001 said:
well, since no one answered i figured out the new kernel (3.1) is the issue. replacing the kernel with the old kernel (2.6) in recovery.img solved the problem, but partitions dont get mounted and couldnt get them mounted, since i barely know the internals of a linux kernel and the kernel ramdisk
Click to expand...
Click to collapse
I tried doing the same thing and just catting the resulting recovery image to boot.
It starts up and adb works, however only external SD on Tegra is accessible.
Code:
~ # find /dev/block/
/dev/block/
/dev/block/loop7
/dev/block/loop6
/dev/block/loop5
/dev/block/loop4
/dev/block/loop3
/dev/block/loop2
/dev/block/loop1
/dev/block/loop0
/dev/block/mmcblk0p1
/dev/block/platform
/dev/block/platform/sdhci-tegra.2
/dev/block/platform/sdhci-tegra.2/mmcblk0p1
/dev/block/platform/sdhci-tegra.2/by-num
/dev/block/platform/sdhci-tegra.2/by-num/p1
/dev/block/platform/sdhci-tegra.2/mmcblk0
/dev/block/mmcblk0
~ # cat /proc/partitions
major minor #blocks name
179 0 15351296 mmcblk0
179 1 15347200 mmcblk0p1
From dmesg:
Code:
<6>[ 3.855253] sdhci: Secure Digital Host Controller Interface driver
<6>[ 3.855433] sdhci: Copyright(c) Pierre Ossman
<4>[ 3.856721] mmc0: Invalid maximum block size, assuming 512 bytes
<6>[ 3.856848] mmc0: no vmmc regulator found
<7>[ 3.858202] Registered led device: mmc0::
<6>[ 3.861711] mmc0: SDHCI controller on platform [sdhci-tegra.3] using ADMA
<4>[ 3.863024] mmc1: Invalid maximum block size, assuming 512 bytes
<6>[ 3.863145] mmc1: no vmmc regulator found
<7>[ 3.864473] Registered led device: mmc1::
<6>[ 3.866846] mmc1: SDHCI controller on platform [sdhci-tegra.0] using ADMA
<4>[ 3.867178] tegra_gpio_irq_set_wake() called
<3>[ 3.867284] sdhci sdhci-tegra.2: SD card wake-up event registrationfailed with eroor: -22
<4>[ 3.868587] mmc2: Invalid maximum block size, assuming 512 bytes
<6>[ 3.868706] mmc2: no vmmc regulator found
<7>[ 3.870035] Registered led device: mmc2::
<6>[ 3.872372] mmc2: SDHCI controller on platform [sdhci-tegra.2] using ADMA
<7>[ 3.872860] Registered led device: button-backlight
<4>[ 3.872961] keypad_led_probe success
<6>[ 3.874563] tegra-se tegra-se: tegra_se_probe: complete
<6>[ 3.875491] usbcore: registered new interface driver usbhid
<6>[ 3.875681] usbhid: USB HID core driver
<6>[ 3.876370] logger: created 256K log 'log_main'
<6>[ 3.876608] logger: created 256K log 'log_events'
<6>[ 3.876939] logger: created 256K log 'log_radio'
<6>[ 3.877259] logger: created 256K log 'log_system'
<4>[ 3.972419] mmc0: switch to bus width 1 ddr 0 failed
<3>[ 3.972635] mmc0: error -110 whilst initialising MMC card
<4>[ 4.085800] mmc0: switch to bus width 1 ddr 0 failed
<3>[ 4.086013] mmc0: error -110 whilst initialising MMC card
<4>[ 4.213528] mmc0: switch to bus width 1 ddr 0 failed
<3>[ 4.213657] mmc0: error -110 whilst initialising MMC card
<4>[ 4.379808] mmc0: switch to bus width 1 ddr 0 failed
<3>[ 4.379939] mmc0: error -110 whilst initialising MMC card
This is how things should look (from the new kernel):
Code:
~ # find /dev/block/
/dev/block/
/dev/block/loop7
/dev/block/loop6
/dev/block/loop5
/dev/block/loop4
/dev/block/loop3
/dev/block/loop2
/dev/block/loop1
/dev/block/loop0
/dev/block/mmcblk1p1
/dev/block/mmcblk1
/dev/block/mmcblk0boot0
/dev/block/mmcblk0boot1
/dev/block/mmcblk0p13
/dev/block/mmcblk0p12
/dev/block/mmcblk0p11
/dev/block/mmcblk0p10
/dev/block/mmcblk0p9
/dev/block/mmcblk0p8
/dev/block/mmcblk0p7
/dev/block/mmcblk0p6
/dev/block/mmcblk0p5
/dev/block/mmcblk0p4
/dev/block/mmcblk0p3
/dev/block/mmcblk0p2
/dev/block/mmcblk0p1
/dev/block/platform
/dev/block/platform/sdhci-tegra.2
/dev/block/platform/sdhci-tegra.2/mmcblk1p1
/dev/block/platform/sdhci-tegra.2/by-num
/dev/block/platform/sdhci-tegra.2/by-num/p1
/dev/block/platform/sdhci-tegra.2/mmcblk1
/dev/block/platform/sdhci-tegra.3
/dev/block/platform/sdhci-tegra.3/mmcblk0boot0
/dev/block/platform/sdhci-tegra.3/mmcblk0boot1
/dev/block/platform/sdhci-tegra.3/mmcblk0p13
/dev/block/platform/sdhci-tegra.3/mmcblk0p12
/dev/block/platform/sdhci-tegra.3/mmcblk0p11
/dev/block/platform/sdhci-tegra.3/mmcblk0p10
/dev/block/platform/sdhci-tegra.3/mmcblk0p9
/dev/block/platform/sdhci-tegra.3/mmcblk0p8
/dev/block/platform/sdhci-tegra.3/mmcblk0p7
/dev/block/platform/sdhci-tegra.3/mmcblk0p6
/dev/block/platform/sdhci-tegra.3/mmcblk0p5
/dev/block/platform/sdhci-tegra.3/mmcblk0p4
/dev/block/platform/sdhci-tegra.3/mmcblk0p3
/dev/block/platform/sdhci-tegra.3/mmcblk0p2
/dev/block/platform/sdhci-tegra.3/mmcblk0p1
/dev/block/platform/sdhci-tegra.3/by-num
/dev/block/platform/sdhci-tegra.3/by-num/p13
/dev/block/platform/sdhci-tegra.3/by-num/p12
/dev/block/platform/sdhci-tegra.3/by-num/p11
/dev/block/platform/sdhci-tegra.3/by-num/p10
/dev/block/platform/sdhci-tegra.3/by-num/p9
/dev/block/platform/sdhci-tegra.3/by-num/p8
/dev/block/platform/sdhci-tegra.3/by-num/p7
/dev/block/platform/sdhci-tegra.3/by-num/p6
/dev/block/platform/sdhci-tegra.3/by-num/p5
/dev/block/platform/sdhci-tegra.3/by-num/p4
/dev/block/platform/sdhci-tegra.3/by-num/p3
/dev/block/platform/sdhci-tegra.3/by-num/p2
/dev/block/platform/sdhci-tegra.3/by-num/p1
/dev/block/platform/sdhci-tegra.3/by-name
/dev/block/platform/sdhci-tegra.3/by-name/UDB
/dev/block/platform/sdhci-tegra.3/by-name/CAL
/dev/block/platform/sdhci-tegra.3/by-name/FOT
/dev/block/platform/sdhci-tegra.3/by-name/MLT
/dev/block/platform/sdhci-tegra.3/by-name/DRM
/dev/block/platform/sdhci-tegra.3/by-name/UDA
/dev/block/platform/sdhci-tegra.3/by-name/NVA
/dev/block/platform/sdhci-tegra.3/by-name/USP
/dev/block/platform/sdhci-tegra.3/by-name/MSC
/dev/block/platform/sdhci-tegra.3/by-name/CAC
/dev/block/platform/sdhci-tegra.3/by-name/APP
/dev/block/platform/sdhci-tegra.3/by-name/LNX
/dev/block/platform/sdhci-tegra.3/by-name/SOS
/dev/block/platform/sdhci-tegra.3/mmcblk0
/dev/block/mmcblk0
~ # cat /proc/partitions
major minor #blocks name
179 0 15267840 mmcblk0
179 1 10240 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 1572864 mmcblk0p3
179 4 393216 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 81920 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 13062144 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 16384 mmcblk0p10
179 11 20480 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 47104 mmcblk0p13
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
179 48 15351296 mmcblk1
179 49 15347200 mmcblk1p1
And dmesg:
Code:
<6>[70:01:01 00:00:08.609] sdhci: Secure Digital Host Controller Interface driver
<6>[70:01:01 00:00:08.609] sdhci: Copyright(c) Pierre Ossman
<6>[70:01:01 00:00:08.609] sdhci-pltfm: SDHCI platform and OF driver helper
<4>[70:01:01 00:00:08.609] mmc0: Invalid maximum block size, assuming 512 bytes
<6>[70:01:01 00:00:08.609] mmc0: no vmmc regulator found
<7>[70:01:01 00:00:08.609] Registered led device: mmc0::
<6>[70:01:01 00:00:08.609] mmc0: SDHCI controller on sdhci-tegra.3 [sdhci-tegra.3] using ADMA
<6>[70:01:01 00:00:08.609] sdhci-tegra sdhci-tegra.0: vddio_sd_slot regulator not found: -19. Assuming vddio_sd_slot is not required.
<6>[70:01:01 00:00:08.609] sdhci-tegra sdhci-tegra.0: Error: tegra3 io dpd not supported for sdhci-tegra.0
<4>[70:01:01 00:00:08.609] mmc1: Invalid maximum block size, assuming 512 bytes
<6>[70:01:01 00:00:08.609] mmc1: no vmmc regulator found
<7>[70:01:01 00:00:08.609] Registered led device: mmc1::
<6>[70:01:01 00:00:08.619] mmc1: SDHCI controller on sdhci-tegra.0 [sdhci-tegra.0] using ADMA
<3>[70:01:01 00:00:08.619] Failed gpio lp0 enable for irq=405, error=-22
<3>[70:01:01 00:00:08.619] sdhci-tegra sdhci-tegra.2: SD card wake-up event registrationfailed with eroor: -22
<6>[70:01:01 00:00:08.619] sdhci-tegra sdhci-tegra.2: vddio_sd_slot regulator not found: -19. Assuming vddio_sd_slot is not required.
<4>[70:01:01 00:00:08.619] mmc2: Invalid maximum block size, assuming 512 bytes
<6>[70:01:01 00:00:08.619] mmc2: no vmmc regulator found
<7>[70:01:01 00:00:08.619] Registered led device: mmc2::
<6>[70:01:01 00:00:08.619] mmc2: SDHCI controller on sdhci-tegra.2 [sdhci-tegra.2] using ADMA

RuedasLocas said:
Did you tried install Windows7 and after change the "windows" folder for the one from XP?
Doesn't make sense, right?
Click to expand...
Click to collapse
That comparison doesn't make sense, in fact.
The linux kernel is not linked to the userspace like in windows, you can have the same system running either an early 2.6 version or a very latest 3.x with no changes at all to the rest of the programs.
And use the same version of lilo or grub to boot both kernels, for what the bootloader is concerned.
Not that android can be compared with no "if's" to a standard linux box, but makes more sense than compare it to windows.
And for what it's worth, Sony released an upgrade from Gingerbread to ICS for their 2011 line keeping the same kernel. (and GB to ICS is a way bigger leap than ICS to JB)

ircalf said:
That comparison doesn't make sense, in fact.
The linux kernel is not linked to the userspace like in windows, you can have the same system running either an early 2.6 version or a very latest 3.x with no changes at all to the rest of the programs.
And use the same version of lilo or grub to boot both kernels, for what the bootloader is concerned.
Not that android can be compared with no "if's" to a standard linux box, but makes more sense than compare it to windows.
And for what it's worth, Sony released an upgrade from Gingerbread to ICS for their 2011 line keeping the same kernel. (and GB to ICS is a way bigger leap than ICS to JB)
Click to expand...
Click to collapse
I confess that I was "unhappy" in that expression

ircalf said:
That comparison doesn't make sense, in fact.
The linux kernel is not linked to the userspace like in windows, you can have the same system running either an early 2.6 version or a very latest 3.x with no changes at all to the rest of the programs.
And use the same version of lilo or grub to boot both kernels, for what the bootloader is concerned.
Not that android can be compared with no "if's" to a standard linux box, but makes more sense than compare it to windows.
And for what it's worth, Sony released an upgrade from Gingerbread to ICS for their 2011 line keeping the same kernel. (and GB to ICS is a way bigger leap than ICS to JB)
Click to expand...
Click to collapse
i guess his point was that what the o.p tried to do didnt make sense, so what he said was in the same context, also its obvious that with new bootloader that it would not boot with the previous boot,img otherwise we wouldnt have such problems like not being able to use the v20a bootloader with the previous v10 firmware

[Q] Overclock omap4470 Kernel.

Has anyone tried this? Seems to be easy enough.
Code:
@@ -545,6 +546,8 @@
OPP_INITIALIZER("mpu", "virt_dpll_mpu_ck", "mpu", true, 1300000000, OMAP4470_VDD_MPU_OPPNITRO_UV),
/* MPU OPP4 - OPP-Nitro SpeedBin */
OPP_INITIALIZER("mpu", "virt_dpll_mpu_ck", "mpu", false, 1500000000, OMAP4470_VDD_MPU_OPPNITROSB_UV),
+ /*OVERCLOCK*/
+ OPP_INITIALIZER("mpu", "virt_dpll_mpu_ck", "mpu", false, 1600000000, OMAP4470_VDD_MPU_OPPNITROSB_UV),
/* L3 OPP1 - OPP50 */
OPP_INITIALIZER("l3_main_1", "virt_l3_ck", "core", true, 116000000, OMAP4470_VDD_CORE_OPP50_UV),
/* L3 OPP2 - OPP100 */
Not so sure this is needed, but doesn't hurt, I guess.
Code:
@@ -733,7 +736,10 @@
if (!trimmed)
pr_info("This is DPLL un-trimmed SOM. OPP is limited at 1.2 GHz\n");
if (omap4_has_mpu_1_5ghz() && trimmed)
+ omap4_opp_enable("mpu", 1100000000);
+ omap4_opp_enable("mpu", 1300000000);
omap4_opp_enable("mpu", 1500000000);
+ omap4_opp_enable("mpu", 1600000000);
GPU overclock
Code:
@@ -567,13 +570,13 @@
/* SGX OPP2 - OPP100*/
OPP_INITIALIZER("gpu", "dpll_per_m7x2_ck", "core", true, 307200000, OMAP4470_VDD_CORE_OPP100H_UV),
/* SGX OPP3 - OPPOV */
- OPP_INITIALIZER("gpu", "dpll_per_m7x2_ck", "core", true, 384000000, OMAP4470_VDD_CORE_OPP100_OV_UV),
+ OPP_INITIALIZER("gpu", "dpll_per_m7x2_ck", "core", true, 416000000, OMAP4470_VDD_CORE_OPP100_OV_UV),
/* BB2D OPP1 - OPP50 */
OPP_INITIALIZER("bb2d", "dpll_per_m6x2_ck", "core", true, 192000000, OMAP4470_VDD_CORE_OPP50_UV),
/* BB2D OPP2 - OPP100 */
OPP_INITIALIZER("bb2d", "dpll_per_m6x2_ck", "core", true, 307200000, OMAP4470_VDD_CORE_OPP100H_UV),
/* BB2D OPP3 - OPP-OV */
- OPP_INITIALIZER("bb2d", "dpll_per_m6x2_ck", "core", true, 384000000, OMAP4470_VDD_CORE_OPP100_OV_UV),
+ OPP_INITIALIZER("bb2d", "dpll_per_m6x2_ck", "core", true, 416000000, OMAP4470_VDD_CORE_OPP100_OV_UV),
/* FDIF OPP1 - OPP25 */
OPP_INITIALIZER("fdif", "fdif_fck", "core", true, 32000000, OMAP4470_VDD_CORE_OPP50_UV),
/* FDIF OPP2 - OPP50 */
So in making the following changes, if I go to /sys/devices/system/cpu/cpu0/cpufreq
and do a 'cat cpuinfo_max_freq' , I get 1600
a 'cat scaling_available_frequencies' gives:
396800 800000 1100000 1300000 1500000 1600000
I have been unable to test properly because my attempts to make a working boot.img have been unsuccessful.
If anyone could share on how to properly package a zImage and ramdisk.cpio.gz into a flashable boot.img, I would be forever thankful.
I've already extracted the "green loader"/cyanoboot and ramdisk from a working boot.img
I would love to get this working. It would also be fairly easy to tweak the Samsung lpddr ram timings. I also noticed the 'succulent' kernel turned down the core voltage slightly...

OK, so,... are you saying if I go into that folder and make that change it will overclock it?
cuz I'll just go and do that if its that easy.
I don't have any knowlege of compiling kernels so I can't help with that.

I believe it was verygreen who said that he experimented with overclock when building CM and determined it was of little benefit to our devices. That said, I would be most interested in seeing how far we can push the OC on these things, but so far no one with knowledge of Android inner workings wants to build anything for our devices.
Sent from my BN NookHD+ using XDA Premium HD app

I have more questions than answers about it myself.
Nook development seems to be from an "elite" group with closely guarded secrets.
I was actually able to get a "ram console"/last_kmsg
Code:
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.0.31-green+ ([email protected]) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-188) ) #6 SMP PREEMPT Sun Jan 26 09:22:35 EST 2014
[ 0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: OMAP4 ovation board
[ 0.000000] Ovation EVT1B detected - selecting Novatek panel
[ 0.000000] android_display: setting default resolution 1920*1280, bpp=4
[ 0.000000] android_display: tiler1d 56623104
[ 0.000000] android_display: setting fb0.vram to 39321600
[ 0.000000] android_display: setting vram to 39321600
[ 0.000000] android_display: ion carveouts: 77594624 tiler2d, 0 nonsecure
[ 0.000000] omap4_total_ram_size = 0x40000000
[ 0.000000] omap4_smc_size = 0x300000
[ 0.000000] omap4_ion_heap_secure_input_size = 0x3000000
[ 0.000000] omap4_ion_heap_secure_output_wfdhdcp_size = 0x1000000
[ 0.000000] omap4_ducati_heap_size = 0x3000000
[ 0.000000] omap4_ion_heap_tiler_mem_size = 0x4a00000
[ 0.000000] omap4_ion_heap_nonsec_tiler_mem_size = 0x0
[ 0.000000] omap4_smc_addr = 0xbfd00000
[ 0.000000] omap4_ion_heap_secure_input_addr = 0xbcd00000
[ 0.000000] omap4_ion_heap_secure_output_wfdhdcp_addr = 0xbbd00000
[ 0.000000] omap4_ducati_heap_addr = 0xb8d00000
[ 0.000000] omap4_ion_heap_tiler_mem_addr = 0xb4300000
[ 0.000000] omap4_ion_heap_nonsec_tiler_mem_addr = 0xb4300000
[ 0.000000] omap_ion_init: secure_input id=2 [bcd00000-bfd00000] size=3000000
[ 0.000000] omap_ion_init: secure_output_wfdhdcp id=5 [bbd00000-bcd00000] size=1000000
[ 0.000000] omap_ion_init: tiler id=1 [b4300000-b8d00000] size=4a00000
[ 0.000000] omap_ion_init: nonsecure_tiler id=3 [b4300000-b4300000] size=0
[ 0.000000] omap_ion_init: system id=0 [0-0] size=0
[ 0.000000] omap_ion_init: tiler_reservation id=4 [0-0] size=0
[ 0.000000] Reserving 39845888 bytes SDRAM for VRAM
[ 0.000000] Memory policy: ECC disabled, Data cache writealloc
[ 0.000000] OMAP4470 ES1.0
[ 0.000000] SRAM: Mapped pa 0x4030d000 to va 0xfe40d000 size: 0x1000
[ 0.000000] SMC: Allocated workspace of 0x300000 Bytes at (0xbfd00000)
[ 0.000000] PERCPU: Embedded 7 pages/cpu @c10a7000 s7136 r8192 d13344 u32768
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 197536
[ 0.000000] Kernel command line: androidboot.hardware=ovation androidboot.serialno=3024550263104319 boot.fb=b2200000
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 256MB 506MB 17MB = 779MB total
[ 0.000000] Memory: 778596k/778596k available, 269980k reserved, 18048K highmem
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
[ 0.000000] vmalloc : 0xf0800000 - 0xf8000000 ( 120 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xf0000000 ( 768 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .init : 0xc0008000 - 0xc0083000 ( 492 kB)
[ 0.000000] .text : 0xc0083000 - 0xc06ea000 (6556 kB)
[ 0.000000] .data : 0xc06ea000 - 0xc073ff00 ( 344 kB)
[ 0.000000] .bss : 0xc073ff24 - 0xc089bdf8 (1392 kB)
[ 0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] NR_IRQS:410
[ 0.000000] omap_hwmod: dpll_mpu_m2_ck: missing clockdomain for dpll_mpu_m2_ck.
[ 0.000000] OMAP clockevent source: GPTIMER1 at 32768 Hz
[ 0.000000] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms
[ 0.000000] Console: colour dummy device 80x30
[ 0.000000] console [tty0] enabled
[ 0.000915] Calibrating delay loop... 1590.23 BogoMIPS (lpj=6213632)
[ 0.007904] pid_max: default: 32768 minimum: 301
[ 0.031616] Mount-cache hash table entries: 512
[ 0.031616] Initializing cgroup subsys debug
[ 0.031616] Initializing cgroup subsys cpuacct
[ 0.032348] Initializing cgroup subsys freezer
[ 0.032409] CPU: Testing write buffer coherency: ok
[ 0.032928] L310 cache controller enabled
[ 0.032928] l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x5e470000, Cache size: 1048576 B
[ 0.111358] CPU1: Booted secondary processor
[ 0.181396] Brought up 2 CPUs
[ 0.181427] SMP: Total of 2 processors activated (3188.82 BogoMIPS).
[ 0.184509] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for emif_fw
[ 0.184509] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l3_instr
[ 0.184509] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l3_main_1
[ 0.184509] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l3_main_2
[ 0.184509] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_abe
[ 0.184509] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_cfg
[ 0.184509] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_per
[ 0.184509] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for l4_wkup
[ 0.184509] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for mpu_private
[ 0.184814] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for sl2if
[ 0.184814] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for thermal_sensor
[ 0.184906] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for usbhs_ohci
[ 0.184906] omap_hwmod: _populate_mpu_rt_base found no _mpu_rt_va for usbhs_ehci
[ 0.184906] omap_hwmod: l3_div_ck: missing clockdomain for l3_div_ck.
[ 0.184906] omap_hwmod: l4_div_ck: missing clockdomain for l4_div_ck.
[ 0.186859] _omap4_module_wait_ready: Timeout waiting for module enable (mcpdm_fck: clkctrl = 0x30002)
[ 0.189697] omap_hwmod: mcpdm: cannot be enabled (3)
[ 0.194641] print_constraints: dummy:
[ 0.194641] NET: Registered protocol family 16
[ 0.195312] GPMC revision 6.0
[ 0.195312] EMIF0 is enabled with IRQ142
[ 0.196380] EMIF1 is enabled with IRQ143
[ 0.196380] Last reset was cold reset (PRM_RSTST=0x1)
[ 0.196380]
[ 0.196624] OMAP GPIO hardware version 0.1
[ 0.197662] omap_mux_init: Add partition: #1: core, flags: 2
[ 0.199371] omap_mux_init: Add partition: #2: wkup, flags: 2
[ 0.199554] Samsung DDR Memory
[ 0.199645] kxtf9 i2c address = 0xe
[ 0.199920] ovation_touch_init: Registering touch controller device
[ 0.201629] Using Ovation ETV1A wifi configuration
[ 0.206634] OMAP DMA hardware revision 0.0
[ 0.206634] omap_rproc_get_pool: dsp - static memory is unavailable: 0x0, 0x0
[ 0.207031] omap_rproc_get_pool: ipu - carveout memory is unavailable: 0x0, 0x0
[ 0.212768] bio: create slab <bio-0> at 0
[ 0.212951] print_constraints: vdd_lcdtp: 3300 mV normal
[ 0.213531] print_constraints: vwl1271: 1800 mV
[ 0.213531] print_constraints: vsys-wlan: 3875 mV
[ 0.213714] i2c-core: driver [twl] using legacy suspend method
[ 0.213714] i2c-core: driver [twl] using legacy resume method
[ 0.213714] usbcore: registered new interface driver usbfs
[ 0.214172] usbcore: registered new interface driver hub
[ 0.214355] usbcore: registered new device driver usb
[ 0.214935] omap_i2c omap_i2c.1: bus 1 rev4.0 at 400 kHz
[ 0.214935] Skipping twl internal clock init and using bootloader value (unknown osc rate)
[ 0.217071] twl6030: PIH (irq 39) chaining IRQs 368..387
[ 0.218963] print_constraints: LDOUSB: 3300 mV normal standby
[ 0.221466] twl6030_usb twl6030_usb: Initialized TWL6030 USB module
[ 0.224090] print_constraints: VANA: 2100 mV normal standby
[ 0.224731] print_constraints: CLK32KG:
[ 0.225402] print_constraints: CLK32KAUDIO:
[ 0.226318] print_constraints: SYSEN:
[ 0.227203] print_constraints: REGEN1:
[ 0.227630] print_constraints: LDO5: 1200 <--> 3000 mV at 3000 mV normal standby
[ 0.228210] print_constraints: LDO1: 1800 <--> 2500 mV at 1700 mV normal standby
[ 0.228668] suspend_set_state: LDO7: No configuration
[ 0.228881] print_constraints: LDO7: 1800 mV normal standby
[ 0.229858] print_constraints: LDO6: 1800 mV normal standby
[ 0.230651] print_constraints: LDOLN: 1800 mV normal standby
[ 0.231506] print_constraints: LDO2: 1000 <--> 3000 mV at 2800 mV normal standby
[ 0.231903] print_constraints: LDO4: 1800 mV normal standby
[ 0.232696] print_constraints: LDO3: 1800 mV normal standby
[ 0.233123] omap_i2c omap_i2c.3: bus 3 rev4.0 at 400 kHz
[ 0.233825] omap-rproc omap-rproc.0: dsp is available
[ 0.233825] omap-rproc omap-rproc.1: ipu is available
[ 0.233825] Advanced Linux Sound Architecture Driver Version 1.0.24.
[ 0.234588] Bluetooth: Core ver 2.16
[ 0.234588] NET: Registered protocol family 31
[ 0.234588] Bluetooth: HCI device and connection manager initialized
[ 0.234588] Bluetooth: HCI socket layer initialized
[ 0.234588] Bluetooth: L2CAP socket layer initialized
[ 0.234771] Bluetooth: SCO socket layer initialized
[ 0.234771] Switching to clocksource 32k_counter
[ 0.236053] Switched to NOHz mode on CPU #0
[ 0.236083] Switched to NOHz mode on CPU #1
[ 0.241699] musb-hdrc: version 6.0, musb-dma, otg (peripheral+host)
[ 0.242248] musb-hdrc musb-hdrc: USB OTG mode controller at fc0ab000 using DMA, IRQ 124
[ 0.242675] NET: Registered protocol family 2
[ 0.242706] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.243774] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.243774] TCP bind hash table entries: 65536 (order: 8, 1572864 bytes)
[ 0.243774] TCP: Hash tables configured (established 131072 bind 65536)
[ 0.243774] TCP reno registered
[ 0.243774] UDP hash table entries: 512 (order: 3, 32768 bytes)
[ 0.248352] UDP-Lite hash table entries: 512 (order: 3, 32768 bytes)
[ 0.248352] NET: Registered protocol family 1
[ 0.267456] Trying to unpack rootfs image as initramfs...
[ 0.359802] Freeing initrd memory: 1832K
[ 0.812927] omap_init_opp_table: no hwmod or odev for hsi, [26] cannot add OPPs.
[ 0.812927] omap_init_opp_table: no hwmod or odev for hsi, [27] cannot add OPPs.
[ 1.328552] ram_console: got buffer at 90000000, size 200000
[ 1.329376] ram_console: no valid data in buffer (sig = 0x08f9f706)
[ 1.329650] console [ram-1] enabled
[ 1.329650] omap-iommu omap-iommu.0: ducati registered
[ 1.329650] omap-iommu omap-iommu.1: tesla registered
[ 1.337341] highmem bounce pool size: 64 pages
[ 1.337646] ashmem: initialized
[ 1.344177] fuse init (API version 7.16)
[ 1.344787] msgmni has been set to 1489
[ 1.344787] Registering char device tf_driver (122:0)
[ 1.344787] SMCAG01.06p6.0 D
[ 1.346649] io scheduler noop registered
[ 1.346649] io scheduler deadline registered (default)
[ 1.346649] io scheduler cfq registered
[ 1.346771] start plist test
[ 1.350708] end plist test
[ 1.751861] OMAP DSS rev 4.1
[ 1.754333] Keyboard driver not present
[ 1.755004] novatek-panel display0: novatek_probe
[ 1.755065] novatek-panel display0: novatek_probe done
[ 1.755065] dsscomp: initializing.
[ 1.755065] misc dsscomp: display0=novatek-panel
[ 1.755065] misc dsscomp: display1=hdmi_panel
[ 1.755065] misc dsscomp: found 2 displays and 4 overlays, WB overlay 1
[ 1.755859] could not allocate slot
[ 1.756011] omap-rproc omap-rproc.1: powering up ipu
[ 1.756378] virtio_rpmsg_bus virtio0: rpmsg backend virtproc probed successfully
[ 1.756988] virtio_rpmsg_bus virtio1: rpmsg backend virtproc probed successfully
[ 1.756988] omap-rproc omap-rproc.0: powering up dsp
[ 1.757446] virtio_rpmsg_bus virtio2: rpmsg backend virtproc probed successfully
[ 1.757446] omap_uart.0: ttyO0 at MMIO 0x4806a000 (irq = 104) is a OMAP UART0
[ 1.758636] omap_uart.3: ttyO3 at MMIO 0x4806e000 (irq = 102) is a OMAP UART3
[ 1.759094] omap_ion_probe: adding heap secure_input of type 2 with [email protected]
[ 1.759094] omap_ion_probe: adding heap secure_output_wfdhdcp of type 2 with [email protected]
[ 1.759552] omap_ion_probe: adding heap tiler of type 4 with [email protected]
[ 1.759552] omap_ion_probe: adding heap nonsecure_tiler of type 4 with [email protected]
[ 1.759704] omap_ion_probe: adding heap system of type 0 with [email protected]
[ 1.759704] omap_ion_probe: adding heap tiler_reservation of type 5 with [email protected]
[ 1.759704] brd: module loaded
[ 1.766052] loop: module loaded
[ 1.766052] usbcore: registered new interface driver ub
[ 1.766052] (stk) :sysfs entries created
[ 1.766052] (stk) : debugfs entries created
[ 1.769134] (hci_tty): inside hci_tty_init
[ 1.769134] (hci_tty): allocated 251, 0
[ 1.799896] tun: Universal TUN/TAP device driver, 1.6
[ 1.799896] tun: (C) 1999-2004 Max Krasnyansky <[email protected]>
[ 1.799896] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.799896] usbcore: registered new interface driver usbserial
[ 1.802398] USB Serial support registered for generic
[ 1.802398] usbcore: registered new interface driver usbserial_generic
[ 1.802490] usbserial: USB Serial Driver core
[ 1.802490] USB Serial support registered for GSM modem (1-port)
[ 1.802490] usbcore: registered new interface driver option
[ 1.802490] option: v0.7.2:USB Driver for GSM modems
[ 1.802673] USB Serial support registered for pl2303
[ 1.802673] usbcore: registered new interface driver pl2303
[ 1.802825] pl2303: Prolific PL2303 USB to serial adaptor driver
[ 1.804382] android_usb gadget: Mass Storage Function, version: 2009/09/11
[ 1.804412] android_usb gadget: Number of LUNs=1
[ 1.804412] lun0: LUN: removable file: (no medium)
[ 1.804504] android_usb gadget: android_usb ready
[ 1.804504] musb-hdrc musb-hdrc: MUSB HDRC host driver
[ 1.804504] musb-hdrc musb-hdrc: new USB bus registered, assigned bus number 1
[ 1.804931] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.804931] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.805114] usb usb1: Product: MUSB HDRC host driver
[ 1.805114] usb usb1: Manufacturer: Linux 3.0.31-green+ musb-hcd
[ 1.805114] usb usb1: SerialNumber: musb-hdrc
[ 1.805694] hub 1-0:1.0: USB hub found
[ 1.805694] hub 1-0:1.0: 1 port detected
[ 1.806274] mousedev: PS/2 mouse device common for all mice
[ 1.806854] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[ 1.807067] input: omap4-keypad as /devices/platform/omap/omap4-keypad/input/input1
[ 1.807800] usbcore: registered new interface driver xpad
[ 1.807861] FTX: ft5x06_module_init(): INFO: Initializing FT I2C Touchscreen Driver (Built Jan 26 2014 @ 09:05:13)
[ 1.807861] 3-0038: FTX: ft5x06_probe(): INFO: probing for ft5x06-i2c @ 3-0038 .
[ 2.079406] 3-0038: FTX: ft5x06_probe(): INFO: focaltech controller with Product ID=0x06 found @ 0x38.
[ 2.138580] 3-0038: FTX: ftx_input_device_initialize(): INFO: Successfully initialzed slots; using Type B protocol.
[ 2.138580] input: ft5x06-i2c as /devices/platform/omap/omap_i2c.3/i2c-3/3-0038/input/input2
[ 2.138580] twl6030_pwrbutton_probe: Enter
[ 2.139739] input: twl6030_pwrbutton as /devices/platform/omap/omap_i2c.1/i2c-1/1-0049/twl6030_pwrbutton/input/input3
[ 2.242523] kxtf9 1-000e: WHO_AM_I = 0x08
[ 2.242523] kxtf9(8) detected
[ 2.243164] input: kxtf9_accel as /devices/virtual/input/input4
[ 2.244049] input: twl6040_hskeys as /devices/platform/omap/omap_i2c.1/i2c-1/1-004b/twl6040-audio/twl6040-hskeys/input/input5
[ 2.247314] using rtc device, twl_rtc, for alarms
[ 2.247680] twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
[ 2.247894] i2c /dev entries driver
[ 2.247894] Linux video capture interface: v2.00
[ 2.248321] usbcore: registered new interface driver uvcvideo
[ 2.248321] USB Video Class driver (v1.1.0)
[ 2.248321] dmm: probe base: fd300000, irq 145
[ 2.248321] finish bat_low irq. gpio_bat_low:42
[ 2.250579] bq27x00-battery 1-0055: support ver. 1.2.0 enabled
[ 2.466979] bq2419x driver init
[ 2.467041] bq2419x probe
[ 2.467254] bq24196 1-006b: read_reg=0x2a
[ 2.467254] bq24196 1-006b: identified chip BQ24196_REV_1_3
[ 2.467315] bq24196 1-006b: found chip at 0x6b
[ 2.468292] bq24196 1-006b: omap_get_clk_load: 0x821d6fff
[ 2.468780] bq24196 1-006b: resting registers
[ 2.469787] bq24196 1-006b: INTERRUPT 08=0, 09=0
[ 2.469787] bq24196 1-006b: S: Not Power Good
[ 2.469848] bq24196 1-006b: S: CHARGE STATE = 0 (NOT CHARGING)
[ 2.469879] bq24196 1-006b: S: VBUS STATE = 0 (Unknown)
[ 2.469909] device-mapper: uevent: version 1.0.3
[ 2.469909] device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: [email protected]
[ 2.469909] Bluetooth: Bluetooth Driver for TI WiLink - Version 1.0
[ 2.473449] cpuidle: using governor ladder
[ 2.473480] cpuidle: using governor menu
[ 2.478057] Registered led device: omap4:green:debug0
[ 2.479034] usbcore: registered new interface driver usbhid
[ 2.479064] usbhid: USB HID core driver
[ 2.479095] usbip_core: USB/IP Core v1.0.0
[ 2.479370] vhci_hcd vhci_hcd: USB/IP Virtual Host Controller
[ 2.479431] vhci_hcd vhci_hcd: new USB bus registered, assigned bus number 2
[ 2.479888] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 2.479919] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.479949] usb usb2: Product: USB/IP Virtual Host Controller
[ 2.479980] usb usb2: Manufacturer: Linux 3.0.31-green+ vhci_hcd
[ 2.480010] usb usb2: SerialNumber: vhci_hcd
[ 2.480529] hub 2-0:1.0: USB hub found
[ 2.480560] hub 2-0:1.0: 8 ports detected
[ 2.480895] vhci_hcd: USB/IP 'Virtual' Host Controller (VHCI) Driver v1.0.0
[ 2.481079] usbcore: registered new interface driver usbip
[ 2.481109] usbip_host: USB/IP Host Driver 1.0.0
[ 2.481445] logger: created 256K log 'log_main'
[ 2.481567] logger: created 256K log 'log_events'
[ 2.481689] logger: created 256K log 'log_radio'
[ 2.481811] logger: created 256K log 'log_system'
[ 2.482147] pcb_temp_sensor pcb_temp_sensor.0: pcb_sensor : 'pcb_temp_sensor'
[ 2.485229] SDP4430 SoC init
[ 2.489685] twl6040-codec twl6040-codec: couldn't get VDDHF regulator -19
[ 2.521148] asoc: null-codec-dai <-> MultiMedia1 mapping ok
[ 2.522430] asoc: null-codec-dai <-> MultiMedia2 mapping ok
[ 2.527130] asoc: null-codec-dai <-> Voice mapping ok
[ 2.528259] asoc: null-codec-dai <-> Tones mapping ok
[ 2.529388] asoc: null-codec-dai <-> Vibra mapping ok
[ 2.530212] asoc: null-codec-dai <-> MODEM mapping ok
[ 2.530944] asoc: null-codec-dai <-> MultiMedia1 LP mapping ok
[ 2.532409] asoc: FM Digital <-> omap-mcbsp-dai.1 mapping ok
[ 2.533508] asoc: twl6040-dl1 <-> mcpdm-dl mapping ok
[ 2.535247] asoc: dmic-hifi <-> omap-dmic-dai-0 mapping ok
[ 2.537628] twl6040-codec twl6040-codec: ASoC: Failed to create Aux/FM Stereo In debugfs file
[ 2.538574] asoc: twl6040-dl1 <-> mcpdm-dl1 mapping ok
[ 2.539398] asoc: twl6040-ul <-> mcpdm-ul1 mapping ok
[ 2.540252] asoc: twl6040-dl2 <-> mcpdm-dl2 mapping ok
[ 2.541107] asoc: twl6040-vib <-> mcpdm-vib mapping ok
[ 2.541992] asoc: Bluetooth <-> omap-mcbsp-dai.2 mapping ok
[ 2.542877] asoc: Bluetooth <-> omap-mcbsp-dai.2 mapping ok
[ 2.543762] asoc: FM Digital <-> omap-mcbsp-dai.1 mapping ok
[ 2.544616] asoc: MODEM <-> omap-mcbsp-dai.1 mapping ok
[ 2.545501] asoc: dmic-hifi <-> omap-dmic-abe-dai-0 mapping ok
[ 2.546356] asoc: dmic-hifi <-> omap-dmic-abe-dai-1 mapping ok
[ 2.547210] asoc: dmic-hifi <-> omap-dmic-abe-dai-2 mapping ok
[ 2.548187] asoc: null-codec-dai <-> omap-abe-vxrec-dai mapping ok
[ 2.550445] input: Ovation Line-Out Jack as /devices/platform/soc-audio/sound/card0/input6
[ 2.550781] input: Ovation Headset Jack as /devices/platform/soc-audio/sound/card0/input7
[ 2.553558] asoc: hdmi-audio-codec <-> hdmi-audio-dai mapping ok
[ 2.554046] ALSA device list:
[ 2.554046] #0: TI OMAP4 Board
[ 2.554077] #1: OMAP4HDMI
[ 2.554168] GACT probability NOT on
[ 2.554199] Mirror/redirect action on
[ 2.554229] u32 classifier
[ 2.554229] Actions configured
[ 2.554260] Netfilter messages via NETLINK v0.30.
[ 2.554351] nf_conntrack version 0.5.0 (12194 buckets, 48776 max)
[ 2.555267] xt_time: kernel timezone is -0000
[ 2.556274] IPv4 over IPv4 tunneling driver
[ 2.557647] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 2.557739] TCP cubic registered
[ 2.557769] NET: Registered protocol family 17
[ 2.557800] NET: Registered protocol family 15
[ 2.557922] Bluetooth: RFCOMM TTY layer initialized
[ 2.557952] Bluetooth: RFCOMM socket layer initialized
[ 2.557983] Bluetooth: RFCOMM ver 1.11
[ 2.558013] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 2.558105] lib80211: common routines for IEEE802.11 drivers
[ 2.558135] lib80211_crypt: registered algorithm 'NULL'
[ 2.558166] Registering the dns_resolver key type
[ 2.558197] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 2.558258] ThumbEE CPU extension supported.
[ 2.558288] Registering SWP/SWPB emulation handler
[ 2.561767] >>> setting nvalues for oh = smartreflex_core
[ 2.561828] >>> sr_set_nvalues v = 10145780, sr_efuse_offs = 254
[ 2.561828] >>> sr_set_nvalues v = 10126506, sr_efuse_offs = 257
[ 2.561859] >>> sr_set_nvalues v = 10126506, sr_efuse_offs = 257
[ 2.561889] >>> sr_set_nvalues v = 11198099, sr_efuse_offs = 25a
[ 2.562133] >>> setting nvalues for oh = smartreflex_iva
[ 2.562164] >>> sr_set_nvalues v = 10091001, sr_efuse_offs = 22c
[ 2.562194] >>> sr_set_nvalues v = 10063493, sr_efuse_offs = 22f
[ 2.562194] >>> sr_set_nvalues v = 11202269, sr_efuse_offs = 232
[ 2.562225] >>> sr_set_nvalues v = 11182739, sr_efuse_offs = 235
[ 2.562255] >>> sr_set_nvalues v = 11177602, sr_efuse_offs = 238
[ 2.562408] >>> setting nvalues for oh = smartreflex_mpu
[ 2.562438] >>> sr_set_nvalues v = 10141671, sr_efuse_offs = 240
[ 2.562469] >>> sr_set_nvalues v = 11205796, sr_efuse_offs = 243
[ 2.562500] >>> sr_set_nvalues v = 11190917, sr_efuse_offs = 246
[ 2.562530] >>> sr_set_nvalues v = 11247585, sr_efuse_offs = 249
[ 2.562561] >>> sr_set_nvalues v = 11245013, sr_efuse_offs = 24c
[ 2.562774] Reprogramming LPDDR2 timings to 466666666 Hz
[ 2.563018] sr_init: No PMIC hook to init smartreflex
[ 2.563201] smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver initialized
[ 2.563415] smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver initialized
[ 2.563598] smartreflex smartreflex.2: omap_sr_probe: SmartReflex driver initialized
[ 2.563903] SmartReflex class 1.5 driver: initialized (86400000ms)
[ 2.564117] cpufreq_interactive_input_connect: connect to ft5x06-i2c
[ 2.564178] 3-0038: FTX: ft5x06_resume(): INFO: driver is resuming.
[ 2.564575] Power Management for TI OMAP4.
[ 2.564727] OMAP4 PM: Static dependency added between MPUSS and DUCATI <-> L4_PER/CFG and L3_1.
[ 2.570953] mmc0: new high speed DDR MMC card at address 0001
[ 2.571380] mmcblk0: mmc0:0001 MBG4GA 29.1 GiB
[ 2.571563] mmcblk0boot0: mmc0:0001 MBG4GA partition 1 2.00 MiB
[ 2.571746] mmcblk0boot1: mmc0:0001 MBG4GA partition 2 2.00 MiB
[ 2.574066] Alternate GPT is invalid, using primary GPT.
[ 2.574188] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10
[ 2.576599] mmcblk0boot1: unknown partition table
[ 2.577514] mmcblk0boot0: unknown partition table
[ 2.579376] clock: disabling unused clocks to save power
[ 2.641052] sr_class1p5_calib_work: iva Stop sampling: Voltage Nominal=950000 samples=12
[ 2.641082] sr_class1p5_calib_work: iva: Calibration complete: Voltage Nominal=950000Calib=835600 margin=0
[ 2.714233] mmc1: host does not support reading read-only switch. assuming write-enable.
[ 2.727020] mmc1: new high speed SDHC card at address 1234
[ 2.727325] mmcblk1: mmc1:1234 SA16G 14.6 GiB
[ 2.728820] mmcblk1: p1 p2 p3
[ 2.729339] Enable wl12xx power
[ 2.821319] 3-0038: FTX: ft5x06_resume(): INFO: driver resumed.
[ 2.950256] mmc2: card claims to support voltages below the defined range. These will be ignored.
[ 2.953399] copying uboot splash: 39321600 bytes from 0xf5000000 to 0xf2000000
[ 2.985473] mmc2: queuing unknown CIS tuple 0x91 (3 bytes)
[ 2.986083] mmc2: new SDIO card at address 0001
[ 2.986694] Disable wl12xx power
[ 3.144378] cannot apply mgr(lcd) on inactive device
[ 3.163330] Console: switching to colour frame buffer device 240x80
[ 3.182678] cannot apply mgr(lcd) on inactive device
[ 3.182769] omapfb omapfb: failed to apply dispc config
[ 3.182861] cannot apply mgr(tv) on inactive device
[ 3.182983] omapfb omapfb: failed to apply dispc config
[ 3.183074] cannot apply mgr(lcd2) on inactive device
[ 3.183197] omapfb omapfb: failed to apply dispc config
[ 3.183258] novatek-panel display0: enable
[ 3.183319] novatek-panel display0: power_on
[ 3.183746] novatek-panel display0: power_on done
[ 3.184326] regulator_init_complete: LDO1: disabling
[ 3.185791] twl_rtc twl_rtc: setting system clock to 2014-01-27 04:13:49 UTC (1390796029)
[ 3.186096] Warning: unable to open an initial console.
[ 3.186218] Freeing init memory: 492K
[ 3.203613] sr_class1p5_calib_work: mpu: Calibration complete: Voltage Nominal=1380000Calib=1316680 margin=0
[ 3.219207] sr_class1p5_calib_work: core: Calibration complete: Voltage Nominal=1190000Calib=1076140 margin=0
[ 3.259979] init: cannot open '/initlogo.rle'
[ 3.280609] init: Unable to open persistent property directory /data/property errno: 2
[ 3.280883] 3-0038: FTX: ft5x06_suspend(): INFO: driver is suspending.
[ 3.289459] 3-0038: FTX: ft5x06_suspend(): INFO: driver suspended.
[ 3.311126] omap-rproc omap-rproc.0: rproc_loader_cont: failed to load tesla-dsp.bin
[ 3.311523] omap-rproc omap-rproc.1: rproc_loader_cont: failed to load ducati-m3.bin
[ 3.330047] HDCP: failed to load keys
[ 3.353820] android_usb: already disabled
[ 3.354064] init: using deprecated syntax for specifying property 'ro.product.manufacturer', use ${name} instead
[ 3.354278] init: using deprecated syntax for specifying property 'ro.product.model', use ${name} instead
[ 3.354492] init: using deprecated syntax for specifying property 'ro.serialno', use ${name} instead
[ 3.354766] android_usb: already disabled
[ 3.355957] adb_open
[ 3.355987] adb_bind_config
[ 3.356567] SysRq : Emergency Remount R/O
[ 3.356689] Emergency Remount complete
[ 3.357208] Disabling non-boot CPUs ...
[ 3.357666] CPU1: shutdown
[ 3.563873] 3-0038: FTX: INFO: Shutdown.
[ 3.579956] bq24196 1-006b: bq2419x_charger_shutdown
[ 3.595825] kxtf9: Shutdown.
[ 3.626617] omap_hsmmc omap_hsmmc.1: shutting down mmc
[ 3.667175] novatek-panel display0: disable
[ 3.685577] Restarting system with command 'bootloader'.
[ 3.700927]
[ 3.716278] Restarting Linux version 3.0.31-green+ ([email protected]) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-188) ) #6 SMP PREEMPT Sun Jan 26 09:22:35 EST 2014
[ 3.716278]
0 Corrected bytes, 218 unrecoverable blocks
I believe part of my problem is that (my) toolchain needs to match that with what CM was built with. (Which means I would probably have to build the whole CM package in order for it to work). I have an overclocked recovery, but that doesn't make much sense
There seems to be lots of discussion between conflicts between smartreflex and various governors.
Since these things normally run at 396 or 800 Mhz, I wonder if it would be more advantageous to tweak ram settings and such at those speeds
TBH, my main goal is to get Arch linux on this thing.
To that end, I plan on purchasing a Prolific PL2303 USB to serial adaptor so as to have a console.
This won't help me with any bootloader work, but I don't wish to disassemble my nook to solder in two wires to get a uart console (would still have to purchase a FT232RL USB to Serial breakout board for voltage level shifting).

Success! Check out the attached screenshots. First benchmark is stock CM10.1, second benchmark is with overclocked kernel. CM10.1 doesn't benchmark near as well as CM11 or Carbon, so I imagine I could great results using a Carbon rom.

Awesome man, I'm impressed. Were you modifying voltage as well? Also let us know how far you can take it.

Holy cr$$. Does actual use feel as fast as benchmark indicates? Is your nook hot? Does it crash all over the place? (I guess it's stable enough to finish the benchmark!) What does this do to your battery life?

This was mainly meant as a proof of concept, in trying to elicit kernel development discussion and trying to fish for more information on how to do it.
I was slightly frustrated in that there's overclock kernels available for the kindle fire hd (same proc as ours), but if you follow the links to source, the overclock code is always missing. They have AVAILABLE: CPU up to 1.7 and GPU up to 512. I don't think anyone is actually achieving that.
After playing with it for awhile my take is that these things are maxed out already. I did leave stock voltages alone.
1600 seems to work OK, instead of adding extra stepping, prolly easier just to change the two 1500's to 1600's.
GPU over clock is buggy in that it breaks video playback of certain formats (probably a timings issue). I've heard of people getting up to 440.
No overclock is bug free for me.
Samsung lpddr ram timings are interesting, but again not much leeway.
Here's some info to anyone interested.
I used the gcc-linaro-arm-linux-gnueabihf-4.7-2013.04-20130415_linux.tar toolchain, available on the launchpad linaro toolchain binaries download page (after fighting with crosstool-ng).
A big help for me was using a hex editor, ended up compiling okteta.
Take a working boot.img open it in your hex editor. Cut 0000:0000 - 000F:FFFF, this is your "green loader". (I realize this can be done with dd, have at it).
After this has been cut out, your boot.img can be split into zImage and initramfs.cpio.gz using umkbootimg. This will also give the command to put it back together.
Code:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x80000000 --cmdline 'androidboot.console=ttyO0 console=ttyO0,115200n8 def_disp=lcd2' --pagesize 4096 -o new_boot.img
Then you will need to take your new_boot.img and append the green loader onto the beginning (turn off overwrite mode).
To fix ram_console turn on little endian support in kernel config (missing in official builds to date).
Good luck! I wish I had been given this tutorial....
Edit: I also played around with adding various I/O schedulers, I expect to do the same with governors as time permits.
These would probably make the most difference in battery life and performance.

Wrong boot.img. The one posted has IPv6 disabled in the kernel (as an experiment). Most everything google is broken (although browser still works). It does have some interesting logcat entries (googleconversionpings and such). It actually does a good job if you want a very basic secure tablet.
Here, this should be correct.
(1620/405)
mediafire<dot>com/download/6xjogrrbt1693ps/cm-10.1.3-ovation_OC2.zip
BTW, the config can be found in /proc/config.gz. Also compiled with kexec support.

Third version.
I believe this to be the smoothest, fastest, (and I dare say), most stable rom out there available for the HD+/ovation.
Give it a test run and tell me what you think.
Video playback performance is phenomenal.
mediafire<dot>com/download/6uvpqid45l5s99d/cm-10.1.3-ovation_OC3.zip
(kernel version should read Tue Mar 11 17:14, if I packed it correctly)
my kernel source:
mediafire<dot>com/download/d289cudx4pq6bvm/android_kernel_bn_omap-cm-10.1_v1.tar.gz
extra kernel modules, most users won't need these unless you're trying to set up a vpn or something:
mediafire<dot>com/download/670pzf1r2lu1dy8/extra_modules_ovation_cm10.1.3.tar.gz
A collection of linux tools for .img file work in case someone wants to make their own kernel
mediafire<dot>com/download/ny2209vapfi8ngg/bootimg_tools_ovation_1.tar.gz
What I have for pvr-sgx kernel module source.
mediafire<dot>com/download/04z6o0xlp513h4l/pvr_source.tar.gz
I think the kernel or the pvr source needs a patch (possibly something to do with remoteproc power management), as the versions I've compiled are unstable.
It could possibly be the command line I'm using?
make ARCH=arm CROSS_COMPILE=arm-eabi- BUILD=release TARGET_SGX=544sc
Click to expand...
Click to collapse
Could anyone help me on this? Being able to compile working pvr modules would help greatly with kernel development (so the pvr matches the kernel you're hacking).
Anyway I believe the above ROM is going to be my go-to daily driver.

Took a stab at fixing our ft5x06 touchscreen issues.
This is the result:
http://www.mediafire.com/download/he3reojs86oh0b3/ovation-kernel-cm10.1.3_v1.zip
(just the kernel- to be flashed over one of my previous roms).
Much better touchscreen performance (took out the twitch without using "fuzz", and I haven't experienced any more lockups with random/phantom touches, focus/selecting seems to work better too... but I'm still testing).
Surprisingly enough the issues seem to have been with kernel 3.0 i2c-core bus drivers rather than the touchscreen driver itself.

OCCCC
Although overclocking is obviously against CM policy, I'd love it for our Nooks to have access to modifying our CPU speeds.
But then I read awhile back that verygreen said that ocing the CPU didn't improve much and speculated that ocing the GPU would help more. o.o

I'm continuing to work on it and fine tune the results as time permits (until I'm happy with it).
This is my latest.
http://www.mediafire.com/download/hk136whf6f0ew60/ovation-kernel-cm10.1.3_v2.zip
(again kernel update only- to be flashed over one of my previous roms).
This one has lowered voltages. Slightly modified ram timings.
Same basic overclock and has the touchscreen fixes.
I ran into a problem where my browser was crashing and logs indicated libdrm/dalvik.
Wiping the dalvik cache took care of it. Just FYI, as it took me forever to figure out.
I haven't had a single crash on this kernel yet.
This one should run much cooler than even stock.

Jon Lee said:
I'm continuing to work on it and fine tune the results as time permits (until I'm happy with it).
This is my latest.
http://www.mediafire.com/download/hk136whf6f0ew60/ovation-kernel-cm10.1.3_v2.zip
(again kernel update only- to be flashed over one of my previous roms).
This one has lowered voltages. Slightly modified ram timings.
Same basic overclock and has the touchscreen fixes.
I ran into a problem where my browser was crashing and logs indicated libdrm/dalvik.
Wiping the dalvik cache took care of it. Just FYI, as it took me forever to figure out.
I haven't had a single crash on this kernel yet.
This one should run much cooler than even stock.
Click to expand...
Click to collapse
I flashed this over CM10.1 stable and got a bootloop. What do you mean with "flash over one my previous roms" - which ROMs?
EDIT: My bad, didn't see the links you posted. They weren't red like usual.
I will try it! Thanks!
EDIT2: Wow, it is really stable and fast. But i have extreme touchscreen twitching on the right hand side of the screen. Increasing Fuzz fixed that for me in other builds.
EDIT3: Got random reboot while restoring apps with Titanium Backup. It would be great it you could take a look at the log. I have been getting reboots on every ROM out there, maybe you know the problem.
last_kmsg: https://drive.google.com/file/d/0B5xpEXQcSQncMENxR3lyOXAwNlU/edit?usp=sharing
And do I have to flash the ROM, Kernel v1 and then v2 or does v2 include the changes from v1?

Here's a complete, to-date ROM. (So as to save from flashing multiple files).
http://www.mediafire.com/download/cifx5qa8xvv3u1j/cm-10.1.3-ovation_OC4.zip
Be sure to wipe dalvik cache!
I'm not sure if you can use titanium to restore apps from 10.2 to 10.1 without causing problems.
Just a note, you won't be able to flash my kernel updates on stock CM without being prepared to adb push /system/lib/modules/*
(IE bootloops, etc)
If you continue to have problems with wl12xx, I would take a look at your wireless access point settings (perhaps change encryption type, etc).
I see a lot of deauthenticated, reason 7. I would love to fix this but compiling my own working wl12xx drivers is a major PITA.

Jon Lee said:
Here's a complete, to-date ROM. (So as to save from flashing multiple files).
http://www.mediafire.com/download/cifx5qa8xvv3u1j/cm-10.1.3-ovation_OC4.zip
Be sure to wipe dalvik cache!
I'm not sure if you can use titanium to restore apps from 10.2 to 10.1 without causing problems.
Just a note, you won't be able to flash my kernel updates on stock CM without being prepared to adb push /system/lib/modules/*
(IE bootloops, etc)
If you continue to have problems with wl12xx, I would take a look at your wireless access point settings (perhaps change encryption type, etc).
I see a lot of deauthenticated, reason 7. I would love to fix this but compiling my own working wl12xx drivers is a major PITA.
Click to expand...
Click to collapse
This one has your kernel already in it correct? Any special recovery needed?

Jon Lee said:
Here's a complete, to-date ROM. (So as to save from flashing multiple files).
http://www.mediafire.com/download/cifx5qa8xvv3u1j/cm-10.1.3-ovation_OC4.zip
Be sure to wipe dalvik cache!
I'm not sure if you can use titanium to restore apps from 10.2 to 10.1 without causing problems.
Just a note, you won't be able to flash my kernel updates on stock CM without being prepared to adb push /system/lib/modules/*
(IE bootloops, etc)
If you continue to have problems with wl12xx, I would take a look at your wireless access point settings (perhaps change encryption type, etc).
I see a lot of deauthenticated, reason 7. I would love to fix this but compiling my own working wl12xx drivers is a major PITA.
Click to expand...
Click to collapse
Okay, I will try that.
So what exactly was the reason for my reboot? What is wl 12xx? I am not an expert

Slightly aggravated. Typed a long post, only to be logged out, and lost it, and I continue to have login/password issues.
Calling this project quits.
This is THE FINAL VERSION.
http://www.mediafire.com/download/x4cksy5scvi1874/cm-10.1.3-ovation_OC5.zip
WORKING PVR SOURCE.
http://www.mediafire.com/download/at6yl23jrvpweav/pvr_source_1.tar.gz
Kernel source than matches rom above.
http://www.mediafire.com/download/ohcxmrgz9j4ly8y/android_kernel_bn_omap-cm-10.1_v2.tar.gz
What this lacks.
http://processors.wiki.ti.com/index...1_compat_wireless_implementation_Architecture
Thank you.
Edit: BTW, that was a quick fix from OC4, which was no good (voltages). Working pvr_sgx source opens up a whole can of worms as far as having matching dpll_cascading symbols in the pvr module or not (as far as kernel updates go), which is a good enough reason to call it quits here to save on confusion. Seriously, the above is as good as I'm going to get it.
To put it another way, no other kernels will work on this ROM (pvr missing dpll_cascading symbols), and If I were to make any other kernel updates, they wouldn't work on any other roms (including the first ones I did).

Jon Lee said:
Here's a complete, to-date ROM. (So as to save from flashing multiple files).
cm-10.1.3-ovation_OC4.zip
Be sure to wipe dalvik cache!
I'm not sure if you can use titanium to restore apps from 10.2 to 10.1 without causing problems.
Just a note, you won't be able to flash my kernel updates on stock CM without being prepared to adb push /system/lib/modules/*
(IE bootloops, etc)
If you continue to have problems with wl12xx, I would take a look at your wireless access point settings (perhaps change encryption type, etc).
I see a lot of deauthenticated, reason 7. I would love to fix this but compiling my own working wl12xx drivers is a major PITA.
Click to expand...
Click to collapse
wow I don't know, what was wrong with my device or with CM10.2 (I had a lot of Reboots every day) but this release works like a charm :good:
actually i wasn't intrested in OC (becauce of Battery usage) but if this CM is the only stable release for my device I will keep it
thx man

Thanks, if it wasn't obvious, I was more interested in stability than I was in any overclock... (for me), because I'm wanting to use this too. I did try to take care of several kernel bugs that were common across all ROMS (l3_noc, mmc, I2C), without causing further problems.
That last version does seem stable (especially if you clear dalvik cache after installing). One thing I did notice is that I played with IVA clock a little (as an experiment), and although we don't use DSP/tesla, it seems to have slightly affected the I2C touchscreen bug. Perhaps the IVA clock is somehow connected to the I2C clock. I'm making one now where I reduced it instead of increasing it, and see if that further reduces any I2C jitters. Shouldn't affect performance because we don't use tesla (although as an experiment, I did get a tesla bin to load properly, and even had the rpmsg communication channel and everything).
I also managed to compile a compat.ko module last night. Still doesn't work properly. WIFI is going to kick my butt. That is really the last thing that remains to be done.
Eventually, if I could leave well enough alone, I would like to see how long I could go without a reboot, and we could prove "What is the Most Stable ROM" debate scientifically with a 'cat /proc/uptime', but at the moment I'm continually playing with it, so I'm not going to have a decent uptime.

Kernel is not booting at all

Hello,
I tried to build a kernel myself and it just fails to boot. I have UART access (through headphone adapter) and I just get nothing in the serial console.
I have CM 11.0 and I cloned CM's android_kernel_lge_hammerhead repo and checked out stable/cm-11.0 with hammerhead_defconfig.
I used google's arm-eabi-4.8 precompiled toolchain.
To boot:
Code:
ttouch android_kernel_lge_hammerhead> sudo fastboot boot arch/arm/boot/zImage-dtb
creating boot image...
creating boot image - 8583168 bytes
downloading 'boot.img'...
OKAY [ 0.375s]
booting...
OKAY [ 0.123s]
finished. total time: 0.498s
Here is what I get in UART:
Code:
welcome to hammerhead bootloader
[10] Power on reason 81
[10] DDR: elpida
[90] Loaded IMGDATA at 0x11000000
[90] Display Init: Start
[170] MDP GDSC already enabled
[170] bpp 24
[210] Config MIPI_CMD_PANEL.
[210] display panel: ORISE
[210] display panel: Default setting
[340] Turn on MIPI_CMD_PANEL.
[390] Display Init: Done
[390] cable type from shared memory: 8
[390] vibe
[590] USB init ept @ 0xf957000
[610] secured device: 1
[610] fastboot_init()
[660] splash: fastboot_op
FASTBOOT MODE
PRODUCT_NAME - hammerhead
VARIANT - hammerhead D821(E) 16GB
HW VERSION - rev_11
BOOTLOADER VERSION - HHZ11k
BASEBAND VERSION - M8974A-2.0.50.1.16
CARRIER INFO - None
SERIAL NUMBER - <blablablabla>
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked
[770] splash: start
[1260] splash: bootloader
[1260] Fastboot mode started
[1260] udc_start()
�����l[60660] -- reset --
[60660] -- portchange --
[60820] -- reset --
[60820] -- portchange --
[60990] fastboot: processing commands
��[112660] fastboot: download:0082f800
downloading...
[113140] fastboot: boot
[113150] Found Appeneded Flattened Device tree
[113150] DTB: platform id 126, board id 150, soc rev 20002, board rev 11
[113160] get_display_kcal = 0, 0, 0, x
[113200] vibe
[113300] splash: boot
[113340] splash: unlocked
[113380] cmdline: uart_console=enable lcd_maker_id=primary lge.hreset=off lge.reset=unknown gpt=enable lge.kcal=0|0|0|x lge.rev=rev_11 androidboot.laf androidboot.emmc=true fastboot=true androidboot.serialno=<blablablabla> androidboot.bootloader=HHZ11k androidb[113400] Updating device tree: start
[113420] Updating device tree: done
[113420] booting linux @ 0x10008000, ramdisk @ 0x11000000 (0), tags/device tree @ 0x10000100
[113430] Turn off MIPI_CMD_PANEL.
[113430] Continuous splash enabled, keeping panel alive.
[113430] undefined abort, halting
[113430] r0 0x00000000 r1 0x00000000 r2 0x10000100 r3 0x003996e3
[113430] r4 0x10008000 r5 0x0f92607a r6 0x0f925d5b r7 0x0f925f89
[113430] r8 0x0f955652 r9 0x0f9556c7 r10 0x00000001 r11 0x10000100
[113430] r12 0x20000193 usp 0x00000000 ulr 0x00000000 pc 0x1000800c
[113430] spsr 0x40000193

I've never installed a kernel like that (via fastboot) and I had to look up the headphone UART adapter thing.
I don't have much to offer. I always use mkbootimg to link my kernel and ramdisk, then flash it via fastboot. Looking at your serial dump, the only thing I see is that the base, ramdisk, and tags offsets look completely different from the ones I use with mkbootimg.
BASE=0x00000000
PAGESIZE=2048
RAMDISK_OFFSET=0x02900000
TAGS_OFFSET=0x02700000
I'm playing around with my breadboard and an FTDI USB<-->Serial board I have to try and make a working serial console and I'll see what my N5 dumps.

Gene Poole said:
I've never installed a kernel like that (via fastboot) and I had to look up the headphone UART adapter thing.
I don't have much to offer. I always use mkbootimg to link my kernel and ramdisk, then flash it via fastboot. Looking at your serial dump, the only thing I see is that the base, ramdisk, and tags offsets look completely different from the ones I use with mkbootimg.
BASE=0x00000000
PAGESIZE=2048
RAMDISK_OFFSET=0x02900000
TAGS_OFFSET=0x02700000
Click to expand...
Click to collapse
Thanks, I'll try that.
Gene Poole said:
I'm playing around with my breadboard and an FTDI USB<-->Serial board I have to try and make a working serial console and I'll see what my N5 dumps.
Click to expand...
Click to collapse
I guess you're trying to build the N4 cable, but it does not work.
For the N5 to work you need to supply 3V3 and not 1V8 to the VCC
The RX though (serial input to the N5) should be 1V8 (done with a simple voltage divider, try 1K and 1.2K to GND) or there is a chance that you'll fry your serial.

Yeah, my search showed that the N5 version needed no resistors, but I used some anyway just to shunt some voltage. It worked. I got a dump and it does appear that your offsets are not right. Here's my dump up to the kernel taking over:
Code:
welcome to hammerhead bootloader
[10] Power on reason 80
[10] DDR: hynix
[90] Loaded IMGDATA at 0x11000000
[90] Display Init: Start
[170] MDP GDSC already enabled
[170] bpp 24
[210] Config MIPI_CMD_PANEL.
[210] display panel: ORISE
[260] Found Appeneded Flattened Device tree
[260] DTB: platform id 126, board id 150, soc rev 20002, board rev 11
[300] Set panel ON cmds [35]
[420] Turn on MIPI_CMD_PANEL.
[470] Display Init: Done
[470] cable type from shared memory: 8
[470] reboot_mode restart reason = power_on
[520] vibe
[620] splash: boot
[660] splash: unlocked
[700] use_signed_kernel=0, is_unlocked=1, is_tampered=0.
[700] Loading boot image (9226240): start
[1030] Loading boot image (9226240): done
[1030] Found Appeneded Flattened Device tree
[1040] DTB: platform id 126, board id 150, soc rev 20002, board rev 11
[1040] get_display_kcal = 0, 0, 0, x
[1050]
Booting Linux
[1050] cmdline: console=ttyHSL0,115200,n8 androidboot.hardware=hammerhead user_debug=31 maxcpus=2 msm_watchdog_v2.enable=1 selinuxt
[1090] Updating device tree: done
[1090] booting linux @ 0x8000, ramdisk @ 0x2900000 (714802), tags/device tree @ 0x2700000
[1100] Turn off MIPI_CMD_PANEL.
[1100] Continuous splash enabled, keeping panel alive.
[ 0.000000] Booting Linux on physical CPU 0
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.4.0-hoxnet-gd745771 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #7 SMP PREE5
[ 0.000000] CPU: ARMv7 Processor [512f06f0] revision 0 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
...
I see a fastboot option, -b, for specifying the kernel base address. Try with -b 0x8000.
Edit: maybe it's -b 0. looks like the address gets 0x8000 added by default.

Gene Poole said:
Yeah, my search showed that the N5 version needed no resistors, but I used some anyway just to shunt some voltage. It worked. I got a dump and it does appear that your offsets are not right. Here's my dump up to the kernel taking over:
Code:
welcome to hammerhead bootloader
[10] Power on reason 80
[10] DDR: hynix
[90] Loaded IMGDATA at 0x11000000
[90] Display Init: Start
[170] MDP GDSC already enabled
[170] bpp 24
[210] Config MIPI_CMD_PANEL.
[210] display panel: ORISE
[260] Found Appeneded Flattened Device tree
[260] DTB: platform id 126, board id 150, soc rev 20002, board rev 11
[300] Set panel ON cmds [35]
[420] Turn on MIPI_CMD_PANEL.
[470] Display Init: Done
[470] cable type from shared memory: 8
[470] reboot_mode restart reason = power_on
[520] vibe
[620] splash: boot
[660] splash: unlocked
[700] use_signed_kernel=0, is_unlocked=1, is_tampered=0.
[700] Loading boot image (9226240): start
[1030] Loading boot image (9226240): done
[1030] Found Appeneded Flattened Device tree
[1040] DTB: platform id 126, board id 150, soc rev 20002, board rev 11
[1040] get_display_kcal = 0, 0, 0, x
[1050]
Booting Linux
[1050] cmdline: console=ttyHSL0,115200,n8 androidboot.hardware=hammerhead user_debug=31 maxcpus=2 msm_watchdog_v2.enable=1 selinuxt
[1090] Updating device tree: done
[1090] booting linux @ 0x8000, ramdisk @ 0x2900000 (714802), tags/device tree @ 0x2700000
[1100] Turn off MIPI_CMD_PANEL.
[1100] Continuous splash enabled, keeping panel alive.
[ 0.000000] Booting Linux on physical CPU 0
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.4.0-hoxnet-gd745771 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #7 SMP PREE5
[ 0.000000] CPU: ARMv7 Processor [512f06f0] revision 0 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
...
I see a fastboot option, -b, for specifying the kernel base address. Try with -b 0x8000.
Edit: maybe it's -b 0. looks like the address gets 0x8000 added by default.
Click to expand...
Click to collapse
Didn't work.
I also tried to build a boot.img, I flashed it (just to be sure) and I get all the same results.
My tags/device tree is different and I don't know how to change it. There is no available option in fastboot or mkbootimg

ttouch said:
Didn't work.
I also tried to build a boot.img, I flashed it (just to be sure) and I get all the same results.
My tags/device tree is different and I don't know how to change it. There is no available option in fastboot or mkbootimg
Click to expand...
Click to collapse
mkbootimg has an undocumented --tags_offset option. I don't know why it doesn't show up in the --help. I found it in the source for mkbootimg (in the AOSP tree) when I first ran the unpackbootimg and noticed that it dumped text files containing info about the offsets.
I have a shell script I use to make boot images. Here it is:
Code:
#!/bin/sh
RAMDISK=ramdisk
KERNEL=zImage
BASE=0x00000000
PAGESIZE=2048
RAMDISK_OFFSET=0x02900000
TAGS_OFFSET=0x02700000
CMDLINE="console=ttyHSL0,115200,n8 androidboot.hardware=hammerhead user_debug=31 maxcpus=2 msm_watchdog_v2.enable=1 selinux=1"
echo Making ramdisk image ...
(cd ${RAMDISK} ; mkbootfs . | gzip -9c > ../${RAMDISK}.cpio.gz )
echo Making boot image ...
mkbootimg --kernel ${KERNEL} --ramdisk ${RAMDISK}.cpio.gz --cmdline "${CMDLINE}" -o boot.img --base ${BASE} --pagesize ${PAGESIZE} --ramdisk_offset ${RAMDISK_OFFSET} --tags_offset ${TAGS_OFFSET}
"ramdisk" is a directory containing the unpacked AOSP stock ramdisk (plus my modifications). These offset values were obtained from unpackbootimg executable but I can't remember where I found the source. I'll send you a copy if you want it.

Gene Poole said:
mkbootimg has an undocumented --tags_offset option. I don't know why it doesn't show up in the --help. I found it in the source for mkbootimg (in the AOSP tree) when I first ran the unpackbootimg and noticed that it dumped text files containing info about the offsets.
I have a shell script I use to make boot images. Here it is:
Code:
#!/bin/sh
RAMDISK=ramdisk
KERNEL=zImage
BASE=0x00000000
PAGESIZE=2048
RAMDISK_OFFSET=0x02900000
TAGS_OFFSET=0x02700000
CMDLINE="console=ttyHSL0,115200,n8 androidboot.hardware=hammerhead user_debug=31 maxcpus=2 msm_watchdog_v2.enable=1 selinux=1"
echo Making ramdisk image ...
(cd ${RAMDISK} ; mkbootfs . | gzip -9c > ../${RAMDISK}.cpio.gz )
echo Making boot image ...
mkbootimg --kernel ${KERNEL} --ramdisk ${RAMDISK}.cpio.gz --cmdline "${CMDLINE}" -o boot.img --base ${BASE} --pagesize ${PAGESIZE} --ramdisk_offset ${RAMDISK_OFFSET} --tags_offset ${TAGS_OFFSET}
"ramdisk" is a directory containing the unpacked AOSP stock ramdisk (plus my modifications). These offset values were obtained from unpackbootimg executable but I can't remember where I found the source. I'll send you a copy if you want it.
Click to expand...
Click to collapse
My mkbootimg does not have the tags_offset.
When I try to build the boot image with tags_offset, mkbootimg shows me the help message, which means it got no tags_offset option.
EDIT: Nevermind, I cloned and compiled the latest mkbootimg from here. Trying to boot it now...
EDIT2: IT WORKS!!

Since the AOSP build has to create a boot image, it is included in the utilities. I always use the one native to the build tree. It is in:
[aosp_root]/out/host/linux-x86/bin/mkbootimg
and the source is in:
[aosp_root]/system/core/mkbootimg/