IRC log for #htc-linux on 20090601

00:00.19cr2306.23 MB
00:01.00NetRipperext2 is not flash-friendly
00:01.36tmztI guess you need to read the ce partition table
00:01.48cr2awk '{printf("%.6f\n",306.23*1024*1024)}'
00:01.48cr2321105428.480000
00:01.53tmztI'm trying to figure this out also
00:01.54cr20.48 bytes :)
00:02.32cr2tmzt: what is ce partition table ?
00:02.53cr2tmzt: the oemsbl has 'partition' command
00:02.58tmztdream_kill: can you help us? are you awake
00:03.06cr2is there something like that in appsbl (aka spl) ?
00:03.38tmztwhatever itsutil is using I think is the partiiton table
00:03.41dcordes-kaistmzt you cooking on a bootloader?
00:03.48tmzttrying to
00:04.01tmztI have a basic one that will embed the zImage and replace xip
00:04.10cr2tmzt: i think i've posted the itsutils output
00:04.12dcordes-kaisI have seen you mentioning uboot
00:04.14dcordes-kaiswow
00:04.14tmztyeah
00:04.22tmztI mean where does it get that from
00:04.25cr2dcordes-kais: it's for msm8x50 only
00:04.51cr2which needs cpu register changes
00:04.52tmztmaybe we need to look at itsutils.dll source
00:05.15tmztwell, the spl has to be reading short blocks
00:05.21tmztto get the partition table
00:05.21cr2tmzt: and add to haret ?
00:05.28tmztpossibly
00:05.44tmztbut wouldn't it tell us where in ce the partition table is
00:05.50tmztor in nand or whatever
00:06.13dcordes-kaishow are you working on msm8x50? with qct experimental code?
00:08.06cr2dcordes-kais: somebody has written an uboot patch for msm8x50 dev board
00:08.19cr2458.50M (0x1ca80000) DSK1:
00:08.19cr2|           3.12M (0x31f000) Part00
00:08.31cr2|           4.50M (0x480000) Part01
00:08.31cr2|         143.38M (0x8f60000) Part02
00:08.31cr2|         307.50M (0x13380000) Part03
00:08.51cr2tmzt: 306.23 != 307.50
00:09.05tmztyeah
00:09.14tmztand Part03 is the beginning of tfat?
00:09.22tmztcan you raw dump that point?
00:10.29tmztwhere are you getting 306.23 from?
00:10.48dcordes-kaiscr2 got a link? are the differences between 8* and 7*A known?
00:11.14cr2awk '{print 0x31f000+0x480000+0x8f60000+0x13380000}'
00:11.21cr2480768000
00:11.53cr2dcordes-kais: tmzt posted a link here
00:11.58tmztdecimal?
00:12.03cr2yes
00:12.35tmzthttps://www.codeaurora.org/patches/quic/le/u-boot-2009.03_PATCH_2009_05_14.patch
00:12.43cr2458.496MB
00:12.45tmztit's from qualcomm, some unit of qualcomm
00:13.08tmztthat's the total nand size?
00:13.28tmztyeah, it's utils listed that as well
00:13.34tmztitsutils
00:13.38cr2it's hte itsutils sum of all partitions
00:14.01dcordes-kaisinteresting
00:14.29cr2=0x1ca7f000
00:14.42tmztyeah
00:15.30cr2weird
00:16.49cr2<PROTECTED>
00:16.51cr2<PROTECTED>
00:16.52cr2<PROTECTED>
00:16.54cr2146816 -rw------- 1 root root 150339584 26. Apr 10:24 RAPH02
00:16.55cr2314880 -rw------- 1 root root 322437120 26. Apr 10:41 RAPH03
00:20.29*** join/#htc-linux madCoder- (n=madcoder@c-71-225-60-178.hsd1.pa.comcast.net)
00:21.25cr2hi madCoder-
00:29.46tmztcr2: what debian initrd were you using, an installer one?
00:30.14cr2dcordes-kais compiled
00:30.52cr2initrd-angstrom.cpio.gz
00:30.57tmztoh
00:31.00tmztnot really debian
00:31.06cr2hm. yes
00:31.09tmztbut it shouldn't detect either
00:32.26*** join/#htc-linux maejrep (n=madcoder@c-71-225-60-178.hsd1.pa.comcast.net)
00:34.00cr2hey maejrep.-ETOOMANYNICKS
00:39.23*** join/#htc-linux xsacha (n=sacha@123.100.137.226)
00:39.53xsachaattempting to kill init .. this means that init doesnt run anything after it runs?
00:40.56tmztright, init never exits
00:41.06tmztpaste your init.rc
00:43.52*** join/#htc-linux Perkka (n=perkka@ua-83-227-207-92.cust.bredbandsbolaget.se)
00:45.30xsachamm cant view the ext2 partition.. on windows right now, brb
00:52.21*** join/#htc-linux Perkka (n=perkka@ua-83-227-207-92.cust.bredbandsbolaget.se)
00:52.48*** join/#htc-linux xsacha (n=sacha@123.100.137.226)
00:52.50xsachahttp://pastebin.ca/1442959
00:54.22xsachain the strace, the kernel panic happens just after the config files (default.prop, ashmem (but ashmem doesnt exist)) are looked at
00:54.40xsachai dont see any errors in the config files though
00:55.08xsachaactually, the last thing before the kernel panic is closing default.prop
00:55.52dcordesnote: glue uSD card reader into usb slot with 5 minute epoxy in order to not lose it any longer
00:56.53tmztashmem? what version of android is this?
00:56.56tmztoh right
00:56.58xsacha1.1
00:56.59tmztemulator version
00:57.05xsachayeah
00:57.22xsachait looks for ashmem but doesnt seem to care that it isn't there
00:57.45cr2good night
00:57.50xsachagnite cr2
00:58.00tmztyou don't need panic_on_oops
00:59.39xsachak
01:00.01xsachathat wouldn't be the problem though, right?
01:00.10tmztno
01:00.36tmzthciattach
01:00.39tmztthat could be it
01:00.49tmztcomment out all of that
01:00.49xsachadisable that service?
01:01.53xsachaall that stuff around there is for bluetooth?
01:03.16xsachaare you sure the init.rc gets run?
01:03.29xsachait has some mkdir commands in there but the directories havent been created
01:04.15xsachait creates all the folders in data, but the only thing i have in data in /data/app
01:07.33tmztyeah
01:07.37tmztbut it's not finishing
01:07.46tmztdid you comment out hciattach?
01:07.54xsachayeah, no change
01:08.15xsachado the directories just not get written to the drive because of kernel panic?
01:08.48*** join/#htc-linux zycho (n=zycho@dslb-088-070-073-162.pools.arcor-ip.net)
01:09.54tmztyeah
01:10.04tmztor it didn't get there yet
01:11.05xsachavery last stuff before kernel panic: read(5, "#\n# .....", 93) = 93          close(5) = 0    SIGSEGV (Segmentation Fault) @ 0 (0)
01:13.16xsachacould it be caused by not having the right patches in kernel?
01:15.34xsachamy kernel does have drivers/staging/android by the way (which includes a binder.c -- thing you were talking about?)
01:17.23xsachathere's also drivers/video/pxafb.c and use of pxafb in i780.c, but i guess you meant to patch it?
01:17.30tmztand what is fd 5?
01:17.35tmztyes
01:17.39xsachafd 5 is default.prop
01:17.49tmztthat makes no sense
01:18.01tmztit's after close(5)?
01:18.03xsachayes
01:18.04*** join/#htc-linux paulproteus (i=paulprot@2002:db69:2513:0:0:0:0:1)
01:18.05tmztplease paste it
01:18.21xsachamm it doesnt save to file (cause of the kernel panic).. ill write it out though
01:18.28*** join/#htc-linux zycho_ (n=zycho@dslb-088-070-073-162.pools.arcor-ip.net)
01:18.29tmztoh, that doesn't really mean anything
01:18.43tmztok, just give me the last lines
01:19.40xsachaopen("/dev/ashmem", O_RDWRIO_LARGEFILE) = -1 ENOENT (No such file or directory)
01:19.58xsachaopen("/default.prop", O_RDONLYIO_LARGEFILE) = 5
01:20.09xsachalseek(4, 0, SEEK_END) = 93
01:20.09tmztxsacha: we need to move to the android generic kernel tree
01:20.21xsacha5 not 4!
01:20.22tmztor find a current copy of the patch
01:20.24tmzthold on
01:20.32xsachalseek(5, 0, SEEK_SET) = 0
01:21.06xsacharead(5, "#\n# ADDITIONAL_DEFAULT_PROPERTIE"..., 93) = 93
01:21.11xsachaclose(5) = 0
01:21.21xsacha--- SIGSEGV .............
01:23.27tmztit still shouldn't be segfaulting
01:24.44xsachathere's no way any of that stuff before the segfault could cause it right?
01:25.06xsachais strace unable to show the line it crashes on?
01:25.28tmztno, you would have to gdb
01:25.46tmztI think it will be easier to add your board to android generic
01:26.29xsachaok... i dont know where melgurth got this base kernel.. are you sure it isn't already android generic?
01:27.43tmztdoes it have drivers/android?
01:27.46xsachayes
01:27.51tmztthen it is
01:28.01tmztwhat defconfig are you using?
01:28.02xsachadrivers/staging/android with heaps of stuff
01:29.14xsachamm i dont have a defconfig.. ?
01:29.21tmztxsacha: are you in #android?
01:29.24xsachano
01:29.33xsachanow i am.. is defconfig the same as .config?
01:30.07tmztI don't see you
01:30.19xsachaoops, i clicked on the one with question mark :P
01:30.30tmztdefconfig is not the same, it just gets copied to .config
01:30.50xsachathis is my .config http://pastebin.ca/1443005
01:30.56xsachamy Kconfig generates
01:33.25tmztnone of the android stuff is enabled though
01:34.12xsachaoh ok
01:34.13*** part/#htc-linux tre9 (n=ubuntu@lepke.dreamhost.com)
01:36.30xsachathere's no option in my Kconfig for android
01:37.28tmztso you don't have the right kernel
01:37.35tmztI don't what melgurth is using
01:37.47xsachaweird :( wrong config but has android drivers
01:38.24xsachaohh is this the defconfig?
01:38.26xsachaarch/arm/configs/msm_defconfig:CONFIG_ANDROID_LOGGER=y
01:38.54tmztgit://android.git.kernel.org/kernel/common.git
01:39.26xsachaonly the msm one has android in it though
01:39.27tmztI think you have an upstream kernel with some of the commits made for android, but not the recent ones
01:39.43tmztcommon should have it
01:40.08xsachawell ill check out this android kernel then
01:40.54xsachaslow net.. 400KB/s, will take some time
01:41.29xsacha300MB kernel? gee
01:41.38xsachabrb
01:42.47tmztdo you have local git tree checked out?
01:50.37tmztxsacha: git clone --reference /local/git/tree git://android.git.kernel.org/kernel/common.git
01:54.42xsachahould i cancel my d/l and do that one?
01:57.33tmztyeah
01:57.38tmztdo that in a new directory
01:57.43xsachawell my d/l already finished..
01:57.47tmztoh
01:57.50tmztthen don't
01:58.05tmztwait, 400kb/s is slow?
01:58.28xsachayeah said it'd take like 10 minutes!
01:58.43xsachamore, i think like 15
02:00.03xsachagonna take more than 15 minutes to resolve deltas/patches tho
02:00.12*** join/#htc-linux Guest85947 (n=fnord@24-151-90-116.static.nwtn.ct.charter.com)
02:08.55xsacha80%
02:13.58*** join/#htc-linux xsacha2 (n=sacha@123.100.137.226)
02:14.23xsacha2[12:10] <xsacha> ok well i have to go now and hand in an assignment...
02:14.25xsacha2[12:10] <xsacha> so basically i add i780 machine to this generic android kernel?
02:14.26xsacha2[12:10] <xsacha> do i have to do anything special in setting up the defconfig/Kconfig?
02:15.06tmztdo what you did yesterday
02:15.09tmztcopy your board
02:15.16tmztadd to mach-types
02:15.19xsacha2im just wondering about config
02:15.20tmztadd to Kconfig and Makefile
02:15.23tmztthat's all
02:15.28xsacha2so config is good to go?
02:15.33tmztafter you pull you need to
02:15.41tmztgit checkout android-2.6.27
02:15.45tmztor 29 if you want
02:16.49tmztI don't see any defconfig that will work for you
02:16.56xsacha2me either :(
02:17.02tmztthe relevant ptions are in msm_defconfig
02:17.03xsacha2no pxa3xx
02:17.07xsacha2ok
02:17.14tmztCONFIG_BINDER
02:17.18xsacha2so just copy android options from msm..?
02:17.23tmztCONFIG_ASHMEM
02:17.25tmztyes
02:17.33tmztbut not CONFIG_MSM options
02:17.35xsacha2alright
02:17.38xsacha2thx
02:17.44xsacha2cya :)
02:20.13dcordesbye
02:41.53*** join/#htc-linux WyrM (n=wyrm@20158169087.user.veloxzone.com.br)
03:05.14*** part/#htc-linux WyrM (n=wyrm@20158169087.user.veloxzone.com.br)
03:08.23*** join/#htc-linux mrmoku|a` (n=mrmoku@ppp-93-104-100-134.dynamic.mnet-online.de)
03:21.25*** join/#htc-linux mint (n=mint@adsl-99-38-14-63.dsl.rcsntx.sbcglobal.net)
03:25.40*** join/#htc-linux ljp (n=lpotter@218.185.108.156)
03:31.13javaheadseems to be a quiet room...
03:36.22javaheadjust followed the kernel building instructions and got android up and running on my kaiser.
03:37.24javaheadthank you XDA Contributors!
03:56.53javaheadanyways.  interesting in contributing sometime in the future.  will contact via email instead.
03:59.14tmzthey
03:59.29tmztjavahead: it's quiet right now
03:59.38tmztjavahead: logs are at irclog.netripper.com
04:07.20*** join/#htc-linux DJW|Home (i=djwillis@82-46-19-72.cable.ubr02.bath.blueyonder.co.uk)
04:08.00parinfidel206: is you usb device working on the ba?
04:11.08tmztNetRipper: hey, do you know why usb would stop working on raph500?
04:11.13tmztwith current kernel
04:14.27partmzt what kernel vers
04:15.22tmzt41d96b6e5515092288494212b822eb0ab73a39ba
04:15.31tmztthis is for touch pro though
04:15.39tmzthave you tried the lastest kernel on vogue?
04:16.00parnah i haven't startd anything on vogues
04:16.17pari'm runnin android vers 1.1 thats about it
04:16.28tmztyeah, which kernel though?
04:16.37tmztdoes usbnet work at all
04:18.08pari never use it, i just run android
04:19.17*** join/#htc-linux goxboxlive (n=goxboxli@237.80-202-137.nextgentel.com)
04:20.59par2.6.25-00777-gd41a387
04:24.52tmztthere was a report that it was broken on htc-vogue as well
04:25.02tmztwith the lastest kernel on htcandroid site
04:25.34paroh in 1.5 yes
04:25.53parwell at least ithink that was part of the problem
04:26.12parunsure, you follow that kernel much more than i do, so ;)
04:28.11parright now i'm jsut trying to get maximum functionality out of the ba...on whatever kernel version i can do that
04:29.10parhave you played around with tvout on your pro/
04:29.15tmztno
04:29.24tmztwhen it has kernel support I will try it
04:29.31parneeat
04:29.35tmztI could use no2chem's but I haven't yet
04:29.58parsoemday someone will probably be using those as a ultrapc
04:30.02tmztas for ba, pH5's work should apply there, there's little chance of hh20 improving much
04:30.32paryeah, i'm thinking pH5's shelving the old processors.. dunno tho
04:31.20tmztba because it has gsm, or because it has keyboard?
04:31.26tmztI don't think so
04:31.43tmztif anything he's picked them up to get asic3_mmc working
04:31.56tmztit's basically the last things for uni, ba, etc.
04:32.16tmztit should be possible to carry them forward with much less effort now
04:38.26paryeah i've been watching very closely his progess on it
04:39.03par(because he was working on sable's asic3_mmc)
04:39.29*** join/#htc-linux TeringTuby (n=Maarten@195-241-125-243.ip.telfort.nl)
04:39.37pari'd be happy with a ba that ran 2.6.30 and all devices working
04:40.14parthen it gives the device much more value due to the hostapd / access point use of it.
04:41.19parat this point the acx100 only does wep.. but any wireless even with wep where i can use a cellphone as access point all over the world is a huge advantage
04:42.23parits becomes a very available device and there are is plenty of part availability for it
04:42.25tmztieee80211 can do wpa or whatever in software with the right driver
04:43.50parwhen you can be in the jungle and become an AP for an entire classroom over gprs thats really something poweful
04:44.20parespecially when under examination the phone would only appear to be a normal local carrier phone running windows ce
04:46.14pari may throw the firmware on this lenny image and see if i can bring up the acx
04:46.38parits rough because all input is throught he built in keyboard until i get connectivity
04:47.15parbut i can add things into the image from my box as needed , like the firmware
04:47.49parand its running a dropbear ssh server on boot so it should be ok once i have the wlan
04:48.17*** join/#htc-linux droid0011 (n=mc@p4FDCF170.dip.t-dialin.net)
04:48.55paras it is right now i'm sure adhoc networking will work
04:49.12parbut it would be nice to be an AP
04:52.12parthe real winner several years from now will be the touch pro
04:52.20parwith its tvout ;)
04:54.17tmztyou don't need AP or adhoc to do that from one computer though
04:54.24tmztyou can use usb networking and iptables
05:01.53partrue, but that tends to be visually obvious and has no mystery to it ;)
05:04.01*** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz)
05:05.03parexpecially in places where if people see it, man its probabl gonna disappear real quick in someones bag :-)
05:05.53paror in even more severe cases where its simply not allowed
05:08.13pari've been to schools in asia where for lack of internet connectivity because of exhorbitant fees .. none of the machines ever get updated or patched.. so everything is rampant with viruses and hardly works when the kids go to use the 2 or 3 computers the the entire school has.
05:11.47parand those are the two or three computers in the locked places that have already weathered theft and vandalism...
05:12.22parschool mostly is free, but machinery for sale means profit for food.
05:13.04*** join/#htc-linux dream_kill (n=nospam@89.131.127.37) [NETSPLIT VICTIM]
05:13.04*** join/#htc-linux nizox (n=none@eros.ph0k.eu) [NETSPLIT VICTIM]
05:13.04*** join/#htc-linux nrirclog (n=nrirclog@netripper.com) [NETSPLIT VICTIM]
05:13.47*** join/#htc-linux NetRipper (n=netrippe@netripper.nl)
05:14.04para girl i dated there was robbed at gunpoint on the street for her cellphone
05:14.52parso, its a place i don't even flash around a ba running windows 2k3
05:15.35tmztNetRipper: you here?
05:39.02parhmm gives a hotplug error but lenny is runnign udev which hotplug is deprecated by udev so... confusing
05:39.22pari'll just try throwing it in /lib/firmware
06:07.20*** join/#htc-linux WeinerWagon (n=laray@cpe-67-244-58-190.twcny.res.rr.com)
06:15.58*** join/#htc-linux furtardo (n=mks@nat/yahoo/x-78239c194d24b406)
06:20.46*** join/#htc-linux furtardo (n=mks@nat/yahoo/x-94b61178424d64f9)
06:46.46*** join/#htc-linux kiozen (n=oeichler@p5492151D.dip0.t-ipconnect.de)
06:57.31*** join/#htc-linux Echo31 (n=olivier@mir31-4-82-240-194-54.fbx.proxad.net)
07:30.35*** join/#htc-linux xsacha (n=xsacha@124-171-136-151.dyn.iinet.net.au)
07:31.08parhmm well its 397.31 bogomips
07:31.21parnot bad for an old paperweight
07:32.17xsachahey i checked for service manual and turns out heaps of stuff on xda wiki: http://wiki.xda-developers.com/index.php?pagename=Samsung_i780
07:32.43xsachaimportantly, there is a service manual.. reading it now
07:34.58parcool
07:35.20xsachaHOLY *****
07:37.08xsachadoes every service manual contain a pic like this? http://img269.imageshack.us/img269/1849/capturexdd.png
07:38.16parneat
07:39.43xsachasweet, a huge list of parts!
07:40.39xsachaQME03 Unit touch panel GH59-04930A   <-- touchscreen for tmzt
07:44.38xsacha4709-001544 <-- bluetooth and 4709-001527 <-- wifi  SEC codes
07:59.11xsachawhat good is the SEC code? how do i find out manufacturer?
08:20.34xsachaSamsung Electronics Corporation? :(
08:22.49xsachaSamsung linux kernel? http://opensrc.sec.samsung.com/
09:11.10*** join/#htc-linux zycho (n=zycho@dslb-088-070-073-162.pools.arcor-ip.net)
09:11.38*** join/#htc-linux wippeout (n=wippeout@unaffiliated/wippeout)
09:11.41wippeouthello
09:12.00wippeoutis there a way to port htc sapphire rom on htc blackstone ?
09:12.31wippeoutit seems that the both devices have the same hardware
09:12.51parwhat "rom" are you talking about
09:13.05wippeoutthe android rom of the htc sapphire
09:13.14paroh android?
09:13.28pari think someone is already working on blackstone
09:14.09wippeoutthere is no news since 2009/03/10 on the blackstone wiki
09:14.12wippeoutabout android
09:15.23xsachaif they have the same hardware and could get a complete dump, couldnt you just flash that on to blackstone?
09:15.27xsachaneed jtag right?
09:15.54pari don't know anyone here who's every used jtag for an htc device
09:16.17par(so probably not)
09:17.12xsachasomeone was on here yesterday
09:17.18paryeah, thats depressing that no one has worked on reverse engineering it since 03/01/2009
09:17.29xsachathey had jtag for diamond or something
09:17.37paroh neat
09:17.39xsachaand they flashed their g1 with it? or was it other way around
09:17.47xsachacan check yesterdays logs
09:18.15parhere its pretty much haret and reverse engineering
09:19.56xsacha"dream_kill flashed diamond dump in a g1 :P "
09:20.57paroh, he was just here then
09:21.15parseveral hours ago
09:21.49parthey don't have exactly the same hardware though
09:23.04parwow getting this lenny distribution of armel to work with the old hh20 kernel is a real PITA
09:23.28wippeoutok thanks bye
09:23.32parinfidel206: i hope you made an image of the setup you did so far :)
09:23.51pari got the acx kmod loading but no interface
09:25.30parmissing all kinds of stuff that has to be moved over from the angstrom rootfs
09:26.27parxsacha: what phone are you working on?
09:31.13*** join/#htc-linux marex (n=marex@eduroamgw.prf.cuni.cz)
09:31.17xsachai780
09:31.31xsachai have lenny working fine on it
09:38.49paryep, i'm sure
09:38.59parwhat kernel are you running
09:40.59dream_killhi guys
09:41.37dream_killif u need a full dump from sapphire i can give u one
09:41.41dream_killfull nand dump
09:41.54dream_killso i need someone brave to flash it in the blackstone :P
09:41.58xsacham running one from handhelds.org
09:42.06xsachabut need to switch to generic android one now
09:42.35dream_killur device is security unlocked?
09:43.05paryou mean hardspl?
09:43.14dream_killnope i mean security unlocked :P
09:43.21paras in?
09:43.22dream_killwhen in spl it will show security unlocked :P
09:43.55parso what rom did you dump?
09:44.08parinto the g1
09:44.09dream_killfull nand :P
09:44.30dream_killfrom address 0 till 100000000
09:44.32dream_kill:D
09:44.35paryou don't need jtag to do that
09:44.46dream_killif security unlock no need :P
09:44.57dream_killif security locked then u can use jtag :P
09:45.18parhow much of it functioned when you dumped it into another device
09:45.29dream_killif security unlock then go in oemsbl and use pdump to read the nand
09:45.35dream_killand rwfactory to write it back
09:45.57dream_killnot had to much time to play with it. I flashed diamond rom in the g1
09:46.00dream_killamss started
09:46.10dream_killbut had no image on screen
09:46.13parwhat all worked i the g1?
09:46.25parwell yeah, its different hardware mang
09:46.26dream_killso think was screen parameters wrong
09:46.37dream_killneed to connect jtag on the g1 again and do more tests
09:46.44dream_killbut this days a bit busy with day job :P
09:47.00paruh, but you know that its different hardware
09:47.10parare you just trying to see what needs to be changed
09:47.23dream_killis a bit different yes
09:47.30paryes, like they all are
09:47.58dream_killjust a bit as i said :P
09:48.02dream_killbut
09:48.18dream_killas u said, blackstone = sapphire and topaz = hero
09:48.20pari mean sure we do the same thing but its usually to see how far the image gets
09:48.29parand then work on what needs to be changed to bring it up
09:48.50dream_killin the htc partition and mfg partition seems to be the screen setup
09:49.00parand i'm not a kernel programmer btw :)
09:49.09dream_killso theory, if i keep them same from the original device
09:49.14dream_killit should work
09:50.21parhow will you keep the screen from the regular device apart from your dump from another?
09:50.42parand why would they work together?
09:50.58parespecially if the main dump is looking for something different
09:55.33parif you are just copying parts of nand
09:55.46parwhy wouldn't xda-developers already have done that?
09:56.13*** join/#htc-linux pH5 (n=ph5@p5485C9A6.dip.t-dialin.net)
09:56.23parhi pH5
09:56.31pH5morning
09:56.44NetRippertmzt, am now
09:57.18dream_killpar: who does it before like so ? never seen it :P
09:58.35pardream_kill: more power to you if you have a way to get android working simply by copying parts of nand from one device and leaving the screen portion in nand for another device in place while dumping the portion of nand from the other device.
10:00.00parwhat mfg stuff do you have that you can slice it up that way?
10:00.26dream_killkeep the MFG part intatct i said
10:00.42dream_killas in MFG u have screen tunning, wifi, and bluetooth
10:01.57parwell, show us the easy way then
10:02.24dream_killif u have ur device security unlock and wana test let me know :P
10:02.41paryeah i have a security unlocked device
10:02.59paryou ain't using it for a jtag guinea pig tho
10:03.33parif you are simply slicing up the nand..
10:03.44paryou just need all the rom dumps
10:04.33pari think you're loony tho
10:04.56dream_killok, flash a mfg spl first
10:05.12dream_killso we dump ur rom in full:P
10:05.13parand then flash a portion after?
10:05.29dream_killif is security unlock we do the safe parts only
10:05.45pardesribe the "Safe parts"
10:05.59dream_killu made urself a serial cable ?
10:06.13parregaardless it doesn't matter i can probably bring the phone back from anything that could be done to it.. since spl isn't a problem
10:06.50pari don't use a serial cable i use the boot loader
10:06.56parand usb
10:06.56dream_killif u have serial cable u can access the OEMSBL even if the SPL is dead
10:07.17dream_killHAVING access to oemsbl we can reflash SPL any time
10:07.19dream_killso
10:07.30dream_killYOU need a SERIAL CABLE
10:07.50dream_killfirst we will flash 2400000 till 24c0000
10:07.55dream_kill(SPL portion)
10:08.23dream_killif all ok it should start up the device with Android spl and then we can flash the rest
10:08.37dream_killif not ok, ,using the serial cable we can flash back the SPL from original
10:08.45dream_killthis is the safe part
10:09.12parsure, ok but you are talking about flashing a newer version of android from an entirely different phone with different hardware
10:09.27dream_killif wana play more dangerous, then from ur dump i extract the HTC partiton and MFG, and then i make u a sapphire full nand and then we can flash it that
10:09.35dream_killbut if this fail u need a jtag to bring it back
10:09.51parwhy would i want a sapphire full nand in my vogue nand?
10:09.54parwhy ever?
10:09.55dream_killi mean flashing ONLY SPL in first case
10:10.06dream_killa SPL which HAS blackstone support inside
10:10.44parregardless of whether its for that version of android or not ?
10:10.46dream_killur device is BLACKSTONE or vogue?
10:10.52pari have vogue...
10:11.03parthere was a guy here before with a blackstone
10:11.24dream_killi was talking about blacksone as i saw references in the HBOOT from android for it!
10:11.34dream_killnot seen anything about vouge inside
10:11.38dream_killso not sure about it
10:11.48*** join/#htc-linux zycho_ (n=zycho@dslb-088-070-073-162.pools.arcor-ip.net)
10:12.07parso you are talking about grabbing spl's from all the different htc devices
10:12.36parand then flashing android from any device along with the spl for the specific device
10:12.49dream_killlet me explain
10:13.06dream_killdevice starts radio then it loads the SPL which loads the OS
10:13.24dream_killthe spl from the wince devices is different from the devices with android on it
10:13.57dream_killsince the android SPL (they rename it to HBOOT) is kinda universal for the HTC android devices
10:14.26dream_killidea is to flash it in the wince devices, and from there flash the rest part of the OS (BOOT.img, system.img)
10:14.49dream_killand then the device should boot up android without need to go in wince
10:14.55*** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo)
10:15.19parhahhaah
10:15.22parahahahaha
10:15.31dream_killso that was the idea
10:15.50parnah, there's several bootloaders being written for it
10:15.57parwince is nothing to do with it
10:16.17parits just an easy reference for reverse engineering
10:16.20dream_killdo something else
10:16.39dream_killsoft spl the hboot 1.33.2005
10:16.46dream_killsee if it starts on ur device
10:17.20parbut i have a device that was never made to run linux
10:17.57dream_killvogue = kaiser yes :P ?
10:18.21pari have a blueangel
10:18.32parand in fact it was the first port of android
10:18.45dream_killnow u said u have a vouge now blueangel ...
10:18.53paryeah, i have lots of htc phones
10:18.56dream_killneed a device which has MSM7200A as cpu
10:19.06paryes
10:19.10dream_killthis is for devices with CPU MSM7200A
10:19.22parmy android runs on pxa25x
10:19.23dream_killit will not work on INTEL devives or other cpu
10:19.30parhahaahah
10:19.44parpxa?
10:19.54dream_killman, what i tryed to explain was the experiment for this devices with cpu MSM7200A
10:20.10paryes yes i know, i understand what you mean ompletely
10:20.16dream_killso for sure it will NOT work in PXA devices
10:20.41*** join/#htc-linux DJW|Home (i=djwillis@82-46-19-72.cable.ubr02.bath.blueyonder.co.uk)
10:21.07par2400000 till 24c0000
10:21.15parthats all we ever need right?
10:21.46dream_killtheoretical, but, i seen the amss also have some references to android
10:21.56dream_killso might need to flash full radio too
10:21.58dream_killfirst
10:22.01dream_killon ur voogue
10:22.06parjust copy that memory address out to another nand with the same hardware and gank everything else but that from any other htc device in msm7200 class
10:22.56dream_killbasicly replace the spl ..24000000 till 24c0000 is the spl area in nand
10:23.12paralready flashed to the latest radio.. even never released for my vogue
10:23.33dream_killbut, this might not be enough. i said as a first experiment which is safe since ur radio is security unlocked
10:23.52dream_killdid u flashed android radio ?
10:23.57pari think thts pretty much insane
10:24.10parspl isn't a seperate area like radio
10:24.20paror extended rom
10:24.24paris it?
10:24.27dream_kill:D
10:24.29dream_killyes it is
10:24.34dream_killso u have nand chip
10:24.46dream_kill0 -24000000 is radio part + some htc partitions
10:24.56dream_kill24000000-24c0000 is SPL
10:25.06parok
10:25.10dream_kill24c0000 - 25000000 is the MISC-MFG partition
10:25.28dream_kill25000000-2520000 is wlan and mfg partion
10:25.39dream_killafter this is the rom partiton and then extended rom
10:26.32parso what are the locations of nand that you will always copy to other htc phones?
10:27.16dream_killvougue = kaiser???
10:27.22Echo31Hi pH5
10:27.50parno
10:27.55parvogue is vogue
10:27.57parlike elfin
10:28.34pH5hi Echo31
10:28.41dream_killaaa
10:28.58dream_killdifferent qualcom then isnide
10:29.44dream_killmsm7500
10:29.45pardream_kill: ok so what are the locations you would always copy?
10:29.45paryes
10:29.45dream_killit will not work then
10:29.45dream_killsorry
10:29.45parthats ok.. thats why htc-linux is here :)
10:29.45parso it will work for all
10:29.45dream_kill:D
10:30.01dream_killwhich radio did u flshed on it and still worked :P ?
10:30.05dream_killfor what devices :P ?
10:30.19paroh i forget i think i grabbed it from a bell canada
10:30.28parits 1.3.5 soemthing
10:30.39xsachawhats this about? http://opensrc.sec.samsung.com/
10:30.42parits the newest one thats compatible
10:31.24parit also helps me to unlock my carrier block of gps
10:31.31parso i have gps unlocked also.
10:31.59parwhich works pretty well in it actually
10:33.24*** join/#htc-linux zycho_ (n=zycho@dslb-088-070-073-162.pools.arcor-ip.net)
10:35.52Echo31pH5: I tried understand your information about athena gpio. It is not easy.
10:38.09*** join/#htc-linux DJWillis (i=djwillis@82-46-19-72.cable.ubr02.bath.blueyonder.co.uk)
10:42.34pardream_kill:i can understand if its only for msm7200a, then yeah it might work
10:42.59pardream_kill: let me know how it goes
10:43.27parwe have many variants here though
10:43.48pareven 7201 which i dunno wtf that is and how it differs from a regular msm7200a
10:46.18parfor example sapphire is a msm7201a
10:46.54paris that exactly the same as msm7200a?
10:47.46parm vogue is actually about 3/4 inch less screen than a sapphire
10:48.06parits smaller and easier to carry, i actually think i like it better
10:48.17*** join/#htc-linux cr2 (n=cr2@ip-90-187-92-176.web.vodafone.de)
10:48.25pari'm only running android v1.1 though
10:49.17parhi cr2
10:49.55pardream_kill was just saying that he was going to flash a sapphire  nand (except for the spl portion) into a blackstone to see if it would work
10:50.42dream_killpar: seems i talked in vain till now
10:51.01dream_killwhat i said and what u understand :P
10:51.38dream_killi said to flash a full nand WITHOUT MFG and HTC partition into the blackstone
10:51.46dream_killscroll up and READ properly
10:51.51Echo31pH5: What are the first modifications of your magician code for starting (booting) on athena device ? What are the elements that are needed and not needed?
10:51.55*** join/#htc-linux DJWillis (n=djwillis@82-46-19-72.cable.ubr02.bath.blueyonder.co.uk)
10:52.11pardream_kill: ok yes sir. sorry
10:52.19dream_killbut as a fist test to FLASH ONLY SPL part!
10:52.49dream_killso u totaly mixed up :P
10:53.22parthats ok, its sort of anticlimactic for me at my angle anyway
10:53.46*** join/#htc-linux zycho (n=zycho@dslb-088-070-073-162.pools.arcor-ip.net)
10:53.49pH5Echo31: maybe set up w100fb first to see something on the screen, assuming you inherit a properly set up lcd from winmo when booting via haret.
10:53.50pardreamkill
10:54.04par_do the phones ever ship security unlock normally?
10:54.40dream_killonly samples to providers :P
10:54.55parok, thanks i didn't know that
10:55.26parto us in public use, it has been referred to as "hard spl" when the phone is security lock
10:55.36dream_kill2 sec
10:55.43dream_killu don't understand it :P
10:55.46*** join/#htc-linux MethoS- (n=clemens@host-091-097-245-151.ewe-ip-backbone.de)
10:56.21dream_killsecurity unlock means the device is unlocked so user can change CID at his own wish using at@cid command and can unlock the device with ANY unlock code
10:56.24paryeah, i have no idea what the terms are for any of it
10:56.45dream_killHARDSPL is a hacked SPL to allow you to flash ANY singned or unsigned roms
10:56.46parright CID unlocked
10:56.57dream_killCID unlocked is different too
10:57.01parok, i didn't know the terms
10:57.08cr2hi
10:57.36pH5hi cr2
10:57.57dream_killIF on a device CID is set as 00000000 or 11111111 then device is CID unlocked, means can get flashed (without any hacked spl) with any official signed roms from HTC for the same model ID!
10:57.59parsecurity unlock is a known algorithm apparently
10:58.14cr2dream_kill: can you post the output from 'partition' oemsbl command ? i've not soldered the docking station serial pins
10:58.24parbecause i see a guy selling it through email
10:58.48dream_killu can security unlock it not problem via a radio patch :P
10:59.01cr2btw, everything a hacked spl does, can be done in linux. i don't really see any point for a hacked spl.
10:59.04dream_killcr2 what devices u need?
10:59.24cr2dream_kill: raph100 will be the best. but diam is ok too.
10:59.38cr2diam with 512MB nand
10:59.53tmzthey, git is broken for me
11:00.03tmztsmd1 and usb
11:00.10dream_killi don't have a diamond, got a raphael. The diamond dump i have it from someone :P
11:00.18dream_killmine is raph600!
11:00.21tmztI have been trying to regress and bisect all night
11:00.28cr2dream_kill: ok. i have raph100
11:01.03tmztAstainHellbring: here?
11:01.04*** join/#htc-linux StarLite (n=nnscript@s55916ca6.adsl.wanadoo.nl)
11:01.07cr2tmzt: i have glued all partitions dumped with itsutils into one image. it looks reasonable.
11:01.30tmztah, looking into partition stuff stilk
11:01.36cr2tmzt: the evildoers store wince dmesg into "unused" nand area before the imgfs
11:01.45tmztfound an interesting post from cmonex
11:02.10parheh, use most itsutils for forensics ;)
11:02.14tmztabout finding imfs offset
11:02.15cr2tmzt: maybe i should edit the wiki and add this data too.
11:02.45cr2par: it should be visible in linux too.
11:02.53paryep
11:03.09tmztgood, I would like to get proper and current documentation on flash - nbh - and nand image formats
11:03.43cr2tmzt: write one yourself in wiki
11:04.11tmzthttp://www.diypda.com/redirect.php?tid=51310&goto=lastpost
11:04.31paryeah, that would be very helpfull.. as well as maybe a nand mfg and reference list for each device
11:05.01cr2pH5: w100fb on athena ?
11:05.20dream_killMIBIB: 0
11:05.20dream_killQCSBL: 10
11:05.20dream_killOEMSBL1: 14
11:05.20dream_killOEMSBL2: 20
11:05.21dream_killHTC: 26
11:05.21dream_killAMSS: 42
11:05.23dream_killAMSSEFS2: 234
11:05.25dream_killFOTA: 278
11:05.27dream_killRESERVED: 286
11:05.29dream_killAPPSBL: 288
11:05.31dream_killMISC_MFG: 294
11:05.33dream_killSPLASH_1: 296
11:05.35dream_killSPLASH_2: 298
11:05.37dream_killDEBUG: 307
11:05.38*** join/#htc-linux zycho_ (n=zycho@dslb-088-070-073-162.pools.arcor-ip.net)
11:05.39dream_killAPP: 321
11:05.41dream_killEXTENDED_ROM: 953
11:05.43dream_killthis is partition on raphael
11:05.51dream_killbut, as i could see all other devices have same :P
11:06.00dream_kill10 is BLOCK number
11:06.08dream_killwhere a block = 0x800 bytes :P
11:06.31cr2dream_kill: thanks. this is a table i have seen stored in nand.
11:06.37dream_killyes
11:06.50dream_killalso same in G!
11:06.50pH5cr2: is athena pxafb?
11:06.52dream_killG1
11:06.56dream_killand sapphire
11:07.10cr2pH5: vsfb
11:07.20dream_killbut, there the APPSBL (SPL or HBOOT as you wana call it) defines the android partitions :P
11:07.28pH5ahh. I thought it has some ati w2284 that can be driven by w100fb.
11:07.51cr2dream_kill: there should be a difference between 256M and 512M nands. maybe in the EXTENDED_ROM size
11:08.10dream_killposible
11:08.23dream_killdo like so
11:08.27dream_killradio
11:08.38dream_killqmat software
11:08.42cr2dream_kill: the partitions are provided to the linux kernel as an "ATAG". so it's haret here instead of HBOOT
11:08.46dream_killbreak the radio in parts
11:08.55dream_killand look in the partition sections :P
11:09.00cr2lol
11:09.35dream_kill:P
11:09.47dream_killwait
11:10.24dream_killon the 256 page size is 2048 (0x800)
11:10.31cr2pH5: yes, in an ideal world ati w2284 will use w100fb, but many PLL/clock registers have different layout. so w100fb will need some serious patching
11:10.39*** join/#htc-linux tsdogs (n=tsdogs@tsdogs.metalit.net)
11:10.53dream_killand on a 512 page size is 4096 (0x1000)
11:11.24cr2dream_kill: must be 2 chips 2k*2
11:11.35cr2dream_kill: so the page size is still 2k
11:11.50dream_killRTC works
11:11.50dream_killNAND_FLASH_READ_ID : SAMSUNG_512MB_FLASH_256MB_SDRAM
11:12.06cr2dream_kill: raph has 512MB nand, and my blocksize is 2k.
11:12.12dream_killmaker_id=0xEC,device_id=0xBC
11:12.13dream_killmaker_id = EC
11:12.13dream_killdevice_id = BC
11:12.13dream_killtotal_no_devices = 23
11:12.13dream_killWe have found a match of IDs
11:12.13dream_killDevice_probe, page size = 2048, width=2, block count=4096
11:12.16dream_killyep my mistake
11:12.22dream_killlet me check dream
11:12.32cr2SAMSUNG_512MB_FLASH_256MB_SDRAM means they are physically on one chip.
11:12.39dream_killyep
11:13.40dream_killMIBIB: 0
11:13.40dream_killQCSBL: 10
11:13.40dream_killOEMSBL1: 14
11:13.40dream_killOEMSBL2: 20
11:13.40dream_killHTC: 26
11:13.41dream_killAMSS: 42
11:13.43dream_killAMSSEFS2: 234
11:13.45dream_killFOTA: 278
11:13.47dream_killRESERVED: 286
11:13.49dream_killAPPSBL: 288
11:13.51dream_killMISC_MFG: 294
11:13.53dream_killSPLASH_1: 296
11:13.55dream_killSPLASH_2: 298
11:13.57dream_killDEBUG: 307
11:13.59dream_killAPP: 321
11:14.01dream_killEXTENDED_ROM: 953
11:14.03dream_killthis is G1
11:14.05dream_kill(PowerOn Status,Boot Reason)=(1,1)
11:14.07dream_killNAND_FLASH_READ_ID : HYNIX_256MB_FLASH_128MB_SDRAM
11:14.27cr2ok, thanks.
11:15.31dream_killPowerOn Status,Boot Reason)=(1,1)
11:15.31dream_killNAND_FLASH_READ_ID : HYNIX_256MB_FLASH_128MB_SDRAM
11:15.31dream_killARM9_BOOT_MODE0, Boot Android
11:15.31dream_kill+Í¡16 bit
11:15.31dream_kill-msm_nand_probe
11:15.32dream_kill[MDDI] Bitmap_Width = 480
11:15.34dream_kill[MDDI] Bitmap_Height = 640
11:15.36dream_kill[MDDI] RGB_Capability = 0x8888
11:15.38dream_kill[MDDI] Mfr_Name = 0xD263
11:15.40dream_kill[MDDI] Product_Code = 0x0
11:15.42dream_killGetModelName- Default[DREA*****]
11:15.49dream_killthis still dream :P
11:16.10dream_killwhat is starnge i have a debug > prompt in dream :P
11:16.55*** part/#htc-linux kiozen (n=oeichler@p5492151D.dip0.t-ipconnect.de)
11:17.44dream_killwhich i don't understand where is from :P ?
11:17.53dream_killas in radio and HBOOT i can't find it :P
11:20.36dream_killPARTITIOM_NUM_MAX =6 Valid partition num=6
11:20.36dream_killdebug> debug> ps
11:20.36dream_killpid   ppid  prio task            pc
11:20.36dream_kill<PROTECTED>
11:20.36dream_kill<PROTECTED>
11:20.37dream_kill<PROTECTED>
11:22.05cr2amss kernel debugger ?
11:22.12dream_killnot sure
11:22.14dream_killposible :P
11:22.37dream_killsame for wince :P
11:22.39cr2then it should have other commands, not only 'ps'
11:22.40dream_killi have same debug :P
11:22.50dream_killtell me and i test :P
11:23.03cr2if this is amss, wince or whatever does not matter
11:24.39cr2showtcbext ?
11:25.12cr2dumpphys
11:25.35cr2help :)
11:25.49cr2stats
11:25.51cr2arch
11:26.02cr2ptab
11:26.19cr2dumpframe
11:26.29cr2cp15dump
11:26.38cr2tlbdump
11:29.03dream_killPARTITIOM_NUM_MAX =6 Valid partition num=6
11:29.03dream_killdebug> debug> dumpframe
11:29.03dream_killdebug> tlbdump
11:29.03dream_killdebug> stats
11:29.03dream_killdebug> help
11:29.04dream_killdebug> arch
11:29.06dream_killdebug> ptab
11:29.08dream_killdebug> showtctext
11:29.10dream_killdebug> ps
11:29.12dream_killnope
11:29.14dream_killonly ps works
11:29.48dream_killand works only until full os loaded
11:31.13tmztps?
11:31.58tmztdo you know how to offsets from .nb.payload?
11:32.07tmztfor xip, imgfs
11:32.16tmztsize if possible
11:32.23dream_killsorry nope
11:32.33cr2dream_kill: the 'partitions' output is in 128K blocks
11:32.40*** join/#htc-linux MLM (n=mlvdmeid@meide.xs4all.nl)
11:32.49cr2awk '{printf("%s 0x%x\n",$3,$4*2^16*2)}' raph.partitions
11:32.59cr2MIBIB: 0x0
11:33.01cr2QCSBL: 0x140000
11:33.02cr2OEMSBL1: 0x1c0000
11:33.04cr2OEMSBL2: 0x280000
11:33.05cr2HTC: 0x340000
11:33.07cr2AMSS: 0x540000
11:33.09cr2AMSSEFS2: 0x1d40000
11:33.10cr2FOTA: 0x22c0000
11:33.12cr2RESERVED: 0x23c0000
11:33.13cr2APPSBL: 0x2400000
11:33.14cr2MISC_MFG: 0x24c0000
11:33.16cr2SPLASH_1: 0x2500000
11:33.18cr2SPLASH_2: 0x2540000
11:33.19cr2DEBUG: 0x2660000
11:33.21cr2APP: 0x2820000
11:33.24cr2EXTENDED_ROM: 0x7720000
11:33.28cr2this looks reasonable. at least in the first part
11:33.49cr2APPSBL: 0x2400000
11:33.55cr2<PROTECTED>
11:34.15cr2so the fat is at  EXTENDED_ROM: 0x7720000
11:34.56cr2subtracting APP from EXTENDED_ROM you get the imgfs size.
11:36.04dream_killas i said before 2400000 -24c0000 is spl :P now u have it in proof :P
11:36.45cr2it's in itstutils. and i see it in linux.
11:36.53tmztnbinfo, runs in wine
11:36.56cr2the only problem was the EXTENDED_ROM offset
11:37.18cr2hehe. DEBUG
11:37.28par;)
11:37.48cr2+0x260000
11:39.06cr2par: can you access http://www.htc-linux.org ?
11:39.43cr2tmzt: nbinfo should run in linux
11:40.48cr2tmzt: the only problem was the .lzma and .xpr compression. both algorithms have free software implementation, so if somebody wanted to write linux tools, it's not a problem.
11:42.07parwow, its just hanging cr2
11:42.10parpar@dipole$ telnet www.htc-linux.org 80
11:42.10parTrying 83.167.180.132...
11:42.10parConnected to htc-linux.org.
11:42.10parEscape character is '^]'.
11:42.10parGET / HTTP/1.1
11:42.17parjust hanging on reply
11:42.32cr2yeah, something is broken there.
11:42.38paris it been dos'ed or attacked or anything? who runs it?
11:42.58cr2a provider in uk
11:43.02parah
11:43.17paris that where the admin is?
11:43.44cr2more or less yes.
11:44.17dream_killseems DEBUG section is all FF:P
11:44.34cr2dream_kill: on g1 ? hehe
11:44.34tmztyou might need Host:
11:44.45cr2dream_kill: wince dmesg junk here.
11:44.59tmztcr2: it runs
11:45.01dream_killalso in  diamond
11:45.26tmztbut I'm having trouble with sectors
11:45.31dream_kill(got full nand dump from g1 and diamond)
11:46.18cr2tmzt: yes, some have 0x200 and others 0x800
11:47.07cr29 shadowed, and 7 open partitions
11:47.17tmztxip?
11:47.20dream_killok some debug in 26c0800
11:47.22cr2tmzt: is it ok for mtd ?
11:47.33tmztis what?
11:47.44cr216 partitions
11:47.51tmztI haven't even looked at raw nad stuff yet
11:47.56tmztI think so
11:48.14cr2you don't usually want to touch the first 9
11:48.18tmztpartition table for mtd is not on disk
11:48.30dream_killerror
11:48.44dream_killstarts at 26c0000 is the boot partition for android
11:48.51cr2and they are protected, so you can even read them.
11:49.31dream_killso seems that the radio partitions are valid till splash2
11:49.42dream_killthen it's repartition by the hboot!
11:49.54tmztflashimage can flash rhose
11:50.01*** join/#htc-linux hollo (n=hollo@3e6b7b2c.rev.stofanet.dk)
11:50.06cr2dream_kill: repartition ?
11:50.20dream_killthe partition table for the kernel :P
11:51.00dream_killas in android u have: misc, boot, recovery, system, userdata, cache partition
11:51.15dream_killand if is a HBOOT mfg then u also can see MFG partition too :P
11:51.24cr2dream_kill: ok. APP+EXTENDED_ROM is a "wince" partition. they can be joined.
11:51.33dream_killyep
11:51.53cr2dream_kill: it's possible to use EXTENDED_ROM for linux/androed
11:52.03cr2without blowing wince part.
11:52.04dream_killwe can try this :P
11:52.11dream_killneed to patch the spl :P
11:52.15dream_killto make it dualboot :P
11:52.30tmztis there room?
11:52.38parcool
11:52.49cr2[13:32] <cr2> APPSBL: 0x2400000
11:52.50cr2[13:32] <cr2> MISC_MFG: 0x24c0000
11:53.09cr20xc0000 for the SPL
11:53.16cr2whatever it is
11:53.31tmztnice, is it loaded into ram?
11:53.40cr2the wince SPL is < 0x80000
11:55.01cr2the boot flags are in the MISC_MFG section
11:55.20cr2http://wiki.xda-developers.com/index.php?pagename=RaphaelNAND
11:55.36cr2<PROTECTED>
11:55.37cr2<PROTECTED>
11:55.39cr2<PROTECTED>
11:55.40cr2<PROTECTED>
11:55.43cr2just after the SPL
11:56.18cr2i have "WarmBoot" string here -> +0x20   =0xf - cold boot
11:58.45cr20x7720000-0x2820000=0x4f00000
11:59.12cr264+15MB
11:59.28cr2so imgfs is 79MB
12:00.34tmztit looks like there is a table at MSFLSH50
12:00.49tmztwith flash regions
12:01.15cr20x188e0000 is the fat size
12:01.23tmztin payload, but I don't know if that is in nand
12:01.28cr20x20000000-0x7720000
12:01.33*** join/#htc-linux xsacha (n=xsacha@124-171-136-151.dyn.iinet.net.au)
12:02.21cr2it's 393MB
12:02.47cr2392.875
12:03.11cr2what does wince and itsutils report is black magic for me.
12:03.43xsachahey cr2.. i looked at the samsung i780 service manual and it refers to my parts by SEC codes
12:03.48xsachaany idea what those are?
12:04.10parwhat does itsutils show?
12:05.16cr2xsacha: probably completely useless info
12:05.50cr2par: need to look in the logs
12:06.04park
12:07.16cr2[Mo Jun 1 2009] [02:08:13] <cr2>        458.50M (0x1ca80000) DSK1:
12:07.17cr2[Mo Jun 1 2009] [02:08:13] <cr2>        |           3.12M (0x31f000) Part00
12:07.19cr2[Mo Jun 1 2009] [02:08:13] <cr2>        |           4.50M (0x480000) Part01
12:07.20cr2[Mo Jun 1 2009] [02:08:13] <cr2>        |         143.38M (0x8f60000) Part02
12:07.22cr2[Mo Jun 1 2009] [02:08:13] <cr2>        |         307.50M (0x13380000) Part03
12:07.46cr2and wince talks about  306.23MB disk size
12:08.10tmztif the blocks are F000+1000 does that make sense?
12:08.28tmzt1000 being extra data
12:08.36cr2tmzt: 0x10000 ?
12:08.49cr264K blocks in imgfs. why not.
12:08.52tmztyeah
12:09.05tmztthat's what nbsplit says
12:09.31cr2ok, then these are nbh blocks
12:10.23parok, so it is a valid reference then
12:10.48tmzt(imgfs in blovks / f000) * 10000
12:10.55tmztdoes that work?
12:11.07cr2nbh is like tar/cpio :)
12:11.13tmztwait, let me check
12:11.54cr2but tar blocks are 512bytes afair ;)
12:12.13tmztsorty, that's nbh not nb
12:12.28tmztfrom htc flasher
12:14.16tmztexcept it says that's for emulator
12:14.53tmzttian is 0x800+0x08 for nb files
12:14.56*** join/#htc-linux mickey_jaw (n=mike@78-105-123-214.zone3.bethere.co.uk)
12:15.22cr2tmzt: i phear that the data for 16 partitions will exceed the ATAG size, because MSMp is a hack, and the union of the "standard" tags is not very big.
12:15.35parhtc-linux.org is back up
12:16.41cr2par: yes
12:16.42tmztyou can as many ATAGs as there is ram for
12:17.06cr2tmzt: the single tag size is limited
12:17.06tmztat least for MEM, etc.
12:17.12tmztyeah
12:17.19cr2and MSMp is 1 tag
12:18.07cr2i think it's possible to provide the mtd partition data in cmdline ?
12:18.36cr2but it will break the g1 nand_partitions.c code probably.
12:19.31cr2MSMp ATAG data is in 128K blocks too
12:20.53tmztyeah, mtd=
12:21.46cr2what is the biggest current ATAG ?
12:21.46tmzt#define RUUBLOCK 0x100000
12:22.00cr21MB ?
12:22.43tmztnot sure this matters to us though
12:24.47cr2does the 2.6.27 kernel defconfig support yaffs2 ?
12:25.42cr2#define BOOT_PARAMS_SIZE 1536
12:25.43cr2static char __initdata atags_copy[BOOT_PARAMS_SIZE];
12:30.33cr2ok. 7 partitions should be enough for everybody :)
12:31.24dream_kill:P
12:31.31dream_killwhat u doing ?
12:35.26tmztflash region 0
12:35.35tmztXIP
12:35.59tmztsz log bl: 0x3c
12:36.14tmztsz sectors: f00
12:36.32tmztsec per bl: 0x40
12:36.56tmztbytes per bl: 0x20000
12:37.10xsachahey tmzt
12:37.24xsachai have i780 service manual
12:38.24tmztmeans, bytes per sector: 0x800
12:38.35tmzt2048
12:38.39tmzt2k
12:39.49xsachabut the parts like wifi, bluetooth and screen are only referenced by SEC codes
12:39.57xsachadoes this mean anything tmzt?
12:40.07tmztSamsung?
12:40.11xsachathe touchscreen has ORA in brackets.. yueah samsung
12:40.19tmztinternal parts numbers
12:41.47xsachaso means nothing?
12:42.53xsachahere's the service manual anyway: http://deblocage77.free.fr/sam/root/Samsung%20SGH-i780%20service%20manual.pdf  (~6MB)
12:43.00cr2xsacha: do you have the spl dump ? the wince rom dump ?
12:43.13cr2# CONFIG_YAFFS_FS is not set
12:43.15cr2# CONFIG_JFFS2_FS is not set
12:43.24cr2tmzt: yaffs2 ?
12:44.15tmztsorry?
12:44.29xsachai dont have any spl
12:44.54xsachaall i have is bootloader+pda+radio for winmo
12:44.59tmztit's not upstream but it should definately be in android kernel
12:45.11cr2xsacha: i mean bootloader
12:45.14tmztSamsung doesn't use spl
12:45.20xsachaoh yeah, i have bootloader
12:45.27cr2something that is at 0x0
12:45.30xsachayou use it when you do complete flash
12:46.27tmztcr2: looks like sectors are 2k
12:46.49cr2tmzt: do we have the g1 .config ?
12:47.20tmztxip +0x40 is b 0x1000
12:47.29tmztI do somewhere
12:49.18*** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix)
12:50.56tmzt4>[    0.603775] yaffs Mar 26 2009 12:03:24 Installing.
12:51.04tmztjust dmesg
12:51.44tmztcan you check android git msm_defconfig?
12:52.19cr2ok
12:52.26cr2j0b0: ping
12:57.58tmztcr2: drivers/fs/yaffs2/Kconfig
12:58.16tmztconfig YAFFS_FS
12:58.18tmzt...
12:58.49tmzt'   select YAFFS_YAFFS1
12:58.53tmzt'   select YAFFS_YAFFS2
12:59.40tmztyaffs1: not needed for 2k page devices
13:00.01tmztyaffs2: not about on-nand format
13:00.58tmztnote
13:01.34tmztYAFFS_DOES_ECC
13:02.07tmztdoes it's own ecc rather than using MTD-NAND driver
13:03.00tmztread Kconfig and driver ;) very educational
13:03.33tmztwe will probably need to make a tfat using it's layer if we care
13:06.01tmztYAFFS2_AUTO_YAFFS2
13:06.30tmztdetects appropriate format based on device page size
13:06.50tmztyaffs1 for 512
13:07.01tmztyaffs2 for 2k
13:16.25*** join/#htc-linux skodde (n=skodde@adsl-ull-183-1.47-151.net24.it)
13:20.34tmztcr2: ah, yaffs sets up the nand as well, I think that's why msm_nand made no sense
13:20.49tmztwe should look at flash_image source
13:21.09tmztsets up the mtd I mean
13:26.14*** join/#htc-linux MethoS-- (n=clemens@host-091-097-242-129.ewe-ip-backbone.de)
13:26.51cr2tmzt: ok, i'll leave it to you :)
13:27.13tmztto do what?
13:27.22cr2nand yaffs
13:27.38tmztI'm saying if you have g1 .config
13:27.47tmztit should just work
13:28.11*** join/#htc-linux AntiXpucT (n=Skim@77.106.108.232)
13:28.12tmztmostly that was reading and copying
13:28.29cr2even on mtd15 ?
13:28.32tmztthough it gave me a chance to look at the code
13:28.41tmztwhat do you mean?
13:28.47cr2btw, how do i set readonly mtd flag for spl
13:29.18cr2i'll try to mount extended_rom now.
13:29.25tmztlet me see, forget where atag parsing is
13:29.31cr2then we can discuss what to do with android
13:29.54tmztsomething special about mtd15?
13:30.34cr2no, just that android will access other partitions and format them ;)
13:30.35tmztI think the community there would very much like to resize partitions independently of hboot
13:30.53tmztthat's not good
13:30.57tmztoh
13:31.08tmztyeah, in initrc
13:31.33tmztthe cache partition takes up toomuch space
13:31.59tmztand it's only used by OTA from t-mobile
13:33.05tmztand yaffs2 system is full on some builds now, so apps go to sd card with symlinks
13:33.31tmztthe system/data split is artificial
13:34.01tmztrecovery is nice, but some might prefer the full usable nand  e rw root
13:34.11tmztbe
13:34.37tmztthis would need a new bootloader
13:34.53tmztdream_kill: is that what you said?
13:35.28cr2tmzt: sorry. i use initrd-htcraphael-20090412.cpio.gz
13:35.52cr2not initrd-angstrom.cpio.gz
13:36.12tmztyeah, I misunderstood what you said about android
13:36.47tmztI certainly wouldn't do anythin with it with a valid mtd table
13:37.32tmztI'm just saying there may be some users interested in working on bootloader for both/all devices
13:37.41cr2ok
13:38.01tmztto replace spl/hboot/eng/and the git one
13:38.01cr2diam has the same 512MB nand as raph ?
13:38.20dream_killyes
13:38.27cr2ok
13:38.27dream_killwait
13:38.29dream_killnope
13:38.30dream_kill256
13:38.44cr2dream_kill: hmm. well.
13:39.36cr2i see that a lot of diam people complain about something in xda-dev thread
13:40.14cr2i think they are screwed because once i've enabled the second SDRAM bank :)
13:40.26dream_kill:d
13:40.33cr2hehe. should buy better hardware :)
13:40.35*** join/#htc-linux wirelessdreamer (n=dreamer@c-71-239-79-222.hsd1.il.comcast.net)
13:40.39dream_killyep :P
13:41.41cr2well, it should be trivial to add if (machine_*) instead of if(1)
13:44.40*** join/#htc-linux syn-fin (n=alien@access68.terremark.com)
13:47.29cr2TSystem.Drawing, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
13:48.24*** join/#htc-linux syn-fin (n=alien@access68.terremark.com)
13:49.22cr2ok, i can't mount fat off the nand anyway
13:49.33dream_killwhy not?
13:49.34dream_kill:P ?
13:50.48tmztright
13:51.18cr2mount -o ro /dev/mtdblock6 /mnt/cf/
13:51.32cr2[  405.515399] end_request: I/O error, dev mtdblock6, sector 64
13:51.33cr2[  405.515429] msm_nand_read_oob: unsupported ops->len, 512
13:51.35cr2[  405.515460] end_request: I/O error, dev mtdblock6, sector 72
13:51.36cr2[  405.515490] msm_nand_read_oob: unsupported ops->len, 512
13:51.38cr2[  405.515521] end_request: I/O error, dev mtdblock6, sector 80
13:51.39cr2[  405.515551] msm_nand_read_oob: unsupported ops->len, 512
13:51.41cr2[  405.515551] end_request: I/O error, dev mtdblock6, sector 88
13:51.43cr2[  405.515612] msm_nand_read_oob: unsupported ops->len, 512
13:51.44cr2[  405.515612] end_request: I/O error, dev mtdblock6, sector 96
13:51.45cr2[  405.515643] msm_nand_read_oob: unsupported ops->len, 512
13:51.53tmztthere might be trick for that
13:51.55cr2hmm. how can i teach it about 2048 blocksize ?
13:52.22cr2man mount
13:52.25dream_killin the nand detect wasn't block size??
13:52.36tmztright a tfat driver, copy the setup from yaffs
13:52.49cr2but fat is 512 ;)
13:52.50tmztdoes, dd bs 2048 work?
13:53.02tmztcluster size
13:53.02cr2yes
13:53.09dream_killaa
13:53.13dream_killhack vfat :P
13:53.17dream_killto have 2048 :P
13:53.20tmzttry imaging to sd
13:53.37cr2tmzt: what is tfat ?
13:53.56tmzttransactional fat
13:54.00tmzton msdn
13:54.04cr2tmzt: hehe. mount -o loop
13:54.46tmztdoes that work?
13:55.29tmzttfat updates a different fat each time, not sure why though
13:55.31cr2Mount options for fat
13:55.40cr2<PROTECTED>
13:55.42cr2<PROTECTED>
13:56.26cr2root@htcraphael:~# mount -t vfat -o ro,blocksize=2048 /dev/mtdblock6 /mnt/cf/
13:56.30cr2mount: /dev/mtdblock6: can't read superblock
13:56.31cr2that looks much better
13:57.06dream_killmkfs.fat ../:P
13:57.14cr2LOL
13:57.18cr2[  715.858386] FAT: "blocksize=2048" option is obsolete, not supported now
13:57.20cr2[  715.858782] msm_nand_read_oob: unsupported ops->len, 512
13:57.21cr2[  715.858813] end_request: I/O error, dev mtdblock6, sector 0
13:57.22cr2[  715.860736] FAT: unable to read boot sector
13:57.38dream_kill:P
13:57.44dream_killhack kernel:P
13:57.57cr2but i don't see the boot sector anyway
13:58.05cr2in the data
13:58.16tmztno signature?
13:58.22cr2dream_kill: mke2fs -j -m 0
13:58.31cr2tmzt: no
13:58.44cr2tmzt: i've compared with the itsutils dump. it looks the same
13:59.08cr2tmzt: it seems that we need to parse the imgfs data ;-)
14:00.02tmztit looks like the wrong partition
14:00.11tmztlook at Part03
14:00.18cr2<PROTECTED>
14:00.20cr2<PROTECTED>
14:00.22cr2<PROTECTED>
14:00.23cr2HAHA
14:00.28tmzt...MSWIN4.1
14:00.33tmzt...
14:00.42cr2the flags from MSMp ATAG are not used
14:00.47tmzt'  TFAT32
14:01.19tmztwhat does that mean?
14:01.45cr2od -c RAPH skip=$((0x7720000))
14:02.09cr2tmzt: if is set readonly flag in MSMp
14:02.19cr2then it's ignored by g1 code. LOL
14:03.21cr20000000 203 203 203 203   4 020 327   s 001  \0  \0  \0 234  \n  \0  \0
14:03.26cr20000020 200 002  \0  \0  \0 340  \0 200 354 001 001  \0 354 001 001  \0
14:03.26cr20000040 354 341 001 200  \0  \0  \0  \0 354 341 001 200  \0  \0  \0  \0
14:03.26cr20000060  \0  \0  \0  \0  \0  \0  \0  \0 257  \0  \0  \0  \0  \0 377 200
14:03.46*** join/#htc-linux sdt555 (n=titus@147.145.40.44)
14:03.51*** part/#htc-linux sdt555 (n=titus@147.145.40.44)
14:04.00cr2erm
14:04.05cr20000000    ] 030 031 234 360 221   E 267 375 341 202   K   1 035 244 303
14:04.07cr20000020    $   {   ` 342 026   J 020 310 300 341 006   N   \ 002 243 213
14:04.08cr20000040  371 221   H 302 223 214   @   I 002 036 204 020 362   $  \t   Q
14:04.10cr20000060  216 250   " 200  \b   P 347   Z 030   l   @ 220  \a 027 265   9
14:04.12cr2mtd6
14:05.25cr2dumb me
14:05.25cr2od -c RAPH -j $((0x7720000)) | less
14:05.25tmztimgfs has XPR in the first block
14:06.03cr27720000   ] 030 031 234 360 221   E 267 375 341 202   K   1 035 244 303
14:06.32cr27720010   $   {   ` 342 026   J 020 310 300 341 006   N   \ 002 243 213
14:06.32cr27720020 371 221   H 302 223 214   @   I 002 036 204 020 362   $  \t   Q
14:06.32cr27720030 216 250   " 200  \f   P 347   Z 030   l   @ 220  \a 027 265   9
14:06.32cr27720040 220   B 022   )   8   p 026 030   # 034   0 204 005  \n 036 201
14:06.32cr27720050 211 026   a 204 301 307 016 372   e 321 242 211   Q   2 342 347
14:06.33cr27720060 022 214 244 001 250 004   K 004   A 005 025   i   H   `   B 020
14:06.35cr2so itsutils output is the same as lnx
14:06.41cr2imgfs is not a problem
14:06.43cr2mtd5
14:06.56cr2tmzt: not always XPR
14:07.10cr2tmzt: can be LZM, or no compression at all
14:07.21tmztok
14:07.29tmztmine is XPR
14:07.43cr2od -A x -c RAPH -j $((0x2820000)) | less
14:08.04cr2yes, XPR is most often
14:08.07cr2but i'm looking at the ondisk data
14:08.31cr22820000 351 375 377  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
14:08.56cr22820010  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
14:08.57cr2*
14:08.57cr22820800   M   S   F   L   S   H   5   0  \0  \0  \0  \0   T  \0  \0  \0
14:08.57cr22820810  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0   =  \0  \0  \0
14:08.59cr2*
14:09.01cr22821000 376 003  \0 352  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
14:09.03cr22821010  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
14:09.05cr2*
14:09.07cr22821040   E   C   E   C  \0 264 021 200  \0 264 021  \0  \0  \0  \0  \0
14:09.09cr22821050  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
14:09.11cr2no XPR here
14:12.01cr2strange
14:12.05cr2240400000 351 375 377  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
14:12.06cr2240400020  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
14:12.32cr20000000  367  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
14:12.33cr20000020   \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0  \0
14:14.31cr2and i don't like these messages
14:14.35tmztgot fspanic, invalid cluster chain after changing first two bytes to match vfat
14:14.35cr2[ 1737.359332] msm_nand_read_oob 2827800 800 0 failed -74, corrected 0
14:15.04tmztthe fs driver has to set it up I think
14:15.15tmztwe should have a block layer
14:15.33cr2ok
14:16.15cr2but ignoring the MSMp flags is a g1 kernel bug
14:16.24cr2imho
14:16.25tmztinvalid fsinfo
14:19.11cr2the hboot is more difficult to disassemble, because there is no dumprom for it.
14:20.26cr2<PROTECTED>
14:20.27cr2<PROTECTED>
14:20.28tmztstill mounts with most the bootable part replaced with TFAT signature
14:20.30cr2<PROTECTED>
14:21.10tmztI need nde for this though
14:21.21tmztdon't have a copy here
14:21.32cr2err -74
14:21.40cr2but 0 ecc errors
14:21.44tmzthave you looked at mtdif in yafds?
14:22.05tmztecc is in hw
14:22.23*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
14:22.27tmztyou would only see an error if one occured
14:22.32cr2SUPPORT_WRONG_ECC_CONFIG ?
14:22.35tmztAstainHellbring: really here now?
14:22.43tmztno
14:22.48tmztnot for msm
14:22.57cr2#define SUPPORT_WRONG_ECC_CONFIG 1
14:23.22tmztwhere?
14:23.39cr2#define EBADMSG         74      /* Not a data message */
14:23.56cr2in /drivers/mtd/devices/msm_nand.c
14:24.58AstainHellbringhuh tmzt?
14:25.05cr2ok, i'll leave it to you.
14:26.03cr2root        23  0.0  0.0      0     0 ?        S<   16:44   0:00 [synaptics_wq]
14:26.04tmztAstainHellbring: can you boot latest git on raph800?
14:26.26cr2root        13  0.0  0.0      0     0 ?        D<   16:44   0:00 [rpcrouter]
14:26.33tmztcr2: I can research but not ready to test it yet
14:26.53tmztactually my kernel isn't working now
14:27.10cr2why synaptics, and why rpcrouter is D ?
14:27.12tmztand I can't figure out why
14:27.26tmztsynaptics is cap.screen
14:27.37cr2on g1 maybe
14:27.45tmztyeah
14:27.54cr2but i don't have g1
14:28.19AstainHellbringI has a g1
14:28.38AstainHellbringtmzt can you build me a kernel or link me to one and I'll try on the 800
14:29.56tmztok, it will take a while to upload
14:29.57cr2AstainHellbring: can you checkout the clean git tree ?
14:30.16cr2AstainHellbring: i have my own that works, and don't want to break it :)
14:31.05AstainHellbringcr2 I dont have a box with git on it atm
14:31.52cr2ok
14:31.53cr2root@htcraphael:~# cat /proc/iomem
14:31.53cr210000000-158fffff : System RAM
14:31.53cr2<PROTECTED>
14:31.53cr2<PROTECTED>
14:31.54cr217100000-17300000 : msm_panel.0
14:32.01cr220000000-27ffffff : System RAM
14:32.01cr2a0300000-a0300fff : msm_serial_hs.1
14:32.01cr2a0500000-a0500fff : msm_sdcc.2
14:32.02cr2a0800000-a0801000 : msm_hsusb
14:32.04cr2a9900000-a9900fff : msm_i2c.0
14:32.06cr2<PROTECTED>
14:32.08cr2aa200000-aa2effff : mdp
14:32.10cr2aa600000-aa600fff : msm_mddi.0
14:32.20cr2framebuffer is in sdram
14:33.45cr2htc-linux.org doesn't answer again
14:36.30cr2the ssbi and tssc are not registered ?
14:37.05cr2Blame NetRipper again :)
14:37.14NetRipperoi, stop blaming me!
14:37.15NetRipper;)
14:37.22AstainHellbringblames NetRipper
14:37.29NetRipperbastards!
14:39.52cr2LOL
14:41.08*** join/#htc-linux maejrep[w] (n=madCoder@smtp-n.myyearbook.com)
14:42.28tmztAstainHellbring: people.openezx.org/tmzt/zImage-testraph1 + 2
14:42.39tmzteither, both, doesn't matter
14:42.56tmzt2 is head htcraphael_defconfig
14:43.12tmzt1 is one that didn't work
14:43.56tmztno usb detected, and cat /dev/smd1 fails
14:48.30cr2smd1 ?
14:48.49tmztour ppp
14:49.14AstainHellbringok downloaded those
14:49.15tmztmaejrep mapped it to the correct address
14:49.39AstainHellbringcr2 did you need something pulled from g1?
14:50.06tmztconfig.gz
14:50.08cr2AstainHellbring: can you ssh to g1 as root ?
14:50.19AstainHellbringshould be able to one sec
14:50.45AstainHellbringbooting g1 up now
14:50.53AstainHellbringhas the new spl so it takes bloody forever
14:51.17tmztnew spl?
14:52.19AstainHellbringsaphire spl port I believe
14:52.23*** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz)
14:52.38AstainHellbringhttp://code.google.com/p/sapphire-port-dream/
14:52.42AstainHellbringthe spl from there
14:53.17tmztah
14:53.27dream_kill1.33.2005?
14:53.38AstainHellbringdream_kill yes
14:53.46dream_killis fast for me :P
14:54.21AstainHellbringfor me it takes longer to boot then the old spl
14:54.25dream_killthe 1.33.2005 has different partitions setup (system is 91 meg compare with 71 meg as original)
14:54.27AstainHellbringdream_kill what rom you running?
14:54.50dream_killdon't ask ;)
14:54.58dream_killh**o :P
14:54.58AstainHellbringbah!
14:55.12dream_killbeta1 :P
14:55.40AstainHellbringbeta1 huh
14:55.43AstainHellbringnot this one:  http://forum.xda-developers.com/showthread.php?t=521059
14:55.53dream_killthat one is older :P
14:55.55cr2btw, what gX libararies are closed source ?
14:56.18dream_killok got to run
14:56.31AstainHellbringI have a link somewhere to beta4 I think
14:56.35dream_killcr2...managed to make nand work ?
14:57.00dream_killbeta1 was release on 25 may :P
14:57.03tmztcr2: gx?
14:57.13cr2dream_kill: no. feel tired now.
14:57.17dream_killok
14:57.19cr2tmzt: g1/g2
14:57.21dream_killl8er then :P
14:57.26tmztoh
14:57.30tmztgpu
14:57.34tmztaudio
14:57.45tmztril
14:58.09cr2gps ?
14:58.14cr2qcamera ?
14:58.15tmztaucustic, what ever that is
14:58.17*** join/#htc-linux xsacha (n=sacha@123.100.137.226)
14:58.21tmztnot sure
14:58.27tmztcamera yes
14:58.28cr2htc_acoustic
14:58.31cr2htc_ril
14:58.42xsachahey im back
14:58.45AstainHellbringok tmzt ready to try to boot those
14:58.48cr2acoustic is your AudioPar/ ADIE ?
14:59.02xsachaso tmzt, you said there was no defconfig for my phone so i had to use the MSM one..
14:59.11tmztswetland said it was for headsets, so I think yes
14:59.21xsachabut the kernel i was using before had the msm one with android configs as well.. cant i just use my old kernel?
14:59.22tmztxsacha: no
14:59.35tmztrelevant atuff from it
14:59.45xsachayeah that's what i mean
15:00.02xsachalike CONFIG_BINDER and CONFIG_ASHMEM
15:00.08tmztyou were using an msm kernel?
15:00.11xsachano
15:00.21tmztwhich?
15:00.24xsachathe kernel source i was using had a defconfig from msm that contained android relevant parts
15:00.39tmztwhat git
15:00.47xsachai dunno, it's the one melgurth had
15:00.53xsachai just used what he had since he had screen working on it
15:00.58tmztI thought you were working on upstream
15:01.13xsachai dont know how to find out where he got it from
15:04.07xsachawell there's much more android stuff in the android one than the one from melgurth anyway
15:05.07*** join/#htc-linux mickey_jaw (n=mike@78-105-123-214.zone3.bethere.co.uk) [NETSPLIT VICTIM]
15:05.11xsachaok well you say take the relevant stuff from msm defconfig.. but.. mm which defconfig do i base it on?
15:05.39tmztzyl, or some other pxa3xx
15:05.42tmztor none
15:05.53xsachaoh zylonite.. k
15:06.34xsachadefault one is versatile.
15:09.24AstainHellbringbrb gotta reboot
15:11.33xsachado i need to disable all MTD stuff again?
15:11.57xsachanevermind, it doesnt use MTD.. whew
15:12.04*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
15:17.51xsachai dont know if this affects anything, but keyboard and touchscreen seem to be disabled? CONFIG_INPUT_KEYBOARD,.. should i enable?
15:18.09xsachai know touchscreen probably still wont work without right driver, but still?
15:24.37xsachaon the service manual it had TOUCH UNIT (ORA)   could ORA be a manufacturer?
15:27.08*** join/#htc-linux Echo31 (n=olivier@mir31-4-82-240-194-54.fbx.proxad.net)
15:30.21cr2<PROTECTED>
15:30.48*** join/#htc-linux syn-fin (n=alien@access68.terremark.com)
15:35.52*** join/#htc-linux MethoS- (n=clemens@host-091-097-242-129.ewe-ip-backbone.de)
15:36.22xsachammm whys it asking me hard questions lol.. enable group scheduler?
15:44.43xsachayay! :)
15:50.00xsachatmzt: a lot of my pxa files like pxafb tell me to use pxafb257.c instead of pxafb2xx.c for example.. is this important?
15:50.43tmztnever heard of it
15:51.03tmzthow many MACH options are enabled now?
15:51.13xsachaactuall, it's the header file, not the c file
15:51.30xsachajust the one i hope.. I780
15:52.42tmztdefintely keyboard
15:53.02xsachak.. keyboard was disabled in zylo...
15:53.03tmzttouchscreen depends on controller
15:53.14tmztprobably wm97xx
15:53.21xsachayeah, cant just guess the controller?
15:53.26xsachatry 1, see if it works, etc..?
15:53.41tmztyes
15:53.44xsachait has to be one of the 6 listed right?
15:53.54xsachaand it's not synaptics cause they only do multi-touch i think
15:54.02tmztand if you have the irq we found
15:54.22xsachabut we werent sure if that irq was right (pxa2xx... pxa3xx issue)
15:54.28tmztit's probably what I said, like omnia
15:54.36xsachaomnia uses wm97xx?
15:54.47tmztfor something
15:54.57tmztprobably sound and ts
15:55.21tmztI think the irq was right
15:58.51xsachatouchscreen IRQ on my phone... GPIO23(87)=1
15:59.05xsachaon GEDR0
16:00.13tmztit's under 96
16:00.29tmztit's almost certainly right
16:00.35cr2tmzt: ?
16:00.45tmztyou have to add it to your board
16:00.48cr2gpio23 is certainly under 96 ?
16:01.04tmztcr2: 3 banks are the same
16:01.29xsachaarg.. didnt boot.. no filesystem support :P
16:01.31tmztin reg-pxa.py and 310 pdf file
16:01.50xsachaso we dont need to change the python file for 3xx?
16:02.00tmztwe do
16:02.13xsachajust to change the names though? register per number or something
16:02.18tmztbut there is a lot of overlap
16:02.52j0b0cr2, pong @ 14:52:25<cr2> j0b0: ping
16:03.16tmztfor mfp, but gedr is the same for those banks
16:03.48*** join/#htc-linux kiozen (n=oeichler@rgnb-5d87d5a3.pool.einsundeins.de)
16:04.32xsachaso for the touchscreen.. is it wm9705, 9712, 9713 or i just use xx?
16:05.34tmztfind a board that uses it and copy
16:05.44tmztname has to match
16:06.05xsachahuh? but am not sure with 97 it is
16:06.29tmztit won't hurt anything to try
16:06.43xsachawm9713 for omnia says it is an audio codec?? how's that work
16:06.50tmztit's an i2c device right?
16:06.58tmztadc
16:07.09xsachaCONFIG_TOUCHSCREEN_WM97XX
16:07.10tmztlook up the chip
16:07.17tmztyes
16:07.53xsachaso it controls audio and touchscreen?
16:07.59tmztit might
16:08.28tmztyou could try what cr2 said with bootloader
16:08.44tmztthought ts and audio aren't always in there
16:08.50tmztthough
16:09.00xsachawhat was that about bootloader?
16:09.32xsachacheck it for strings?
16:10.09tmztthat's one way
16:10.21tmztyou won't get mappings though
16:10.55xsachawhen are they gonna make a touchscreen version of bash :)
16:13.17AstainHellbringtmzt #1 wouldnt boot for me
16:15.16AstainHellbring#2 seemed good
16:17.40*** join/#htc-linux BabelO_ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
16:18.38tmzt1 won't boot at all?
16:18.49tmztdid usb work in 2?
16:18.58tmztdoes your pc see it
16:20.09xsachathis image (from android.git.kernel.org) is much smaller than previous image i used!
16:20.19xsachaonly 2.4MB
16:21.02AstainHellbringchecking now tmzt
16:21.45xsachaummm.. m doing something wrong.. "Root-NFS: No NFS Server available, giving up"
16:23.05xsachacomments out everything to do with NFS
16:23.26tmztyour missing some configuratios
16:23.29AstainHellbringtmzt seems like maybe my rom I'm running is pissing off the booting process
16:23.51xsachadunno why it attempts to load nfs instead of what i specify as root in my kernel cmdline
16:23.52tmztwhat's it dping?
16:24.25xsachai dont need SUNRPC right? (takes a while to compile)
16:24.37tmztxsacha: CONFIG_BLOCK_MMC should be it
16:24.53tmztyou don't need it
16:25.03xsachawell that'd explain it.. line isnt there at all
16:25.10tmztbut you kernel is just falling back to nfs
16:25.34tmztnot sure that's exactly the right name
16:26.01tmztyou msm_defconfig from a working android branch?
16:26.03xsachashould CONFIG_MMC be enabled too?
16:26.08tmztyes
16:26.21tmztthe one upstream doesn't work
16:26.22xsachaok.. CONFIG_MMC is disabled in msm_defconfig and there's no block_mmc either
16:26.44tmztwhere did you get this kernel?
16:26.44xsachaim using android.git.kernel.org one
16:26.49tmztplease
16:27.04xsachathe one you linked to me
16:27.08tmztdid you checkout after pull?-
16:27.26tmztgeneric.git?
16:27.33xsachamm no
16:27.50tmztwhat's the git you cloned?
16:28.28xsachaurl = git://android.git.kernel.org/kernel/common.git
16:28.37tmztcat .git/config |grep url
16:28.43tmztyeah ok
16:28.49tmztgit branch
16:29.56xsachayeah
16:30.05xsacha2.6.27
16:30.08tmztoutput?
16:30.12tmztmaster?
16:30.21xsacha* android-2.6.27
16:30.25tmztwhat has *
16:30.27tmztok
16:30.36tmztoh, yeah
16:31.05tmztgo into menuconfig and enable what you need
16:31.18xsachathat'll take forever? :P
16:31.36tmztthe msm_defconfig is no updated because this isn't an msm tree
16:31.57tmztit's missing a lot things
16:33.26xsachaso i'll just enable things reevant to screen, memory card, touchscreen, keyboard, processor and i780 mmm
16:34.36tmztyes
16:37.09xsachaahh here we go
16:37.23xsacharoot=/dev/nfs .... nfsroot=192.168.1.100...
16:38.06xsachaill leave the default string blank :P
16:38.19tmztright
16:38.47tmztgoogle/android probably used that on halibut
16:39.18xsachamm ill enable bluetooth and wireless
16:39.33*** join/#htc-linux MethoS- (n=clemens@host-091-097-242-129.ewe-ip-backbone.de)
16:39.56tmztthey probably won't work yet
16:40.06tmztit shouldn't hurt though
16:40.08xsachayeah, but will add them one day
16:40.27tmztI think you have libertas on sdio
16:40.48xsachathat's wireless? but what's sdio?
16:41.01tmztmarex might be able to help with that
16:41.25tmzttreats sd protocal as a periphrial bus
16:41.36marexno idea ... with what ?
16:42.02tmztyou have the other portds disabled right now
16:42.10tmztmarvell wifi
16:42.12xsachado i need to enable RAM block device?
16:43.17AstainHellbringtmzt usb works I see a driver prompt
16:43.35marextmzt, join #libertas
16:46.56xsachaMMC embedded SDIO device support?
16:47.34tmztno
16:47.40tmztwell maybe
16:48.07tmztnot necessarily requied if it can enumerate
16:48.29xsachaand no real time clock?
16:48.49tmztpxartc or sa1100-rtc
16:49.23xsachaoh yeah it's down the bottom SA11x0/PXA2xx (NEW)
16:51.22xsachawhy it doesnt let me turn off mouse support? hmmm
16:51.40xsachaMice Interface
16:52.08tmztwhere?
16:52.20xsachaInput device -> Mouse Interface
16:53.28*** join/#htc-linux dcordes-kais (n=dcordes-@ip-77-25-15-100.web.vodafone.de)
16:55.26tmztPS/2 mouse?
16:55.30xsachayeah
16:55.46xsachawont let me disable that
16:55.52tmztthat shouldn't be enabled
16:56.09tmzthalibut might have at keyboard port
16:56.26tmztdo it in .config then
16:56.31xsachak
16:57.17xsachai have AC97 driver for the pxa2xx chip enabled.. should i enable ASoC too?
16:57.48xsachapower efficient alsa for battery powered devices?
16:58.00tmztyou don't have a driver yet
16:58.16xsachaoh, it's not the same as touchscreen one?
16:58.20tmztyou can always enable things
16:58.51xsachathe AC97 driver for pxa2xx wont work?
16:59.07tmztit maybe the same chip, but there are usually other things involved
16:59.11xsachak
16:59.23tmztthat's only the dai host
17:02.00xsachaah thats why it listed no partitions? needed ms dos partition support?
17:03.18tmztyeah
17:03.36tmztbut you also had no mmc at all
17:03.46tmztdos partition
17:03.48tmztvfat
17:03.54tmztext2/3
17:03.56xsacha:P
17:04.00tmztcramfs
17:04.03xsachai dont need ext3 though right?
17:04.12tmztno
17:05.11*** join/#htc-linux BabelO__ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
17:05.28xsachathe wm97xx touchscreens dont appear in menuconfig.. so manually i guess
17:07.25xsachamm i tried to make Image and it forced me to put the INPUT_MOUSEDEV back
17:09.44tmztdon't think that's a problem
17:10.08tmztdid you enable i2c?
17:10.12xsachajust weird i didnt need it before. now when i boot up it says initialising PS/2 :)
17:10.18xsachayeah i enabled i2c
17:10.50tmztso you need to add some stuff to your board
17:11.20xsachaCONFIG_I2C=y    CONFIG_I2C_BOARDINFO=y        CONFIG_I2C_CHARDEV=y      CONFIG_I2C_HELPER_AUTO=y
17:11.30tmztfind one with wm97xx and copy the code
17:11.35xsachak
17:11.44tmztright, board info
17:11.59tmztpxa i2c as well?
17:12.49xsachaoops no.. didnt see that there
17:13.47tmztI skip menuconfig and read Kconfig's now
17:14.08xsachai780.c: wm9713_irq = mfp_to_gpio(MFP_PIN_GPIO26);  <-- this is a relic from zylonite
17:14.08tmztthe layout on arm makes no sense to me
17:14.14tmztpc was fine
17:14.45xsachazylonite is the only other pxa board with wm97xx
17:15.24tmztcopy that back then
17:15.29xsachain fact the only other board in arm with it
17:15.39tmztsorry if I had you remove it
17:15.45xsachait's still there :)
17:15.45tmztupstream, yeah
17:15.52*** join/#htc-linux kiozen_ (n=oeichler@rgnb-5d87d423.pool.einsundeins.de)
17:16.04tmztfix the irq/gpio then
17:16.12xsachait wont be the same?
17:16.13AstainHellbringtmzt did you need stuff from me still?
17:16.28xsachawm9713_irq = mfp_to_gpio(MFP_PIN_GPIO26)
17:16.34tmztaddress should be standard, maybe not
17:16.44tmzthuh
17:16.52tmztnever seen that before
17:17.09tmztAstainHellbring: anything in dmesg when booting?
17:17.43xsachazylonite has a different gpio for pxa320 (15) and pxa300/310 (26)
17:18.10xsacha<xsacha> touchscreen IRQ on my phone... GPIO23(87)=1
17:18.14tmztthat's beacause there are two or three zyl's
17:18.18tmztyeah
17:18.34xsachaso it should be MFP_PIN_GPIO23 on my phone?
17:18.37tmztwe probably need  e mfp thing though
17:18.43tmztyes
17:19.00tmztI think, this changed in 3xx
17:19.52tmzt<PROTECTED>
17:19.53tmztmfp_to_gpio(MFP_PIN_GPIO26)
17:20.06xsacha<PROTECTED>
17:20.10tmztlike that
17:20.23tmztbut your GPIO
17:20.26xsachak
17:20.41tmztit's because the gpio can move on 3xx
17:20.46tmztit's weird
17:20.51xsachalol
17:21.34xsachaim not sure what the wm9713_irq then goes on to do..
17:21.46xsachacause then it init's i2c and nothing happens after
17:22.05tmztwhen you touch the screen it fires
17:22.13xsachabut that variable never gets used?
17:22.17tmztcausing the driver to be called
17:22.27tmztirq - interrupt request
17:22.41tmztkernel handles that part
17:22.49tmztand the driver
17:22.51xsachai mean where does int wm9713_irq get used? cant see any function taking it
17:23.06tmztin a different file
17:23.17xsachahmm k
17:23.28tmztdrivers/input/touchscreen
17:23.40AstainHellbringtmzt nothing special about dmesg that I saw...
17:23.41tmztor drivers/i2c/chips
17:24.00tmztAstainHellbring: no usb device? cdc-ether, etc?
17:24.04tmztlsusb
17:24.11tmztifconfig usb0
17:24.36tmztthat's the problem, it's not showing up on the bus
17:25.06tmztif you unplug/replug usb it should print some messages
17:25.13tmztmine wasn't
17:25.31xsachait asked me:   Intel PXA2XX I2C Slave comms support (I2C_PXA_SLAVE) [N/y/?] (NEW)
17:26.01*** join/#htc-linux BabelO__ (n=fcr@193.253.141.89)
17:26.42xsachagoing with default i guess
17:28.44xsachathink there might be an issue with that sa1100-rtc.. it sets my clock to 1970
17:28.49tmztn
17:29.06tmztwindows sets it wrong
17:29.18tmztthe new driver should work though
17:29.27tmztdisable the old one
17:29.32xsachainput: wm97xx touchscreen as /class/input/input1   :D
17:29.45tmztand no i2c slave, only if you know you need it
17:29.50tmztyay
17:29.57AstainHellbringtmzt I need to switch from android as my os to boot from zimage
17:29.58xsachaALSA device list: #0: pxa2xx-ax97 (Wolfson WM9713, WM9714)
17:30.07tmztcat /dev/input/event1
17:30.15xsachacant, kernel panicked
17:30.27xsachacant open root device "mmcblk0p2"
17:30.43tmztoh
17:31.03tmztcan ypu diff this config with your old on?
17:31.17xsachayeah was thinking about that.. some mmc option i must be missing
17:32.05tmzt<PROTECTED>
17:32.16tmztgreat
17:32.30xsachawhat about these? < CONFIG_EXT2_FS_POSIX_ACL=y                                            < CONFIG_EXT2_FS_SECURITY=y                                             < CONFIG_EXT2_FS_XIP=y
17:32.43xsachaoh those are new things i added in this kernel
17:32.45tmztwoah, it sees you codec?
17:32.50xsachayeah it does :)
17:33.13tmztthe one thing ac97 is good for
17:33.17tmzt<PROTECTED>
17:33.33xsachaohh i know why clock isnt working
17:33.35xsacha> CONFIG_RTC_DRV_PXA=y
17:33.42xsachainstead of the SA1100
17:33.47tmztno
17:33.52tmztwell maybe
17:33.59xsachaclock worked in last imag
17:34.14tmztit could be the old one that's compatible with win ce
17:34.15tmztok
17:35.01xsachayeah it would be these options.. ill add them in: > CONFIG_MMC_PXA=y                                                     > CONFIG_MMC_SDHCI=y                                                    > CONFIG_MMC_SPI=y
17:35.19tmztyeah
17:35.33tmztI gues it's not mci then?
17:35.39tmztno
17:35.46tmztyou don't need those
17:36.00xsachaoh?
17:36.09tmztespecially the last one
17:36.25xsachalast one only for SD controller?
17:36.27tmztyou have pxa-mci
17:36.49tmztthe first one is your driver
17:37.06xsachai mean middle one
17:37.32xsachado i need this? > CONFIG_SPI_PXA2XX=y
17:37.33tmztmci is a version of it I think
17:37.39tmztyes
17:38.59xsachapower management? CONFIG_PXA_PWM
17:40.13tmztbacklight probably
17:40.18tmztmaybe
17:40.29tmztjust enable it here
17:42.16xsachawell ill try it now
17:43.39xsachaso i dont need?   Secure Digital Host Controller Interface support (MMC_SDHCI) [N/m/y/?] n
17:43.41*** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbf9264.pool.einsundeins.de)
17:43.58tmztI think you have to write a driver to expose it sysfs
17:44.06tmztno
17:44.09xsachak
17:44.41tmztthere is something wrong but that's not it
17:46.37xsachayay! :)
17:46.41xsachait ran init
17:46.50tmztgood
17:46.55xsachanew kernel panic :D
17:46.56tmzttry the ts
17:47.04xsacha(im running android init)
17:47.05tmztwhat is it?
17:47.27xsachaUnable to load NLS charset    FAT: codepage cp437 not found
17:47.36tmztyeah, that's not a good one for working with hardware
17:47.42tmztthat panic'd?
17:47.43xsachathats after it did a stat64 on dbus-daemon
17:47.45xsachayes
17:48.02tmztyou need to enable that
17:48.15xsachak, in the extended filesystems somewhere
17:48.29tmztbut it means your init has gotten further than I thought
17:48.34tmztwhat?
17:48.35xsachayay!
17:48.49xsachafurther than reading the config files?
17:48.58tmztprobably
17:49.22tmztunless you have an explicit mount command
17:49.31tmztno this makes sense
17:49.40tmztwas it killing init?
17:49.42xsachano mounting done
17:49.46xsachayeah killed init
17:50.01tmztnls normally won't panic
17:50.26tmztthe init is doing the commands in sequence
17:50.34tmztthen
17:50.45xsacha< CONFIG_VFAT_FS=y   < CONFIG_FAT_DEFAULT_CODEPAGE=437    < CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
17:50.53tmztone is failing and init segfaults
17:51.05xsachathose are things the new kernel has, the old one doesnt
17:51.09tmztjust run oldconfig now
17:52.03tmztit's not normal to require this much work to config the kernel
17:52.22xsachamm
17:52.30xsachaold config?
17:52.49tmztARCH=arm make oldconfig
17:52.49*** join/#htc-linux BabelO__ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
17:53.49xsachak
17:54.45xsachause that Image?
17:55.50*** join/#htc-linux surge (i=surge@pool-98-118-165-224.bflony.fios.verizon.net)
17:55.55xsachastrange, it didnt update my Image
17:56.36xsacha<PROTECTED>
17:58.01tmztare you make zImage or Image?
17:58.06xsachaImage
17:58.21tmztnow I get what you meant about the size
17:58.26tmztuse zImage
17:59.36xsachaumm.. make isn't compiling anything anymore :(
17:59.54xsachawas it meant to change?
18:00.25xsachait just copied Image to zImage with piggy.gz
18:01.25tmztwhat?
18:01.38tmztyeah
18:01.46tmztit compressed it
18:02.02xsachabut i mean what was make oldconfig for?
18:02.16tmztto fix your selects
18:02.25tmztdid it ask anything?
18:02.31xsachano
18:02.36xsachadoes this make a difference?< CONFIG_NLS_DEFAULT="iso8859-1"                                        --
18:02.38xsacha<PROTECTED>
18:02.38tmztok
18:02.50tmztmaybe
18:03.18tmztit loks like that caused the panic in that case
18:03.37xsachaill try again now
18:05.41xsachasuper fast boot time
18:05.50xsachanew kernel panic
18:06.14tmztwith zImage?
18:06.24xsachaafter stat64("/system/bin/playmp3"....           sh: can't access tty; job control turned off
18:06.27xsachayeah zImage..
18:06.31tmztok
18:06.42xsachawhich config is job control.. ? lol
18:06.44tmztwhat's the panic though?
18:06.58xsachaseg fault.. kernel panic: attempted to kill init!
18:06.59tmztyour are in a shell
18:07.13tmztcomment out playsound
18:07.28xsachawhere is playsound?
18:07.28tmztthat probably caused the segfault
18:07.39tmztnot sure
18:07.48tmztit's not in init.rc?
18:07.58tmztyour are in a shell
18:08.04tmztsorry
18:08.14xsachait stat'ed the following files: debuggerd, rild, app_process, mediaserver, playmp3...   PANIC! :)
18:08.26tmztyeah
18:08.46tmztso comment it out
18:08.58tmztoneshot probably
18:09.02xsachaoh it has a SIGCHILD (Child exited) before segfault
18:09.11tmztok
18:09.57*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
18:10.54xsachashould i comment out the whole playsound service or just 'oneshot' ?
18:11.09tmztthe whole lines
18:11.12xsachathis segfault is due to bad sound driver?
18:11.23tmztit doesn't work anyway
18:11.24tmztno
18:11.30xsachaoh ok
18:11.41tmztlack of qdsp I think
18:12.48xsachacool.. the trace went on forever... i saw a sort of splash screen maybe? like A N D R O I D?
18:13.04tmztgood
18:13.13tmztget the pxafb patch now
18:13.15xsachabut i got a new segfault with FAT: IO charset iso8859-1 not found
18:13.25tmztthen you will have android
18:13.50xsacha(i had just changed it from -1 to -2 like the other kernel had)
18:14.11tmztCONFIG_NLS
18:14.17xsachaand i thought that resolved the first error? :\
18:15.03tmztCONFIG_NLS_DEFAULT="iso8859-1"
18:15.07xsachak
18:15.23tmztCONFIG_NLS_CODEPAGE_437=y
18:15.23xsachathats what it was originally, yeah
18:15.29xsachaso ill set it back
18:15.33tmztthat works
18:15.42tmztmsdos codepage
18:15.58tmztoh
18:16.10tmztCONFIG_NLS=y
18:16.30tmztCONFIG_NLS_ISO8859=y
18:16.47xsachathe android splash screen is meant to be graphical like in the emulator? it's in text because need pxafb patch?
18:17.01tmztyes
18:17.14tmztsurfaceflinger won't start
18:17.44tmztCONFIG_VFAT_FS=y
18:17.54xsachayeah got all those :)
18:18.18tmztCONFIG_FAT_DEFAULT_CODEPAGE_437=y
18:18.36xsachayep :)
18:18.47tmztCONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
18:18.56tmztthat's all
18:19.06xsachabooting..
18:19.11tmztget the patch then
18:19.22xsachadamn!
18:19.41xsachafutex(0x40001004, FUTEX_WAKE, ....
18:19.42tmztthen you have to ad support for configuring ts
18:19.45xsachaseg fault
18:19.54tmztwhere?
18:20.03tmztstill panic?
18:20.06xsachayes
18:20.56xsachait stat mediaserver, then clock get time, then futex when it crashes
18:21.44tmzttake out strace
18:21.59tmztit might slow it down too much
18:22.21xsachak
18:24.23xsachanow i get A N D R O I D Kernel Panic - not syncing: Attempted to kill init!
18:25.07xsachaand i can see an error about the rtc device not existing
18:25.20tmztstart commenting thing out in init.rc
18:25.59tmztnot dalvik or whatever it is that starts android
18:26.20tmztthat's a warning
18:26.44xsachayeah no /drivers/rtc/htosys.c or something
18:27.11tmzthtc?
18:27.28tmztnone of that should be enabled
18:27.28xsachai dunno, it's back on winmo now
18:28.05xsachawell the thing after mediaserver is ... dbus
18:28.25tmztleave that
18:28.27xsachabluetooth
18:28.32tmztwhat else?
18:28.40xsachahcid
18:29.00xsachahfag, hsag,
18:29.08xsachaand lastly installd
18:30.02tmztcomment mediaserver
18:30.02j0b0evening
18:30.02tmztno shell process?
18:30.02j0b0my git is busted
18:30.02j0b0error: bad index file sha1 signature \ fatal: index file corrupt
18:30.02xsachashell? no
18:30.02tmztj0b0: you know this stuff?
18:30.03tmztah
18:30.03j0b0is there a way to repair it or to export all local branches and re-import in a new clone?
18:30.16xsachazygote is before mediaserver
18:30.20tmztyou can clone a local repo
18:30.49j0b0clone the corrupt repo into a new directory?
18:30.50tmztzygote is android, won't work without it very well
18:30.55xsacha:)
18:30.58tmztyeah
18:31.06j0b0will try. thanks
18:31.24tmztthen copy .git/config
18:31.29tmztand pull
18:31.46xsachai have 2: pxa2xx-mci.0:unable to stop clock.. think they matter?
18:31.57xsachait still panicks
18:31.59tmztnot now
18:32.17tmztremove bluetooth
18:32.20tmztcomment
18:33.15xsachaso the whole dbus?
18:33.20tmztcould be something in default.rc
18:33.28tmztnot yet
18:33.38tmztprop
18:33.55tmztif it's looking for qemud
18:34.09xsachaservice dbus /system/bin/dbus-daemon --system --nofork     socket dbus stream 660 bluetooth bluetooth     user bluetooth    group bluetooth net_bt_admin
18:34.32tmztcheck default .prop and see if qemu anything is 1
18:34.41tmztleave that
18:34.44xsacharo.secure=1 ro.debuggable=1 persist.service.adb.enable=1
18:34.53tmztthose are just groups
18:34.57tmztno
18:35.00xsachanothing else is in default.prop
18:35.22tmztmove the goldfish files off of sd
18:35.38xsachainit.goldfish.rc and the ones in /etc?
18:35.56xsachaone*
18:36.12tmztwhat's in there?
18:36.22xsachainit.goldfish.rc
18:36.31xsacha.sh in the /etc folder
18:37.00tmztname?
18:37.07xsachainit.goldfish.sh
18:37.23tmztwhat's in it?
18:37.55xsachastarts net, then qemud=`getprop.ro.kernel.android.qemud`
18:38.24xsachaand sets dns
18:38.24tmztadd back stace as strace -ff
18:38.29tmzttry again
18:38.46xsachado i keep the goldfish.rc in root?
18:38.52tmztI don't think it's running
18:38.58tmztmove that
18:39.07tmztsomewhere else
18:39.17xsachabut keep the shell file?
18:39.25tmztyeah
18:40.03xsachastrace -ff without the -p 1?
18:41.43tmztno
18:41.54tmztforgot we did that
18:42.08tmztadd -ff there
18:42.21xsachahmmm?
18:42.36xsachareads the man
18:43.20tmztwrong command?
18:43.24xsachaso just strace -ff &  ?
18:43.30tmztno
18:43.49tmztstrace -ff -p 1 &
18:44.04tmztit follows subprocesses
18:44.17xsachak, cause before we only saw what init did
18:44.38xsachaand output to tty0?
18:44.46tmztyes
18:45.38xsachaAHA!
18:45.56xsachawhere do i start..
18:46.13tmztsegfault
18:46.18xsacha.. /system/lib/libreference-ril.so (Permission Denied)
18:46.26xsachaheaps of files it cant find
18:46.41tmztdid I say to comment that?
18:46.42xsachatries to access mmcblk0p1p7, p8, p9
18:46.59tmztit will do that
18:47.40xsachathen p=428 does poll ( <unfinished ...> and then futex on pid = 1 resumes and SEGFAULT
18:48.14tmztwhat program?
18:48.33xsachacant tell
18:49.16tmztcheck man, include open, fork, exec, read, write
18:49.20xsachait's the one that searches for mmcblk0p1p7..
18:49.29tmztmountd?
18:49.35xsachait gets returned to by 429
18:49.42tmztcomment that
18:49.43xsachaand then all it does is check those
18:50.21tmztthis isn't 1.5 then?
18:50.24xsacha1.1
18:50.29tmztok
18:50.39tmztvold repla
18:50.44tmzt<PROTECTED>
18:51.21xsachathis?  service mountd /system/bin/mountd    socket mountd stream 0660 root mount
18:54.08xsachanow it panicks while reading some binary file
18:54.25xsachalicicui18n.so
18:54.29xsachalib*
18:55.55xsachapid=420 begins to read it, it gets SIGCHLD (child exited), then pid=420 begins to read again and it shows 4KB
18:56.26xsachathen it does a seek to -8 from end.. and then does a read where it segfaults
18:57.02xsachai dont know why it would seek to the end and then do a read
18:58.15tmztnormal trick
18:59.09xsachawouldnt it go over the end?
18:59.47tmztwe need to debug then
18:59.53tmztman gdbserver
19:00.25xsachatty0 --attach 420?
19:00.33xsachawhen 420 exists..
19:01.24tmztno
19:01.44tmztyou need a copy for the phone anyway
19:02.23tmztI think you can use it start a process and wait for the debugger to connect
19:02.45tmztbut we have a few issues here
19:02.58tmztyou can't debug init directly
19:05.02*** join/#htc-linux BabelO (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
19:05.14xsachahow do i connect to laptop?
19:05.35tmztplug in the usb
19:05.45xsachathatll work?
19:06.07tmztwe don't have an android function driver so we'll have to use g_ether
19:06.14tmztit should
19:06.53*** join/#htc-linux WigglerAway (n=james@92-235-224-158.cable.ubr12.stav.blueyonder.co.uk)
19:07.25tmztthe thing is crashing a service shouldn't bring down init anyway
19:08.07tmztnormally logcat will tell you the problem, what service is crashing
19:09.07xsachamm booting up angstrom to test all those devices right now
19:09.16tmztbut tge kernel is crashing and we don't have a chance
19:09.22tmztok
19:09.26tmztadd
19:09.54tmztDrivers Usb Gadget Network
19:10.00tmztand PXA
19:10.18tmztwill make it easier
19:10.56tmztangstrom should have the corect stuff in /etc/network/interfaces
19:11.09tmztbut check the ip
19:11.37xsachadrivers/usb/gadget/...
19:12.07xsachacant see any network or pxa
19:13.10tmztmenuconfig
19:13.36tmztdo you see gadget?
19:14.14tmztyou can check Kcondig in there though
19:14.37xsachamm no.. no gadget?
19:15.29tmztwhere?
19:15.34xsachaCONFIG_USB_GADGET i see in config
19:15.48tmztok, =y that
19:15.57tmztand do oldconfig
19:19.01xsachahmm?
19:19.07xsachait deleted the USB_GADGET i stuck in
19:19.44xsachathere was no CONFIG_USB_GADGET in Kconfig or my original .config.. it was in another machines defconfig tho
19:20.00*** join/#htc-linux marcin_ (n=marcin@chello089077185047.chello.pl)
19:20.02tmztdelete the is not set line
19:20.18xsachathere is no is not set line though
19:20.26tmztand add the new one-
19:20.31xsachaE486: Pattern not found: GADGET
19:20.54tmztadd it
19:20.56xsachashould i add a new entry to Kconfig?
19:21.02tmztno
19:21.04xsachacause when i add it to .config, make oldconfig deletes it
19:21.54xsachasacha@X ~/androidkernel $ make oldconfig     scripts/kconfig/conf -o arch/arm/Kconfig    #    # configuration written to .config    #    and it's gone :(
19:22.01tmztif you look at Kconfig it should say why
19:22.23xsachain Kconfig: E486: Pattern not found: GADGET
19:22.52tmztdrivers/usb/Kconfig
19:23.14xsachaE486: Pattern not found: GADGET
19:23.30tmztread the file
19:23.33xsachait's in drivers/usb/gadget/Kconfig
19:23.47tmztyes
19:24.11tmztwhich is why there's source line
19:25.20*** join/#htc-linux RoBaDo (n=RoBaDo@adsl-177-48-fixip.tiscali.ch)
19:25.54j0b0tmzt, after cloning the old local repo, all my branches are now remotes/origin/what-they-were.
19:26.21j0b0at least i can check them out and produce diffs, so nothing is lost
19:29.43tmztI haven't figured out why that is
19:30.09tmztif you look at the text files in .git it might make sense
19:30.34*** join/#htc-linux RoBaDo (n=RoBaDo@adsl-177-48-fixip.tiscali.ch)
19:31.00tmztI tink you can move them to branches as well
19:31.14tmzt.git/info
19:33.17xsachaok i think i have gadget working now
19:33.37tmztgood
19:33.54*** join/#htc-linux mib_pdtgvi (i=d4feb130@gateway/web/ajax/mibbit.com/x-a46d5e5c6b01ac32)
19:34.44xsachahmm but now i get: led-core.c:(.text+0x47720): undefined reference to `switch_set_state'
19:34.55xsachadont think i changed any led stuff
19:34.58j0b0that just contains 'exclude'. i think i will just manually export some diffs from the cloned corrupted repo and apply in a fresh clone. it feels safer
19:35.59tmztif you cat the branches in the old one you'll see they are sha1's
19:36.00*** join/#htc-linux puregenius (n=chatzill@brln-4d0ced34.pool.mediaWays.net)
19:36.21tmztit's simple and complex at the same time
19:36.58tmzta little like the internet and dns really
19:37.11tmztnames for numbers
19:42.56xsacha00:00:24.807155 open("/system/lib/libicui18n.so", O_RDONLY|O_LARGEFILE) = 3                   00:00:24.808475 lseek(3, -8, SEEK_END)  = 754908                               00:00:24.809376 read(3, "\0\0@\255PRE ", 8) = 8
19:43.36tmztit stopped ther again?
19:43.47xsachastill stops there, but that's what it is meant to do
19:43.51xsachaon mine it doesnt do that
19:44.26xsachaon mine it opens file, reads / sigchld exit, then it starts process again, reads from file, seeks, then reads, sigfault
19:45.18tmztif comment out mouuntd does it still panic?
19:45.27tmztwhat lib again?
19:45.34xsachayeah we commented out mountd before
19:45.39*** join/#htc-linux StarLite (n=nnscript@s55916ca6.adsl.wanadoo.nl)
19:45.41xsachato fix other problem
19:45.52tmztso it's another program?
19:46.00xsachalibicui18n.so
19:46.07xsachais file it tries to read
19:46.52tmztrun file on that
19:47.39tmztcan you dind out what program?
19:47.55tmzteven grep -ra if needed
19:48.03xsachaapparently /system/bin/runtime
19:48.20xsachawhatever that is
19:48.44*** join/#htc-linux tsdogs (n=tsdogs@net203-187-146.mclink.it)
19:48.45xsachai think it's init
19:49.48xsachalibicui18n.so: ELF 32-bit LSB shared object, ARM, version 1 (SYSV), dynamically linked, stripped
19:50.25xsachasame as all others
19:51.20tmztand strings |grep lib?
19:52.24xsachalibicuuc.so libicudata.so libc.so libstdc++.so libm.so libicui18n.so
19:53.12tmztwhat is runtime?
19:53.44xsachait's init i think
19:54.03xsachaother people have /system/bin/runtime instead of init
19:54.26xsachaanyway my kernel isnt compiling with gadget
19:54.38tmztis ini a symlink?
19:54.44xsachano
19:54.49tmzterrors
19:55.06xsachaled-core.c:(.text+0x47720): undefined reference to `switch_set_state'
19:55.16xsachain drivers/builtin.o
19:55.48xsachano idea how gadget affected leds
19:58.33tmztgrep GADGET .config , only pate the used ones here
19:59.02tmztdo you have CONFIG_INPUT?
19:59.14xsachayeah
20:00.22xsachaCONFIG_USB_GADGET_M66592=y   # CONFIG_USB_GADGET_PXA27X is not set          grr it keeps changing this!
20:00.48xsachaGADGET, DUALSPEED, SELECTED and PXA27X
20:00.54tmztis there one for 3xx?
20:00.57xsachano
20:01.16tmztthat should work yhen
20:01.28tmztcheck Kconfig for deps
20:01.32xsachaim thinking something to do with LEDs came u
20:01.41tmztrm drivers/builtin.o
20:01.51tmzttriggers
20:03.32xsachai disabled LED thing and now i get
20:03.38xsachapxamci.c:(.text+0x47720): undefined reference to `switch_set_state'
20:03.51xsachaseems a lot of things wanted this switch set state
20:05.56tmztCONFIG_SW?
20:06.18tmztgit grep that
20:06.30xsachaSWAP?
20:06.40tmztno
20:06.44xsachaswitch?
20:06.50tmztyes
20:07.03xsachadisabled
20:07.06tmztenable led
20:07.14tmztenable that
20:07.33xsachak
20:08.30*** join/#htc-linux MLM_ (n=mlvdmeid@meide.xs4all.nl)
20:08.44*** join/#htc-linux RBCS (n=Rbcs@adsl-177-48-fixip.tiscali.ch)
20:09.15xsachathat worked! :)
20:09.38tmztyay
20:10.39*** part/#htc-linux RoBaDo (n=RoBaDo@adsl-177-48-fixip.tiscali.ch)
20:11.57xsachahow do i test my touchscreen @ /class/input/input1?
20:13.19xsacha"setting pen detect pull-up to 8000 Ohms" hmm
20:16.10xsachamm /dev/input/uinput?
20:20.28*** join/#htc-linux RBCS (n=Rbcs@adsl-177-48-fixip.tiscali.ch)
20:23.36tmztBabelO: can you join #xda-devs ?
20:23.53tmztxsacha: sorry?
20:24.53tmztit appears to work
20:25.33tmztcat /dev/input/event1
20:25.39tmzttouch screen
20:27.52xsachaso it's a problem i dont have that dev?
20:28.01xsachai only have mice in /dev/input
20:28.52tmztignore that
20:29.23tmztls /sys/class/input
20:29.39tmztyou're missing evdev it looks like
20:29.52tmztbut ls anyway
20:29.58xsachaohh
20:30.01tmztit could be mdev
20:30.26xsachaINPUT_EVDEV?
20:30.45tmztBabelO: oh, wasn't sure, sorry
20:31.07tmztxsacha: yes
20:31.10BabelOtm:)
20:31.18BabelOtmzt: no problem
20:31.24xsachawell /sys has nothing in it btw
20:31.49tmztmount -t sysfs sys /sys
20:32.09tmztunless your missing that config as well
20:32.13xsachaaha
20:32.38tmztin which case you defconfig is very broken
20:32.57xsachamount worked..
20:33.14tmztit's not in /etc/fstab ?
20:33.40xsachathere is no fstab on android
20:34.00tmztI thought you where in angstrom
20:34.02xsachaim running busybox on android (instead of android)
20:34.08xsachayeah i switched :P
20:34.36xsachaangstrom didnt have one either though
20:34.39tmztuncomment that mount in init.rc
20:34.56xsachathere is no mount in init.rc :\
20:35.23tmztyour running init=/bin/sh ?
20:35.35tmztso no init at all
20:35.53tmztand no specials except the ones we made
20:35.55xsachayes
20:36.17xsachamm input1 is a folder
20:36.27tmztcat /sys/class/input/event1/dev
20:36.57xsachano dev
20:37.04xsachaoh event1
20:37.14xsachayou mean input1
20:37.32tmztcat /sys/class/input/event1/name
20:37.33tmztno
20:37.57xsachals /sys/clas/input   input0 input 1 mice
20:38.47xsachausing input 1, if i cat name i get: wm97xx touchscreen
20:39.20tmzt.config, INPUT_DEVICE or whatr evdev is
20:39.33xsachak
20:39.48tmztyour ts probably works
20:40.26tmztandroid won't work without some patches
20:40.38xsachak
20:40.48tmztzaurus android sjould have them
20:41.10paryeah thats my prob too i find myself moving over a bunch of stuff from angstrom to lenny
20:41.24tmztI have something else for you to try that doesn't though
20:41.42tmztpar: have any of your code still?
20:41.55tmztfor android on pxa
20:43.07xsachacompiled evdev in.. input still blank
20:43.44tmztwhich?
20:43.57xsachainpu_evdev
20:43.59paroh i never did any of that, i'm not a coder
20:44.17parsome guy nmaed ffetsomething or other did it.. i'll see if i can find it
20:44.27tmztpar: I mean do you have, remember how to patch, etc.
20:44.59tmztxsacha: sys or dev?
20:45.17xsachaoh dev.. it's in sys like you showed before
20:45.21parFbettag
20:45.23xsachacat dev gives 13:65
20:45.28xsachawhatever that means
20:45.33parand it was just Android 1.0
20:45.34tmztmknod c that
20:45.49tmztpar: looking for pxafb patch
20:45.52*** join/#htc-linux zycho (n=zycho@dslb-088-070-073-162.pools.arcor-ip.net)
20:45.58tmztnot userspave
20:46.24parhttp://forum.xda-developers.com/showthread.php?t=415665
20:46.28xsachamknod c.. what?
20:46.47partheres a rootfs.. i'm trying to see if there is a link for any of the code anywhere
20:46.58tmztmknod /dev... c major minor
20:47.28xsachayeah i got the dev and c part.. not the major and minor :)
20:49.13tmztmajor:minor
20:49.18*** join/#htc-linux lama_ (i=lama@netbsd.pl)
20:49.21tmztfrom dev
20:49.37par- took the Kernel from handhelds.org (2.6.21-hh20) with
20:49.37parhtcblueangel_defconfig
20:49.37par- patched it with http://android-on-n8xx.googlecode.com/files/linux-2.6.21_rx-34_androi...
20:49.37par<PROTECTED>
20:49.37parandroid.diff is for 2.6.23 and causes some trouble.
20:49.38par- activated Android specific settings and compiled it
20:49.40par- created the userland-img like in http://www.alextreme.org/drupal/?q=android_on_n810
20:49.42par- used haret to boot the kernel off the sd-card (mostly copied from
20:49.44parangstrvm)
20:50.09parwe can look at the patches he used
20:51.07parlooks like he mostly patched from the n810
20:52.24xsacha13, 65?
20:52.52xsachamy keyboard cant do numbers other than 0 and 1 :P
20:53.38parlook at fbettag's post here: http://tinyurl.com/m3qh8x
20:55.03parjeez, he's booting with an omap kernel? 2.6.21-hh20-omap1
20:55.35parprobably just says that cuz was never changed
20:55.50parCPU: XScale-PXA255 [69052d06] revision 6 (ARMv5TE), cr=0000397f
20:56.47parunfortunately none of that has anything about the framebuffer
20:57.07parand in fact the screen is all messed off even when you boot tht
20:57.48xsachaandroid loads?
20:58.37partry it.. just go to that tinyurl link i posted and make an sd card
20:59.29parloads but plenty of stuff is messed up and needs fixin
20:59.38parincluding the screen
21:00.15tmztxsacha: it's what telnet is for
21:00.58xsachamajor minor is 13, 65?
21:02.37tmztwhatever dev said
21:02.47xsachaohhhh
21:03.08tmzttry the n8x0 userland
21:03.22tmztyours seems broken
21:03.24xsachai read that post but looks like he didnt get it working?
21:03.50*** join/#htc-linux sdt555 (n=titus@147.145.40.44)
21:03.55*** part/#htc-linux sdt555 (n=titus@147.145.40.44)
21:04.01tmzttalk to solca in #android or look up nitdroid project
21:09.23parwell the ts doesnt' work.. navigation is by the dpad
21:10.48paran keyboard works
21:15.56parfound some stuff , including that patch here: http://alextreme.org/android/
21:16.22tmztit's omap though
21:16.39tmztwe can use that userland build
21:16.48tmztbut not kernel
21:16.53paryah
21:17.19tmztwe either need to use zaurus one or write it again
21:17.49tmztnot that hard, could even be faster on pxa310
21:18.30pari'm just looking at their patch
21:18.47parmostly its omap stuff
21:19.04parhe just used a kernel built from hh20 for ba
21:20.02tmztwhy?
21:20.42cr2looking for a wince expert now :)
21:21.05cr2wince programming, to be more accurate
21:22.17par+# CONFIG_ARCH_PXA is not set
21:22.25par+CONFIG_ARCH_OMAP=y
21:22.32cr2when i'm moving the stylus, what event does the window receive ?
21:23.16*** join/#htc-linux zycho (n=zycho@dslb-088-070-073-162.pools.arcor-ip.net)
21:23.36*** join/#htc-linux BHSPitLappy (n=BHSPitLa@unaffiliated/bhspitmonkey)
21:28.18cr2haha
21:28.21cr2WM_MOUSEMOVE The user moved the stylus while the tip was pressed to the screen.
21:28.22tmztcr2: window message?, #hpcdev might work, actuall talking in there now about bootloader
21:28.39cr2http://msdn.microsoft.com/en-us/library/ms924836.aspx
21:28.53cr2i have some (many) evil plans for haret
21:29.01tmztcool
21:29.08tmztitsme
21:29.14tmztgeneric atags
21:29.43tmztfull feature bidirectional protocol?
21:30.09tmztuspl launcher
21:30.17tmztdownload to ram
21:30.24cr2no, these are practical things. i'm thinking about evil ones
21:30.41cr2download to ram works already.
21:30.55tmztfrom host?
21:31.07cr2Kevin2 even started resume into boot
21:31.19tmztyeah
21:31.41cr2i don't know if librapi2 is functional enough
21:31.52tmztthere's room in xip area for something like softice apparently
21:32.04tmztit h  RapiInvoke
21:32.24cr2does it work ?
21:32.47cr2all these p* itsutils tools depend on it.
21:32.54*** join/#htc-linux dcordes (n=luke@unaffiliated/dcordes)
21:33.57tmztno idea, couldn't parse win32 headers enough
21:34.08tmztto make sane gnu structs
21:35.31tmztoh yeah, we need an autmatic bsp generator :)
21:35.42cr2ok, next wince question.
21:36.04cr2how to enumerate the windows ?
21:36.24tmztthere is an api
21:36.44tmztdon't know the name
21:36.47cr2i have a similar program working on x11, but windows programming is too hideous for me :)
21:37.05tmztcould be FindWindowEx
21:37.36cr2so i want to find a window from haret, and send this WM_MOUSEMOVE event
21:38.32cr2in 11 i'm sending XK_Right & such. but wince may miss the keyboard and key events.
21:38.42xsachatmzt: cat /dev/input/input1
21:38.50tmztno
21:38.50xsachaa(box)X   (twice)
21:39.04tmztevery time?
21:39.17xsachai can only do it once
21:39.39xsachathen random characters fly everywhere lol
21:39.45cr2The FindWindowEx function retrieves a handle to a window whose class name and window name match the specified strings.
21:39.46tmztI think you have the wrong device then
21:39.53tmztyes
21:40.07tmztand it should let you keep looking
21:40.08xsachaevent0/dev ?
21:40.23tmztkeyboard probably
21:40.59xsachaohhh
21:41.16*** join/#htc-linux lama (i=lama@netbsd.pl)
21:41.19cr2tmzt: Ex is not really needed
21:41.24cr2HWND FindWindow(
21:41.38cr2LPCTSTR lpClassName,
21:41.38cr2LPCTSTR lpWindowName );
21:41.45tmztyeah
21:41.55cr2tmzt: but how can i list all windows with names ?
21:42.12tmztyou have HWND
21:42.30cr2EnumWindows ?
21:42.32tmztsome other api must give you the title
21:42.38tmztoh
21:42.43tmztmaybe
21:43.22cr2GetWindow/CeGetWindow
21:44.02cr2HWND GetActiveWindow(void);
21:44.03*** join/#htc-linux cmonex (n=xy6091@ioz8tsz7bb.adsl.datanet.hu)
21:44.04cmonexhi
21:44.06cmonexparty?=)
21:44.12cr2LOL
21:44.33tmztmy fault,
21:45.03tmztit was the evil haret thing
21:45.12tmztnow win32 apis
21:45.31cmonex?
21:46.13tmztreading msdn, trying to figure out how to enumerate windows
21:47.04cr2i want to extend haret a bit, but it's quite some time ago that i've read Petzold's book :)
21:47.19cr2for win3.1 :)
21:47.37xsacharun win3.1 in dosbox, yay
21:49.24cr2cmonex: i want to have a programmable window screengrabber in haret.
21:50.35cr2to compare the data in my PNA with OSM.
21:51.32tmztthis is the evil thing?
21:51.55cr2xsacha: i wish it was possible to run barebones wince in qemu
21:53.19*** join/#htc-linux kolonibal (n=kll@cust-IP-31.data.3.dk)
21:53.55cr2tmzt: imagine a script
21:54.09tmztyeah
21:54.14cr2tmzt: that moves 1/2 width right, dumpfb, ...
21:55.03tmztor hook WM_UPDATE, grab the dc when it's done?
21:55.04cr2after that you have an atlas on the SD
21:55.45cr2fullscreen mode ?
21:55.47xsachatmzt: ok i did cat input1
21:56.05tmztsee I forget most the windows stuff I actually learned
21:56.07cr2dcordes: sleeping ?
21:56.09xsachawm97xx-ts 0-0:WM9713,WM9714: No IRQ specified
21:56.13xsachawhy would it think that?
21:56.18dcordescr2, no I'm fully operational.
21:56.38tmztit probes the i2c though?
21:57.10cr2dcordes: i think we forgot the adsp_5200.c file
21:57.25tmztyeah
21:57.26cr2tmzt: why not do 'dump pxa27x' first ?
21:57.28dcordesin which commit?
21:57.47tmztit's pxa310 if you mean xsacha
21:58.02cr2dcordes: in the last one. it's just a copy of adsp_6210.c, for now.
21:58.08tmztand it's crashed every device I've tried it on
21:58.11xsachai know the IRQ
21:58.22xsachai did dump and i got a bunch of values
21:58.49tmztbut does it want pen irq or the i2c one, or is there one?
21:58.53cr2tmzt: you must have strange devices :)
21:59.21cr2tmzt: the source is available. to parse everything by hand is pita.
21:59.43tmztI could use a wm_send feautre though
22:00.15xsachait says that no irq was specified.. so it doesnt think i gave it one
22:00.28xsachabut hang on!!
22:00.39xsachawhenever i touch the screen, all this mumbo jumbo appears on the screen
22:00.49tmztxsacha: look at driver source and find that message
22:00.52cr2tmzt: sendmesage(getactivewindow,...) ?
22:01.08tmztnot active window
22:01.13xsachathats a good sign right? that means it's working?
22:03.23cr2sendmessage/postmessage. evil :)
22:03.53xsachait says message about no specified irq, but touching the screen provides output
22:04.25cr2tmzt: http://www.tech-archive.net/Archive/VB/microsoft.public.vb.winapi/2007-04/msg00160.html
22:09.51xsachaif (!wm->pen_irq) dev_err(wm->dev, "No IRQ specified\n");
22:18.54dcordescr2, https://www.codeaurora.org/gitweb/quic/le/?p=kernel/msm.git;a=blob;f=arch/arm/mach-msm/qdsp5/adsp_6210.c ?
22:19.40*** join/#htc-linux Shinto (n=John@g227193193.adsl.alicedsl.de)
22:21.57cr2dcordes: no, the adsp_6210.c from the same 2.6.27 tree
22:22.05cr2but i think they are the same
22:22.28*** join/#htc-linux marcin_ (n=marcin@chello089077185047.chello.pl)
22:35.20dcordescr2, http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=commit;h=b7d0434ab2bbb4d52f38cd75355554f31f4ccaad
22:37.56cr2dcordes: thanks
22:38.03dcordesnp
22:38.37xsachatouchscreen works :D:D
22:39.55xsachaanyone know of a touchscreen console app?
22:44.38toerwe also need a couple of defconfig changes for the qdsp to even compile dont we
22:45.15*** join/#htc-linux surge (i=surge@pool-98-118-165-224.bflony.fios.verizon.net)
22:49.25dcordesxsacha, ts_test ? what do you want to do?
22:50.30cr2dcordes: can we do some changes to initrd eventually ?
22:50.58dcordessure. what's on your mind?
22:51.26cr2vodafone-de in /etc/ppp/peers
22:51.54cr2and to remove partition scanning. don't know where it's located though. and the ts_* tools
22:52.19cr2toer: the qdsp and rpc are not in defconfig ? hmm. you are right
22:53.26toerhttp://privatepaste.com/b41DPfCRbz
22:54.02cr2dcordes: a new patch ?
22:54.55cr2toer: i don't know how to test them in non-android environment. i'm not that so far with the gps rpc.
23:10.24dcordesI need faster internet. OE fetching takes so long
23:14.15tmztgit is still broken for me with htcraphael_defcofig
23:14.56tmzteven tried disabling CPUFREQ
23:16.54toermine hangs to its a long time since i tried to boot linux, looks like mine hangs at console hangover
23:17.22toerbut it vibrates
23:18.12dcordestmzt, what's the last known working commit for you?
23:18.15tmztit usually times out mmc
23:18.33tmztdcordes: trying to figure that out
23:20.12dcordesk
23:20.35tmztnot going very well
23:24.19tmztI have been able to get usb back but not smd1
23:24.23cr2toer: which phone do you have ?
23:24.57cr2tmzt: add a rootdelay, or boot with initrd and mount SD
23:25.09cr2tmzt: wtf is smd1 ?
23:25.32tmztthe mmc timeout isn't the prboblem
23:25.52tmztthat's only with a very long handover
23:26.31tmztthe channel maejrep set up for ppp data
23:27.46dcordescr2, what are you using for ppp data?
23:28.43tmztthe reason for that it couldn't be enumerated in smem for some reason
23:28.54cr2tmzt: smd1 is packet channel with the current code. do you really want it ?
23:28.54tmztso it's set up manually
23:29.17cr2dcordes: what do you mean ? cu+pppd, manually.
23:29.19tmztI've tried changing that, didn't help
23:29.43cr2tmzt: can it be made smd7 ?
23:29.54tmztif I could figure out what it was
23:29.56tmztyes
23:30.09tmztit wouldn't use for anymore
23:31.31tmztbut it would work
23:31.40tmztand diag is on 1
23:31.53tmztor should be I think
23:33.14cr2yes
23:33.35toercr2: raph100
23:33.46cr2raph100 is very g1 compatible, so it's better to stay this way.
23:34.04cr2toer: any success/failure with qdsp/rpc ?
23:34.47tmzthave figured out what packet means?
23:36.09toertried the diff from lavendert a couple of months ago which i guess are similar to whats in git
23:36.44toerno success though
23:40.17cr2toer: it was a "hello" server there.
23:40.21paris android booting and running on the raph yet?
23:40.53cr2toer: now the snd/adsp/audiomgr are added with right numbers.
23:41.00tmztyeah
23:41.09tmztconnect-utb.com
23:41.13cr2par: it was long ago. the question is if it's usable
23:43.50tmztcr2: can we properly init usb now?
23:44.04*** join/#htc-linux UnknownArtists (n=unknown@84.19.198.127)
23:45.09toercr2: ill try some tomorrow its getting late..
23:45.20toergood thing im on the late shift at work this week
23:46.21*** join/#htc-linux UnknownArtists (n=unknown@84.19.198.127)
23:50.32*** join/#htc-linux UnknownArtists (n=unknown@84.19.198.127)
23:55.42cr2good  night

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.