00:08.18 | *** join/#htc-linux gh0ul (n=asds@host81-154-247-76.range81-154.btcentralplus.com) |
00:09.01 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
00:09.03 | Untouchab1e | hi all |
00:10.17 | *** join/#htc-linux balsat (n=kra@87.72.13.87) |
00:13.07 | *** join/#htc-linux addman3333 (n=skool@cpe-67-9-134-92.austin.res.rr.com) |
00:22.47 | *** join/#htc-linux Zinbolic (n=zinbolic@0x57344a18.vgnxx3.dynamic.dsl.tele.dk) |
00:37.27 | *** join/#htc-linux nato2k (n=templarn@76.250.180.218) |
00:43.42 | Untouchab1e | anyone here? I need to turn my qwerty.kcm file into a binary file layout |
00:43.46 | Untouchab1e | but have no idea how |
00:49.55 | *** join/#htc-linux maejrep[w] (n=madCoder@smtp-n.myyearbook.com) |
00:57.28 | tmzt | Untouchable: you mean dumped from busybox? |
01:03.39 | cr2 | maejrep[w]: too late for w ? |
01:03.56 | *** join/#htc-linux reformatt (n=chatzill@71-37-165-208.bois.qwest.net) |
01:06.17 | cr2 | good night |
01:06.18 | maejrep[w] | heading home now :) |
01:06.30 | maejrep[w] | (i'm eastern US, only 8pm here :p) |
01:06.50 | cr2 | maejrep[w]: the vreg_switch is understood |
01:06.59 | maejrep[w] | nice |
01:07.11 | cr2 | maejrep[w]: the vreg_level not yet |
01:07.16 | maejrep[w] | anything else new? or I can just read my backlog when I get home |
01:07.39 | cr2 | have you seen the vreg_level being changed ? |
01:07.53 | maejrep[w] | which command was that? |
01:08.03 | maejrep[w] | I don't think so |
01:08.20 | maejrep[w] | when I saw the sd card being enabled and disabled, it was just that, no level change |
01:08.32 | cr2 | the SD clock formula is fixed. combined with the 'gp6' vreg the SD should work |
01:08.48 | cr2 | i think you have a level change once |
01:09.07 | maejrep[w] | damn, I saw the gp6 vreg in the trout code .. was thinking about that :x |
01:09.14 | cr2 | g1 does not use level change |
01:09.26 | maejrep[w] | no, but it does a vreg_enable on gp6 |
01:09.56 | cr2 | your proc_comm_wince mask for vreg_switch is |
01:10.06 | cr2 | 2^g1idx |
01:10.47 | cr2 | so for a vreg 'foo' you pick the g1idx |
01:11.14 | cr2 | and send the proc_comm_wince x15/x16 2^g1idx |
01:11.22 | maejrep[w] | got it |
01:11.42 | cr2 | i'll add it to wiki. later. |
01:11.54 | maejrep[w] | cool, see ya |
01:12.01 | cr2 | i'll also fix PCOM_GPIO_CFG |
01:12.34 | cr2 | please check the rapahel_gpio for 800 |
01:12.53 | cr2 | and use a separate column in wiki |
01:13.19 | cr2 | then we will finally have a clean setup. |
01:13.50 | cr2 | and can start removing junk from the code. |
01:14.16 | cr2 | 2:13 here ;) good night |
01:20.38 | reformatt | has anybody got the latest build from connect-utb working on the diamond? everything seems to be for the raphael |
01:22.49 | tmzt | build of what? |
01:23.48 | reformatt | latest android release on the connect-utb website. I know its still a WIP but that release I can't even start on my diamond when earlier releases worked just fine other then the issues that are still be resolved |
01:24.27 | tmzt | raph has some different gpios |
01:24.54 | tmzt | I think you want to change root and sdcc slot |
01:25.01 | tmzt | it might work then |
01:25.03 | reformatt | ok |
01:25.16 | tmzt | it would be helpful to know what error you get |
01:25.38 | reformatt | don't get any error harriot just locks up when I select run |
01:26.08 | tmzt | check mtype |
01:26.21 | reformatt | im using the latest build and change the mtype to 1805 which was for diamond I thought |
01:26.27 | *** join/#htc-linux DracoDan| (n=F@pool-71-163-138-224.washdc.east.verizon.net) |
01:26.29 | tmzt | use the one that matches the zImage not your device |
01:26.51 | *** join/#htc-linux zycho_ (n=zycho@a89-182-206-32.net-htp.de) |
01:26.54 | tmzt | use the raph one |
01:27.02 | reformatt | i did |
01:27.07 | reformatt | :P |
01:28.43 | reformatt | u know the link to jobo site to get the latest zimage |
01:47.10 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
01:47.26 | Untouchab1e | Good evening :) |
01:55.19 | *** join/#htc-linux Gabe_ (n=chatzill@208.79.15.102) |
01:56.35 | maejrep | <cr2> i think 1 is 'active high' <-- what is "active low" then? :) (cof, my keyboard irq :( lol) |
02:00.17 | maejrep | <cr2> writel((1U << 16) | (~level & 0xffff), <-- ... srsly? :| |
02:02.08 | *** join/#htc-linux piusvelte (n=irchon@71.175.8.29) |
02:26.29 | *** join/#htc-linux BHSPitLappy (n=BHSPitLa@unaffiliated/bhspitmonkey) |
02:32.01 | *** join/#htc-linux br1ck (n=br1ck@xdslck144.osnanet.de) |
02:44.56 | *** part/#htc-linux exco (n=exco@e181084064.adsl.alicedsl.de) |
03:06.59 | *** join/#htc-linux zycho (n=zycho@a89-182-206-32.net-htp.de) |
03:15.12 | *** join/#htc-linux RZK333 (n=rzk@daemonet.ru) |
03:47.16 | *** join/#htc-linux reformatt (n=chatzill@71-37-165-208.bois.qwest.net) |
03:48.09 | reformatt | with the latest android zimage do we still still use 1805 as mtype for diam? |
03:48.43 | reformatt | i have tried 1910 and the vkeyboard is on the right hand side of the screen |
03:48.59 | tmzt | I don't think both are enabled in your zImage |
03:49.06 | tmzt | so only one works |
03:49.25 | tmzt | also, you should be able to drag the vkeyb to where you want it |
03:49.32 | reformatt | ok sounds right because I tried 1805 and harriot froze |
03:49.54 | tmzt | it didn't freeze, arm linux won't boot if the mtype is not supported |
03:50.05 | reformatt | ohh I see |
03:50.30 | tmzt | since this includes what drivers are used for everything, including display, there is no way to print an error (except serial which we don't have access to) |
03:58.56 | *** join/#htc-linux Chicago (n=Chicago@c-98-223-56-126.hsd1.in.comcast.net) |
03:59.13 | Chicago | Hola |
04:00.28 | *** join/#htc-linux skodde (n=skodde@e178060173.adsl.alicedsl.de) |
04:01.06 | tcccp | chicago indiana? |
04:01.41 | maejrep | :| |
04:01.53 | Chicago | tcccp: nah... my IP is in Indiana, my handle is Chicago. |
04:02.12 | tcccp | A bogus chicago...hmmmm |
04:03.59 | *** join/#htc-linux reformatt (n=chatzill@71-37-165-208.bois.qwest.net) [NETSPLIT VICTIM] |
04:08.02 | *** join/#htc-linux maxwellsmart (n=fungistr@c-24-12-251-254.hsd1.il.comcast.net) |
04:09.08 | maxwellsmart | what kind of functionality does the current version have on the kaiser? Does it work as well as the G1? |
04:09.55 | maejrep | negative |
04:10.08 | maxwellsmart | well basics? |
04:10.35 | maxwellsmart | sms, phone, internet, imap? |
04:10.39 | maejrep | google had the documentation they needed to build support for the g1. we don't :) |
04:10.49 | AstainHellbring | sup maejrep |
04:10.50 | maxwellsmart | oh right |
04:10.56 | maejrep | that much I couldn't tell you |
04:11.01 | maejrep | AstainHellbring, hi |
04:11.05 | AstainHellbring | whats new maejrep |
04:11.16 | maxwellsmart | it would be nice if you guys had that doc |
04:11.26 | maejrep | probably same thing that was frustrating me last time we talked :) |
04:11.36 | maejrep | maxwellsmart, yeah ;p |
04:11.43 | AstainHellbring | lol |
04:12.34 | AstainHellbring | anything I can help you with maejrep? |
04:13.11 | maejrep | if you know how I can reset an active-low irq so that it can fire more than once :D |
04:13.22 | maxwellsmart | is there like a feature list of 1.0? or not even there yet? |
04:13.35 | AstainHellbring | nope.. guess not :) |
04:13.48 | maejrep | maxwellsmart: I don't know much about kaiser myself |
04:14.05 | maxwellsmart | hmm what you guys devolpoing it for? |
04:14.06 | maejrep | I'm sure the wiki or the forums have something that could answer that |
04:14.14 | maxwellsmart | oh theres a wiki?! |
04:14.19 | maejrep | I'm working on raphael |
04:14.34 | maejrep | http://wiki.xda-developers.com/ ;) |
04:14.34 | maxwellsmart | is that the "diamond"? |
04:14.38 | maxwellsmart | gracias |
04:14.40 | maejrep | it looks like the diamond |
04:14.45 | maejrep | but with a keyboard |
04:14.48 | maejrep | (touch pro) |
04:14.49 | maxwellsmart | mine is the "tilt" |
04:15.04 | AstainHellbring | tilt == kaiser raphael == touch pro |
04:15.05 | maxwellsmart | i HATE WM |
04:15.11 | maejrep | http://wiki.xda-developers.com/index.php?pagename=HTC_Linux_Android |
04:15.58 | maxwellsmart | ahh ok, thats how i ended up here |
04:16.59 | maxwellsmart | its one hell of a thread |
04:17.23 | maxwellsmart | i guess theres no risk if its just emulated nayway |
04:20.58 | *** join/#htc-linux t3chi32 (n=blarg@ip24-250-216-85.ga.at.cox.net) |
04:20.59 | *** join/#htc-linux greenspan (n=fungistr@c-24-12-251-254.hsd1.il.comcast.net) |
04:33.41 | *** join/#htc-linux BHSPitLappy (n=BHSPitLa@unaffiliated/bhspitmonkey) |
04:35.22 | *** join/#htc-linux HeLLs (n=h@host86-144-186-152.range86-144.btcentralplus.com) |
04:35.25 | HeLLs | enas |
04:36.29 | tmzt | sorry? |
04:37.37 | HeLLs | sorry, ment hello |
04:37.47 | HeLLs | wrong language, happens sometimes |
04:39.13 | tmzt | ok, do you have a question? |
04:40.31 | HeLLs | well if i must, has anyone been able to instal android on htc s620? |
04:40.36 | HeLLs | aka dash |
04:40.52 | tmzt | yeah, penguinz but we can't find him |
04:41.00 | tmzt | there is some information on the xda forums |
04:41.00 | HeLLs | lol ouch |
04:41.06 | HeLLs | im reading now |
04:41.24 | HeLLs | thats why i didnt ask :P |
04:42.59 | HeLLs | so did penquinz manage to sort all the drivers? |
04:43.20 | tmzt | as far as I know I didn't follow that closely |
04:45.38 | *** join/#htc-linux RZK333 (n=rzk@daemonet.ru) |
04:45.57 | HeLLs | i just finished installing mac on my pc, wonder if anyone has managed to install iphone on another phone? |
04:47.11 | tmzt | not that I know of |
05:02.47 | *** join/#htc-linux RZK333 (n=rzk@daemonet.ru) |
05:17.58 | *** join/#htc-linux the_sys0p (n=the_sys0@cpe-75-85-249-111.bak.res.rr.com) |
05:24.12 | *** join/#htc-linux RZK333 (n=rzk@daemonet.ru) |
05:41.44 | *** join/#htc-linux nato2k (n=templarn@76.250.180.218) |
05:58.22 | *** join/#htc-linux goxboxlive (n=goxboxli@mail2.hjellnesconsult.no) |
06:10.11 | *** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz) |
06:15.17 | *** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be) |
06:16.56 | *** join/#htc-linux PoohbaLT (n=Poohba@c-98-235-66-242.hsd1.nj.comcast.net) |
06:21.33 | *** join/#htc-linux Othello (i=Othello@gateway/tor/x-b7837bcbc1a2cfdb) |
06:27.09 | *** join/#htc-linux Guimli (n=guimli@ecu69-1-82-231-127-213.fbx.proxad.net) |
06:31.41 | *** join/#htc-linux kiozen (n=oeichler@rgnb-5d87c53c.pool.einsundeins.de) |
06:41.57 | *** join/#htc-linux lpotter (n=ljp@58.173.176.153) |
06:45.38 | *** join/#htc-linux Shinto (n=John@g227124179.adsl.alicedsl.de) |
06:59.44 | *** join/#htc-linux Balsat (n=kll@87.72.13.87) |
07:02.37 | maejrep | ok, last try for that night |
07:03.11 | tmzt | are you able to dump keycode values in the driver? |
07:05.13 | maejrep | [ 54.351076] ::: Button = 29; currently pressed: 1 |
07:05.14 | maejrep | [ 57.236267] ::: Button = 29; currently pressed: 0 |
07:06.01 | *** join/#htc-linux meetdave (n=meetdave@S0106002129c35dd9.gv.shawcable.net) |
07:07.00 | *** join/#htc-linux meetdave (n=meetdave@S0106002129c35dd9.gv.shawcable.net) |
07:07.26 | maejrep | takes about .5 seconds right now to go through each firing of the irq, but that's with a lot of printks, and with two mdelay(100)'s |
07:07.55 | tmzt | is the work queue still neccessary? |
07:07.58 | maejrep | but the delay means you have to hold for longer than usual in order for it to register the release event |
07:07.59 | *** join/#htc-linux meetdave (n=meetdave@S0106002129c35dd9.gv.shawcable.net) |
07:08.08 | maejrep | i'm not sure |
07:08.23 | tmzt | I don't think you are supposed to sleep in irq context if you have to have a delay |
07:08.45 | tmzt | very cool though |
07:08.50 | maejrep | about damn time :P |
07:08.59 | maejrep | and you can sleep in a workqueue |
07:09.05 | maejrep | just not in the irq handler |
07:09.17 | tmzt | but it lead to some information about irqs and vregs through some weird process of discovery |
07:09.21 | tmzt | yeah |
07:10.16 | maejrep | I think once I clean it up and find out exactly what it needs to not clobber other events, it'll perform better |
07:11.07 | tmzt | what other events? |
07:11.23 | maejrep | like if I press and release too quickly, it won't register the release properly |
07:11.35 | maejrep | it'll show as releasing scancode 0 |
07:11.50 | tmzt | does the keyboard support multiple keys? |
07:11.54 | tmzt | in ce |
07:12.11 | maejrep | yes |
07:12.19 | maejrep | at least, for things like shift, ctrl, fn, etc |
07:12.47 | tmzt | what do press release events look like? |
07:12.59 | tmzt | s/ss re/ss and re/ |
07:14.16 | maejrep | they look the same, but with a bit set on release: |
07:14.44 | maejrep | 002.491 7803d944: ldr r3, [r3] # b230000c==00000008 <-- press |
07:14.46 | maejrep | 003.501 7803d944: ldr r3, [r3] # b230000c==00000088 <-- release |
07:14.59 | maejrep | 0x80 is set on release |
07:15.34 | *** join/#htc-linux pichurri (n=pichurri@users3.ilo.org) |
07:16.20 | *** join/#htc-linux _workkaze (n=kaze@ABordeaux-152-1-28-129.w83-193.abo.wanadoo.fr) |
07:16.28 | tmzt | what does it look like if you press/release quickly? |
07:17.15 | maejrep | http://www.privatepaste.com/5b1fhmpar2 - this is from my printks heh |
07:18.30 | maejrep | i don't think i have a dump showing it quickly |
07:19.50 | tmzt | when you say keycode 0, you mean 0x80 is the keycode or 0? |
07:20.27 | maejrep | the address responds with '0' |
07:20.28 | tmzt | how many keycodes are there, there has to be more the 16 so I'm missing something |
07:20.39 | maejrep | so what I said above was wrong: looks like you're pressing scancode 0 |
07:20.50 | tmzt | could it not have data ready or you have to mask/unmask something else? |
07:20.57 | maejrep | yes, there's more than 16 ;o |
07:21.07 | maejrep | http://wiki.xda-developers.com/index.php?pagename=RaphaelKeyboard |
07:21.21 | maejrep | 0x01 - 0x47 |
07:21.40 | tmzt | <PROTECTED> |
07:21.48 | tmzt | <PROTECTED> |
07:22.05 | maejrep | right |
07:22.25 | tmzt | the channel only returns one byte at a time? |
07:22.27 | maejrep | which gives you up to 127 possible values in between |
07:22.31 | maejrep | yes |
07:22.41 | tmzt | can you decode what writing 0x50 means |
07:22.41 | maejrep | though it returns 2 (separately) |
07:22.57 | maejrep | request notifications, stop notifications |
07:23.10 | maejrep | 0x50,0x01 = requeset, 0x50,0x00 = stop |
07:23.23 | maejrep | and after each irq fires, you have to re-request |
07:23.31 | tmzt | do you see any 0x50 messages with other operands? |
07:23.38 | maejrep | nope |
07:23.48 | maejrep | only spotted the 0x00 by luck |
07:23.58 | maejrep | otherwise I would have assumed it was always 0x01 |
07:24.15 | tmzt | this isn't flow control though, it's enabling/masking the irq? |
07:24.59 | maejrep | no, sending 0x50,0x01 makes it bring GPIO 27 high |
07:25.13 | maejrep | which is what resets the IRQ to be fired again |
07:25.37 | maejrep | we still have to disable/enable the IRQ separately (i guess technically we don't even have to do that, but I do) |
07:25.56 | maejrep | actually we probably do have to, since the 50 reset happens between two ce/cf reads |
07:26.27 | tmzt | you mean in the kernel or on the msm? |
07:26.38 | maejrep | which? |
07:27.21 | maejrep | i mean wince reads from ce,10, then reads from ce,11, then sends cc,50,1, then reads from ce,10 and ce,11 again |
07:27.26 | *** join/#htc-linux rmoravcik (n=rmoravci@gtsgw.ttc.cz) |
07:27.36 | maejrep | I don't know why |
07:28.22 | maejrep | but I do notice that the 2nd ce,10 read does not have the same scancode in its response |
07:29.02 | maejrep | http://www.privatepaste.com/8817Tbah5Q -- a raw haret trace |
07:30.00 | maejrep | bbiaf |
07:32.38 | *** join/#htc-linux cr2 (n=cr2@ip-90-187-20-7.web.vodafone.de) |
07:33.01 | tmzt | cr2: maejrep has found how to reenable the irq from the chip |
07:33.12 | tmzt | cr2: not on the msm side but an i2c write |
07:34.12 | *** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo) |
07:36.43 | maejrep | ok, I'm off to bed :p |
07:37.22 | maejrep | I documented that 0x50 in KLT |
07:37.56 | tmzt | there are two writes and two reads |
07:37.57 | tmzt | ? |
07:38.02 | cr2 | maejrep: alt=3 is not a must for the irqs |
07:38.05 | tmzt | in that trace each keypress |
07:38.27 | cr2 | i need more gpio cfg data from other phones |
07:38.51 | cr2 | to split the alt cfg into pull,alt,drvstr |
07:39.33 | maejrep | tmzt: the ce,10 and ce,11 are both reads |
07:40.06 | tmzt | http://www.privatepaste.com/8817Tbah5Q |
07:40.11 | maejrep | it does ce,10 and ce,11 then writes to cc,50, then reads ce,10 and ce,11 again |
07:40.39 | cr2 | and i will fix my raph100 gpio docs too |
07:41.23 | tmzt | 03:14 < tmzt> can you decode what writing 0x50 means |
07:41.23 | tmzt | 03:14 < maejrep> though it returns 2 (separately) |
07:41.23 | tmzt | 03:14 < maejrep> request notifications, stop notifications |
07:41.24 | tmzt | 03:14 < maejrep> 0x50,0x01 = requeset, 0x50,0x00 = stop |
07:41.24 | tmzt | 03:15 < maejrep> and after each irq fires, you have to re-request |
07:41.26 | tmzt | 03:15 < tmzt> do you see any 0x50 messages with other operands? |
07:41.28 | tmzt | 03:15 < maejrep> nope |
07:41.53 | maejrep | that was wrong -- I did see 0x50 with a 0 after checking my haret logs |
07:42.01 | cr2 | maejrep: hmm, i need to check. didn't see 0x50 here |
07:42.10 | maejrep | haretlog-20090109_233258.log-000225: mmutrace 7803dad4: e5863000(str) b2300000 000001cc (00000000) |
07:42.10 | maejrep | haretlog-20090109_233258.log:000225: mmutrace 7803db0c: e5863000(str) b2300000 00000050 (00000000) |
07:42.10 | maejrep | haretlog-20090109_233258.log-000225: mmutrace 7803db48: e5863000(str) b2300000 00000200 (00000000) |
07:42.31 | maejrep | the 0x200 just means its the last byte being written |
07:42.32 | cr2 | maejrep: there are a lot of variations for 0xcc |
07:42.39 | tmzt | how did you get that header with grep? I get it sometimes and sometimes not |
07:42.41 | maejrep | so its actually writing 50,00 |
07:42.59 | cr2 | but the variant detection code is not yet written :) |
07:43.01 | maejrep | tmzt: I grepped on *, so it reports the filename it was found in |
07:43.21 | tmzt | I wish that worked with -r without find magic, thanks anyway |
07:43.26 | maejrep | if you grep on just one file, you don't see the filename |
07:43.35 | maejrep | you can still make it spit out the filename |
07:43.35 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
07:43.38 | maejrep | with -l i think? |
07:43.55 | maejrep | no, maybe -H: -H, --with-filename print the filename for each match |
07:44.15 | cr2 | maejrep: which dll handles the 0xcc/navi ? |
07:44.30 | tmzt | anyway my question was about the two ldr's in a row |
07:44.30 | maejrep | i think its a combination of keypad.dll and htcnavi.dll |
07:44.54 | maejrep | oh, that means the chip responded with 2 bytes |
07:44.56 | *** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz) |
07:45.58 | cr2 | maejrep: i think many ops return multibyte buffers |
07:46.04 | maejrep | yes |
07:46.09 | maejrep | navi returns 18 :) |
07:46.36 | cr2 | i have (at least tried) to add 'multi' where it was obvious |
07:47.09 | cr2 | ok, going to work now. |
07:47.15 | maejrep | going to bed :P |
07:47.21 | cr2 | bye |
07:53.11 | *** join/#htc-linux _7lima_ (n=7lima@ham-dakosy-hsrp.eurogate.eu) |
07:57.04 | Untouchab1e | new day, new possibilities |
07:57.08 | Untouchab1e | :) |
07:57.20 | tmzt | hey, what is a .kcm? |
07:58.23 | Untouchab1e | its actually a binary layout file (.bin) extracted as a text file (I think). I just found qwerty.kcm file, edited it, and now need to build it back to a binary layout file (.bin) in order to copy it back to my ADP1 |
07:59.08 | tmzt | is this specific to android? |
07:59.20 | Untouchab1e | qwerty.kcm if android specific I think, yeah |
07:59.21 | tmzt | or is this a form of the kernel keymap (loadkeys)? |
08:00.07 | tmzt | can you paste one or two meaningful lines if this is plain text? |
08:00.21 | Untouchab1e | yeah, h/o |
08:00.40 | Untouchab1e | # keycode display number base caps fn caps_fn |
08:00.40 | Untouchab1e | <PROTECTED> |
08:00.40 | Untouchab1e | A 'A' '2' 'a' 'A' 'a' 'A' |
08:00.40 | Untouchab1e | B 'B' '2' 'b' 'B' 'b' 'B' |
08:00.40 | Untouchab1e | C 'C' '2' 'c' 'C' 0x00e7 0x00E7 |
08:01.16 | tmzt | that doesn't look like a kernel keymap then unless it's a very simplified form |
08:01.28 | Untouchab1e | you can get it from: http://android.git.kernel.org/?p=platform/development.git;a=blob_plain;f=emulator/keymaps/qwerty2.kcm;hb=HEAD |
08:01.48 | Untouchab1e | http://forum.xda-developers.com/showthread.php?t=468703 |
08:01.50 | tmzt | this is not form g1/adp1 I think but qemu |
08:06.09 | tmzt | Untouchab1e: can you find it in core.git or anywhere other than .../emulator/... ? |
08:07.58 | tmzt | Untouchab1e: from reading kernel source I believe this is actually handled in the kernel through a command line option |
08:08.12 | tmzt | Untouchab1e: it mentions qwertz for instance |
08:09.06 | Untouchab1e | I remember something about that I read yesterday, will try to find it again, h/o (in class too, so a bit slow atm :) ) |
08:09.57 | tmzt | it's still linux, you can load a kernel keymap with busybox, it also uses a binary format that we haven't been able to convert |
08:17.34 | tmzt | Untouchab1e: huh, it appears it is android/linux related http://groups.google.com/group/android-developers/msg/59d787140217fe60 |
08:17.40 | tmzt | search for kcm |
08:18.07 | tmzt | something called EventHub |
08:18.18 | *** join/#htc-linux tsdogs (n=tsdogs@net70-17.metalit.net) |
08:25.05 | Untouchab1e | hmm |
08:26.12 | Untouchab1e | tmzt, do you have a Diamond or Raph? |
08:26.36 | tmzt | neither |
08:27.22 | tmzt | I'm going to look at the eventhub and keyinputqueue for my own reasons soon |
08:27.49 | tmzt | I hope to get all the calibration out of the kernel on devices with keyboards |
08:28.05 | tmzt | if I find anything interesting I will let you know |
08:28.37 | Untouchab1e | cool! thank you |
08:29.32 | Untouchab1e | Im just trying to get easier access to norwegian characters on the G1's qwerty keyboard ^^ |
08:29.38 | *** join/#htc-linux _7lima (n=7lima@ham-dakosy-hsrp.eurogate.eu) |
08:30.46 | Untouchab1e | Reason I asked you about the Diamond and Raph is because I have a raph, and when running Android on it, I feel that the resistive screen just isnt good enough. I cant drag the notification curtain down, and the cupcake keyboard isnt very usuable. I think this is partly due to the VGA resolution (which is much higher than the G1's) and the resistive touch screen |
08:34.07 | tmzt | possibly, the limitation might be in the kernel but I'm not sure |
08:34.33 | Untouchab1e | what kind of limitations? |
08:35.19 | tmzt | the kernel does some scaling on the touchscreen data which is necessary for vkeyb |
08:35.42 | tmzt | a real keyboard driver might be more interesting anyway |
08:40.59 | Untouchab1e | yeah |
08:55.34 | Untouchab1e | Damn, weather is nice here today ^^ |
09:12.03 | *** join/#htc-linux _7lima (n=7lima@ham-dakosy-hsrp.eurogate.eu) [NETSPLIT VICTIM] |
09:23.58 | lupine_85 | ooooh, cool, maejrep: you seem to be awesome :) |
09:26.51 | Untouchab1e | PointUI Home 2 might be released very soon |
09:26.56 | Untouchab1e | considering their website is down for "maintenance" |
09:34.33 | *** join/#htc-linux dream_kill (n=nospam@92.56.48.66) |
09:35.08 | *** join/#htc-linux imfloflo (n=imfloflo@cap31-6-88-180-73-121.fbx.proxad.net) |
09:35.11 | *** join/#htc-linux metter (n=metter@159.86.202.62.cust.bluewin.ch) |
09:38.07 | lupine_85 | boooo, missing init |
09:47.46 | *** join/#htc-linux timebomb (n=tb@e176117163.adsl.alicedsl.de) |
09:50.21 | Untouchab1e | ? |
09:51.44 | *** join/#htc-linux RZK333 (n=rzk@daemonet.ru) |
09:56.19 | *** join/#htc-linux imfloflo_ (n=imfloflo@cap31-6-88-180-73-121.fbx.proxad.net) |
09:57.59 | *** join/#htc-linux radem205 (n=aaa@92-108-47-154.dynamic.upc.nl) |
09:58.10 | *** join/#htc-linux imfloflo (n=imfloflo@cap31-6-88-180-73-121.fbx.proxad.net) |
10:07.31 | *** join/#htc-linux rmoravcik (n=rmoravci@gtsgw.ttc.cz) |
10:16.33 | *** join/#htc-linux pichurri (n=pichurri@users3.ilo.org) |
10:19.24 | *** join/#htc-linux BabelO_ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net) |
10:24.12 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
11:06.43 | *** join/#htc-linux dcordes (n=zsirc@ip-77-24-27-212.web.vodafone.de) |
11:16.33 | *** join/#htc-linux kilian_ (n=kilian@92.66.94.81) |
11:23.06 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
11:47.15 | lupine_85 | dcordes: fso-image is missing an init ? |
11:47.48 | lupine_85 | (unless I'm missing something) |
11:50.53 | *** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be) |
11:56.10 | *** join/#htc-linux Shark_7-11 (n=Wallace@uu-041-209-022-011.uunet.co.ke) |
11:58.17 | Shark_7-11 | hello, anyone here? |
12:09.07 | dcordes | lupine_85 I did only build fso-console-image |
12:13.53 | lupine_85 | dcordes: no worries. I shall add init - plus anything else that might show up - to fso-image |
12:14.17 | lupine_85 | (in fact, I might just add all of fso-console-image's packages to fso-image. it makes sense to me) |
12:14.36 | *** join/#htc-linux _7lima (n=7lima@ham-dakosy-hsrp.eurogate.eu) |
12:21.33 | Shark_7-11 | so on that technical note.. where do i ask newb qquestions like "Which rom is best for kaiser" |
12:27.25 | dcordes | Shark_7-11 xda-devs ? |
12:27.46 | dcordes | I'm using the latest htc WWE english rom now |
12:31.14 | dcordes | #xda-devs |
12:45.02 | Shark_7-11 | dcordes: k cool tx |
12:45.08 | *** part/#htc-linux Shark_7-11 (n=Wallace@uu-041-209-022-011.uunet.co.ke) |
12:51.29 | *** join/#htc-linux BabelO_ (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net) |
12:54.07 | *** join/#htc-linux stefan_schmidt (n=stefan@w1769.wlan.rz.tu-bs.de) |
12:55.44 | *** join/#htc-linux mightymouse (n=wmirc_us@174-144-153-217.pools.spcsdns.net) |
12:56.34 | *** part/#htc-linux yoyey (n=yoann@bro69-3-82-237-160-83.fbx.proxad.net) |
13:14.08 | *** join/#htc-linux t3chi3 (n=blarg@ip24-250-216-85.ga.at.cox.net) |
13:14.44 | *** join/#htc-linux piusvelte (n=chatzill@nat.philau.edu) |
13:36.04 | *** join/#htc-linux nato2k (n=templarn@76.250.180.218) |
13:37.40 | *** join/#htc-linux bffn (n=jonas@ua-85-227-18-133.cust.bredbandsbolaget.se) |
13:38.50 | bffn | pichurri, any progress regarding the lcd issues on blackstone? |
13:39.13 | pichurri | bffn, hey there, sorry, haven't had time... |
13:39.42 | pichurri | bffn, I know that at least 3 other guys are working on that too, but I guess they haven't got time either...:( |
13:40.01 | bffn | pichurri, ok. |
13:40.54 | bffn | pichurri, I have setup my dev enviroment for blackstone (kernel, ssh access etc). So I'm rdy to help with the port. |
13:41.40 | bffn | pichurri, do you have any public git repo or git branch? |
13:44.54 | pichurri | we're still using the raphael/diamond ones... |
13:45.29 | pichurri | I posted a patch against but on late december there were some changes, so it might not work... |
13:47.03 | pichurri | I mean, with the latest version, but should be easily to update, some guy here at irc, said that apparently mmc interface is the same, so android 1.0 is just 1 step away, if we correct screen output that is., |
13:47.36 | pichurri | still, all the other drivers, buttons and stuff is missing, but, it'd be nice to have android booting/running. :) |
13:50.16 | mightymouse | whats the progress on getting color issue fixed on DIAM500 for android? |
13:51.13 | mightymouse | this is the fiam version for the sprint network |
13:54.25 | *** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz) |
13:59.09 | bffn | picurri, yeah I noticed that the patch did not apply clean, but I managed to fix the conflicts (I think). |
14:04.09 | *** join/#htc-linux dream_kill (n=nospam@92.56.48.66) |
14:06.12 | *** join/#htc-linux xutywx (n=xutywx@195.205.38.92) |
14:06.50 | maejrep | C 'C' '2' 'c' 'C' 0x00e7 0x00E7 <-- someone was being a smartass? ;p |
14:06.59 | *** join/#htc-linux nato2k (n=templarn@76.250.180.218) |
14:07.04 | *** join/#htc-linux xutywx (n=xutywx@195.205.38.92) |
14:12.21 | *** join/#htc-linux Armand (n=Armand@SantaYnez-11-116.resnet.ucsb.edu) |
14:17.00 | *** join/#htc-linux kiozen (n=oeichler@rgnb-5d87c53c.pool.einsundeins.de) |
14:24.01 | *** join/#htc-linux gmarzioz (n=gmarzioz@host11-34-dynamic.61-82-r.retail.telecomitalia.it) |
14:24.39 | gmarzioz | hi |
14:25.08 | gmarzioz | i can use tux in a blueangel qtek9090 ??? |
14:26.23 | BabelO_ | gmarzioz: you again ? :) |
14:28.48 | gmarzioz | yes |
14:29.02 | gmarzioz | i hate windows |
14:29.10 | gmarzioz | but i have many problem |
14:29.15 | gmarzioz | !!!! |
14:29.52 | gmarzioz | how i can resolve |
14:30.47 | gmarzioz | what pda you have?? |
14:30.54 | gmarzioz | BabelO_, |
14:31.29 | gmarzioz | the upgrade go dowc |
14:31.32 | gmarzioz | down |
14:31.45 | gmarzioz | the kernel not boot |
14:31.48 | *** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring) |
14:42.54 | AstainHellbring | morning |
14:47.03 | BabelO_ | gmarzioz: i have htc blueangel , and i ve done the bluenagel image available at linuxtogo |
14:52.02 | gmarzioz | ok now i try |
14:54.06 | *** join/#htc-linux addman3333 (n=azachars@nat/sun/x-3fb1aa71d08356b4) |
14:54.40 | *** join/#htc-linux skola28 (n=skola28@32.144.76.121) |
15:13.30 | *** join/#htc-linux kiozen (n=oeichler@rgnb-5d87c53c.pool.einsundeins.de) |
15:15.41 | *** join/#htc-linux MethoS (n=lem@host-091-097-244-073.ewe-ip-backbone.de) |
15:31.25 | skola28 | too much chatter this morning! |
15:32.45 | *** join/#htc-linux t3chi3 (n=blarg@n128-227-109-82.xlate.ufl.edu) |
15:33.25 | *** join/#htc-linux claus (i=claus@clausdal.dk) |
15:43.21 | *** join/#htc-linux GPFerror (n=gpferror@cpe-76-187-41-132.tx.res.rr.com) |
15:46.42 | gmarzioz | BabelO_, can you send me a link for blueangel ?? |
15:46.55 | *** join/#htc-linux exco (n=exco@e181105080.adsl.alicedsl.de) |
15:49.29 | *** join/#htc-linux addman3333 (n=azachars@nat/sun/x-5383df373c304724) |
15:52.04 | *** part/#htc-linux claus (i=claus@clausdal.dk) |
15:58.02 | *** join/#htc-linux goxboxlive (n=goxboxli@24.84-48-212.nextgentel.com) |
16:02.12 | *** part/#htc-linux bffn (n=jonas@ua-85-227-18-133.cust.bredbandsbolaget.se) |
16:02.27 | *** join/#htc-linux Othello (i=Othello@gateway/tor/x-d6939e512cf03eb1) |
16:07.27 | gmarzioz | sorry |
16:07.44 | gmarzioz | what is a jffs2 ???? |
16:09.04 | *** join/#htc-linux XD (i=t3st1fy@ircop.com) |
16:09.22 | AstainHellbring | gmarzioz its a file system |
16:10.27 | gmarzioz | nd |
16:10.46 | gmarzioz | i'm trind openmoko for blueangel |
16:10.59 | gmarzioz | how i must procede |
16:11.10 | gmarzioz | first the tar.gz |
16:11.24 | gmarzioz | and later the jffs2 !!! |
16:12.15 | gmarzioz | AstainHellbring, help |
16:12.43 | AstainHellbring | sorry dunno much on the blueangel systems |
16:14.00 | gmarzioz | AstainHellbring, how i can use that jffs2? |
16:38.47 | *** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz) |
17:05.10 | *** join/#htc-linux Guimli (n=guimli@ecu69-1-82-231-127-213.fbx.proxad.net) |
17:05.53 | *** join/#htc-linux gmarzioz (n=gmarzioz@host11-34-dynamic.61-82-r.retail.telecomitalia.it) |
17:19.45 | *** join/#htc-linux Rogro82 (n=rogro82@s5591104d.adsl.wanadoo.nl) |
17:29.11 | *** join/#htc-linux Balsat (n=kll@87.72.13.87) |
17:40.29 | *** join/#htc-linux _7lima (n=7lima@p5099402d.dip0.t-ipconnect.de) |
17:52.20 | *** join/#htc-linux Untouchab1e (n=Untoucha@82.147.51.146) |
17:53.58 | *** join/#htc-linux Balsat (n=kll@87.72.13.87) |
17:55.27 | *** join/#htc-linux mightymouse (n=wmirc_us@174.144.153.217) |
18:08.09 | gmarzioz | nessuno che mi da una mano??? |
18:08.52 | *** join/#htc-linux dcordes (n=dcordes@unaffiliated/dcordes) |
18:11.45 | *** join/#htc-linux mrincredible (n=wmirc_us@174-144-153-217.pools.spcsdns.net) |
18:12.44 | dcordes | lupine_85: any luck with that fso-image? |
18:16.25 | *** join/#htc-linux Armand (n=Armand@SantaYnez-11-116.resnet.ucsb.edu) |
18:32.07 | *** join/#htc-linux mrincredible (n=wmirc_us@174-144-153-217.pools.spcsdns.net) |
18:39.15 | *** join/#htc-linux mrincred (n=wmirc_us@174-144-153-217.pools.spcsdns.net) |
18:51.25 | *** join/#htc-linux infernixx (n=nix@unaffiliated/infernix) |
18:58.13 | *** join/#htc-linux Armand (n=Armand@SantaYnez-11-116.resnet.ucsb.edu) |
18:58.52 | dcordes | did somebody try the new PIO code in htc-vogue ? |
18:58.57 | dcordes | for sd |
18:59.56 | *** join/#htc-linux gmarzioz_ (n=gmarzioz@host11-34-dynamic.61-82-r.retail.telecomitalia.it) |
19:02.51 | *** join/#htc-linux Balsat (n=kll@87.72.13.87) |
19:04.35 | maejrep[w] | what is PIO ? :) |
19:06.38 | *** join/#htc-linux imfloflo (n=imfloflo@cap31-6-88-180-73-121.fbx.proxad.net) |
19:11.29 | *** join/#htc-linux kimhoon (n=kimhoon@s559116c1.adsl.wanadoo.nl) |
19:14.29 | dcordes | dzo: could you upload the kernel with the updated PIO code somewhere and drop a link in here? |
19:14.32 | dcordes | bbl |
19:17.23 | *** join/#htc-linux stefan_schmidt (n=stefan@p5B037356.dip.t-dialin.net) |
19:26.41 | *** join/#htc-linux kaze_ (n=kaze@pac33-1-82-235-251-34.fbx.proxad.net) |
19:28.30 | *** join/#htc-linux SKyLiNe (n=SKyLiNe@195-240-0-202.ip.telfort.nl) |
19:28.50 | *** join/#htc-linux exco (n=exco@e181105080.adsl.alicedsl.de) |
19:29.00 | [SKyLiNe] | evening :) |
19:30.24 | *** join/#htc-linux marmotta (n=skodde@unaffiliated/skodde) |
19:30.40 | *** part/#htc-linux exco (n=exco@e181105080.adsl.alicedsl.de) |
19:36.11 | *** join/#htc-linux Balsat (n=kll@87.72.13.87) |
19:43.14 | *** join/#htc-linux stefan_schmidt (n=stefan@p5B033FAA.dip.t-dialin.net) |
19:51.11 | *** join/#htc-linux timebomb (n=tb@p548F8269.dip0.t-ipconnect.de) |
19:51.20 | *** join/#htc-linux drasar (n=maik@lamer.optinet.cz) |
19:52.55 | *** join/#htc-linux cr2 (n=cr2@ip-90-187-248-205.web.vodafone.de) |
19:59.16 | *** join/#htc-linux rubberducky (n=rubberdu@83.101.31.73) |
19:59.25 | rubberducky | anyone got aircrack-ng to do packet injection on blueangel? |
19:59.51 | rubberducky | ? |
19:59.53 | rubberducky | ping |
20:00.14 | zycho | ping |
20:00.36 | rubberducky | hi |
20:01.06 | zycho | hi |
20:01.19 | rubberducky | packet injection? |
20:02.14 | cr2 | maejrep[w]: the 0xc4 is psoc, and 0xcc/0xce is microP |
20:03.06 | rubberducky | ? |
20:03.13 | cr2 | maejrep[w]: so there may be 2 chips |
20:14.35 | cr2 | in PCOM_GPIO_CFG the func is 4 bits, pull is 2 bits and drvstr is 4 bit |
20:15.26 | cr2 | and they are combined into the wiki 'alt' value |
20:16.14 | *** join/#htc-linux Balsat (n=kll@87.72.13.87) |
20:19.10 | [SKyLiNe] | hm. android wont take my sim pin :S |
20:22.53 | *** join/#htc-linux tsdogs (n=tsdogs@net203-187-146.mclink.it) |
20:26.56 | cr2 | kiozen: the bootloader that we have dumped with you is identical to my code |
20:27.44 | cr2 | kiozen: i've found the data in the referenced location, but now i have another strange problem |
20:27.50 | cr2 | bx lr |
20:27.52 | *** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbf985a.pool.einsundeins.de) |
20:28.31 | cr2 | is called without any subroutine context. i'm confused ;) |
20:28.58 | *** join/#htc-linux Xime (n=xime@bankize.net) |
20:31.03 | *** join/#htc-linux Mullins (n=bw@89.204.250.9) |
20:40.30 | Mullins | dzo: Is the latest GIT revision running Android for you on Kaiser? |
20:41.30 | *** join/#htc-linux dcordes (n=zsirc@ip-77-25-252-140.web.vodafone.de) |
20:42.03 | dcordes | Mullins hi |
20:42.15 | Mullins | dcordes: hi, I posted the latest GIT revision for you |
20:42.31 | Mullins | boots Angstrom but resets at Android startup |
20:42.42 | *** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be) |
20:43.09 | dcordes | does sd work? |
20:43.27 | Mullins | hmm, sec I will see |
20:44.20 | *** join/#htc-linux ltxda (n=anon@unaffiliated/ltxda) |
20:44.37 | dcordes | maybe it freezes during the andeoid bootup because smd writes kil arm9 |
20:49.02 | Mullins | cant tab is it mmcblk0p1? |
20:51.28 | cr2 | dcordes: can you calculate the clock speeds for kaiser ? |
20:51.54 | *** join/#htc-linux XD (i=t3st1fy@ircop.com) |
20:52.18 | drasar | Hi cr2 |
20:52.38 | dcordes | Mullins uncertain what you mean mmcblk0p1 is first part on the first sd card |
20:53.17 | dcordes | cr2 if you give me some pointers I'll give it a go |
20:53.34 | dcordes | didn't calculate much since end of school |
20:53.52 | drasar | cr2: Did you try to commit my himalaya patch to the hh.org CVS? |
20:54.27 | Mullins | dcordes: device reset when I tried to copy from SD card |
20:55.12 | Mullins | dcordes: Am seeing events for the cursor keys now though which is great |
20:58.53 | cr2 | drasar: i don't have a linux computer with a net access yet. wait till the weekend |
21:00.37 | cr2 | dcordes: at the bottom |
21:00.44 | cr2 | http://wiki.xda-developers.com/index.php?pagename=MSM_SDIO |
21:03.13 | dzo | hi dcordes, i've been playing with kaiser sd a lot, pio mode crashes just the same as dma so its not a dma problem. i've got some ideas, looking at how the clock gets set up now, there is some extra stuff that kaiser does, hopefully that will help. |
21:03.52 | Mullins | dzo: should latest commit run Android? |
21:05.06 | dzo | it does sometimes with the 1.65.24 radio but what i think is happening is that amss crashes and on that radio version it just lets the a11 keep going while other radios kill it. |
21:05.07 | *** join/#htc-linux br1ck (n=br1ck@xdslck144.osnanet.de) |
21:05.56 | dzo | the error the gets printed on the at channel happens exactly the same time that radio 1.71 craps out. |
21:06.34 | Mullins | dzo: grand, just thought I had something different on my end. |
21:07.19 | dzo | on 1.65.24 sometimes it reboots but sometimes it survives but amss is still dead which is why smd channels don't work. |
21:08.02 | dzo | i'll work on it today and see what i can do, i'm narrowing it down though. |
21:08.29 | cr2 | dzo: you are fixing the sd clock now ? |
21:09.07 | Mullins | dzo: and you can see the cursor keys now judging by the debug messages? |
21:09.30 | dzo | trying to, kaiser uses some strange magic while enabling it (not rpc or pcom) but some writes to smem. |
21:10.18 | dzo | Mullins: yes, i ripped out the cpld key polling, it just has to be redone using interrupts, not hard. |
21:10.38 | Mullins | dzo: nice, thanks. I leave you in peace now! |
21:11.29 | *** join/#htc-linux Rogro820 (n=rogro82@s5591104d.adsl.wanadoo.nl) |
21:11.34 | *** join/#htc-linux HeLLs (n=at@host86-139-130-112.range86-139.btcentralplus.com) |
21:11.44 | dzo | cr2: it also writes to AXI ROW_RESET at CLK_CTL+0x214 for some reason. |
21:11.56 | cr2 | dzo: is it the gp6 vreg ? i'm a bit 7201A biased, don't know how it's done on 7200. |
21:12.15 | cr2 | hmm. ok. |
21:12.46 | HeLLs | anyone has been able to get android os in the htc s620? |
21:12.50 | dzo | on 7200 its all done directly with the bits in CLK_CTL |
21:13.39 | cr2 | a0/a4 and a8/ac |
21:13.49 | Rogro820 | dzo: any luck on getting the smd code to work? |
21:13.50 | cr2 | but 0x214 is strange... |
21:13.52 | dzo | yes |
21:14.24 | dzo | Rogro82: I think smd code will work when the sd problem is really fixed. |
21:14.25 | cr2 | dzo: the a0/a4 part is the same on all out msm phones. |
21:15.44 | Rogro820 | dzo: I can make it boot using the smd code sometimes on my polaris... but most of the time it crashes on the fatal errors (WCDMA fatal etc)... |
21:16.57 | Rogro820 | dzo: noticed its more stable when you turn on the phone and the data connection in winmo and load a page in the webbrowser... youll see the page getting downloaded on boot but most of the time it continues after the errors... strange |
21:17.27 | Rogro820 | dzo: but if it does the connection will fail and it throws a pmem error |
21:22.00 | *** join/#htc-linux diogene31 (n=rj@mur31-2-82-243-122-54.fbx.proxad.net) |
21:26.04 | drasar | cr2: ok, I shouldn't be so impatient :) |
21:28.41 | *** join/#htc-linux br1ck (n=br1ck@xdslck144.osnanet.de) |
21:30.13 | *** join/#htc-linux dcordes (n=zsirc@ip-90-187-155-139.web.vodafone.de) |
21:30.19 | tmzt | dzo: how is the smd problem related to the sd problem? |
21:34.17 | cr2 | dzo: from the wiki -> +0x214 sd related |
21:34.42 | cr2 | so i've seen it too ;) |
21:36.29 | tmzt | 09:41 < mightymouse> whats the progress on getting color issue fixed on |
21:36.29 | tmzt | <PROTECTED> |
21:36.29 | tmzt | 09:42 < mightymouse> this is the fiam version for the sprint network |
21:36.36 | tmzt | what?? |
21:38.15 | cr2 | tmzt: the epson mddi contrller needs a different setup from toshiba |
21:39.20 | tmzt | yeah, I mean why is diam500 on sprint |
21:39.45 | tmzt | raph500 is verizon, so I thought diam500 was also |
21:39.58 | *** join/#htc-linux exco (n=exco@e181105080.adsl.alicedsl.de) |
21:40.14 | tmzt | what is a write to smd other than DEX/proc_comm/rpc/ONRPC ? |
21:41.15 | cr2 | there is an interface to the "radio bootloadr" for pmic control |
21:41.27 | cr2 | but it's not used in wince itself |
21:43.18 | *** join/#htc-linux pichurri (n=pichurri@194.230.146.90) |
21:53.55 | *** join/#htc-linux NetRipper (n=netrippe@netripper.nl) |
21:54.01 | *** join/#htc-linux Czarnas (n=czarnas@imik.wip.pw.edu.pl) |
21:54.37 | NetRipper | bitch ass internet connection |
21:54.48 | cr2 | hehe |
21:55.28 | cr2 | NetRipper: i don't see any reason why you do not get the ts irq |
21:56.53 | NetRipper | cries |
21:57.22 | NetRipper | cant it be i have to reset some flag somewhere? as in... the ts hardware doesn't issue a new interrupt as long as it doesn't see a "processed" flag? |
21:57.25 | cr2 | can you create a barebones msm_ts2.c driver ? |
21:57.42 | tmzt | tssc is a adc builtin to the msm chip? |
21:57.58 | cr2 | something like that |
21:58.01 | NetRipper | oh yea, it should be |
21:58.27 | tmzt | I mean is it generic and does it have a block of address space with it's own registers? |
21:58.34 | dzo | NetRipper: is it a cpld interrupt? |
21:58.37 | tmzt | rather than a dedicated ts controller |
21:58.41 | cr2 | barebones == without any weird android stuff |
21:58.58 | NetRipper | dzo, what is cpld? |
21:59.12 | cr2 | dzo: no, it's a core msm vic irq |
21:59.33 | dzo | what device are we talking about |
21:59.41 | NetRipper | raph* and diam* |
21:59.59 | dzo | OK, does that use the msm ts then. |
22:00.12 | NetRipper | druidu wrote a msm_ts driver |
22:00.15 | cr2 | dzo: yes |
22:00.44 | cr2 | NetRipper: if the irq is enabled, you'd get the irq |
22:00.47 | NetRipper | it request_irq()'s the interrupt... and we have seen it fire... occasionally... exceptionally.. but only once and not reprodable |
22:00.51 | NetRipper | reproduceable |
22:01.06 | cr2 | NetRipper: can you post the link to msm-ts.c ? |
22:01.10 | NetRipper | yes, sec. |
22:02.09 | NetRipper | http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=blob;f=drivers/input/touchscreen/msm_ts.c;h=ca4a7bdae0b3ffde5c505656c29c8c6ff18ffee1;hb=34c8afa173e6e8080eb2e26174e90ef0c29831e8 |
22:02.20 | cr2 | thanks |
22:04.15 | cr2 | writel(readl(MSM_TS_BASE + TSSC_CTL) & ~0xc00, MSM_TS_BASE + TSSC_CTL); |
22:04.35 | cr2 | should be ~0x800 |
22:04.40 | cr2 | to look better |
22:05.07 | cr2 | haret will show 0xc00, but it's 0x800 in the wincve driver |
22:05.27 | NetRipper | aren't it two flags? |
22:05.34 | NetRipper | the 0xc00 just combines two flags afaik |
22:06.06 | cr2 | yes, it's only a cosmetical change |
22:06.23 | cr2 | because the 0x800 is the data_available flag. |
22:06.45 | cr2 | wince loops on it before reading out the data |
22:07.25 | NetRipper | so what is the 0x400 flag then, which 0xc00 also removes? |
22:07.31 | NetRipper | wince must do that too |
22:08.02 | *** join/#htc-linux DJW|Home (i=djwillis@82-46-19-72.cable.ubr02.bath.blueyonder.co.uk) |
22:08.27 | cr2 | 0x400+0x800=0xc00 |
22:08.37 | NetRipper | yes |
22:08.43 | cr2 | 0x400 at first, and then 0x800 |
22:08.57 | NetRipper | ohhh right |
22:09.00 | NetRipper | it does 0x400 as well |
22:09.03 | NetRipper | sorry |
22:09.04 | cr2 | yes |
22:09.04 | NetRipper | missed that line |
22:10.04 | NetRipper | btw, the TSSC_CTL mentioned there, is different from the TSSC you mentioned in your wiki page |
22:11.09 | NetRipper | is it possible the irq is masked or something like that? |
22:11.14 | tmzt | does halibut use TSSC or the same as trout? |
22:11.43 | cr2 | no, they have an external ts controller |
22:12.03 | cr2 | vogue/kaiser et al. too |
22:12.42 | NetRipper | the really weird thing is that it seems to get fired eventually.. also at a moment when the touchscreen is touched.. but at a random moment |
22:13.09 | cr2 | tssc_ctl is the first reg in the tssc block |
22:13.31 | cr2 | cat you post the /proc/interrupts ? |
22:13.43 | NetRipper | let me boot then |
22:13.46 | NetRipper | sec |
22:13.48 | cr2 | ok |
22:15.42 | NetRipper | i've played around a bit already.. so you'll see 29/30/31 (all touchscreen irqs).. building zimage |
22:16.09 | cr2 | change 0xc00 to 0x800 |
22:17.02 | NetRipper | yes just did |
22:17.12 | *** join/#htc-linux woodyPL_ (i=woody@gateway/shell/blinkenshell.org/x-7c94475f598bbefa) |
22:18.16 | cr2 | ok |
22:20.42 | NetRipper | http://netripper.pastebin.com/m112c0a75 |
22:22.05 | cr2 | how are the mddi,mdp and sdcc irqs requested ? |
22:26.09 | *** join/#htc-linux Xmoo (n=Xmoo@h241015.upc-h.chello.nl) |
22:26.46 | Xmoo | hi all |
22:26.51 | Xmoo | long time agoo |
22:26.54 | Xmoo | got one question |
22:27.05 | Xmoo | Has someone tried getting Android to work on the Touch HD |
22:27.07 | Xmoo | ??? |
22:27.29 | cr2 | Xmoo: yes |
22:27.58 | NetRipper | cr2, INT_SDC2_0 with IRQF_SHARED flag (the sdcc cmd one) |
22:28.25 | Xmoo | cr2 any succes with the screen issue? |
22:29.10 | cr2 | NetRipper: why is it shared ? are there 2 drivers using the same irq ? |
22:29.45 | cr2 | Xmoo: no, somebody should document the epson controller init |
22:29.47 | NetRipper | cr2, i havent seen it.. but mmc driver probably supports it being shared, thus it should be flagged shared for compatibility |
22:30.07 | cr2 | Xmoo: it's the same on raph800/500 |
22:30.41 | cr2 | NetRipper: ok. what bout the others ? |
22:30.54 | Xmoo | I know |
22:31.00 | Xmoo | but why is the screen messed up then? |
22:31.22 | Xmoo | could it be the resolution in the kernell |
22:31.40 | cr2 | Xmoo: because the toshiba controller setup is used |
22:32.06 | cr2 | which g1 and raph100 have in common :) |
22:32.55 | NetRipper | cr2, but for sdc a 'irq resource' is defined.. not sure what it does with the other things in that struct... but to requesT_irq() it only passes the INT_SDC2_0, a callback, and the IRQF_SHARED.... checking the others now |
22:33.23 | Xmoo | what would be the best way to fix that |
22:33.34 | cr2 | Xmoo: the LCD panel will tell you the resolution. you may want to override it only in some strange cases |
22:34.53 | NetRipper | drivers/video/msm/mdp.c: ret = request_irq(INT_MDP, mdp_isr, IRQF_DISABLED, "msm_mdp", NULL); |
22:34.57 | NetRipper | drivers/video/msm/mddi.c: ret = request_irq(irq, mddi_isr, IRQF_DISABLED, name, mddi); |
22:35.09 | NetRipper | those are the mdp and mddi interrupts |
22:35.12 | Xmoo | hmz doesn't tell me any thing |
22:35.21 | cr2 | Xmoo: http://wiki.xda-developers.com/index.php?pagename=RaphaelLCD |
22:35.23 | Xmoo | I think I should pick a day off and try to work with it |
22:35.39 | Xmoo | and what about the X1 having messed u colours |
22:35.46 | Xmoo | this was also oin the touch hd when I booted Android |
22:35.54 | Xmoo | the android loading screen with the small android flashing |
22:35.57 | Xmoo | was messed up |
22:36.57 | addman3333 | cr2, how was that init code obtained? |
22:37.28 | NetRipper | Xmoo, jobo has a patch that makes the colors normal in X, but not in android.. it's a dirty hack where the bitpacking is manually set in msm_fb.c.. the X's fbdev driver honors the bitpacking settings, but android totally ignores it |
22:38.28 | cr2 | Xmoo: there are many differences in the init for non-raph100 devices |
22:38.54 | cr2 | addman3333: by disassembling the spl aka appsbl. |
22:39.30 | NetRipper | hm cr2, something interesting |
22:39.35 | Xmoo | I tried the last one from the raph1000 |
22:39.43 | cr2 | Xmoo: including the voltages, and clock speeds |
22:39.44 | NetRipper | sec let me pastebin it |
22:39.46 | Xmoo | the screen was messed up bit still better than the other kernells |
22:40.20 | cr2 | the current raph100 code is not perfect too |
22:40.39 | NetRipper | cr2, look at the few lines below request_irq() http://netripper.pastebin.com/m31eb65c2 |
22:40.54 | cr2 | and it should implement the "wiki code" too. |
22:42.20 | Xmoo | Hmz alright I think I know currently enough |
22:42.25 | Xmoo | I can't contact Lukas |
22:42.35 | Xmoo | I wanted to give him his X1 so he could also start |
22:42.37 | cr2 | NetRipper: add enable_irq() for ts |
22:42.41 | Xmoo | but he hasn't been on msn for 2 days now :( |
22:42.56 | NetRipper | cr2, already did that.. got an unbalanced irq warning |
22:44.00 | Xmoo | i'm off 2 sleep |
22:44.02 | cr2 | hm. ok |
22:44.02 | Xmoo | good night all |
22:44.29 | cr2 | yes, request_irq probably enables it too |
22:44.39 | NetRipper | cr2, might be interesting too: http://netripper.pastebin.com/d7bfc1d80 |
22:44.43 | NetRipper | yes request_irq enables it |
22:44.57 | NetRipper | and we supress a printk() there |
22:45.04 | cr2 | NetRipper:where is the mdp irq reenabled ? |
22:45.21 | NetRipper | they enable the irq when an mddi transfer is being executed |
22:45.24 | NetRipper | and disable it afterwards |
22:45.37 | NetRipper | cr2, see the paste above |
22:46.35 | cr2 | yes |
22:46.48 | NetRipper | lol let me give you the link to the whole file |
22:46.53 | cr2 | why do you use irqf_disabled ? |
22:47.50 | NetRipper | it was druidu originally that put that, but i believe it is because he wanted to manually disable/re-enable the interrupts to prevent getting an interrupt while already busy handling one |
22:48.14 | cr2 | ok |
22:48.17 | NetRipper | when receiving the interrupt, a work item is scheduled.. which handles the data checks |
22:48.26 | NetRipper | it disables the irq in the meantime |
22:48.57 | cr2 | i suggest to create a small msm-ts2.c for tslib testing |
22:49.21 | NetRipper | why tslib? |
22:49.39 | NetRipper | lupine made a patch that enables the current driver for tslib btw |
22:49.42 | cr2 | because it's easier to debug |
22:50.14 | cr2 | a very small driver |
22:50.28 | NetRipper | you want it to handle actual data though? |
22:50.43 | cr2 | and the rest code does not belong into this driver anyway |
22:51.03 | NetRipper | calibration stuff you mean? |
22:51.13 | cr2 | yes. |
22:52.23 | j0b0 | NetRipper i added those pressure events to msmts and that works as expected |
22:52.36 | j0b0 | the value is displayed in the pointer location app in dev tools |
22:52.36 | cr2 | you'll have a 10 line driver after removing the non-ts parts |
22:53.08 | *** join/#htc-linux Czarnas (n=czarnas@imik.wip.pw.edu.pl) |
22:53.24 | NetRipper | j0b0, im aware of that, lupine made that patch right? |
22:53.28 | cr2 | and then we can add the init/deinit code properly |
22:53.52 | j0b0 | i think so . it was 6 lines or so |
22:53.59 | NetRipper | yes |
22:54.17 | tmzt | I'm going to take a look at eventhub and keyqueueinput in android |
22:54.41 | lupine_85 | hey hey |
22:54.45 | tmzt | to see if it can support raw ts data and handle calbration for resistive ts's |
22:55.10 | lupine_85 | binary pressure was easy to add, once tmza pointed out what was wrong :) |
22:55.25 | lupine_85 | dunno if it report pressure variably, though |
22:55.37 | NetRipper | it just did 1/0 |
22:55.39 | NetRipper | afaik |
22:56.01 | NetRipper | the driver doesn't support reading the pressure from the hardware yet i think |
22:56.12 | tmzt | Xmoo: dcordes? |
22:56.13 | *** join/#htc-linux BHSPitLappy (n=BHSPitLa@unaffiliated/bhspitmonkey) |
22:58.30 | cr2 | i think it can't measure pressure |
22:58.30 | cr2 | unlike tsc2046 |
22:59.06 | cr2 | the ts on raph is not really great. |
23:00.04 | lupine_85 | NetRipper: the diff I made hardcodes 1 if the pad is being touched, 0 otherwise |
23:00.16 | cr2 | i guess the external ts is used on other phones not without a reason |
23:00.27 | lupine_85 | (and I diked out a bunch of unnecessary code from msm_fb.c in a copy I have ---> over there, incidentally) |
23:00.31 | lupine_85 | dunno how well it runs |
23:01.08 | NetRipper | lupine_85, im making a clean ts driver as we speak |
23:01.27 | lupine_85 | I will be interested to see :) |
23:01.32 | tmzt | NetRipper: that irq resource should be used instead of INT_SDC2_0? |
23:01.34 | lupine_85 | as long as it works with tslib |
23:01.37 | lupine_85 | :p |
23:01.55 | NetRipper | tmzt, no it actually passes INT_SDC2_0 to the request_irq, not the resource |
23:02.14 | lupine_85 | (technically, I guess we shouldn't report pressure if the ts doesn't support it, and write a custom tslib driver... but you know what ?that's too much work from my PoV) |
23:02.18 | NetRipper | lupine_85, how does tslib work? when my ts driver returns uncalibrated data, will android support calibration too? |
23:03.24 | lupine_85 | NetRipper: it just gets the X, Y, button and pressure from /dev/input/touchscreen0 (or event0) |
23:03.34 | lupine_85 | it won't work if any of those events aren't supported |
23:03.48 | tmzt | tslib has to have pressure 0/1 works |
23:04.04 | NetRipper | lupine_85, i know.. but if the X and Y it gets are uncalibrated.. does tslib support calibration? how does that work |
23:04.13 | lupine_85 | NetRipper: it has a calibrator |
23:04.23 | lupine_85 | so calibration happens in tslib |
23:04.33 | NetRipper | lupine_85, ok, do you also know if android uses tslib? |
23:04.39 | lupine_85 | not a clue, I'm afraid |
23:04.46 | NetRipper | i've never seen a calibration window ina ndroid yet |
23:04.53 | tmzt | NetRipper: I know, I'm saying board pecific stuff should should be in padata/resources not a define for the driver |
23:05.17 | lupine_85 | /usr/lib/ts exists? |
23:05.28 | NetRipper | tmzt, ah, ok.. guess we'll clean that stuff up once we get it working ;) |
23:05.32 | maejrep[w] | so, anyone have ideas on how the i2c keyboard driver, the input driver, and the "clamshell" should interact? |
23:05.52 | lupine_85 | maejrep[w]: interact ? |
23:05.57 | NetRipper | tmzt, but SDC resources are defined in arch/arm/mach-msm/common.c.. where it should be i guess |
23:06.16 | tmzt | should we investigate implementing drm as a way of handling offscreen in place of the android ioctl's? |
23:06.38 | cr2 | maejrep[w]: have you seen my microp/psoc wiki changes ? |
23:06.45 | maejrep[w] | I don't think so |
23:06.45 | tmzt | NetRipper: yeah but look at how pxa does it |
23:07.01 | tmzt | maejrep[w]: how is kbd driver? |
23:07.05 | NetRipper | tmzt, i havent looked at pxa |
23:07.12 | maejrep[w] | I haven't worked on it since last night |
23:07.29 | cr2 | maejrep[w]: in a non-android work they should not interact at all |
23:07.42 | cr2 | s/work/world/ |
23:07.54 | maejrep[w] | lupine_85: I mean like, where should the irqs be hooked, where should the data be retrieved, where should the init/pause code be, etc |
23:07.56 | tmzt | devices.c, common.c is fne (leave that to google discretion I think) but pxa still uses resources as far as I an see/remeber |
23:08.27 | lupine_85 | maejrep[w]: ah. not a clue |
23:08.30 | lupine_85 | sowwy :p |
23:08.41 | maejrep[w] | cr2: so the chip driver would expose a function like "request_keypad_notifications()", which the input driver would call? |
23:08.46 | cr2 | tmzt: google code needs many cleanups itself |
23:09.05 | maejrep[w] | probably via pdata |
23:09.13 | tmzt | right, I mean that should be their process my opnion |
23:09.17 | maejrep[w] | or is that too interactive as well? |
23:09.21 | lupine_85 | maejrep[w]: do you have a vaguely working driver now? how's performance? |
23:09.28 | lupine_85 | notes that in wince, the keyboard is generally laggy |
23:09.41 | tmzt | so we don't have diverged code in core msm (and they have some ds) |
23:09.45 | maejrep[w] | it has a couple mdelay's and a lot of prink's, so if you press and release too fast, it gets confused |
23:09.52 | cr2 | tmzt: the hardcode gpio numbers here and there, and use the trout_gpio_foobar() instead of using the generic htc-egpio gpios |
23:09.59 | lupine_85 | presumably they get dumped after debugging though? ;) |
23:10.03 | maejrep[w] | but I'm hoping to clean up those issues |
23:10.16 | maejrep[w] | right, the prinks are just for debugging |
23:10.19 | tmzt | thepause you mean ISR? |
23:10.32 | tmzt | (tiny q kbd right now) |
23:10.34 | maejrep[w] | what is ISR? |
23:10.37 | lupine_85 | speaking of this kind of thing, the ts currently reports events too fast |
23:10.57 | lupine_85 | (msm_ts with the vkeyb) - presumably due to the polling |
23:11.08 | maejrep[w] | because you don't get hte irq? |
23:11.10 | tmzt | not sure you read adc every irq, only when flagged ready |
23:11.17 | lupine_85 | makes typing on userspace vkeybs... interesting |
23:11.24 | tmzt | WyrM: you in here? |
23:11.29 | maejrep[w] | tmzt: I do read on every irq |
23:11.30 | lupine_85 | NetRipper: do you have the ?IRQ working now? |
23:11.46 | NetRipper | lupine_85, no, it's part of why we first want a minimal driver |
23:11.52 | lupine_85 | ah, fair enough |
23:12.04 | maejrep[w] | I need to find out exactly what is necessary and try to strip out anything I don't need |
23:12.15 | maejrep[w] | like I have no idea still what the ce,11 command is for |
23:12.31 | maejrep[w] | nor do I know what the 2nd ce,10 and ce,11 are for in windows during each keypress |
23:12.31 | tmzt | 11 and 10 or you know that one now? |
23:12.40 | maejrep[w] | ? |
23:12.42 | tmzt | can you put the paste back |
23:12.44 | maejrep[w] | I know what ce,10 does |
23:12.47 | tmzt | url |
23:12.48 | lupine_85 | I'm presuming it's due to the polling - so if you're going to be using the driver as a base for anything, you probably only want to send input_* events when one of the parameters have changed from the previous |
23:12.54 | lupine_85 | IMHO :) |
23:12.56 | maejrep[w] | I'm not following :| |
23:13.20 | cr2 | maejrep[w]: 2byte reads ? |
23:13.22 | maejrep[w] | tmzt: the i2c dump? I don't have that currently |
23:13.30 | maejrep[w] | cr2: yes |
23:13.56 | maejrep[w] | ce,10 -> 2 bytes, ce,11 -> 2 bytes, a couple cc,XX writes, then ce,10 and ce,11 again (that's what windows does) |
23:14.37 | cr2 | maejrep[w]: btw, you can add the 'get id' for psoc and microp now |
23:14.53 | maejrep[w] | but a) I don't know what ce,11 returns yet and if we need it, and b) I don't know why ce,10 and ce,11 are done a second time or if we need that |
23:15.05 | maejrep[w] | what is "get id" ? |
23:15.22 | cr2 | can you do 'addr2mod' on the traces ? |
23:15.33 | maejrep[w] | no, I get a helper something error in haret |
23:15.44 | maejrep[w] | toolkit helper ? |
23:15.48 | maejrep[w] | something like that |
23:15.50 | cr2 | so we can see the dll |
23:15.51 | *** join/#htc-linux nebi (n=nebi@170.ftth2.cust.fyrobs1.upps.se.borderlight.net) |
23:15.53 | maejrep[w] | ^ |
23:15.57 | maejrep[w] | I get an error :) |
23:16.02 | cr2 | call it manually |
23:16.08 | maejrep[w] | wut :o |
23:16.16 | maejrep[w] | I know nothing of such things |
23:16.42 | maejrep[w] | compare it to something in lsmod? |
23:16.46 | cr2 | the mmutrace provides you the call address |
23:16.49 | maejrep[w] | yes |
23:16.53 | maejrep[w] | I get that |
23:17.04 | cr2 | use addr2mod 0xcxxxxx |
23:17.08 | NetRipper | lupine_85, that diff you made regarding the pressure thing has been taken offline.. do you still have it somewhere? |
23:17.09 | maejrep[w] | But when I use addr2mod() on the address, it says it can't build some kind of toolkit helper image or whatever |
23:17.20 | cr2 | ah, ok. |
23:17.39 | cr2 | evil mickeysoft |
23:17.48 | maejrep[w] | though I think it may be intermittent |
23:17.50 | cr2 | toolhelp.dll |
23:17.59 | maejrep[w] | cause I do have one log where I was able to get responses from it |
23:18.02 | maejrep[w] | but only that one file |
23:18.09 | maejrep[w] | every other time I tried it, I got that toolhelp error |
23:18.13 | cr2 | strange |
23:18.15 | lupine_85 | NetRipper: not cleanly. One second... |
23:18.26 | NetRipper | lupine_85, thx |
23:19.41 | cr2 | maejrep[w]: http://wiki.xda-developers.com/index.php?pagename=RaphaelMicroP |
23:20.02 | cr2 | ce,12,02,x get_version rd |
23:20.11 | maejrep[w] | cr2: I'm gonna be heading home soon to work on the driver, and will also try to get that addr2mod to work. 1) do you agree with the idea of externing a start/stop listen function in the i2c driver, and have a second input driver that uses it to be notified of and read the scancodes to then report to the OS? and 2) what are you asking for with the "get id" |
23:20.22 | lupine_85 | NetRipper: NetRipper: http://rafb.net/p/CSktCw96.html is the full thing I have right now |
23:20.26 | NetRipper | thanks |
23:20.42 | tmzt | layered like ce? |
23:20.52 | maejrep[w] | cr2: so you want me to try that and tell you what I get? Or add it to the driver? |
23:20.52 | NetRipper | lupine_85, can you do a git diff drivers/input/touchscreen/msm_ts.c? |
23:20.53 | lupine_85 | the main things are the extra input_set_abs_params(msm_ts_dev, ABS_PRESSURE, ...) and the input_report_abs(msm_ts_dev, ABS_PRESSURE, 1); |
23:21.17 | maejrep[w] | tmzt: that's what I'm thinking ;o seems to be what cr2 is advocating as well |
23:21.23 | cr2 | maejrep[w]: have you looked at the spi keyboard driver by Kevin2 ? |
23:21.26 | lupine_85 | NetRipper: the source I've got has been much changed from git head, beyond what's needed |
23:21.32 | maejrep[w] | I don't want to have all the input_device code in the i2c chip driver |
23:21.36 | lupine_85 | hence no clean diff |
23:21.43 | maejrep[w] | cr2: i've not, do you know what device or where I can find it? |
23:21.56 | NetRipper | lupine_85, alright |
23:22.09 | cr2 | linuxtogo git, fot htc hermes |
23:22.23 | maejrep[w] | ok I'll look it up and see how he does it |
23:22.28 | cr2 | ok |
23:22.47 | *** join/#htc-linux timebomb (n=tb@e176117163.adsl.alicedsl.de) |
23:22.50 | maejrep[w] | also am I right in thinking that our i2c chip can also work as spi? that would be preferred, yes? |
23:22.56 | cr2 | the psoc/microp device info query is needed anyway |
23:23.17 | lupine_85 | NetRipper: sorry I'm not more help. I'm generally better about not mixing up feature changes in commits :D |
23:23.18 | maejrep[w] | ok, so tell me again what you're wanting with that ? :) |
23:23.19 | cr2 | i doubt that it can be used as spi |
23:23.24 | NetRipper | lupine_85, nps |
23:23.29 | lupine_85 | forgot to git-commit before he hacked some more |
23:23.30 | maejrep[w] | you want me to run it and give you the results? |
23:23.43 | j0b0 | i have that diff applied albeit manually |
23:24.02 | cr2 | maejrep[w]: the commands may depend on the device version |
23:24.09 | maejrep[w] | ahh |
23:24.16 | lupine_85 | well, it's essentially 2 lines of code once you cute out the variable crap |
23:24.22 | maejrep[w] | ok, I'll check that and add it to my probe function as well |
23:24.28 | cr2 | ok |
23:24.45 | maejrep[w] | heading home, bbl ~30 min |
23:24.56 | lupine_85 | (I added placeholder code to remind me to investigate variable-pressure at some point) |
23:25.46 | lupine_85 | dcordes: not sure what's up with fso-image. fso-console-image requires: fso-image.. it's all a bit odd |
23:26.22 | lupine_85 | so I'm building fso-console-image then I shall copy the contents of that into the fso-image rootfs and see what that hybrid does |
23:26.50 | tmzt | can you dep on fso-console-image |
23:26.53 | tmzt | ? |
23:27.18 | lupine_85 | tmzt: dunno. that's what I was planning to do, but that's an infinite loop from my point of view |
23:27.27 | lupine_85 | (maybe bitbake will resolve it sanely, but maybe not) |
23:28.00 | lupine_85 | I'll try once fso-console-image is built |
23:30.03 | *** join/#htc-linux techie (n=blarg@ip24-250-216-85.ga.at.cox.net) |
23:30.31 | lupine_85 | (it has a bunch of IMAGE_INSTALL stanzas, but interestingly, doesn't seem to be missing anything fso-image does) |
23:31.10 | lupine_85 | checks against console-image |
23:33.01 | lupine_85 | task-base-extended is in console-image but not fso-console-image... AFAICT |
23:34.07 | lupine_85 | builds fso-illume-image |
23:34.45 | lupine_85 | whatever thwt is :D |
23:36.16 | *** join/#htc-linux p3t3r__ (n=peter@134.245.164.105) |
23:41.00 | *** join/#htc-linux Czarnas (n=czarnas@imik.wip.pw.edu.pl) |
23:41.03 | *** join/#htc-linux kaze (n=kaze@pac33-1-82-235-251-34.fbx.proxad.net) |
23:53.23 | lupine_85 | humm |
23:53.32 | lupine_85 | the fso-image does actually have an init in it |
23:53.34 | lupine_85 | d'oh |
23:53.38 | lupine_85 | failcopy |
23:55.34 | lupine_85 | ls: cannot access sbin: Stale NFS file handle |
23:58.39 | lupine_85 | remakes |