IRC log for #htc-linux on 20090621

00:21.43*** join/#htc-linux wooj (n=wooj@unaffiliated/wooj)
00:51.11*** join/#htc-linux dzo_ (n=dzo@121-98-128-127.bitstream.orcon.net.nz)
01:02.29*** join/#htc-linux rzk_ (n=rzk@daemonet.ru)
01:04.49*** join/#htc-linux wooj (n=wooj@unaffiliated/wooj)
01:27.08*** part/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821)
01:32.07*** join/#htc-linux gentooer (n=asdfsf@pool-72-90-171-202.nwrknj.east.verizon.net)
01:32.45gentooeranyone have any ideas on how to get around this bug: http://code.google.com/p/android/issues/detail?id=1937
02:27.30*** join/#htc-linux wooj (n=wooj@unaffiliated/wooj)
03:08.13*** join/#htc-linux j0b0 (n=jobo@12.35.60.99)
03:09.28*** join/#htc-linux mrmoku|away (n=mrmoku@ppp-93-104-40-85.dynamic.mnet-online.de)
03:52.44tmztcr2: did we find APPS RESET on 7x00?
03:52.58tmztif so we might be able to init usb properly
04:20.17*** join/#htc-linux droid001 (n=mc@p4FDCD45D.dip.t-dialin.net)
04:20.49*** join/#htc-linux jaSOnGg (n=IamSOG@218.19.240.106)
04:52.04xsachahey tmzt, see my youtube video? :)
04:52.50xsachai found this on web, do you think it helps? http://tomoyo.sourceforge.jp/cgi-bin/lxr/source/sound/soc/pxa/zylonite.c  Zylonite SoC Sound
04:52.55tmztno
04:53.08tmztwe aren't ready for sound yet
04:53.23xsachaoh ok
04:53.25tmztthat's probably in your tree though
04:53.56xsachait's not in my kernel at all.. not even in 2.6.30 kernel i looked in
04:56.07xsachaanyway i saw that there is apparently some zylonite 'accelerated' wm9713 driver, any idea what the difference would be from my normal wm9713 driver?
04:57.37xsachahttp://lwn.net/Articles/321387/ it's new too
04:58.17tmztno
04:58.21tmztni idea
04:58.37xsachaThis is a wm97xx extended touch driver supporting interrupt driven and continuous operation on Marvell Zylonite development systems (which have a WM9713 on board).
04:59.31tmztok
05:00.02tmztwhat happened with usb?
05:00.04xsachais it weird that the chip uses AC97 for touch events?
05:00.10tmztno
05:00.17xsachai still have no clue about usb
05:00.17tmztnot really
05:00.30tmztdid yo get a working rootfs?
05:01.18xsachano
05:06.10xsachaill try debian
05:08.29*** join/#htc-linux j0b0 (n=jobo@12.35.60.99)
05:09.27xsachatmzt: i have debian working
05:09.33xsachai get an error Failed to bring up usb0
05:10.10xsachado you know the username/password for lenny?
05:11.18xsacharoot/root, got it
05:16.02xsachavideo of android working here: http://www.youtube.com/watch?v=9xpEe_qWpEc
05:19.21xsachawhew, i thought i bricked my device! i did reboot in debian and it was stuck at samsung logo... i had to pull out batter
05:21.08*** join/#htc-linux skodde (n=skodde@unaffiliated/skodde)
05:24.02xsachatmzt: so what do i do on debian?
05:25.56*** join/#htc-linux hollo (n=hollo@3e6b7b2c.rev.stofanet.dk)
05:45.22tmztdebian?
05:45.38*** join/#htc-linux goxboxlive (n=goxboxli@140.84-48-184.nextgentel.com)
05:45.59tmztok
05:46.04tmztdmesg
05:46.40tmztsee if it detects when you plug in the usb
05:49.09xsachadmesg is spammed my pxamci things and i get this pxa2xx-mci: unable to stop clock all the time
05:50.20*** join/#htc-linux punkass (i=punkass@unaffiliated/punkass)
05:51.24xsachashould usb be plugged in when im booting or should i plug it in later?
05:53.22xsachado you want me to pastebin the dmesg?
05:55.29xsachadamn for some reason i only have mmc0: stuff in dmesg, repeated over and over and over
05:56.03tmztplugged when booting
05:56.17tmztthen unplug and replug and see what dmesg says
05:56.22xsachaok
05:56.49xsachamy dmesg seems to be full of mmc0: req done (CMD13): 0: 00000e00 5b590000 3cdc7f80 0a40400d mmc0: starting CMD13 arg d5550000 flags 00000015  PXAMCI: irq 00000004 stat 00002140
05:57.02xsachathis roughly 1000 times and i cant see anything else
05:58.36tmztwhich one is sd card?
05:58.50xsachammc0
05:58.59xsachai oly have one mmc slot
05:59.10tmztroot is one there?
05:59.23tmztyes, but wifi might be on mmc
05:59.45xsachayeah the rootfs is on there
06:01.16*** join/#htc-linux BHSPitLappy (n=BHSPitLa@unaffiliated/bhspitmonkey)
06:01.26xsachaseriously i think theres only that stuff in dmesg
06:04.19xsachayeah only mmc0 stuff
06:04.43xsachai piped dmesg in to a file and it seems it has only showed the end of dmesg (the last 10 000 lines or somethng)
06:05.15xsachaeven dmesg | head, it only shows mmc stuff
06:08.12tmztyou need to reboot
06:08.21tmztthe buffer only has so much space
06:08.41xsachawell the buffer was filled up in about 10 secs cause i did the dmesg 10 secs after boot
06:09.55tmzthave you chnaged the code?
06:10.11xsachanot that i know of
06:10.15xsachamci code you mean?
06:10.42xsachai commented out the line that prints "unable to stop clock" because it got so annoying
06:14.48*** join/#htc-linux hollo (n=hollo@3e6b7b2c.rev.stofanet.dk)
06:19.49xsachathe only change i can think of tmzt, is that i was using 2.6.27 before and now im using 2.6.29
06:21.13xsachalooking at kernel log there's been a few changes to pxamci since.. including one "fix NAND and MMC clock initialization"
06:21.41xsacha"Apparently, clk_get in pxamci will also fail for MCI2 on PXA310.but neither pxa3xx_nand nor pxamci supply 'con_id'."
06:22.15xsachathe changes were actually done in mach-pxa/pxa300.c though
06:23.33xsachaINIT_CLKREG(&clk_pxa310_mmc3, "pxa2xx-mci.2", NULL),      //where NULL used to be "MMCCLK"
06:24.42tmztodd
06:24.50tmztI don't really know
06:24.57tmztmaybe try 2.6.30?
06:25.16xsachathere isnt a 2.6.30 for android kernel yet
06:25.16tmztdon't worry about the android patches right now though
06:25.27tmzttheir coming
06:25.33xsachai think this is a regression and hasnt been fixed yet?
06:33.52tmztpossibly
06:35.32xsachacr2: To add to the amounting set of expected Android phones in coming time, Garmin has announced that they will stop making devices with their own operating system and instead switch to solely Android- and Windows Mobile-powered phones.
07:16.18*** join/#htc-linux Shinto (n=John@e181249195.adsl.alicedsl.de)
07:18.51*** join/#htc-linux JuNu_KN (n=chatzill@kons-5f714d76.pool.einsundeins.de)
07:57.53*** join/#htc-linux hollo (n=hollo@3e6b7b2c.rev.stofanet.dk)
08:02.15xsachahey palm released source code for webOS.. does that mean we can boot it now?
08:03.38xsachathey released source for every driver as well :P kernel is 2.6.24
08:06.36xsachathe ROM they use is downloadable too, http://palm.com/ROM
08:31.53tmztxsacha: they didn't release source for webos
08:32.07tmztkernel drivers and gpl user components
08:32.34xsachaoh..
08:35.32xsachai thought the source for webos kernel?
08:36.05xsachathese sites are misleading: http://stuff.techwhack.com/6810-webos
08:38.04xsachaoh they did release kernel source tmzt!
08:38.10xsachahttp://palm.cdnetworks.net/opensource/1.0.1/linux-2.6.24-patch.gz <-- all their patches to 2.6.24
08:40.47dcordes350299 lines
08:41.55xsachaso we can boot palm os right? i already have the webOS rootfs
08:43.15dcordesI'd like the device
08:43.24dcordeshow much is it?
08:44.49xsachawhich device? the pre?
08:45.11xsachano idea, it's US only and sprint only (and cdma only)
08:45.18dcordesuuuh
08:48.31tmztno, it's armv7
08:48.58xsachaoh damn
08:49.28xsachaand im guessing armv7 is very incompatible with armv5 then
08:50.56dcordesthey use qualcomm modem?
08:51.13dcordesconfig PALM_QC_MODEM_HANDSHAKING_SUPPORT
08:52.56xsachayes they do
08:53.08xsachaqualcomm gobi dual-CDMA/HSDPA?
08:57.37tmztyes
08:58.11tmztwe donqt have the gsm firmware and that's only if the rf components are actually there
09:00.12xsachafuture palm phones are gsm (castle?)
09:00.45xsachaand there is castle code in webos already
09:01.29tmztwe don't know what castle is
09:01.44xsachapalm eos
09:01.48xsachais real name
09:02.10tmztif your interested in webos, try #webos-internals
09:02.43xsachaeos will have 320x400 res, quadband gsm
09:03.03xsachawow so many people in that channel
09:05.31xsachatmzt: any reason why you couldnt port the iphone (similar processor and same resolution) to webOS? or some htc device?
09:05.50*** join/#htc-linux Squarc (n=Squarc@82-217-32-29.cable.quicknet.nl)
09:09.45xsachamsm7225 on the palm eos (armv6) to be released later
09:10.52xsachaand tmzt, isn't armv6 backwards compatible with armv5?
09:13.25tmztthe new one?
09:13.47tmztit is backwards compatible, not forward
09:14.00tmzteos won't be omap3?
09:15.08xsachait's a budget phone that is aimed to be $349 outright
09:19.15*** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146)
09:19.18Untouchab1ehi, is anyone in?
09:19.39xsachahi
09:19.49Untouchab1exsacha , could you help me with something really quick
09:20.16Untouchab1eI uploaded an android package last night but I cant seem to get it to download. I just wonder if this happens to others as well?
09:20.16Untouchab1ehttp://connect-utb.com/index.php?option=com_jdownloads&Itemid=68&task=view.download&cid=33
09:20.23Untouchab1esee if you can manage to start the download
09:22.05tmztwhat is it for?
09:22.12xsachafile not found
09:22.16Untouchab1edamn
09:22.21Untouchab1eok..
09:22.24Untouchab1eil sort it out
09:22.25Untouchab1elol
09:23.13Untouchab1etmzt, that package is nothing exiting, but I am putting one together that has the latest images from jobo and the kernel posted on XDA yesterday.. but since downloads suddenly doesnt work, I need to fix that first.. lol
09:23.43tmztkernel for what? raph/diam?
09:24.14Untouchab1eboth
09:49.47*** join/#htc-linux leobaillard (n=leobaill@leobaillard.org)
09:54.40*** join/#htc-linux nebi (n=nebi@217.142.147.19)
10:17.49*** join/#htc-linux pe7er (n=Adium@lpzg-4dbdcb79.pool.einsundeins.de)
10:17.56*** join/#htc-linux sxe (n=sxe@ip-62-143-85-196.unitymediagroup.de)
10:21.45*** join/#htc-linux MethoS (n=clemens@host-091-097-240-129.ewe-ip-backbone.de)
10:52.32xsachacastle gsm/umts firmware is on rom, so it likely support gsm
10:56.36*** join/#htc-linux dcordes_ (n=luke@unaffiliated/dcordes)
11:10.44*** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo)
11:10.52*** join/#htc-linux sxe_ (n=sxe@ip-62-143-85-196.unitymediagroup.de)
11:13.48*** join/#htc-linux kiozen (n=oeichler@p54921668.dip0.t-ipconnect.de)
11:15.00*** join/#htc-linux marex (n=marex@thor.hackndev.com)
11:16.26*** join/#htc-linux Tinyboom_ (n=nahh@62.84-49-90.nextgentel.com)
11:37.32*** join/#htc-linux pe7er (n=Adium@lpzg-4dbdcb79.pool.einsundeins.de)
11:37.43*** part/#htc-linux pe7er (n=Adium@lpzg-4dbdcb79.pool.einsundeins.de)
11:45.29*** join/#htc-linux PoohbaLT1 (n=BlkPoohb@c-69-141-71-249.hsd1.nj.comcast.net)
11:46.35*** join/#htc-linux Moku (n=John@e181249195.adsl.alicedsl.de)
11:48.45*** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo) [NETSPLIT VICTIM]
11:48.45*** join/#htc-linux droid001 (n=mc@p4FDCD45D.dip.t-dialin.net)
11:48.46*** join/#htc-linux cmonex (n=xy6091@p3o7a5a23b.adsl.datanet.hu) [NETSPLIT VICTIM]
11:48.46*** join/#htc-linux madCoder- (n=madcoder@c-71-225-60-178.hsd1.pa.comcast.net) [NETSPLIT VICTIM]
11:48.46*** join/#htc-linux Treibholz (n=treibhol@sozial-inkompetent.de) [NETSPLIT VICTIM]
11:48.46*** join/#htc-linux TeringTu1y (n=Maarten@195-241-125-243.ip.telfort.nl)
11:48.46*** join/#htc-linux PoohbaLT (n=BlkPoohb@c-69-141-71-249.hsd1.nj.comcast.net) [NETSPLIT VICTIM]
11:48.46*** join/#htc-linux Dindon (i=Euroserv@193.27.79.0) [NETSPLIT VICTIM]
11:48.46*** join/#htc-linux Perkka (n=perkka@ua-83-227-207-92.cust.bredbandsbolaget.se) [NETSPLIT VICTIM]
11:49.02*** join/#htc-linux zycho (n=zycho@dslb-088-070-242-216.pools.arcor-ip.net)
11:49.02*** join/#htc-linux cmonex (n=xy6091@p3o7a5a23b.adsl.datanet.hu)
12:01.55Treibholzis 1MB/sec readingspeed from the SD if a HTC-Universal OK? or should I buy a faster card?
12:05.04*** join/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821)
12:13.41xsachaouch!
12:18.41*** join/#htc-linux cr2 (n=cr2@ip-77-25-188-78.web.vodafone.de)
12:19.56cr2hi
12:20.17xsachahi
12:20.40cr2where is the pH5 kernel git llocated ?
12:20.54xsachacr2: To add to the amounting set of expected Android phones in coming time, Garmin has announced that they will stop making devices with their own operating system and instead switch to solely Android- and Windows Mobile-powered phones.
12:21.12xsachabye nuviphone?
12:21.34cr2xsacha: watertight phone ?
12:21.54cr2otherwise i don't see a point in bying garmin phone
12:24.21tmzthey
12:24.59tmztcr2: did we find APPS RESET on 7x00?
12:25.22cr27x00 ?
12:25.35tmztmsm7xxx
12:25.54tmztit's in the uboot patch used to fully reset usb
12:26.21*** join/#htc-linux luben (n=jasv@87.223.66.65)
12:27.45*** part/#htc-linux luben (n=jasv@87.223.66.65)
12:29.24cr2tmzt: i have added everything to wiki
12:31.34Squarctmzt: any new features to test on the diam yet?
12:32.11tmzthttp://forum.xda-developers.com/showthread.php?t=517745
12:32.20tmztabout audiopara on g1
12:32.27tmztoh yeah, wiki
12:32.45tmztbut if we have it can we actually reset usb and ulpi?
12:38.15xsachayeah
12:39.18*** join/#htc-linux BabelO_ (n=fcr@unaffiliated/babelo)
12:44.15tmztdon't see it in wiki (mem map), cr2
12:45.29tmztqsd8x50 - 0xa8600214
12:56.09*** join/#htc-linux zycho_ (n=zycho@dslb-088-070-242-216.pools.arcor-ip.net)
13:05.30*** join/#htc-linux luben (n=jasv@87.223.66.65)
13:06.30tmztok, in mt9t013 driver we have HWIO APPS RESET ADDR defines as MSM CLK CTL BASE + 0x210
13:06.45tmztis that actually the adsp reset?
13:09.08*** join/#htc-linux alkdevil (n=alkdevil@p5B0A825B.dip0.t-ipconnect.de)
13:09.14*** join/#htc-linux sxe (n=sxe@ip-62-143-85-196.unitymediagroup.de)
13:09.24tmztenabling camera makes 210 0
13:09.29tmztnormally it's 1
13:10.06tmztlet me try playing sound, can I do that from haret?
13:10.49*** join/#htc-linux pe7er (n=Adium@f053195139.adsl.alicedsl.de)
13:11.36*** part/#htc-linux pe7er (n=Adium@f053195139.adsl.alicedsl.de)
13:11.59tmztno, stayed 1
13:12.21tmztit could be vfe
13:13.19*** join/#htc-linux mokolade (n=mokolade@85.221.112.173)
13:13.33tmzton raph500 - pd a860000 0x200
13:13.57tmztvalues from 0-0x106
13:14.01tmztthen zeroes
13:18.30*** join/#htc-linux wirelessdreamer (n=dreamer@chrobd01.vailsys.com)
13:36.15lubencan anyone tell me where can I find a linux for a HTC Touch XL (omap850 inside) also known as Elfin? (thx)
13:37.08lubenI've been looking for it but Linwizard doesn't work [ windows mobile doesn't do either ;) so I'm looking for a alternative ]
13:38.21cr2tmzt: MSM_CLK
13:38.31tmztyeah, looking there
13:38.55tmztluben: linwizard should work, it may just be you lcd is not supported
13:39.39tmztcr2: trying to follow wiki, do you know where pcm buffers should be?
13:39.45cr2tmzt: there was an online script by ali1234 to calculate the lcd params for omap850
13:40.02tmztyeah
13:40.15cr2pcm buffers ?
13:40.22*** join/#htc-linux pH5 (n=ph5@e178226191.adsl.alicedsl.de)
13:40.28tmztI think it just doesn't detect one of the lcd versions
13:40.52tmztor mp3 for adsp, trying to see where in smem or wherever they are supposed to be
13:41.06cr2http://www.htc-linux.org/wiki/index.php?title=RaphaelMemoryMap
13:41.09tmztbut I think windows media use pcm
13:41.19tmztyeah, that's where I'm looking
13:41.24cr2search for pcm
13:41.35*** join/#htc-linux MethoS- (n=clemens@host-091-097-243-049.ewe-ip-backbone.de)
13:44.24tmztno data
13:46.11tmzt0x01ffc200
13:46.33*** join/#htc-linux pe7er1 (n=Adium@f053195139.adsl.alicedsl.de)
13:53.39cr2tmzt: i think it's not really necessary when you boot from wince. kaiser works with rpc-only
13:53.55*** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix)
13:54.25tmztaucoustic? that's not what I'm working on
13:54.59tmztI wanted to see if we could reset the hardware after starting linux, at least partially
13:57.12*** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix)
14:03.35*** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo)
14:05.33*** join/#htc-linux stefan_schmidt (n=stefan@p5B036ECF.dip.t-dialin.net)
14:10.03lubentmzt: how can i avoid the frame buffer issue?
14:11.17lubenis there any binarie ready to be used on the htc elfin?
14:12.23lubenwhen I try to run it I get a "No filesystem could mount root, tried: ext2 romfs Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)".
14:12.23lubenAny idea?
14:16.51cr2luben: it's not so easy to say
14:17.09cr2luben: the lcd issue can be fixed
14:17.27cr2luben: are you using the wizard kernel ?
14:18.38*** join/#htc-linux pleemans (n=toi@32.199-78-194.adsl-fix.skynet.be)
14:19.12xsachatmzt: would my device get usb detect gpio if i plugged in headphones?
14:19.27xsachabecause headphones, usb and charge go through same port?
14:19.46lubencr2: I don't know what "wizard" kernel is. (Is a specific release of Linwizard?)
14:20.39cr2luben: you boot linwizard kernel/whatever ?
14:20.43stefan_schmidtxsacha: Just to cross-check. UDC works on your i780? Means you can ssh into the device using the ethernet gadget?
14:20.56cr2luben: ask miknix about linwizard
14:21.24xsachastefan_schmidt: no, but i dont know why not
14:21.53stefan_schmidtxsacha: oh, to bad. I thought it worked for you. Does not work here either on the i900
14:23.00xsachabut you dont have any settings for it on i900 yet
14:23.05xsachahave you tested it?
14:23.32lubencr2: thank you for the info
14:23.36miknixluben, are you running linwizard?
14:23.46lubenmiknix: yes I do
14:23.52lubenbut I get a kernel panic
14:24.07luben"No filesystem could mount root, tried: ext2 romfs Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)"
14:24.17stefan_schmidtxsacha: I hoped that the setup from wm would keep working.
14:24.28xsachaoh
14:24.37stefan_schmidtAnyway, have tu run now. My brothers birthday party.
14:25.11lubencr2: is there other linux working on a HTC Touch XL (Elfin)?
14:25.38miknixluben, there is only one linux
14:25.42xsachathat might be working
14:25.57xsachait stays connected to eth1 if i boot to android with activesync in
14:26.05lubenmiknix: you are right (sorry)
14:26.08miknixwhat are you trying to pass as a initrd?
14:26.17miknixext2 image?
14:26.22xsachathat detection doesnt seem to working for when i pull it out/plug it in
14:26.23lubeni should asked: is there any other linux distro?
14:26.26luben:)
14:27.11miknixif so, check if ext2 is builtin in the kenrel
14:27.30miknix(if it is linwizard, it should though)
14:27.56lubenI'm using this files http://forum.xda-developers.com/showpost.php?p=2764719&postcount=111
14:28.10lubenhow can i check if ext2 is builtin?
14:29.34luben(sorry, I'm a linux user for a few years but i'm only an average user)
14:32.43lubenmiknix: I'm trying to pass initrd-android because I want to achieve this http://avatar21.superihost.com/images/elfindroidgz2.jpg
14:33.05lubenis it possible?
14:33.14lubenshould it work?
14:33.33miknixthere was some people that could run android on the htc wizard
14:33.38miknixbut it was slow like hell
14:33.42xsachais that android? looks weird :P
14:34.53lubenis there any other option?
14:35.03xsachagentoo? debian? :P
14:35.03luben(i want to remove wm 6.1 from my pda)
14:35.16lubenI use lenny on my laptop
14:35.24xsachayou can have lenny on your phone too
14:35.42lubenbut could I send sms and made phone calls :D ?
14:35.58xsachahmmm dunno if they have any program for sms/calls
14:36.27xsachasome people have sim cards in laptop right?
14:36.44miknixluben, http://dev.gentoo.org/~miknix/gpe.png
14:37.09xsachabut no calls? :P
14:37.31cr2miknix: lol. "android slow as hell"
14:37.36lubenok
14:37.54lubenmiknix: looks great but can i use it as a PHONE also?
14:38.02miknixcr2, not sure if hell is slow.. but ..
14:38.36cr2miknix: wince on raph is really slow as hell
14:38.41xsachaone in miknix picture looks like it wouldnt be slow
14:39.08miknixhow can you tell if something is slow from a picture?
14:39.12cr2miknix: but for the performance, java will be my last choice ;)
14:39.52miknixcr2, my last choice too
14:40.09cr2xsacha: gradient color ?
14:40.33miknixspecially when the little omap850 cpu has to do all the graphical rendering on android
14:41.08miknixxsacha, that picture is not android
14:41.13xsachai know
14:41.17miknixah ok
14:41.28xsachaim saying it looks like it would be fast on his phone
14:41.29miknixGPE runs pretty fast actually
14:41.31cr2miknix: why did you use .bdf fonts ?
14:42.00cr2miknix: and not the most pleasing for the eye ones :)
14:42.16miknixgpe runs faster from the SD card than wm5 from the flash
14:42.46miknixcr2, hehe, they take less storage :)
14:43.21xsachasome people have faster sd cards than flash
14:43.28lubenmiknix: if i use your zImage (http://dev.gentoo.org/~miknix/zImage-linwizard) in my htc elfin should it work?
14:43.42xsachathats just the kernel though
14:43.49lubenwhat else do i need?
14:44.02miknixluben, wait, I'm building one for ya
14:44.41lubenmiknix: i'm using haret for linux boot
14:45.09luben(until i get it working i prefer avoid sd formating ;) )
14:46.26cr2miknix: linload.exe ?
14:47.03miknixlinload.exe?
14:47.16miknixluben, http://tinderbox.dev.gentoo.org/embedded/linwizard/linwizard-20090621.bz2
14:47.41miknixcr2,  never tried it
14:48.11miknix<PROTECTED>
14:48.26cr2ok
14:48.36cr2but it's ompa850-specific
14:49.23miknixindeed
14:49.23lubenomap850 ;)
14:49.24lubenmiknix: i've got it
14:49.39lubenthere is only a file inside?!?
14:49.47miknixits the kernel
14:49.57lubenzimage?
14:50.00miknixy
14:50.22miknixI have to finish something now, I'll be back later on
14:50.39lubenmiknix: thank you very much for your time
14:50.53lubenas soon as i try it i tell you what happens
14:56.23*** join/#htc-linux pOH9 (n=ph5@e178217086.adsl.alicedsl.de)
14:58.38cr2pH5: hi. i'd like to compile your 2.6.30 kernel. what was the git link ?
15:00.47pH5hi cr2
15:01.05pH5git://git.linuxtogo.org/home/ph5/kernel.git, branch dev
15:01.22cr2thanks
15:14.52Elleoodd, if I set the RAMADDR so that the kernel gets written in to the VRAM buffer it passes the CRC check (but corrupts the display and dies horribly when trying to load)
15:15.13Elleono idea why writting it elsewhere in memory causes it to become corrupted and fail the crc check :/
15:16.29cr2Elleo: on what cpu ?
15:16.39Elleos3c6410
15:16.48cr2hmm
15:16.55cr2something new :)
15:17.14Elleoyeah, laforge had it booting okay with a slight variant of this phone (the dx900 instead of the m900)
15:17.21Elleobut I'm not having much luck so far
15:17.31cr2it was a problem with ohci dma before.
15:18.06Elleocould easily be that; I'm not able to shutdown two of the dma controllers at the moment
15:18.21Elleoattempting to read/write to them in anyway causes the machine to lock-up
15:18.30cr2can you 'pd/pwf' the first megabytes of ram, and compare the dumps ?
15:18.50Elleocompare the dumps between the dx900 and the m900?
15:19.01cr2Elleo: no, the sdram dumps
15:19.13cr2Elleo: do you know the wince memory map for it ?
15:19.50cr2is there a cache flush haret routine for this cpu ?
15:19.50Elleonot really; I'm not massively familiar with wince or haret appart from the odd bits of poking I've done in the last few days (and a small bit of fiddling on an htc universal years ago)
15:20.26cr2yeah, htc universal had the ohci dma problem.
15:21.12Elleowell, there's currently code that tries to flush the dma controllers by shutting them down (during boot) if that's what you mean?
15:21.34Elleobut I can only get it to actually shutdown the first 2 controllers, the second 2 cause it to crash
15:21.34cr2no, the cpu I/D caches
15:21.56Elleoah, don't think so then;
15:22.19cr2you may also check where these DMA controllers are copying the data
15:22.24Elleowhen would that sort of thing happen? mostly I've been poking at the hardware shutdown stuff performed during boot
15:23.11cr2check other cpus
15:23.37Elleooh hang on,
15:23.52Elleoit's setting flushCache = cpuFlushCache_arm6; so I'm guessing it's using some generic arm6 cache flushing?
15:24.01Elleofrom arch-arm
15:24.16cr2yes
15:25.06*** part/#htc-linux luben (n=jasv@87.223.66.65)
15:35.18tmztmiknix: you're working with pxa3xx now?
15:35.59miknixtmzt, not really, why?
15:36.38tmztxsascha is having trouble getting usb client to work apparently a regression in 2.6.29
15:39.46xsachano thats not the cause tho
15:39.57*** join/#htc-linux kiozen (n=oeichler@rgnb-5d87de2e.pool.einsundeins.de)
15:39.58xsachait's just flooding my dmesg with pxamci stuff
15:40.26*** join/#htc-linux nebi (n=nebi@217.142.147.19)
15:41.22*** join/#htc-linux BabelO (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
15:47.00*** join/#htc-linux fnord_ (n=fnord@24-151-90-116.static.nwtn.ct.charter.com)
15:55.37miknixisnt she beautiful ? http://miknix.homelinux.com/cool-plants/mimosa_pudica-20090621.jpg
15:57.57xsachai dont see anything.. octron?
15:58.03*** join/#htc-linux Echo31 (n=olivier@mir31-4-82-240-194-54.fbx.proxad.net)
15:58.20miknixlol
15:58.38miknixthey are good dvd-rw btw
16:03.28Echo31Hi all
16:11.01Echo31pH5: Hi . How can I provide you with the athena code to merge with the magician branch and to check it?
16:11.43pH5hi Echo31
16:12.23pH5most convenient would be patches that can be applied with git-am.
16:16.16Echo31pH5: what is the original version to create the patch?   kernel 2.6.30-rc4 or later ?
16:17.05*** join/#htc-linux LTxda (n=anon@unaffiliated/ltxda)
16:19.18pH5Echo31: Doesn't matter. The devel branch of Eric Miao's pxa tree would be the best, but anything recent from mainline is fine with me.
16:26.00Echo31pH5: Do you want a code simple or clean because it is a code with a lot of desactivated code ?
16:29.42pH5Echo31: clean :) makes it much easier to review and get it reviewed for mainline inclusion.
16:32.50pH5When I have junk that I want to keep, I always just remove it, commit, re-add it back on top (with git revert) and then squash the removal commit with the commit before.
16:35.02*** part/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821)
16:36.09Echo31ph5: Ok. I have already written a athena patch from 2.6.30-rc4.
16:37.04*** join/#htc-linux wooj (n=wooj@unaffiliated/wooj)
16:37.36marexpH5: hi, long time no see ... how's stuff going ?
16:37.50marexpH5: I hope I can push the uart on/off patch
16:38.14pH5hi marex
16:38.41pH5right now I'm trying to find out why mainline doesn't recognize magician's strataflash.
16:39.50marexpH5: oh ... I'm in similar sh*t now
16:40.16marexI got hw donation (3 * palmtx) and they want me to prepare flash driver and reflash it with linux
16:40.40marexthe problem is palm put two different kinds of chips on TX
16:41.28marexone kind of TX has intel 28F640J3 (flash) and another has MX E064033 (probably macronix, but I have no idea - no info on their page about anything with even similar part ID)
16:41.52marexmoreover the Exxxxxx chip can't be detected by CFI or JEDEC probe (it might be ROM)
16:42.13marexhow the hell am I supposed to reflash a ROM?!
16:43.00woojmagic, of course.
16:43.04woojsacrifice two sheep
16:43.06pH5I don't believe that's a ROM.
16:43.07woojdo the chant
16:43.09woojetc.
16:43.24pH5Still, magic nonstandard NOR isn't much better at first...
16:43.56marexpH5: well what's interesting is the PCBs with intel strataflash and that MX stuff both have the same P/N
16:44.07marexso those two chips are probably pin compatible
16:44.26*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
16:44.36marexpH5: hm ... what is it then ? some custom-made flash ?
16:45.47*** join/#htc-linux sxe (n=sxe@ip-62-143-85-196.unitymediagroup.de)
16:45.54marexI cant find a datasheet to it
16:46.23marexbtw. similar chips (E061433 iirc is in PalmTE2 and E032233 is in PalmZ71)
16:46.30marexI wonder what that means
16:47.05marexmaybe someone rolled a custom ROM chip preflashed with palmos for Palm
16:47.32marexmaybe macronix - but since it's custom, there's that weird type-id on it
16:48.15marex(though I'd be really expensive to make macronix prepare a custom chip for them)
16:48.20marexjeez :-C
16:48.42marexpH5: btw what's the issue with magic NOR ?
16:49.39pH5all cfi probes fail
16:49.55pH5adding some debug printks right now to compare with hh.org kernels
16:50.24marexah ... that's weird ... are you using the pxa2xx-flash driver?
16:50.53pH5physmap
16:51.12cr2marex: hp used mask rom for wince. but it's all <2000
16:51.44marexpH5: I see ... is there any difference between those two ?
16:51.53marex(I tried both and uboot on TX - no luck)
16:52.11cr2Echo31: i'm charging the athena now :)
16:52.14marexcr2: TX is pxa27x - should be >2004
16:52.29marexcr2: do you have any more info about those mask roms ?
16:52.47cr2marex: that's why i don't think it's rom
16:53.20marexcr2: maybe they wanted to make sure you don't reflash it
16:53.36marexcr2: the problem is, all the CFI and JEDEC probes fail
16:53.39cr2marex: where is is mapped ?
16:53.46marex0x0
16:54.08marexif I try the intel detect sequence, I just get contents of the memory if I read back
16:54.22cr2ok
16:54.38marexcr2: it's a memory the CPU boots from
16:55.00cr2garmin used intel NOR
16:55.02marexI assume if I write 0x90 to 0x0 and then read from 0x0 and 0x1, I should get the IDs, right ?
16:55.16*** join/#htc-linux zatix (n=zatix@220.Red-81-39-20.dynamicIP.rima-tde.net)
16:55.31cr2it should work
16:56.11marexwell I get the contents of 0x0
16:56.16*** part/#htc-linux zatix (n=zatix@220.Red-81-39-20.dynamicIP.rima-tde.net)
16:56.17marexthat's in that memory
16:56.25marexnot a response
16:56.42Treibholzhmm, e2fsprogs-libs doesn't want to build in OE...
16:56.47marexit really seems to me that chip has no internal logic - it's like a ROM
16:58.25cr2marex: where there any rom updates for this device ?
16:58.59marexcr2: no, nothing
16:59.21pH5marex: any flashing code in the bootloader?
17:00.13marexnothing I know of
17:00.21cr2pH5: you added hima support too ?
17:04.39pH5no, I didn't
17:04.59cr2<PROTECTED>
17:05.29cr2<PROTECTED>
17:05.30cr2<PROTECTED>
17:05.32cr2<PROTECTED>
17:05.33cr2<PROTECTED>
17:05.35*** join/#htc-linux pe7er (n=Adium@f053195139.adsl.alicedsl.de)
17:06.21pH5hm.
17:07.50pH5what tree is that?
17:08.17pH5The mainline himalaya code was submitted by Zbynek Michl.
17:09.01cr233d9e97ee4712e06ff3e8db8b1d76f8b55935624                branch 'magician' of git://git.linuxtogo.org/home/ph5/kernel
17:09.44cr2i've never lloked at mainline code in the last years.
17:10.02marexyea ... Zbynek Michl ... I helped him cleaning it up
17:10.09marexhe commited it and ran away
17:10.15pH5ah, ok. that branch is old, don't use it.
17:10.19marexhe won't maintain it which is a pity
17:10.28pH5should clean up the ltg repo some time
17:10.33cr2ok
17:11.15cr2hehe. 10 branches there :)
17:11.33pH5hmm, there's still a partial ov9650 driver in that branch :)
17:11.51xsachamy touchscreen just stopped working, very weird. i dont believe i changed anything regarding touchscreen. android boots up, i touch the screen once (it works), then i can never touch again
17:11.53marexpH5: I had this talk with bluelightning today about how George France and RMK has a fight back in 2000 resulting in linux-hh ... so it seems like we might finally get rid of linux-hh soon?
17:12.27marexxsacha: maybe interrupt handler breaks something and doesn't retrigger the irq
17:12.47xsachayes i saw complains about touchscreen irq being null or something in console
17:13.01xsachahow could this be caused?
17:13.33cmonexhi cr2
17:13.42cmonexhow much do you know about topaz yet ?
17:13.54cr2cmonex: nothing
17:14.23cmonexwell ok just got this interesting issue with a specific nand chip on it
17:14.37cmonexit can come with samsung hynix etc... the 512mb versions of course
17:14.47cmonexif it has hynix chip that can be really weird
17:15.01cmonex(same chip was in previous htc's but no problem)
17:15.07cr2ok
17:15.22cmonexwhen you boot an im
17:15.24cmonexer
17:15.30cmonexwhen you boot a bootloader or whatever from WM on it
17:15.45cmonexif it has hynix chip the setup in one of the config registers gets fucked
17:15.54cmonex(then it becomes unable to read or write nand)
17:16.24cr2cmonex: is this chip in the wiki list ?
17:16.29cmonexI dont know the cause yet, the workaround is working
17:16.34cmonexchip is not new, raphael already had it
17:16.39cmonexbut problem is new :)
17:16.56cmonexgive me the wiki list
17:16.59cmonexand i'll tell you which chip it is
17:17.06cmonex(cant recall from memory but i can recognize it)
17:17.09cr2looking
17:17.32cmonexnevermind, found it in spl code
17:17.39cmonexhynix_h8BES0UQ0MCP
17:17.46cmonexthat's just the hynix chip with 512mb flash
17:17.48cmonexnot new at all
17:17.54cr2http://wiki.xda-developers.com/index.php?pagename=MSM_NANDID
17:17.58cmonexok see above
17:18.06cmonexit's listed
17:18.48cmonexother topazs have samsung_kby00n00hm, and it is fine
17:18.54cmonexonly hynix_h8BES0UQ0MCP gets the issue
17:19.04cmonexit'd be nice to know the cause, even though I have a working workaround
17:19.27cmonex(simply setup the config register again with the right value, at the right time, before it's too late :) )
17:19.45cr2hmm. really weird
17:20.28cmonexbtw why arent all the columns named in the wiki?
17:20.57xsachahow would i bind a specific gpio to one key?
17:21.10xsachalike 'W'?
17:21.43cr2cmonex: i forgot to name some of them, and for others i don't know the meaning
17:21.48marexxsacha: you cant bind it - it's hardwires
17:21.51marex*hardwired
17:21.59marexcr2: so you finally think it's a ROM ?
17:22.03marex(in TX)
17:22.19cr2marex: non-wince is difficult
17:22.23xsachai mean when gpio is a certain value, make keypress event?
17:24.02marexxsacha: you just request an interrupt there
17:24.07cmonexcr2 :
17:24.14marexxsacha: request_irq()
17:24.18cmonexmind me editing the wiki them with column names?
17:24.21xsachak
17:24.22cmonexthen*
17:24.35marexcr2: hm ... and noone knows anything
17:24.43cmonexthe first one is total number of blocks the second one is number of pages in one block
17:24.45cr2cmonex: why not ? it's that wiki is for
17:25.08cmonexok just asking if i'm correct :)
17:25.10cmonexwith the names
17:25.27cmonexand then the next not named block is full pagesize (with extra data included)
17:25.33cmonexthe rest no idea :)
17:26.12cr2sounds reasonable
17:26.17cmonexok
17:26.40cr2the column after devid is interesting too
17:28.13cmonexok done
17:28.18cmonexyea but i dunno what that one is. do you?
17:28.44cr2no
17:28.47cmonexheh
17:28.50cmonexoh well
17:29.01cmonexi wanted to know for a while :)
17:29.24cmonexbut all it seems to do is htc setups some things in nand init differently depending if it is 1 or 2...
17:30.33cr2maybe 1 or 2 chips ?
17:30.54cmonexmaybe..
17:34.42Echo31hi cr2.
17:34.44*** part/#htc-linux pe7er (n=Adium@f053195139.adsl.alicedsl.de)
17:36.23cr2Echo31: how big is your patch ?
17:37.45cr2cmonex: we are still working on athena too :)
17:38.00cmonexah :)
17:38.08cmonexwhat are you working on exactly? for athena
17:38.13cmonex<PROTECTED>
17:38.18Echo31cr2: for my first change, the patch size is about 100k
17:39.27cr2cmonex: the miniSD driver will make it usable.
17:40.13cmonexcool, everything else is done?
17:41.19Echo31cr2: i have merged a lot of driver ( sound, w228, video ati fb) from other code, but these drivers did not work
17:42.58cr2cmonex: lol
17:43.46cr2cmonex: once Echo31 will merge his patch, i'll add bt and gps support. the phone support is relatively easy too
17:44.19cr2Echo31: i guess you should split it in logical parts. ati fb is vsfb ?
17:45.29cr2cmonex: i still count athena as the most cool htc gadget
17:45.31cmonexcool. Echo31 you are working on athena then?
17:45.35cmonexcr2 :)) hehe yes :))
17:45.37cmonexi have 2
17:45.41cr2:D
17:45.44cmonexwell, 3rd one is olipro's
17:45.49cmonexcan test on that i guess, if needed :)
17:46.00cr2ok
17:46.01cmonexis jtag worked out for athena yet?M
17:46.07cmonexsomeone pm'd me asking about jtag
17:46.19cr2no, afaik
17:46.35cmonexoh, well this guy is triyng to jtag it, i'll let you know if any success
17:46.42cmonex(it's a bricked one)
17:47.01xsachadoes android allow arbitrary DPIs?
17:47.03cr2the g4 chip ?
17:47.05xsachai just tried 90 and it works
17:48.06lamaoh nice
17:48.19lamamake youtube video :)
17:48.30cr2xsacha: maybe it supports it, but that's just silly
17:48.45xsachanot silly, i can actually see stuff on my screen now
17:49.10cr2dpi is hardware
17:49.10cr2you can't change it.
17:49.24xsachaandroid default virtual dpi is 160
17:49.31xsachamy hardware is definitely not
17:49.56xsachahtc dream has 182 physical dpi, but 160 virtual dpi in android
17:50.37cr2ok, if you are not close to the hardware dpi, you get weird effects
17:51.12xsachawhat do you mean weird effects?
17:51.39lama96 dpi works fine on wm
17:51.51xsachayeah thats what i use on wm.. so i can read more stuff
17:51.54lamathat is hardwar res of i780 afaik
17:51.59Echo31cmonex: yes, i tries but it is not very easy, for example, set the proper values into the htc_egpio_chip structure
17:52.06xsachalama try 90 dpi on android, it's usable!!
17:52.06cr2xsacha: wrong font sizes
17:52.07lamabut samsung ships it with 120dpi
17:52.23lamait makes something like 240x240 screen
17:52.34cmonexEcho31 : do you need datasheets or info from disassembled drivers?
17:52.43xsachacr2: well yes, that was my problem. i was told android only support 120, 160 and 2(20 or 40) DPI.. but my phone is 96 dpi
17:52.45cmonexi can help with the latter
17:54.18cr2Echo31: post the patch, i guess with 3 people looking at it we will get a working config soon.
17:54.18lamaxsacha: show it on youtube :)
17:54.38xsachaok im trying to get back key working again.. i thought it was KEY_BACK?
17:54.40lamaonce i've tried 96 dpi on 800x480@3" :)
17:54.47lamathat was small :)
17:55.00xsachathe one i had on youtube before was 160 dpi!! lol
17:55.02cmonexfor me 128dpi on athena is comfortable
17:55.10cmonex(5" 640x480)
17:55.31cmonexEcho31: I have to go soon but tomorrow we could work on this. what do you say?
17:55.50cr2cmonex: do you know what is the purpose of the extra data channels on athena ?
17:56.12lamaxsacha: yeah that one looks weird
17:56.41cmonexcr2 : give me more info on what you call extra data channels
17:56.57cmonexbtw. is keyboard driver done yet?
17:59.12cr2cmonex: there are AT, P1,P2, P3,P9 and D channels
18:00.06cr2cmonex: the AT and P1 are control+data, D is the MSM diag (don't know what's there), but P2,P3 and P3 are black magic for me
18:00.29cr2cmonex: it's like the extra DATAx channels on raph
18:00.36cmonexah, ok, I will have to look into this.
18:00.57cr2the keyboard driver is available, but needs to be merged into the latest tree
18:01.10cmonexok, cool
18:01.11cr2the keybaord driver is from hermes.
18:01.20cmonexfor me without keyb driver, its not considered usable
18:01.27cmonexah and it works? :P
18:01.37cr2yeah, i use usb keyboard ;)
18:01.48cr2on hermes ? yes.
18:01.50cmonexi only use the integrated one
18:01.52cmonexno, on athena.
18:02.11cr2yes, once merged, it will work
18:02.18cmonexso it was tested M
18:02.20cmonex?
18:02.24cr2yes
18:02.28cmonexcool :)
18:02.44cr2athena needs it to be hotplug, that's the only difference
18:03.03cmonexyeah I see
18:03.10cmonexok, i have to go, back later. :)
18:03.23cr2so the drver needs an extra power gpio, and hotplug irq
18:03.27cr2ok
18:03.33xsachalama: 96 dpi looks better to human eye, 128 dpi looks ok on video and 160 dpi looks very crisp on video but unusable
18:03.50xsachaand from 90 dpi and below fonts go jaggy
18:07.59Echo31cmonex: I will be available only for the end of this week.
18:08.13*** join/#htc-linux nperry (n=nperry@93-97-101-163.zone5.bethere.co.uk)
18:08.21cr2Echo31: can you post the patch ?
18:08.23cmonexok. see you until then!
18:11.27*** part/#htc-linux nperry (n=nperry@93-97-101-163.zone5.bethere.co.uk)
18:15.05Treibholzdamn, kdrive wants libuuid1, but there is only libuuid, where can I fix this?
18:16.39*** join/#htc-linux ccube_ (n=ccube@ssh.ccube.de)
18:17.04Echo31cr2: Where can i post the patch ? on pastebin ?
18:18.19cr2yes
18:55.59Echo31cr2 pH5: find the patch link http://fr.pastebin.ca/1469012
18:58.23*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
18:58.50cr2pH5: what is tosa-bt ?
18:59.01*** join/#htc-linux stickboy (n=anonymou@ool-457e4101.dyn.optonline.net)
18:59.25cr2Echo31: downloading
18:59.32*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
19:01.41*** join/#htc-linux AstainMBL (n=AstainHe@c-67-164-195-234.hsd1.ut.comcast.net)
19:02.39cr2GPIO22_HTCATHENA_DPR_RESET1
19:02.55cr2i think i need to rename these
19:03.40cr2they are not really reset,and the AT/D/P1/P2/P3/P9 name should be added-
19:04.33cr2SSP2 is keyboard ?
19:05.33cr2MMC is wifi, afair
19:05.36cr2LCD power to be revisited
19:05.50*** join/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821)
19:05.56cr2DPR input is DPR irq
19:06.37pH5Echo31: thanks, got it. will check later.
19:06.39Echo31cr2: You can make all changes. I will follow your advice.
19:07.09pH5cr2: tosa-bt is the rfkill driver that tosa uses to turn on/off power to the bt chip.
19:08.44cr2pH5: hmm. the bt power API is real pita. also on the raph ;)
19:09.25cr2<PROTECTED>
19:10.38Echo31cr2: Oups . I tried all posibilities
19:13.29cr2cpld2 has 16gpios
19:13.33cr2http://www.htc-linux.org/wiki/index.php?title=CPLD2
19:14.00cr2i'll edit this page to provide more useful info
19:14.51cr2and cpld1
19:14.54cr2.num_gpios = 16,
19:15.17cr2has 8gpios per bank (on 16bit register)
19:15.38cr2http://www.htc-linux.org/wiki/index.php?title=CPLD1
19:17.40cr2+       .irq_base     = IRQ_BOARD_START,
19:17.54cr2cpld2 does not have irqs
19:18.46cr2+       .num_irqs     = 9, for cpld1 ?
19:18.56Echo31cr2: I wanted  to implement CPLD2. i have tried all possibilities. and i see the cpld2 does not have irqs
19:19.02cr2i think it should be 8. and 3 of them are not used
19:19.32cr2Echo31: cpld2 is more or less exactly the same as egpio on hx4700
19:20.12cr2Echo31: the comments are more or less for me and pH5. you've done a great job :)
19:20.49cr2+struct platform_device ssp_device = {
19:20.51cr2+       .name    = "htc_athena-ssp",
19:21.04cr2is it for the keyboard ? or for the ts/battery ?
19:21.41cr2i think hx4700 uses the proper spi driver infrastructure instead of ssp
19:22.14cr2Echo31: does the ts work ?
19:22.28Echo31cr2: i made only merge from you, pH5 and mistadman
19:23.10cr2the dpram part is completely useless in it current state
19:23.40cr2+  .dev_name  = "ttyDPRAM",
19:23.57cr2smdX is probably a better name
19:25.15cr2what is height/width for vsfb ?
19:25.18cr2+       .height                = -1,
19:25.20cr2+       .width  = -1,
19:26.04*** join/#htc-linux dcordes (n=dcordes@unaffiliated/dcordes)
19:26.36cr2the w2284 stuff is to be discussed
19:27.13cr2the battery coefficients are from hermes, i guess. to be checked too.
19:27.22pH5discussing this would probably be easier on the ML...
19:27.51cr2USB ohci is repeated twice
19:27.56cr2pH5: which one ?
19:28.28cr2+//     &egpio_cpld1,
19:28.29cr2+//     &egpio_cpld2,
19:28.34cr2not initialized ?
19:28.57Echo31cr2: I want understand the code, now.  htcathena_graphics ( fb) comes from mistadman. It is different  vsfb
19:29.03dcordeshi
19:30.42Echo31cr2: The initlization does not work. The cpld value was erroneous
19:32.13cr2Echo31: yes, the cpld initial values need to be checked. otherwise you risk to lose the LCD power, which is fatal for the vsfb
19:32.47cr2Echo31: i don't see any real value in the  htcathena_graphics driver
19:33.19Echo31cr2: yes, my display showed strange colours.
19:33.19cr2because it's not a real w2284fb driver anyway.
19:34.03cr2Echo31: the htcathena_vsfb.c works for me as expected.
19:34.41cr2+extern void      htcathena_cpld2_set( u_int16_t bits );
19:34.42cr2+extern void      htcathena_cpld2_clr( u_int16_t bits );
19:34.44cr2+extern u_int16_t htcathena_cpld2_get(void);
19:34.48cr2this is redundant
19:34.58Echo31vr2: I tried the w2284fb code from mistadman (athena-android); but it does not work.
19:35.52cr2why do you include pxa-regs.h ?
19:36.11cr2in the patch
19:37.17cr2i suggest to drop everything w2284 for now.
19:37.22Echo31cr2: few values are indefined from pxa27x
19:41.45cr2Echo31: pxa sound is not used
19:42.19cr2Echo31: ok, then it's necessary to add just the missing values
19:46.14pH5cr2 discussing patches inline on the ML is better. I promise I'm going to to forget most of this.
19:47.30cr2pH5: i suggest to drop 80% of this patch anyway :)
19:47.55*** join/#htc-linux onen|openBmap (n=quassel@p57BC4D24.dip.t-dialin.net)
19:48.09cr2then there are indeendent drivers like vsfb.c, ad7877.c and patches to pxa-regs.h
19:48.25Echo31cr2: Ok, i will change the  pxa2xx-regs.h
19:48.29*** join/#htc-linux j0b0 (n=jobo@12.35.60.99)
19:48.36cr2and then the cpld config needs to be sorted out
19:48.39cr2hi j0b0
19:48.57*** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo)
19:48.58j0b0hiya cr2
19:49.04j0b0how goes
19:49.39cr2j0b0: i'm suprised that most everybody gave up on raph/diam when we are mostly done with it :)
19:50.13j0b0i think 'most everybody' is looking for the 'click here to have everything woring instantly'
19:50.33cr2hehe
19:50.44Echo31cr2 pH5: This patch is my huge version
19:50.51cr2i mean those who have done something before.
19:51.36cr2j0b0: the rpc *epts are there, i've fixed the adsp numbers, and the rpcs seem to be working
19:52.12cr2j0b0: and i have some minor patches to be committed.
19:52.52Echo31cr2: I can 'rewrite' it and remove the unused drivers
19:52.54j0b0cr2 is it in the wiki? so that it is now merely work, for someone who is more a coder than necesarily a device hacker ;)
19:53.18cr2Echo31: do you know where is the shadow version of the cpld regs ? i don't rememebr if athena cplds are readonly.
19:54.04cr2j0b0: somebody may just try to work with the weird /dev/msm* and their ioctls.
19:54.11*** join/#htc-linux miknix_ghost (n=miknix@81.193.87.173)
19:54.58cr2Echo31: we need to derive the initial cpld values
19:55.28cr2Echo31: with disabled bt/wifi/cam/tvout and so on.
19:55.46cr2only the lcd power and other really critical gpios should be enabled.
19:56.16j0b0i have a patch for the touchscreen driver to detect and report touched area size, which seems to work for all devices, and one for the mddi/mdp 'color issue' so that the destination format is in pdata and does not depend on mtype, but im not sure whether that is done 'properly'
19:56.34cr2Echo31: there are 8 led cpld gpios, it's interesting to assign them to the real leds.
19:57.00cr2j0b0: it looked ok for me.
19:57.58j0b0could that kernel oops (on the keyboard leds) have something to do with that both reading scan codes and setting leds access the same i2c chip at the same time?
19:58.00cr2j0b0: let's commit. some code in the vogue branch is just plain wrong, but it does not stop the people from committing it :)
19:58.19cr2j0b0: maybe.
19:58.33cr2j0b0: why does it enable the FN led in the first place ?
19:58.54j0b0ive been looking through microp-eypad and microp-ksc but havent actually typed in it yet
19:59.03cr2i get wrong scancodes for the 4 "functional" keys, btw.
19:59.13j0b0the wrong led may be because maejrep has a raph800 and we have a raph100 ?
19:59.24cr2you have FN enabled too ?
19:59.28j0b0yes
19:59.32j0b0and the oops as well
19:59.35cr2ok.
19:59.54cr2yes, it may be the firmware difference to raph800
20:00.30cr2there is an LCD (probably backlight) i2c opcode that is different on raph100 vs 800.
20:00.47cr2do we have lcd backlight control now ?
20:01.54cr2FN,SMS/MMS,mail and SYM produce useless symcodes for me
20:02.03cr2everything else looks good.
20:02.08j0b0(ive been away for wwdc and projects for 2 weeks. i guess i will be back home by thursday or so)
20:02.18cr2i'm only puzzled where to put the | key.
20:02.27j0b0iirc we can control backlight through the led driver but i dont know whether its exposed correctly
20:02.53cr2yes, but they say backlight class is better
20:03.20cr2but what about the keybaord & keypad and whatever backlight ? just leds ?
20:04.17j0b0the leds in the navi pad are just leds, and right now, the navi keypad driver even controls them, which it probably shouldnt
20:04.44cr2yes, it should be done in userspace
20:05.00cr2don't know about android
20:05.10j0b0i did that to at least mae it usable and test the led driver at the same time
20:05.56cr2ok
20:06.09cr2i need to dump some more gps rpc data. bb in 10min, will go outside.
20:06.16*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
20:06.24j0b0.where you can see satellites :)
20:11.23*** join/#htc-linux stickboy (n=anonymou@ool-457e4101.dyn.optonline.net)
20:16.40cr2ok
20:16.58cr2now i only need to rememeber how to save tracks in roadmap
20:17.57cr2j0b0: i have a diff to
20:18.02cr2--- a/arch/arm/mach-msm/smd_rpcrouter.c
20:18.03cr2+++ b/arch/arm/mach-msm/smd_rpcrouter.c
20:18.38cr2to send the  RPCROUTER_CTRL_CMD_HELLO
20:18.45cr2as in lavender.t patch
20:19.20cr2yes, and the msleep patch for clock
20:19.22j0b0cr2 right. that creates a bunch of devices
20:19.23cr2-                               msleep(5);
20:19.39cr2+//                             msleep(5);
20:19.51cr2otherwise the BT makes an oops in the clock code.
20:20.31cr2the devices that are really used (in wince) are all doucmented in wiki
20:20.54cr2http://www.htc-linux.org/wiki/index.php?title=MSM_RPC
20:21.35j0b0does the rpcrouter patch make qdsp5 work ootb
20:22.06cr2i have fixed the adsp proc, and the rpc go through without an error
20:22.10cr2as before
20:22.19cr2i'll pastebin my diff
20:23.29cr2j0b0: http://pastebin.ca/1469138
20:24.31sxegn8
20:25.07cr2if i enable the BT power, i get a hard lock in 'stty -F /dev/ttyHS1' though ;)
20:25.13*** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix)
20:25.55j0b0applies it
20:26.04cr2miknix: how portable is your initrd ?
20:26.21cr2j0b0: ok, the patch works, and is trivial anyway.
20:26.47j0b0nice and small
20:28.17cr2j0b0: why are the 4 keys have wrong keycodes ?
20:29.01j0b0do you know whether maejrep got sane values from his battery driver? i added raph100 code to it and i do gt good values
20:29.15j0b0i dont know. is it easy to test andtell which keys need changed
20:29.20cr2didn't hear from him for a long time
20:29.35cr2FN,SMS/MMS,mail and SYM
20:29.36j0b0i know ..  alot of code ive been twiddling with is his
20:30.53cr2<PROTECTED>
20:32.16cr2KEY_FN is there, but it produces a strange combination with the default kernel map
20:33.11cr2#define KEY_FN                  0x1d0
20:33.36cr2> 256 ?
20:34.59cr2maybe LEFT_ALT is a better option ?
20:35.44cr2and RIGHTALT for SYM
20:36.20j0b0how ugly is it to not report it and just abuse it to produce things like pipe, lt, gt, brackets, backslash ...
20:36.32cr2don't know about mail and sms
20:36.51cr2use RIGHTALT /
20:37.31cr2or RIGHTALT (aka ALTGr ) <
20:37.39cr2like it's on my notebook
20:38.13cr2i have no idea what android uses for the keyboard.
20:38.41cr2ok, i suggest to map FN to ALT and SYM to ALTGr right now.
20:39.09cr2<PROTECTED>
20:40.04cr2then loadkeys can create a sensible translation table
20:40.06dzohi cr2, how's raph coming along?
20:40.33cr2dzo: sorted out the sound rpc, but don't know how to test it
20:41.13cr2dzo: if i enable the BT power, i get a hard lockup on stty -F /dev/ttyHS1
20:41.23dzoI saw you asking about the gpu, it uses AHI so the qt drivers may work.
20:42.03cr2dzo: and the ADSP modules seem to be the same as on 6210 for our 52XX AMSS
20:42.05dzoI haven;t tried the hs serial drivers, probably a dma thing, they use the datamover.
20:42.23j0b0do we need imem clock for that
20:42.24cr2yes, something is stuck there.
20:42.25j0b0gpu that is
20:42.41cr2j0b0: imem clock is rpc
20:42.43dzoThat makes it easier, i only know some of the queues numbers on amss 4xxx
20:43.37cr2j0b0: here
20:43.41cr2PMEM_REMOTE  0x30000055   pmem_*
20:43.43cr21,1 pmem_remote_imem_enable (1)
20:43.43dzoimem clock is easy, rpc or just see my clock-msm7x00.c
20:43.44cr22,1 pmem_remote_imem_disable (1)
20:44.04cr2yes
20:44.15*** join/#htc-linux AstainMBL (n=AstainHe@unaffiliated/astainhellbring)
20:44.34dzothat may do something different, i think it maps the imem memory to a11 rather than the gpu.
20:44.58cr2dzo: do you know something about the new wl12xx wifi driver ?
20:45.10cr2dzo: i've traced this rpc on my raph
20:45.12dzono, nothing
20:45.33cr2i've heard it's a rewritten tiacx
20:45.50dzook, on vogue i just need to set a clock bit and imem works.
20:46.14cr2ok, i guess it's the same here.
20:46.21dzodid you guys get anywhere with an xip bootloader?
20:46.41cr2no
20:46.59cr2the main problem is the nonaligned access to nand
20:47.11dzoi might try that sometime, doesn't look too hard.
20:47.26cr2g1 partitions are 128k aligned, so we need a new partition tag
20:47.40cr2to preserve the wince
20:47.55dzoit does 8K pages and you pass the partition info in kernel params or some other way.
20:48.18dzothat's what google does anyway.
20:48.54cr2nand_partition.c multiples the numbers by 64*2048
20:48.55dzoi was thinking of not preserving wince....
20:49.29cr2hehe. we are not quite there yet.
20:49.46cr2i don't want to reflash on each reboot/resume.
20:50.00j0b0ive tried to 'just' enable gpu and got 'enabling clock with no enable bit set (12)' or something similar
20:50.53cr2j0b0: it's a bit more involved. and the message itself is actually harmless
20:51.08dzotry tracing clock_sec_grp_rail_on under wince.
20:51.22j0b0so it still enables the clock?
20:51.24dzothat's what i did.
20:52.15cr2<PROTECTED>
20:52.52dzothe rpc prog no may be different, it is on kaiser i think.
20:52.55cr2for this rpc CLKRGM_SEC  0x3000000f   clk_regime_sec_*
20:53.11dzoyes
20:53.14TreibholzI have a problem with OE: http://paste.debian.net/39858/ Any Idea?
20:53.15cr2dzo: http://www.htc-linux.org/wiki/index.php?title=MSM_RPC
20:53.34cr2dzo: there are some differences for the cam rpcs
20:54.56cr2dzo: btw, the only missing part for the gps is the context pointer return value from pdsm_client_init(). the 0xda3 value in the table
20:55.34cr2i just don't understand the wince rpccall api to a full extent
20:56.56dzono, nor do i, i heard there is a simple on off rpc call fpr gpet_position but i don't know what it is and vogue/kaiser uses 0x30000004 too.
20:57.27dzoi meant one-off call for get_position
20:57.39cr2psdm_get_position needs this context pointer
20:57.48dzoanyway got to go to work, bye for now....
20:57.55cr2the last argument
20:57.57cr2bye
20:58.46cr2j0b0: you really need the imem clk ?
20:59.16cr2j0b0: btw, this is the most funny rpc
20:59.20cr2PM  0x30000061   pm_*
20:59.21cr20xe,2 pm_set_led_intensity (0,3)
20:59.32cr2and it is actually used on raph100 :)
20:59.44j0b0i dont know. its just that i got that message when trying to do hw3d stuff and clock 12 turned out to be imem
21:00.14cr2ok, i'll try to look for imem
21:00.58cr2j0b0: can we export this rpc to sysfs ?
21:02.00j0b0is that the lcd backlight?
21:02.09cr2talking to /dev/30000061:0 seems to be too tricky.
21:02.14cr2no idea.
21:03.36cr2i think it can be a simple template for the gps driver and such.
21:04.04cr2maybe modified from the htc_battery.c
21:04.48j0b0that seems to be the simplest example
21:04.57cr2i'll recompile the kernel with ALT keys
21:04.58cr2yes
21:06.33j0b0..and then when we find out what effect it has, rename it to something that describes it :)
21:11.39cr2:)
21:11.43j0b0capslock does not only turn on the wrong led, and oops, it also doesnt work (doesnt produce capital letters, in android that is)
21:12.02cr2i'll check right now
21:12.23cr2tell me about the sound
21:12.41cr2btw, gps may work in android now.
21:12.51j0b0both left and right shift are as sticky as in win
21:13.15cr2shifts work for me
21:13.23cr2in angstrom initrd
21:16.33j0b0yes. both when you hold while hitting another key and also when you hit shift, release and then the other key
21:22.17cr2j0b0: i have found dex 1 and dex 0x14 in nk.exe
21:22.42cr2j0b0: the dex 0x14 is looking like an arm9 reset/reboot
21:23.16j0b0does that reboot the entire device or just the modem
21:23.28cr2have not tried it.
21:23.41cr2it uses a simplified call form
21:24.02cr2you just put 0x14 in CMD and increment the A2M count numbers
21:25.00cr2hmm. can't boot the kernel anymore
21:25.37miknixcr2, it is totally portable
21:25.43miknixarmv5te-jl
21:26.05miknixs/-jl//
21:26.37j0b0cr2 did you change anything else than the keymap?
21:27.02miknixcr2, we don't do anything wizard specific in the userspace
21:28.03miknixits also eabi, you can disable old abi in the kernel
21:28.03j0b0sometimes merely recompiling and re-copying helps .. :/ (scary)
21:30.30miknix:(
21:30.40*** join/#htc-linux cr2 (n=cr2@ip-77-25-188-78.web.vodafone.de)
21:30.47miknix:)
21:31.35cr2miknix: where do i get it ?
21:31.55miknixhttp://tinderbox.dev.gentoo.org/embedded/linwizard/
21:32.07miknixgizard-xxx is GPE
21:32.23miknixthe e17 images are still incomplete
21:32.47cr2omg.
21:32.56cr243.6MB as a ramdisk ?
21:33.09miknixno, its a root tarball
21:33.16cr2hmm.
21:33.25cr2i'd prefer an initrd :)
21:33.36miknixgpe is too big to fit in a initrd :)
21:33.56cr2ust xsever + twm ?
21:34.27miknixdont have any
21:35.12cr2ok
21:35.18miknixbtw: you can boot gpe from NFS
21:35.28miknixits not the king of speed, but it will work
21:35.29cr2j0b0: the ALT keys report sane values now.
21:35.51cr2miknix: too much to setup
21:35.54j0b0do you get different values for left and right alt?
21:36.07cr2j0b0: of course
21:36.19cr2j0b0: i've just edited the kernel table
21:36.23j0b0i mean combined with other keys
21:36.25j0b0i dont
21:36.38miknixcr2, http://linwizard.wiki.sourceforge.net/booting
21:36.46miknixlook at the bottom
21:37.08cr2j0b0: if i will upload the translation table with loadkeys , it should work
21:37.18cr2j0b0: i'm using initrd
21:37.45cr2j0b0: caps key works
21:37.45j0b0angstrom?
21:38.06cr2yes
21:38.22cr2oops and FN led included.
21:38.30cr2tmzt: are you sleeping ?
21:39.37j0b0you can make it turn on the correct led by swapping fn and caps in linux/inclue/microp-ksc.h (or at least giving caps the value fn had, btu we have no fn anymore anyway)
21:40.32j0b0if it ever worked for maejrep it must be a 800 vs 100 thing
21:40.38cr2FN shoould not be a sticky key
21:40.58cr2i think it's a stupid idea from the very beginning
21:41.31cr2so you don't really need an FN led
21:41.48j0b0at least in android, hitting shift once makes it sticky for the next key hit, hitting shift twice makes it sticky until you hit it again
21:42.41cr2ok, it's up to android how to interpret the input events
21:42.54cr2the kernel does the right thing now.
21:43.37j0b0...except for the led
21:43.43j0b0and the oops ;)
21:45.03cr2yeah
21:45.22j0b0im going down for some food .. bbiab (/me sits in a hotel room in atlanta GA :/)
21:45.24cr2the keymaps are different for 800 and 100 right now
21:45.30cr2lol
21:46.40j0b0i know .. its sad
21:57.24cr2<PROTECTED>
22:03.43cr2j0b0: yes, now it works
22:06.56cr2~ping tmzt
22:17.56cr2miknix: how do you compile qtopia ?
22:18.48miknixcr2, how so?
22:19.10miknixit was used the same toolchain as the others
22:19.27cr2is it usable ?
22:19.32miknixnever tried it
22:19.34miknix: )
22:19.46cr2which is the target device ?
22:20.08miknixarmv5te
22:20.18cr2i mean the phone
22:20.21miknixwizard
22:20.37cr2actually, i'd like to test x11+qt4
22:20.52cr2is it the config of BabelO for arte ?
22:20.55cr2BabelO: ping
22:21.03miknixdespite the touchscreen driver, everything should be portable on those images
22:21.16miknixhum.. no qt4, that image is old I think
22:21.28cr2qtopia is qt4
22:21.59cr2miknix: ts is different on omap850 phones ?
22:22.17cr2i've lost track on 850 long ago :)
22:22.20miknixwe are using tslib, not sure what do you guys use
22:22.42cr2i mean the kernel interface
22:23.05miknixit is still the spi driver from BabelO
22:23.06cr2of course every sane person should use tslib
22:23.10cr2ok
22:23.17miknixyeah, omap850 is kind of old
22:23.32miknixbut there are still new devices coming out with it
22:23.53cr2miknix: what does not work on wizard ?
22:24.02miknixsound and wifi
22:24.03cr2miknix: wifi ? cam ?
22:24.07miknixyeah and cam
22:24.14miknixirda also I think
22:24.23cr2irda should be on uart
22:24.47cr2why can't you make sound work ?
22:25.07miknixali was working on phone , we need a decent phone stack now
22:25.18miknixthe sound driver is going slowly :)
22:25.26BabelOhi cr2
22:25.46miknixthere were some troubles with dma channels
22:25.46*** join/#htc-linux wirelessdreamer (n=dreamer@chrobd01.vailsys.com)
22:25.59miknixonly the first dma transfer was being made
22:26.04miknixit is fixed now
22:26.27miknixnow we have to make the alsa interface
22:26.56miknix(we were piping the audio waveform directly to syren) :)
22:28.22miknixthe driver is based on the motorola sources, opennandra did port it from 2.4
22:28.56miknixcr2, and that is the state of omap850 :)
22:29.13miknixoh, and silven is pretty much finishing the upstream submissions of omap850 patches
22:31.32cr2ok
22:31.48cr2BabelO: just wanted to know the qtopia status :)
22:32.00BabelOcr2: qtopia is dead :(
22:32.18cr2ok
22:32.23miknixlol
22:32.26BabelOcr2: better to play with qlandkarte actually and the wince port
22:32.28cr2x11+qt4 ?
22:32.33BabelOcr2: use android :)
22:32.49cr2java..., barf
22:32.54BabelOcr2: yes i can continue on qtopia ( qtextended )
22:32.56BabelObut ...
22:33.07BabelOccryes same than you with java
22:33.14BabelOcr2: do you like objective C ? :)
22:33.18miknixcr2, did you look at directfb?
22:33.30cr2BabelO: no, too much apples
22:33.44BabelO;)
22:33.48BabelOso, what left
22:33.59miknixgtk (with cairo direcfb backend) can run seamless over directfb
22:34.08cr2miknix: on a 256MB device like raph, the x11 overhead is laughable
22:34.14miknixno Xserver crap is needed
22:34.20miknixoh
22:35.07cr2miknix: writing gui apps with gtk is not for me :)
22:35.28miknixof course there are worse choices :)
22:35.33cr2miknix: i can go with raw xlib
22:35.38miknix: \
22:35.52miknixhat about directfb classes?
22:36.01miknixdont recall the naem
22:36.22marexcr2: how's alsa-soc on n560 going ?
22:36.37cr2marex: waiting for you
22:36.44miknixLiTE
22:36.45BabelOcr2: qt-embedde with qlandkarte M on raph is enough for you  :)
22:36.50miknixhttp://www.directfb.org/index.php?path=Platform%2FLiTE
22:36.56cr2miknix: i'm and oldtimer, i like x11 and 2d.
22:37.29cr2miknix: and consider 3d as hardware resource wasting :)
22:37.46miknixLiTE is pretty much a 2D framework afaik
22:39.13cr2miknix: ok, but where will you get the apps ?
22:39.32miknixthats the problem
22:40.01cr2miknix: actually it may be possible to write a directfb driver for roadmap
22:42.21miknixI like gtk because of that. there is plenty written to it, it is lightweight and it is a good abstraction layer (works over directfb, Xserver, win32api ..)
22:42.43cr2gtk or gtk2 ?
22:42.48miknixsorry gtk+
22:43.52cr2marex: what about resume on n560 ?
22:43.59miknixthere should be an omap processor with python bytecode accelerator :P
22:44.24miknixs/be/exist/
22:44.43cr2doesn't it have jazelle ?
22:45.01miknixit does, but java is nowhere near python
22:45.28cr2BabelO: M on wince takes ages for loading
22:45.47miknixand dont we need a license to use jazzele ? pretty much useless then. even google is not using it
22:45.52BabelOcr2: but fast on execution
22:45.56BabelOloading is not a problem
22:46.05cr2miknix: yes, you need a license i think
22:46.25BabelOcr2: and now it is faster as i compile release and not debug
22:46.34cr2miknix: imho, a non-general purpose cpu is a bad idea
22:47.04miknixgpus?
22:47.24cr2BabelO: roadmap works for me on 6.1 and 5. with gps port autodetection
22:47.58BabelOcr2: ok, i have autodetect as in wince5 or 6 it is always same :)
22:48.00miknixdo you think a gpu is a bad idea?
22:48.10cr2miknix: $language accelerator is bad
22:48.25miknixah ok
22:48.50cr2miknix: nvidia even has written a c compiler for its gpu. guess why ? :)
22:49.08miknixyeah, I agree
22:49.51cr2and c is probably the most portable assembler as it is possible.
22:50.37miknixwe can get some pretty cool optimizations from functional languages
22:50.45BabelOcr2: i will package you a cab file, and you will sync with GT !!!!
22:50.47BabelOgrh
22:51.15miknixI wrote some apps in prolog that will shot any C app you can through at me with the same level of complexity
22:52.01miknixthere is a ocaml interpreter for armv5
22:52.33miknixcorrection: the ocaml interpreter is ported to armv5
22:52.37cr2miknix: prolog was the most strange language i learnd in the university.
22:53.42miknixit is strange yeah, specially with people that learned imperative languages very early
22:53.43cr2miknix: maybe because i have started programming with assembler :)
22:54.29miknixunfortunately I miss asm :( I started with err.. basic 86 on a MSX basic computer
22:54.33cr2BabelO: yes,  a cab will be really nice.
22:55.09cr2BabelO: it's time to kill ozi explorer
22:55.35cr2miknix: MSX ? i think it was some kind of OS for z80 ?
22:55.47miknixyeah
22:55.51miknixfrom microsoft
22:56.08cr2don't think so
22:56.26miknixI still own one of these : hehe http://www.klg.de/compmu/comppics/philipsMSX.jpg
22:56.49miknixhttp://upload.wikimedia.org/wikipedia/en/7/71/Msxbasic.png
22:57.36miknixyes, MSX was from m$ /\
22:58.58cr2omg, i've missed it ;)
22:59.56cr2i think the only useful app on it was the z80/8050 disassembler.
23:00.07cr2s/8050/8051/
23:00.14miknixI think it was the only thing from m$ I used that didnt crash
23:00.21miknixoh, and my mouse
23:00.27BabelOcr2: this is small screen http://linuxbox2.free.fr/qland10.jpeg
23:00.29cr2oem
23:01.09cr2BabelO: will it work in landscape ?
23:01.28BabelOcr2: yes just need to create a ui
23:01.29cr2BabelO: i think the layout is too optimized for portrait
23:01.45BabelOcr2: actually we have two ui 480x640 and 240x320
23:01.56cr2240x240 :)
23:02.20BabelOcr2: layout is not a problem , all interface are ui file if you do it in designer, it is ok, no need code
23:02.26cr2ok
23:03.04cr2BabelO: can i save tracks on it ?
23:03.26BabelOcr2: not now, it is the current step working on :)
23:04.03cr2ok
23:04.10BabelOcr2: after that i create a CAB file
23:04.16cr2oziCE should be the target
23:04.32cr2GT already blows the desktop ozi away.
23:04.37BabelOcr2: yes some friends look M as replacement of OziCE
23:04.57BabelOcr2: i ve added and autodetect tool between gt <-> m
23:05.02BabelOto remove the setup
23:05.07BabelOit works even on windows
23:05.08cr2nice
23:06.06cr2dcordes: still not asleep ?
23:06.17miknixcr2, correction: the qtopia image is qt4
23:06.35*** join/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821)
23:35.58cr2j0b0: i have one more patch
23:44.04j0b0cr i was just reading what ive missed inthe last hour
23:44.07j0b0what is it
23:44.11j0b0+2
23:46.24cr2j0b0: i've edited the bt reset timing, and i get the reboot (poweroff) with dex 0x14
23:46.39cr2j0b0: somebody should try it on raph800 though
23:47.03cr2-       struct msm_dex_command dex = { .cmd = PCOM_RESET_ARM9 };
23:47.04cr2+       struct msm_dex_command dex = { .cmd = PCOM_POWER_OFF };
23:50.16cr2j0b0: the full diff http://pastebin.ca/1469314

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