IRC log for #htc-linux on 20110517

00:00.33*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
00:03.48*** join/#htc-linux jonpry (~jon@199.85.236.239)
00:13.45*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
00:49.57*** join/#htc-linux tmzt (~tmzt@adsl-99-164-104-3.dsl.akrnoh.sbcglobal.net)
00:51.31*** join/#htc-linux jonpry (~jon@199.85.236.239)
01:06.10*** join/#htc-linux mastermerlin1 (~Adium@p4FEE57A8.dip.t-dialin.net)
01:28.55*** join/#htc-linux hardwalker (~hardwalke@122-117-115-146.HINET-IP.hinet.net)
01:31.18*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
01:42.27*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
01:54.19*** join/#htc-linux tmzt (~tmzt@adsl-76-244-153-109.dsl.akrnoh.sbcglobal.net)
02:04.23*** join/#htc-linux remington_3006 (18c0b25d@gateway/web/freenode/ip.24.192.178.93)
02:04.31*** join/#htc-linux |Atom| (~atom@82.194.234.249)
02:04.40remington_3006i have a question
02:05.58remington_3006i just installed the 2.1 version on my tmobile htc touch pro 2 and when i am in the windows side of my phone i have a full battery,  but when i go into the android 2.1....it read my battery is almost dead.....???????????
02:06.26*** join/#htc-linux jonpry (~jon@199.85.236.239)
02:08.42*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
02:08.44*** join/#htc-linux AstainHellbring (~AstainHel@unaffiliated/astainhellbring)
02:16.53*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
02:21.27*** join/#htc-linux tmzt (~tmzt@adsl-99-164-107-73.dsl.akrnoh.sbcglobal.net)
02:22.47*** join/#htc-linux GNUtoo|oeee (~GNUtoo@host13-85-dynamic.51-79-r.retail.telecomitalia.it)
02:32.36*** join/#htc-linux programmer8922 (~Evan@67.219.164.162)
02:33.56*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
02:37.57*** join/#htc-linux swc|666 (~x00@unaffiliated/swc666/x-4934821)
02:38.47*** join/#htc-linux josemakalolot (4122af0c@gateway/web/freenode/ip.65.34.175.12)
02:43.46*** join/#htc-linux arrrghhh (~arrrghhh@c-24-9-150-163.hsd1.co.comcast.net)
02:52.00*** join/#htc-linux programmer8922 (~Evan@67.219.164.162)
03:14.31*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
03:21.13*** part/#htc-linux Cass (~cass@188-220-34-222.zone11.bethere.co.uk)
03:35.47*** join/#htc-linux Nautis (4cda4629@gateway/web/freenode/ip.76.218.70.41)
03:35.48*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
03:41.56*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
03:43.22*** join/#htc-linux tmzt (~tmzt@adsl-76-253-135-25.dsl.akrnoh.sbcglobal.net)
03:57.27*** join/#htc-linux Rob2222 (~Miranda@p4FFF20E2.dip.t-dialin.net)
04:19.51*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
04:31.43*** join/#htc-linux BHSPitMonkey (~stephen@unaffiliated/bhspitmonkey)
04:31.45*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
04:34.11*** part/#htc-linux sado1 (~sado1@static.213-133-103-196.clients.your-server.de)
04:35.58*** join/#htc-linux AstainHellbring (AstainHell@unaffiliated/astainhellbring)
04:44.52*** join/#htc-linux kiozen (~kiozen@ppp-93-104-84-82.dynamic.mnet-online.de)
05:00.06*** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@94.52.236.39)
05:02.58*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
05:09.07*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
05:12.43*** join/#htc-linux programmer8922 (~Evan@67.219.164.162)
05:21.33*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
05:34.42*** join/#htc-linux rzk_ (~rzk@95-25-211-53.broadband.corbina.ru)
05:44.13*** join/#htc-linux Segnale007 (~Segnale00@ppp-133-49.26-151.libero.it)
05:46.50*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
05:52.08*** join/#htc-linux MacDrunk (~marper@201.164.176.184)
05:52.15*** join/#htc-linux mes (~mes@sentry.lazo.ca)
06:08.07*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
06:20.52*** join/#htc-linux kiozen (~kiozen@p5DDF1D13.dip.t-dialin.net)
06:24.17*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
06:36.30*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
06:42.37*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
06:46.22*** join/#htc-linux avinashhm (~avinash-h@192.91.66.186)
06:54.13*** join/#htc-linux dekar_ (~dekar@drms-590c49bb.pool.mediaWays.net)
06:58.47*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
07:20.03*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
07:25.39*** join/#htc-linux gauner1986 (~Miranda@2.210.71.61)
07:26.03*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
07:29.12*** join/#htc-linux rob_w (~bob@ppp-188-174-111-149.dynamic.mnet-online.de)
07:32.30*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
07:34.01*** join/#htc-linux gauner1986 (~Miranda@2.210.71.61)
07:41.06*** join/#htc-linux gauner19861 (~Miranda@2.210.71.61)
07:41.08*** join/#htc-linux HardDisk_WP (~marco@velirat.de)
07:41.10*** join/#htc-linux HardDisk_WP (~marco@wikipedia/harddisk)
07:41.56*** part/#htc-linux kiozen (~kiozen@p5DDF1D13.dip.t-dialin.net)
07:44.33*** join/#htc-linux dekar (~dekar@95.143.165.210)
07:48.57*** join/#htc-linux mdj__ru (~mdj@46.182.128.248)
07:53.51*** join/#htc-linux Dave888 (~Dave888@41.230.61.50)
07:56.06*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
08:15.34*** join/#htc-linux dobrin (~dobrin@85.91.150.26)
08:23.18*** join/#htc-linux Erikson (~Erik@musketeer.wlan.uni-jena.de)
08:37.27*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
08:48.33*** join/#htc-linux mickey|office (~Mickey@business-092-079-168-007.static.arcor-ip.net)
08:52.24*** join/#htc-linux HardDisk_WP (~marco@wikipedia/harddisk)
08:55.33*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
09:02.13*** join/#htc-linux onen|openBmap (~quassel@vbo91-1-89-87-201-85.dsl.sta.abo.bbox.fr)
09:11.43*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
09:19.54*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
09:36.07*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
09:44.16*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
09:59.36*** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@94.52.236.39)
10:05.32*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
10:09.07*** join/#htc-linux tmzt (~tmzt@adsl-76-244-153-158.dsl.akrnoh.sbcglobal.net)
10:11.58*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
10:14.05*** join/#htc-linux tmzt (~tmzt@adsl-76-244-153-158.dsl.akrnoh.sbcglobal.net)
10:17.13*** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@94.52.236.39)
10:18.24*** join/#htc-linux Ceesheim (~ceesheim@p5B346B9B.dip.t-dialin.net)
10:19.07*** join/#htc-linux khorben_ (~dont@office.bearstech.com)
10:19.13*** join/#htc-linux gauner1986 (~Miranda@p5B38288B.dip.t-dialin.net)
10:20.46*** join/#htc-linux tmzt_ (~tmzt@adsl-76-244-151-7.dsl.akrnoh.sbcglobal.net)
10:23.08*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
10:31.18*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
10:31.50*** join/#htc-linux GNUtoo (~GNUtoo@host13-85-dynamic.51-79-r.retail.telecomitalia.it)
10:33.33*** join/#htc-linux tmzt (~tmzt@adsl-99-164-34-54.dsl.akrnoh.sbcglobal.net)
10:38.38*** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@94.52.236.39)
10:47.30*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
10:52.06*** join/#htc-linux Rob2223 (~Miranda@p4FFF20E2.dip.t-dialin.net)
10:58.47*** join/#htc-linux Andreyxxl1 (Andreyxxl@94.52.236.39)
10:59.26*** join/#htc-linux Andreyxxl1 (Andreyxxl@94.52.236.39)
11:00.35*** join/#htc-linux rajkosto (~rajkosto@wan.rajkonet.info)
11:04.43*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
11:05.26*** join/#htc-linux tmzt (~tmzt@adsl-99-164-34-54.dsl.akrnoh.sbcglobal.net)
11:10.24*** join/#htc-linux tmzt (~tmzt@adsl-99-164-34-54.dsl.akrnoh.sbcglobal.net)
11:10.43*** join/#htc-linux Ceesheim (~ceesheim@p5B346CEF.dip.t-dialin.net)
11:14.56*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
11:23.59*** join/#htc-linux tmzt (~tmzt@adsl-69-208-7-234.dsl.akrnoh.ameritech.net)
11:24.38*** join/#htc-linux LordDeath (~LordDeath@cable-81-173-166-52.netcologne.de)
11:31.08*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
11:41.15*** join/#htc-linux gauner1986 (~Miranda@p5B38288B.dip.t-dialin.net)
11:41.50*** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@94.52.236.39)
11:43.25*** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@94.52.236.39)
11:57.44*** join/#htc-linux skodde (~skodde@unaffiliated/skodde)
12:01.00*** join/#htc-linux ali1234 (~ajb@robotfuzz.co.uk)
12:03.29*** join/#htc-linux surge (surge@pool-98-118-157-221.bflony.fios.verizon.net)
12:05.41*** join/#htc-linux jonpry (~jon@199.85.236.239)
12:05.44*** join/#htc-linux raymonddull (raymonddul@pool-70-17-188-200.pitt.east.verizon.net)
12:11.27*** join/#htc-linux gauner1986 (~Miranda@p5B38288B.dip.t-dialin.net)
12:15.34*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
12:21.07*** join/#htc-linux helicopter88 (~helicopte@host122-116-dynamic.33-79-r.retail.telecomitalia.it)
12:27.45*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
12:38.52*** join/#htc-linux tmzt (~tmzt@adsl-76-253-140-86.dsl.akrnoh.sbcglobal.net)
13:04.03*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
13:07.07*** join/#htc-linux LordDeath (~LordDeath@cable-81-173-166-52.netcologne.de)
13:10.41*** join/#htc-linux rpierce99 (~rpierce99@96-42-102-103.dhcp.stcd.mn.charter.com)
13:15.35*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
13:18.22*** join/#htc-linux tmzt (~tmzt@adsl-99-164-48-65.dsl.akrnoh.sbcglobal.net)
13:19.07*** join/#htc-linux arif-ali (~arif-ali@cpat001.wlan.net.ed.ac.uk)
13:19.12*** join/#htc-linux LordDeath|HD2 (~androirc@2001:4dd0:ff78:0:c900:278a:fa90:f151)
13:21.52*** join/#htc-linux gauner1986 (~Miranda@p5B38288B.dip.t-dialin.net)
13:21.52*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
13:28.27*** join/#htc-linux LordDeath|HD2 (~androirc@2001:4dd0:ff78:0:c900:278a:fa90:f151)
13:31.04*** join/#htc-linux LordDeath|HD2 (~androirc@2001:4dd0:ff78:0:c900:278a:fa90:f151)
13:33.05*** join/#htc-linux LordDeath|HD2 (~androirc@2001:4dd0:ff78:0:c900:278a:fa90:f151)
13:33.41*** join/#htc-linux tmzt (~tmzt@76.253.133.36)
13:35.23*** join/#htc-linux ali1234 (~ajb@robotfuzz.co.uk)
13:38.04*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
13:39.11*** join/#htc-linux Rajko (~rajkosto@cable-94-189-150-102.dynamic.sbb.rs)
13:39.22*** join/#htc-linux Rajko (~rajkosto@cable-94-189-150-102.dynamic.sbb.rs)
13:45.12*** join/#htc-linux tmzt (~tmzt@76.244.157.17)
13:48.22*** join/#htc-linux LordDeath|HD2 (~androirc@2001:4dd0:ff78:0:c900:278a:fa90:f151)
13:52.30*** join/#htc-linux LordDeath (~LordDeath@cable-81-173-166-52.netcologne.de)
13:57.52*** join/#htc-linux rpierce99 (~rpierce99@96-42-102-103.dhcp.stcd.mn.charter.com)
14:04.28*** join/#htc-linux Reiko2 (~Reiko2@pd95bdd86.dip0.t-ipconnect.de)
14:11.05*** join/#htc-linux emwe (~emwe@cable-86-56-10-158.cust.telecolumbus.net)
14:12.12*** join/#htc-linux gauner1986 (~Miranda@91.56.40.139)
14:19.25*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
14:25.21*** join/#htc-linux tmzt (~tmzt@adsl-76-244-144-220.dsl.akrnoh.sbcglobal.net)
14:26.55*** join/#htc-linux surgex (surge@98.118.157.221)
14:39.15*** join/#htc-linux helicopter88 (~helicopte@host122-116-dynamic.33-79-r.retail.telecomitalia.it)
14:39.23*** join/#htc-linux rzk_ (~rzk@95-25-211-53.broadband.corbina.ru)
14:40.00*** join/#htc-linux Alex[sp3dev] (~alexander@ip-95-220-0-221.bb.netbynet.ru)
14:43.25*** join/#htc-linux rajkosto (~rajkosto@wan.rajkonet.info)
14:49.34*** join/#htc-linux Segnale007 (~Segnale00@ppp-10-14.26-151.libero.it)
14:54.47*** join/#htc-linux tmzt (~tmzt@99.164.53.190)
15:00.48*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
15:06.33*** join/#htc-linux vinceweis (4463ed13@gateway/web/freenode/ip.68.99.237.19)
15:11.29*** join/#htc-linux Segnale007 (~Segnale00@ppp-10-14.26-151.libero.it)
15:13.03*** join/#htc-linux gauner1986 (~Miranda@p5B38288B.dip.t-dialin.net)
15:19.51*** join/#htc-linux AstainHellbring (~AstainHel@unaffiliated/astainhellbring)
15:28.24*** join/#htc-linux kiozen (~kiozen@ppp-93-104-70-16.dynamic.mnet-online.de)
15:31.15*** join/#htc-linux kiozen (~kiozen@ppp-93-104-70-16.dynamic.mnet-online.de)
15:31.25*** join/#htc-linux GNUtoo (~GNUtoo@host13-85-dynamic.51-79-r.retail.telecomitalia.it)
15:39.42*** join/#htc-linux programmer8922 (~Evan@67.219.164.162)
15:43.28*** join/#htc-linux ecritejr (bdd69adf@gateway/web/freenode/ip.189.214.154.223)
15:48.04*** join/#htc-linux dekar_ (~dekar@drms-590c49bb.pool.mediaWays.net)
15:51.32*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
15:59.02*** join/#htc-linux WisTilt2 (~wisgreg@wireless251.wirelesstcp.net)
15:59.16WisTilt2morning world
15:59.57WisTilt2emwe: any luck finding that SOD commit?
16:02.29emweWisTilt2: it's the call to htc_cable_status_update() imho.
16:02.51WisTilt2where is that called from?
16:03.02emwefrom the proc_comm_wince isr worker
16:03.16emweit's used for the instant cable plug/unplug notification
16:03.49WisTilt2looks like its called in worker and in exit_sleep
16:04.32emwethe exit_sleep is superfluous from local testing
16:05.09emwehave the mutex_lock/unlock in suspicion. a build with DEBUG_[RT]_MUTEXES doesn't show up something nasty yet.
16:05.51emwebut yeah, perhaps it's just better to comment that stuff and have autobuild get in a better shape again.
16:06.22*** join/#htc-linux Alex[sp3dev] (~alexander@ip-95-220-0-221.bb.netbynet.ru)
16:06.30WisTilt2do you want me to remove thos cable status lines and test it on a few phones here today or you pretty sure that's it?
16:06.53emweWisTilt2: oh if you have a chance to do so, then yes, please go for it.
16:07.27WisTilt2its been happening within hours so if i stick it on 3-4 or our phones we'll know pretty quick
16:07.28emweWisTilt2: can't reproduce on the raph (wifi+nosim) on .27 but on the topa. freezes some time over night and then dies due to battery running out.
16:08.03emweWisTilt2: yeah, if you can comment these two calls would be nice for a test.
16:08.06emwehey Alex[sp3dev]
16:08.30Alex[sp3dev]emwe: sup
16:09.02*** join/#htc-linux kiozen (~kiozen@ppp-93-104-70-16.dynamic.mnet-online.de)
16:10.14*** join/#htc-linux gauner1986 (~Miranda@46.115.1.52)
16:10.14emweAlex[sp3dev]: nothing except still trying to figure the incall-freeze. have yet another idea though... you? studies project still going on?
16:10.36Alex[sp3dev]emwe: yep, i'm still coding like a monkey
16:11.09emweAlex[sp3dev]: nice you get to some coding at all.
16:11.21Alex[sp3dev]emwe: what about mmc?
16:11.59emweAlex[sp3dev]: that incall freeze won't let me alone. until i found a fix i am not doing anything else.
16:12.23Alex[sp3dev]emwe: you imported the acoustic from my tree and copied jb's libs yet?
16:12.46*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
16:12.54emweAlex[sp3dev]: no, i was lazy and took the all-in-one from jb's old -acoustic branch because i am still missing your dynamic amss setup.
16:13.10Alex[sp3dev]ok
16:13.29*** join/#htc-linux Segnale007 (~Segnale00@ppp-10-14.26-151.libero.it)
16:13.34*** join/#htc-linux kiozen (~kiozen@ppp-93-104-70-16.dynamic.mnet-online.de)
16:34.40*** join/#htc-linux ORi|| (~ORi@91.181.66.43)
16:44.20*** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@94.52.236.39)
16:48.07*** join/#htc-linux kiozen (~kiozen@ppp-93-104-70-16.dynamic.mnet-online.de)
16:52.55*** join/#htc-linux helicopter88 (~helicopte@host122-116-dynamic.33-79-r.retail.telecomitalia.it)
16:52.56*** join/#htc-linux Proz (~Proz@bzq-84-109-111-31.red.bezeqint.net)
16:52.58Prozhey
16:54.07*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
16:57.52*** join/#htc-linux T-Junk (C7xx@f147035.upc-f.chello.nl)
17:05.25*** join/#htc-linux Andreyxxl1 (~Andreyxxl@94.52.236.39)
17:11.49*** join/#htc-linux arrrghhh (~arrrghhh@184.248.253.160)
17:21.17*** join/#htc-linux nautis (~nautis@adsl-99-39-5-22.dsl.pltn13.sbcglobal.net)
17:22.30*** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@94.52.236.39)
17:24.01*** join/#htc-linux programmer8922 (~Evan@67.219.164.162)
17:24.09*** join/#htc-linux gauner1986 (~Miranda@p5B38288B.dip.t-dialin.net)
17:29.04*** join/#htc-linux LordDeath|HD2 (~androirc@2001:4dd0:ff78:0:290:4cff:fe24:84bf)
17:29.53*** join/#htc-linux swc|666 (~x00@unaffiliated/swc666/x-4934821)
17:30.58*** join/#htc-linux arif-ali (~arif-ali@82-71-22-204.dsl.in-addr.zen.co.uk)
17:32.48*** join/#htc-linux an0key (~an0key@n0rty.an0key.net)
17:44.40*** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@94.52.236.39)
17:49.52*** join/#htc-linux ali1234 (~ajb@robotfuzz.co.uk)
17:50.08*** join/#htc-linux fakker (~noobhands@cpc13-hitc6-2-0-cust129.9-2.cable.virginmedia.com)
17:51.39*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
18:00.05*** join/#htc-linux stroughtonsmith (~steven@86-43-213-252-dynamic.b-ras2.bbh.dublin.eircom.net)
18:00.22jonpryhi WisTilt2
18:06.39*** join/#htc-linux Andreyxxl[HD2EU] (~Andreyxxl@94.52.236.39)
18:06.52WisTilt2howdy jonpry. doing some of our .38 comparisons to how this .39 is setup. lots of stuff we need to add, don't really know where to begin!  i need to finish tssc_manager then im going to take a stab at usb so we can get adb running i think.
18:07.23WisTilt2unless you're going to tell me you already have it working:)
18:08.41*** join/#htc-linux skodde (~skodde@unaffiliated/skodde)
18:08.54*** join/#htc-linux jonpry (~jon@199.85.236.239)
18:17.59*** join/#htc-linux sado1 (~sado1@static.213-133-103-196.clients.your-server.de)
18:18.06WisTilt2jonpry, i think you timed out and missed my reply
18:19.33*** join/#htc-linux rob_w (~bob@ppp-188-174-111-149.dynamic.mnet-online.de)
18:25.56*** join/#htc-linux LordDeath (~LordDeath@cable-81-173-166-52.netcologne.de)
18:26.48WisTilt2emwe: htc_battery.c is not used at all correct?
18:27.29*** join/#htc-linux jonpry (~jon@199.85.236.239)
18:27.31emweWisTilt2: no, htc_battery_smem.c which is a copy of htc_battery.c extended by smem readings and a lot other normalization stuff.
18:28.30WisTilt2just making sure.  no fails as of yet on 4 devices running with that cable status commented.  was just going through the flow to see why it would cause the problem.
18:28.55Alex[sp3dev]why do you need that cable poop? don't all devices have usb detect gpio?
18:29.40WisTilt2seems like there is some delay that can be up to 10 seconds to detect without it.
18:29.40emweAlex[sp3dev]: 82 is it to be on topa. no reaction on the ac-detect isr for me.
18:29.42emweWisTilt2: that 10 sec delay is the battery poller thread in battsmem
18:29.54emweperiodically reads out/fills htc_batt_info
18:30.05emweand that one also upadtes the cable status
18:30.14emweAlex[sp3dev]: you got ac detection gpio on kovs?
18:30.57Alex[sp3dev]emwe: well, it reacts to both usb and ac but to detect the type you need to rely on the hsusb driver
18:31.24emweAlex[sp3dev]: does it react immedeately?
18:31.29WisTilt2does plugging usb in trigger a gpio irq or is that polled?
18:31.43Alex[sp3dev]WisTilt2: yes, there is an irq
18:32.04emweWisTilt2: gpio_ac_detect property of the smem_battery_resources struct
18:32.05WisTilt2irq determined by gpio request irq?
18:32.11Alex[sp3dev]WisTilt2: yep
18:32.14WisTilt2k
18:32.19emweWisTilt2: setup is in battsmem
18:32.43emweAlex[sp3dev]: so you get instant notification of cable plug?
18:33.01emweWisTilt2: you might try gpio 82 which isn't used on rhod and topa iirc.
18:33.10emwe(commented that is)
18:33.10Alex[sp3dev]emwe: of course. you know that in my world everything is perfect.. until i have to face real life
18:33.29*** join/#htc-linux swc|666 (~x00@unaffiliated/swc666/x-4934821)
18:33.49emweAlex[sp3dev]: too lazy to look it up... where is it setup in your tree? boardfile?
18:34.04Alex[sp3dev]emwe: yep
18:36.06WisTilt2emwe since the worker could have vbus pending ints, shouldn't the cable status happen after the ints are handled? seems coming out of sleep usb needs to wait until we're fully awake before moving on.
18:36.42*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
18:37.06WisTilt2ok i see that line 291 seems to address that state
18:37.42emweWisTilt2: in case that is "late" enough...
18:38.49jonpryi think you guys are all barking up the wrong tree with this vbus thing. why not just setup an early suspend thingy that check vbus *right* before it goes to sleep. getting rid of all the bugs that matter
18:39.09WisTilt2yeah thanks for stealing my suggestion:)
18:39.35WisTilt2jonpry we need to get you a better connection
18:39.58emwehuh? what does that help detection cable plug?
18:40.09Alex[sp3dev]you're doin it wrong
18:40.14Alex[sp3dev]<PROTECTED>
18:40.26Alex[sp3dev]why not set it to the value you get from smem?
18:41.42emwemsm_hsusb_set_vbus_state(!!readl(MSM_SHARED_RAM_BASE + 0xfc00c)); ?
18:41.52emwegot that on .35
18:41.58Alex[sp3dev]well, you already read it in that function
18:42.41WisTilt2line 684 has the state correct?
18:42.51*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
18:43.36emweyes
18:44.10WisTilt2msm_hsusb_set_vbus_state(vbus_status); ?
18:44.51emweyes. don't ask me for the values that register carries honestly.
18:45.09emweAlex[sp3dev]: "pda-power" is a generic driver?
18:45.42Alex[sp3dev]emwe: yes. and honestly you should let it do charger stuff and only leave *battery* code in the driver
18:46.26Alex[sp3dev]what i'd like is to have scbs but also a fallback driver which will allow to get approximate values without userland support. and all board-specific coefficients and equations should go to board files
19:08.49WisTilt2emwe: looking deeper into this, I think taking the cable update out of the worker completely and leaving it in exit sleep is what we want. at that point, the device is fully up and any vbus ints have already been handled so usb status shouldn't trash things.
19:09.23WisTilt2im going to run that config on another phone to see
19:11.00emwethe worker is doing nothing when not exited sleep. so dunno if that will help. or i am missing the big picture perhaps.
19:14.12WisTilt2if thats true, line 291 is pointless no?
19:15.56emweonce could have it the other way around. dropping the code in exit_sleep and just have the worker do it works fine as well
19:16.08WisTilt2give me a few, going to test this theory out on device and see if it crashes
19:16.38emwei am digging further through AudioFlinger... why on earth do i have the only device being a PITA on all ends...
19:16.58emwewish i had bought a rhod initially.
19:19.04*** join/#htc-linux mes (~mes@S0106000ce55186df.cc.shawcable.net)
19:27.14*** join/#htc-linux kvaster (~kvaster@vpn-e0.bas-net.by)
19:28.18*** join/#htc-linux bartman` (~bart@2001:470:b014::dd)
19:35.56*** join/#htc-linux NeoMatrixJR (~chatzilla@173-20-63-176.client.mchsi.com)
19:42.40*** join/#htc-linux LordDeath (~LordDeath@cable-81-173-166-52.netcologne.de)
19:43.26*** join/#htc-linux Chester0 (~s@109.61.7.242)
19:45.38*** join/#htc-linux arrrghhh (~arrrghhh@173.5.24.29)
19:57.27*** join/#htc-linux Reiko2 (HydraIRC@xdsl-89-0-154-159.netcologne.de)
19:58.09*** join/#htc-linux vw (4463ed13@gateway/web/freenode/ip.68.99.237.19)
20:02.59*** join/#htc-linux Rajko (~rajkosto@cable-94-189-150-102.dynamic.sbb.rs)
20:03.26*** join/#htc-linux Tinyboom (~nahh@24.84-48-105.nextgentel.com)
20:17.27*** join/#htc-linux bitrot (~rajkosto@2001:5c0:1511:4e02:e0c0:52bf:802:699e)
20:21.17WisTilt2emwe: got another proc_comm question for you when you're free
20:22.05*** join/#htc-linux joshkoss (c0ea0218@gateway/web/freenode/ip.192.234.2.24)
20:30.28emweWisTilt2: if i can answer ;)
20:32.03WisTilt2the last IF statement, what happens to the unknown pending ints?
20:32.10WisTilt2line 345
20:34.01emwenothing yet. but msm_proc_comm_wince_pending_ints is just for the worker anyway. so once hit, we will always get a printk() about it.
20:35.11*** join/#htc-linux gauner1986 (~Adium@p5B38288B.dip.t-dialin.net)
20:36.14emwethe more interessting thing is 369 setting the bits to 0 for the "handled" bits. that call actually is the very same as the one commented in pm.c on resume path.
20:36.27WisTilt2ok so we're not leaving anything unserviced I assume?  So far both tests are good but I did see a binder transaction failing around 10 minutes into plugging in usb.  dont know which it is yet though.
20:36.28emweone could also just write a 0 there in DEX_A9_M2A_6_PENDING_INT_ADDR
20:36.42*** join/#htc-linux khorben_ (~dont@APuteaux-651-1-104-205.w82-124.abo.wanadoo.fr)
20:36.59emweimho, that register might just be a "reason" register. i am not quite sure it's even reverified by arm0
20:37.01emwearm9
20:37.26emwebut as jb came up with that smem semaphores and so on, perhaps it's more then just a wakeup reason register.
20:37.50emwei am just running with a writel(0, ...) which mimics the pm.c behaviour.
20:38.07emwebut shouldn't really matter.
20:38.16*** join/#htc-linux LordDeath (~LordDeath@cable-81-173-166-52.netcologne.de)
20:38.51emwebrb5
20:39.33WisTilt2im currently running with that commented.  only change to current tree is i have 4 phones running with both usb_cable commented and one phone with the one in exit_sleep enabled.  cable detects immediately so we'll see if we get a sod or reboot with either.
20:40.27WisTilt2i confiscated half the rhod here in the office and I think people thought they might be getting fired lol
20:40.50*** join/#htc-linux Chester0 (~s@109.61.7.242)
20:41.56arrrghhhbwhahahaha
20:41.58arrrghhhthat's awesome
20:42.03arrrghhhand howdy WisTilt2 ;)
20:42.11WisTilt2hey arrrghhh
20:42.23WisTilt2yeah i pay for them, i can take them when needed
20:42.44arrrghhhbein the bossman has its perks i'm sure!
20:42.55WisTilt2they shouldn't be using them at work anyway.  unless im having them test something:)
20:43.03arrrghhhhehe
20:43.28arrrghhhhow's .39 goin?  is that what you're hackin at now?
20:43.45WisTilt2any reports on that other test kernel?  i actually thing we have it narrowed down, just curious if anyone see's anything
20:44.28WisTilt2.39 is going, a bitch but going.  jonpry did all the ground work and it boots to unlock screen.  im trying to get usb into it now.
20:44.42*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
20:44.47arrrghhhit was really mixed results.  unfortunately with all the other testing stuff, not many people ran that kernel.
20:44.52arrrghhhnot many people were on the newest autobuild either heh.
20:45.17arrrghhhboots to unlock screen sounds promising, considering last i tried it would freeze (seemingly) at bootani ;)
20:45.54WisTilt2did you see the ml i posted my main rhod 300 running without reboot or any issues for over 30days now?  pretty damn stable i'd say
20:46.15arrrghhhi did, that is awesome.
20:46.35WisTilt2thats running the 4/15 test kernel
20:46.57arrrghhhi wish scbs would get pushed, but it seems it would only benefit RHOD users at this point
20:47.08arrrghhhwhich is the majority of the userbase...
20:47.14arrrghhhAFAIK
20:48.04WisTilt2yes it needs to modded for rhod only at this point until jonpry gets it worked out on other devices.  its a shame its not being used by the mass rhod users, it is far better than anything else out there.
20:48.51arrrghhhno joke!
20:48.57arrrghhhi think the other issue is the algo
20:49.01arrrghhhhe wrote that awesome app
20:49.06arrrghhhbut it's still a very manual process
20:51.59WisTilt2with it added in the rootfs its not manual at all now.  only thing people have to do it cycle the device battery, run the app and away you go.  might need to tweak 1 value for full charge setting but thats a no brainer.
20:52.40arrrghhhnothing is a no brainer with the forums...
20:52.46arrrghhhwith users on the forums i should say.
20:53.03arrrghhhi think you overestimate the ability of our userbase :P
20:53.28WisTilt2yeah probably so.  that's why i stay away from there and let you deal with the headaches:)
20:53.34arrrghhhhehe
20:54.04arrrghhhyea, i think i'm getting burned out on helping so much.  probably gonna step away from the forums a bit...
20:54.17arrrghhhit wouldn't be so bad if i wasn't saying the same thing over and over and over again.
20:54.53arrrghhhbut your talents are much better served hacking at kernels, rather than helping the noobs.  stay away from the forums, i can't say i blame you :P
20:55.00WisTilt2that would frustrate me beyond my tolerance levels and i'd probably be banned for what i'd say at that point.
20:55.08arrrghhhlmao
20:55.38arrrghhhsurprised i haven't been in fact.  i know some mods have been 'keeping a close eye' on me... but i still help even if i do noob bash :P
20:55.49WisTilt2ive read the comments in the forums in the past and wonder how some of those people actually can operate their computers let alone phones.
20:55.56arrrghhhyea
20:56.02arrrghhhi've told a few people to just stick to WinMo lol
20:57.00WisTilt2yep, similar to people that want to get into linux and wonder why its so hard.
20:57.18arrrghhhhahaha
20:58.37arrrghhhRTFM just doesn't work with some people.  there will always be those people who want to be spoon-fed.  then of course they learn nothing from the experience.
20:59.04*** join/#htc-linux CASJ (~s@109.61.7.242)
21:00.53*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
21:01.59*** join/#htc-linux furtardo (~mks@nat/yahoo/x-kqryjavdozygraoc)
21:02.00*** join/#htc-linux mitsutaka (~mitsutaka@p1227-ipbf3907marunouchi.tokyo.ocn.ne.jp)
21:02.02joshkoss:)
21:07.56WisTilt2emwe: is MSM_SHARED_RAM_BASE+0xfc128 a 32bit location for the 32 vic irq's?  that write 0, in pm isnt right then since a high bit is what actually clears vic int clear.
21:08.58*** join/#htc-linux mastermerlin (~Adium@p4FEE57B2.dip.t-dialin.net)
21:09.59WisTilt2proc_comm line 370+ is correct as that does clear M2A_6 correctly.
21:16.56emweWisTilt2: assumed 32bit yes of what i "know". but there's actually 4 byte afterwards not documented in memorymap on htc-linux wiki
21:17.24*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
21:20.48WisTilt2emwe: looks good so far with both tests.  I think removing the usb status in worker and keeping it in exit_sleep is what we want.  usb detects immediately and after numerous plug in/outs, sleeps, etc., no issues so far.  going to run one of each config rest of day and overnight to be sure.
21:21.10emweyeah, running the other way around here over night again
21:22.05WisTilt2it reboots to winmo or sod's usually within a couple hours or so, none at all yet.  another 16-18hrs should tell for sure.
21:23.03emwetopa just stays wake with blank panel. at leat i had it once and even detecting cable plugs according to dmesg
21:23.09emwewe'll see over night
21:23.15emwenot sure about what you said about the high bits
21:23.47emwebit's set indicate a reason evaluated in the worker.
21:24.11emweand line ~370 unsets these bits again
21:24.44emwei gotta run though. time for bed
21:24.49emwewe'll talk tomorrow then.
21:24.50emwegnight.
21:26.07arrrghhhnn
21:28.36WisTilt2emwe: what i meant by high bits is the vic_int_clear bits are cleared when set high, does nothing when set low.  a value of 0 would be ignored and do nothing.
21:29.04WisTilt2nite.  we'll compare results tomorrow
21:29.12*** join/#htc-linux mastermerlin1 (~Adium@p4FEE4642.dip.t-dialin.net)
21:29.37WisTilt2emwe: line 370 actually "sets" the bits, which clears the interrupt:)
21:31.00WisTilt2actually line 370 returns ints remaing, line 372 sets the interrupt clear register.  confusing logic these yoyo's use.
21:40.19*** join/#htc-linux vinceweis_ (4463ed13@gateway/web/freenode/ip.68.99.237.19)
21:41.38*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
21:41.49*** join/#htc-linux mastermerlin (~Adium@p4FEE48E0.dip.t-dialin.net)
22:08.34*** join/#htc-linux furtardo (~mks@nat/yahoo/x-njxkewrlvzjvhmjw)
22:17.51*** join/#htc-linux Rajko (~rajkosto@cable-94-189-150-102.dynamic.sbb.rs)
22:19.02*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
22:22.09WisTilt2jonpry: i can't for the life of me get service on .39! Are you on gsm or cdma down there?
22:33.30arrrghhhWisTilt2, he's GSM.
22:33.32arrrghhhhe's got a 210
22:34.42WisTilt2well he's been able to call into his phone and im still staring at a big X so guess i'll keep tracing
22:39.08*** join/#htc-linux stroughtonsmith (~steven@86-44-116-173-dynamic.b-ras2.bbh.dublin.eircom.net)
22:40.02arrrghhhhrm
22:44.21jonprygsm
22:47.27*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
22:49.56GNUtoohi, the vilvord's ril is outdated
22:50.07GNUtoowhat is the current one you use for wince devices?
22:50.23arrrghhhGNUtoo, depends on the device
22:50.33GNUtoofor msm
22:50.35GNUtooor qsd
22:50.46GNUtoothat has qmi0
22:51.01arrrghhhdunno
22:51.04GNUtoowhat would be the closest for dream and nexusone
22:51.07arrrghhhhd2 folk just used a wrapper
22:51.14GNUtooah ouch
22:51.17arrrghhhand our RIL was completely rewritten by hyc
22:51.22arrrghhhMSM folk i should say
22:51.33GNUtoowhere's the code for hyc?
22:51.41arrrghhhhe used the vogue community RIL as a base
22:51.42arrrghhh1 sec
22:52.20arrrghhhgitorious is now blocked at work, fantastic.
22:52.24rpierce99http://www.gitorious.org/~hyc/xdandroid/hycs-hardware_xdandroid-ril
22:52.31GNUtoothanks a lot
22:52.50arrrghhhthx rpierce99
22:53.07arrrghhhgrrrrr now i need that workaround moar than ever!
22:53.10rpierce99although he is committing directly to the xdandroid ril now, so the most stable code will be there
22:53.24GNUtoook
22:53.44GNUtoosome people experience some CME 100 while calling in USA
22:53.50GNUtooso I'm looking for a fix
22:54.17GNUtooso I searched for non-standard strings for the htc modem
22:54.29GNUtooand found the vilvord's ril
22:54.41GNUtooI'll look at this new xdandroid ril
22:54.43arrrghhhhaven't heard of that one
22:54.51arrrghhhvilvord's, what device did he work on?
22:54.59GNUtooit's a very old ril
22:55.03arrrghhhyea
22:55.06GNUtoototally outdated
22:55.09arrrghhhheh
22:55.25*** join/#htc-linux Cass (~cass@188-220-34-222.zone11.bethere.co.uk)
22:55.37*** join/#htc-linux tjs_bsd (~tjs@mail.CDPA.cc)
22:55.59GNUtoo<PROTECTED>
22:56.09GNUtoofor instance: what does that command do ^^^^
22:56.22arrrghhhno clue.
22:56.46rpierce99hyc or WisTilt2 would be the goto for those types of questions
22:57.01WisTilt2jonpry: did you make changes to init.froyo.rc in your rootfs by chance?
22:57.56WisTilt2hyc probably has that AT cmd memorized lol.  i have no idea and don't recognize that at all.
22:58.12GNUtoothanks a lot for the pointers
22:58.52GNUtoobtw the new ril I was pointed to is based on vilvord
22:59.18Ondalfatleast gtkc accepts in (0-2),(40)
22:59.36GNUtoook
22:59.49arrrghhhGNUtoo, i said it was based on the Vogue Community RIL
22:59.54arrrghhhperhaps he worked on it
23:00.03Ondalfand gtkt is for testing sequences
23:00.14Ondalfsource: http://forum.xda-developers.com/showthread.php?t=361236&page=5
23:00.21GNUtoook thanks a lot
23:00.23GNUtoolooks
23:02.05GNUtooGTKC btw
23:02.09GNUtoonot GTKT
23:02.39Ondalfyep, but i guess that kc is reading the information that testing sequence gives
23:02.43Ondalfjust my guess
23:02.48GNUtoook
23:03.18Ondalfhas no previous experience of this subject but is sometimes a good with guessing :D
23:03.28arrrghhhheh
23:06.39jonpryWisTilt2, i will have tssc manager done in a few minutes
23:08.03WisTilt2jonpry, ok.  i haven't gotten back to that myself.  just found the radio problem here, im setup to use hyc's test ril and on .39 i have no ril pointer at all so fixing that now.
23:08.23WisTilt2kinda hard to get service with no ril:)
23:09.05*** join/#htc-linux arrrghhh (~arrrghhh@c-24-9-150-163.hsd1.co.comcast.net)
23:10.40jonpryWisTilt2, sure did
23:11.38WisTilt2lol, its like using old school packet radio talking to you with that internet connection you have
23:11.46arrrghhhhahaha
23:12.48WisTilt2pigeons might be faster:)
23:14.37jonpryWisTilt2, yeah that would do it
23:15.54arrrghhhyea i think i might be able to run down your message to him :P
23:16.39arrrghhhwhat kind of latency is he experiencing?  gotta be out of the ms territory and in the second or even minute range lol
23:16.53arrrghhhbrb
23:17.28WisTilt2seems like minutes.  most his answers are from questions minutes earlier.  thats got to be frustrating
23:19.34*** join/#htc-linux arrrghhh (~arrrghhh@c-24-9-150-163.hsd1.co.comcast.net)
23:20.18arrrghhhWisTilt2, yea that cxn would drive me bonkers.  i'm so spoiled by my cxn, i couldn't imagine how spoiled you are :P
23:22.50*** join/#htc-linux ksjhsldjkfhlsdkj (~jon@184.171.165.112)
23:23.16jonpryi'm on vpn now, so you guy can quick making fun of my connection
23:23.24WisTilt2lol
23:23.37WisTilt2vpn is over same crapola connection though isnt it?
23:23.53jonpryyeah but they don't drop packets on :443
23:23.58arrrghhhah nice
23:24.04WisTilt2or is it just the peer from your backbone to freenod that is problem?
23:24.48jonpryno idea. depending on the day there is almost connectivity problem to every server in the universe unless its on 443
23:25.35jonprybut the gf is always on the vpn account downloading movies or whatever so i can't use it
23:25.41arrrghhhhahaha
23:25.47arrrghhhgf's gotta have that vpn :P
23:26.06jonpryshould be able to setup a tunnel through my pc
23:26.12WisTilt2jonpry what about a regular vpn so an endpoint up here?
23:26.29WisTilt2i can easily set you up with a client cert vpn to our vpn server
23:26.32jonpryyeah i am jacked in to phx right now
23:26.50arrrghhhseems drastically better.
23:27.00jonpryit is
23:27.30jonpryWisTilt2, free vpn is the best vpn if thats what your selling
23:28.12WisTilt2any openvpn client will work.  i'd just make the certs for you to get on our vpn network and hit the internet on our fiber
23:28.26arrrghhhhaha
23:29.31jonpryno hurry. i have something that seems to work atm
23:30.30jonprywhere is libsensor?
23:31.38WisTilt2kernel side or userland stuff?
23:31.53jonpryuserland, we have no kernel. so i intend to remove the userland
23:32.49WisTilt2only one i know of off the top of my head is in hardware/android-hardware/sensors
23:32.54*** join/#htc-linux p4dawan (73855dbd@gateway/web/freenode/ip.115.133.93.189)
23:33.09*** part/#htc-linux p4dawan (73855dbd@gateway/web/freenode/ip.115.133.93.189)
23:36.43jonprythats not a path in the system.img
23:37.05WisTilt2thats the path in the xdandroid source
23:38.39jonprynow that we have that all cleared up
23:40.14jonpryi don't understand what missing driver is making system_server or whatever peg
23:41.11WisTilt2seems to happen right into bootani
23:41.52WisTilt2ok where was that file to force use_fast_tls = 0
23:42.07WisTilt2i need to start with clean xdandroid again
23:43.11jonpryframeworks/base/opengl/libs/hooks.h :44,
23:43.24WisTilt2thanks, looked everywhere but there
23:43.30WisTilt2frameworks
23:44.07jonpry.35 doesn't have battery. it might not have the funky i2c dev entry error.
23:44.11WisTilt2saving those 2 changes before i wipe and start clean
23:46.12jonpryi'm going to attempt to apply our super patch against rc8 when it comes out
23:46.43WisTilt2that should be interesting
23:47.08WisTilt2are you using the standard htc generic ril?
23:47.20jonprywhatever is in frx05
23:47.51arrrghhhyes
23:47.52WisTilt2im on frx06 but uses same ril.  rebuilding again so now i wait forever
23:47.56arrrghhhthe vogue community RIL 0.8
23:48.07arrrghhhthey're up to like 1.6
23:48.10jonpryWisTilt2, i build with jX relgiously
23:48.12arrrghhhand we're at like 18.5 by now.
23:48.48WisTilt2jonpry for whatever reason i get errors when using anything above -j3 and i have an i7.  use -j8 for kernel np.
23:49.14jonpryyeah i don't that that problem
23:49.36arrrghhhme neither
23:49.47arrrghhhi use -j5 and it pegs all my cores when building
23:49.48WisTilt2what os?
23:49.52arrrghhhi have a lowly quad core tho
23:49.52jonprybut my computer is super slow now because of some ACPI problem so it takes forever anyways
23:50.03arrrghhhWisTilt2, noobuntu.  10.04.2
23:50.18WisTilt2hmm, thats probably the issue, im on fedora 12
23:50.54WisTilt2i put ubuntu 10 on the nand server for acl, should just build xdandroid on it
23:51.12arrrghhheh, i wouldn't think that would cause an issue like that
23:51.17jonprywe will need out own 39 autobuild anyways
23:51.19arrrghhhespecially since you can build the kernel... hrm.  not sure.
23:51.53WisTilt2yeah i was thinking about setting up .39 autobuild but was going to talk to you about how to go about that the best way.
23:52.17WisTilt2i can certainly setup another machine here
23:53.17jonprynot sure how it all works. [acl] knows how to work all the glemsom code
23:53.43arrrghhhshould be pretty easy to adapt for .39
23:54.05jonpryjust different repo i think
23:54.12arrrghhhyup
23:55.17jonprylooks they were using htc_powersupply on 35, seems like it would crap out on probe with no effect
23:57.35jonpryi have to sleep now lol. too much car working today
23:58.07arrrghhhheh
23:58.09arrrghhhgn jonpry
23:58.23WisTilt2ok im going home anyway. ill catch you guys tomorrow sometime.
23:58.39arrrghhhcya WisTilt2

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