IRC log for #htc-linux on 20090627

00:00.21tmzton diam?
00:00.24IceBoneSi.
00:00.25tmztwhich mtype are you using?
00:01.23IceBone1805
00:01.37tmztwhich is for?
00:02.13IceBoneI have no clue, I just copied the default.txt from the diamraph build to the diam500 one which fixed the touchscreen. :P But I got both these issues on every build I tried.
00:02.31tmztyou need to look at the default.txt
00:02.36tmztyou need to use mtype for raph100
00:02.42IceBoneI see.
00:02.44tmztno
00:02.45tmztdiam100
00:02.52IceBonethe first line says set mtype 1805
00:03.18tmzthtcdiamond              MACH_HTCDIAMOND         HTCDIAMOND              1805
00:04.07IceBoneI paste that in instead of just 1805?
00:04.13tmztno
00:04.26tmztset MTYPE 1805
00:04.39IceBoneI should say I'm no programmer. Most of the time I just wing it and hope for the best.
00:04.42IceBoneThat's what it says.
00:05.20IceBoneAll of them do.
00:05.36tmztthis isn't programming, it's a config file
00:05.42tmztjust open it in a text editor
00:05.51IceBoneDude... I told you I did. That's what it says.
00:06.00IceBoneI downloaded several builds, tried them all.
00:06.06IceBoneAll default.txt files have 1805
00:06.26tmztI can only help you if I have a clear picture of what's going on, telling me you've tried "builds" doesn't help
00:06.56IceBoneMoment.
00:07.30IceBoneI've tried this one: http://connect-utb.com/index.php?option=com_rokdownloads&view=file&Itemid=68&id=17:-android-for-htc-touch-pro-raph-a-diam
00:07.57IceBoneWhich has the instructions to rename the correct default.txt for the device you use.
00:08.01*** join/#htc-linux swc|666 (n=infidel2@unaffiliated/swc666/x-4934821)
00:08.04IceBoneWhich has set mtype 1805.
00:08.24IceBoneI also tried this one:
00:08.25IceBonehttp://connect-utb.com/index.php?option=com_rokdownloads&view=file&Itemid=68&id=20:android-for-htc-touch-diamond-diam500
00:08.37IceBoneSaw it had more stuff, but the touchscreen was flipped.
00:08.52IceBoneSo I replaced the default.txt in that diam500 build with the diamond one from the previous build.
00:09.04IceBoneIt fixed the touchscreen, but everything else remained.
00:09.26IceBoneStill no access to internal storage and font size didn't save in spare parts.
00:09.52dcordesgniite
00:09.58IceBoneThe old version didn't have those two issues.
00:11.04IceBonegnight, dcordes
00:14.15IceBoneI'm not much help, am I?
00:18.08*** join/#htc-linux skodde (n=skodde@unaffiliated/skodde)
00:19.14tmztsorry, had to go
00:20.05tmztall the builds should have kernel support for all four devices
00:20.20tmztmtype is what tells kernel which support to use
00:21.45IceBoneI see that raph is 1910, raph800 is 2039. The one I'm using is definitely 1805.
00:22.09tmztok
00:22.25tmztplease paste current mtype and cmdline lines
00:22.35IceBoneset mtype 1805
00:22.42IceBoneset cmdline "root=/dev/ram0 init=/init console=tty0 mem=76M msmsdcc_id=2 imgdevname=/dev/mmcblk0 imgdevnum=0 imgdir=/tmp msmts_calib=0x7a.0x5e.0x35a.0x37f msmvkeyb_toggle=hide"
00:24.59tmztis that calib for diam100?
00:25.03tmztok
00:25.07tmztlooks good
00:25.14tmztremove msm sdcc
00:25.22tmztmsmsdcc id
00:25.35IceBoneRemove completely or replace?
00:26.06tmztremove
00:26.09IceBoneRighto.
00:26.12tmztnot used any more
00:27.13tmztI don't think root=/dev/ram0 is need either but it seems to be okay
00:27.24IceBoneShould that fix it? Do I just boot up or do I need to do a soft reset first? (says so in the instructions)
00:27.59tmztreset is good
00:28.10tmztI don't think it's really necessary
00:28.21tmztit won't hurt though
00:28.35IceBoneTakes 2 minutes 10 seconds to boot up wm and tf3d2... :(
00:29.15tmzteither way
00:29.17IceBoneAndroid on the other hand takes only 40 seconds.
00:29.20IceBone"is nice"
00:29.47IceBoneDo you guys have any info on HTC Sense?
00:30.22tmztnot more than what is known
00:30.38tmztsupposedly "hero" rom has some of that
00:30.41IceBoneIt looks very nice.
00:30.45IceBoneYeah.
00:31.07IceBoneToo bad android isn't optimised for VGA. :(
00:31.11IceBoneLooks so tiny on the Diamond.
00:31.28tmztyou could use it in hvga I think
00:31.34tmztmaybe
00:31.47IceBoneBut that would negate having a VGA screen. :P
00:32.30IceBoneI'm running the sdk emulator in vga mode right now. It's insane how much bigger it is.
00:32.51IceBoneBooting android.
00:33.20IceBoneAnd it stopped on framebuffer console
00:33.27tmzttry again
00:33.33tmztit does that randomly
00:33.38IceBoneYes, I've noticed.
00:33.45IceBoneAny simpler way than red button reset?
00:33.49tmztno
00:33.55IceBoneRoger.
00:34.35IceBoneHow far along has this come, in your opinion?
00:35.02IceBoneFrom start of development to stable build with all features working (or at least functioning basic phone stuff)
00:36.04tmztmostly paying attention to kernel
00:36.39tmztthose builds aren't directly our goal in this channel
00:36.57IceBoneBut quite a ways off still, huh?
00:37.11tmztwe are far more interested in having a stable base for linux, including android to run
00:37.40tmztwe are working on sound today
00:37.43IceBoneThe most I've dabbled in linux was installing Debian sarge on my laptop.
00:38.08IceBoneI still get the "Removed SD Card" notification.
00:38.24tmztthat's a userspace issue
00:38.31tmztseems hard to solve
00:39.04IceBoneWell, it worked on the old version. You must have made major changes since.
00:39.59tmztus?
00:40.05tmztno, 1.5 is different
00:40.10IceBoneAh, I see.
00:40.27tmzttalk to San in #android
00:40.35IceBoneI'm not pointing fingers here, I'm just investigating. :)
00:40.42tmztthat's what I meant by userspace, not kernel
00:41.18IceBoneShould I go ask there?
00:42.06tmztnot really
00:42.18tmztthey don't support diam
00:42.20IceBoneOh, this new change brought something else. If I went into gallery before it said "No media" and I was able to go back. Now, when I try to go back, some code is displayed briefly, but it stays in the media gallery.
00:42.22IceBoneAh.
00:42.26*** join/#htc-linux maejrep (n=madcoder@c-71-225-60-178.hsd1.pa.comcast.net)
00:42.43tmztthe problem is you have a loop fs on the sdcard and are also trying to mount it
00:42.57tmztmaejrep: !!!
00:43.15tmztbusy on yb stuff?
00:43.17tmztmyb
00:44.08IceBoneI think I understand that. :) Yeah, makes sense. I'm assuming same as not being able to access the sd card from the phone when it's connected to the pc.
00:44.42tmztbasically
00:46.49IceBoneWell, if there's anything I can do to help... I can't code though. I might reskin it if I'm given the tools. :D
00:47.41tmztget hero orking?
00:47.49tmztseems some people would like that
00:47.58IceBone:D
00:48.04IceBoneI bet they would.
00:48.09tmztit won't be usable without 3d
00:48.16tmztso we need that first
00:53.14cr2_good night
00:53.30IceBoneWell, good luck with that, I'm a right-brain person, no programming out of me.
00:58.50IceBoneThanks for the help, though.
01:25.48*** join/#htc-linux mburris (i=62d7f536@gateway/web/freenode/x-9839be6b92e00e56)
02:14.48*** join/#htc-linux surge (i=surge@pool-98-118-158-217.bflony.fios.verizon.net)
02:28.54tmzthttps://www.codeaurora.org/patches/quic/le/PATCH_u-boot-2009.03_1144_LCD_support_20090608.tar.gz
02:29.03tmzthttps://www.codeaurora.org/patches/quic/le/PATCH_u-boot-2009.03_1147_nand_support_20090601.tar.gz
02:29.09tmzthttps://www.codeaurora.org/patches/quic/le/u-boot-2009.03_PATCH_2009_05_14.patch
02:29.14tmztNAND and LCD now
02:32.32tmzt+    // Initialize the PHY
02:32.32tmzt+    // ZZZZ replace this with an smem_proc_comm call???
02:32.33tmzt+    usbhs_ulpi_phy_init();
02:32.36tmztplease don't
02:33.41tmzt+    if (apps_part_start_blk == 0)
02:33.41tmzt+    {
02:33.41tmzt+        printf("NAND: starting block of APPS partition is unknown\n");
02:33.41tmzt+        return 0;
02:33.41tmzt+    }
02:33.43tmzt+
02:33.46tmzt+    /*
02:33.49tmzt+     * Can't assume the user knows which block the APPS partition starts in.
02:33.51tmzt+     * To boot from NAND, user should run "nboot <addr> 0 0".  (offset = 0)
02:33.54tmzt+     * This function will add the APPS partition offset automatically.
02:33.56tmzt+     */
02:33.59tmzt+
02:35.50tmzt+/*
02:35.50tmzt+ *  adm.h - Application Data Mover (ADM) definitions
02:35.50tmzt+ *
02:46.16tmzt.
02:46.17tmzt+#ifdef D800_480
02:46.18tmzt+   #define DISP_W     800
02:46.19tmzt+   #define HBP        216
02:46.19tmzt+   #define HFP        40
02:46.21tmzt+   #define DISP_H     600
02:46.23tmzt+   #define VBP        27
02:46.26tmzt+   #define VFP        1
02:46.29tmzt+   #define LCD_MD_VAL_40MHZ 0x0005FFCF
02:46.31tmzt+   #define LCD_NS_VAL_40MHZ 0xFFD41B49
02:46.34tmzt+#endif
02:55.03*** join/#htc-linux TeringTu1y (n=Maarten@195-241-125-243.ip.telfort.nl)
03:08.59*** join/#htc-linux mrmoku|a` (n=mrmoku@ppp-93-104-45-6.dynamic.mnet-online.de)
03:36.41*** join/#htc-linux xsacha-tv (n=sacha@203-214-116-29.dyn.iinet.net.au)
04:05.52*** join/#htc-linux jaSOnGg (n=IamSOG@218.20.195.220)
04:41.03*** join/#htc-linux droid001 (n=mc@p4FDCF54F.dip.t-dialin.net)
04:52.35*** join/#htc-linux Moku (n=John@f048163136.adsl.alicedsl.de)
04:56.17*** join/#htc-linux ptitjes (n=didier@212.73.198-77.rev.gaoland.net)
06:20.59*** join/#htc-linux ImCoKeMaN (n=imcokema@pool-96-249-154-100.hrbgpa.fios.verizon.net)
06:44.41*** join/#htc-linux goxboxlive (n=goxboxli@140.84-48-184.nextgentel.com)
06:49.50*** join/#htc-linux kiozen (n=oeichler@rgnb-5d87d7ff.pool.einsundeins.de)
07:05.22*** join/#htc-linux Echo31 (n=olivier@mir31-4-82-240-194-54.fbx.proxad.net)
07:22.15xsacha-tvhow do i set where my devices go in kernel? eg. /sys/class/timed_output/ ?
07:30.51maejrepxsacha-tv: if you register it as a class, it'll go to /sys/class, if you register it as some other device type, it'll go there, etc
07:30.58maejrep*class device
07:31.24xsacha-tvyeah it's a class, but how do i get it to go in to timed_output?
07:32.24xsacha-tvcause android only looks in timed_output/
07:32.35xsacha-tvTHE_DEVICE "/sys/class/timed_output/vibrator/enable"
07:49.06xsacha-tvmaejrep, sysdev_class_register instead of platform_register_device ?
07:53.23*** join/#htc-linux nebi (n=nebi@217.142.147.19)
08:19.06*** join/#htc-linux hollo_ (n=hollo@3e6b7b2c.rev.stofanet.dk)
08:29.26*** join/#htc-linux pe7er (n=Adium@f053195136.adsl.alicedsl.de)
08:52.50*** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbfd693.pool.einsundeins.de)
08:59.08dcordeseelo
09:02.59xsacha-tvhi
09:03.20xsacha-tvdcordes: what do i change in how i register the device? :\
09:05.05dcordesI have no idea
09:05.23dcordescan't you change it in the userspace? you buuild android yourself
09:09.03*** join/#htc-linux JuNu_KN (n=chatzill@95.113.18.25)
09:10.44xsacha-tvyeah i could
09:10.56xsacha-tvbut i sort of wanted it to work in future builds without customising each one
09:11.14xsacha-tvhang on, there seems to be a timed_output driver in misc/
09:12.39*** join/#htc-linux JuNu_KN_ (n=chatzill@95.113.18.25)
09:14.44*** join/#htc-linux JuNu_KN__ (n=chatzill@95.113.18.25)
09:18.13*** join/#htc-linux JuNu_KN___ (n=chatzill@95.113.18.25)
09:24.18*** join/#htc-linux TeringTuby (n=Maarten@195-241-125-243.ip.telfort.nl)
09:24.30*** mode/#htc-linux [+o dcordes] by ChanServ
09:27.49dcordesJuNu_KN: one nick is not sufficient?
09:28.46*** kick/#htc-linux [JuNu_KN___!n=dcordes@unaffiliated/dcordes] by dcordes (dcordes)
09:28.51*** kick/#htc-linux [JuNu_KN__!n=dcordes@unaffiliated/dcordes] by dcordes (dcordes)
09:28.52*** kick/#htc-linux [JuNu_KN_!n=dcordes@unaffiliated/dcordes] by dcordes (dcordes)
09:28.54*** kick/#htc-linux [JuNu_KN!n=dcordes@unaffiliated/dcordes] by dcordes (dcordes)
09:31.20dcordesxsacha-tv: a pity google don't use convetional userspace interfaces
09:38.38*** join/#htc-linux MethoS (n=clemens@host-091-097-246-153.ewe-ip-backbone.de)
09:43.07*** mode/#htc-linux [-o dcordes] by ChanServ
09:45.05dcordesxsacha-tv: there was a person here who modified some omap kernel for android use. if you search the logs you might find them
09:48.10*** join/#htc-linux ccube_ (n=ccube@ssh.ccube.de)
09:56.19*** join/#htc-linux the_sys0p (n=the_sys0@cpe-67-49-192-228.bak.res.rr.com)
10:09.41*** join/#htc-linux sxe (n=sxe@ip-62-143-86-48.unitymediagroup.de)
10:16.05*** join/#htc-linux pe7er (n=Adium@f053195136.adsl.alicedsl.de)
10:20.08*** join/#htc-linux dream_kill (n=nospam@89.131.127.37)
10:24.19*** join/#htc-linux pe7er (n=Adium@f053195136.adsl.alicedsl.de)
10:32.34*** join/#htc-linux captnoord (i=5147a47b@gateway/web/freenode/x-d19a3ee8b61c35ee)
10:53.23*** join/#htc-linux DJW|Home (i=djwillis@82-46-19-72.cable.ubr02.bath.blueyonder.co.uk)
10:58.38xsacha-tvup2ocr
10:58.46xsacha-tvapt, up2ocr
10:58.46aptextra, extra, read all about it, up2ocr is 0x40600020, or the USB Port 2 Output Control Register, or used for udc
11:17.38*** join/#htc-linux cr2 (n=cr2@ip-90-187-125-182.web.vodafone.de)
11:23.07*** join/#htc-linux pe7er (n=Adium@f053195136.adsl.alicedsl.de)
11:23.23*** join/#htc-linux stephan_ (n=stephan@217.237.166.82)
11:24.27cr2+#define BATTERY_MIMIC_LEGACY_VBATT_READ_PROC 11
11:25.42Echo31hi cr2
11:28.02cr2hi Echo31
11:28.22Echo31cr2: When you plan to update the athena pages of http://wiki.xda-developers.com for gpio,cpld2 and cpld1 ?
11:30.05cr2Echo31: i'll use htc-linux.org wiki
11:30.29cr2Echo31: btw, we have 8 led gpios
11:30.39cr2how many leds are there ?
11:30.52*** join/#htc-linux Zoolooc_ (n=fredsiba@nrbg-4dbfcaa2.pool.einsundeins.de)
11:31.39Echo31cr2: My device is HTC advantage x7500
11:34.55cr2mine is t-mob ameo, but i think they are more or less identical
11:35.44Echo31cr2: I think have 3 leds  (gsm, bt/wifi,alert) + 3 leds of nav button (red, green, orange)
11:37.25cr2orange may be red+green
11:37.49cr2what about baclklight leds for the buttons ?
11:38.28cr2also, the bt/wifi led can be blue/green ?
11:42.37Echo31cr2: i insert a sim card for looking the leds colour
11:45.00cr2ok
11:55.13Echo31cr2:   the userguide in french defines 4 leds: first  for power (green orange red), second for gsm=green and gps=orange, third for bt=blue, wifi=green , forth for notification (no other info)
11:55.58Echo31cr2: if orange is different green+red, i have 8 leds
11:57.15cr2ok, that sounds good
11:59.26cr2Echo31: can you dump the cpld registers ?
12:01.13*** join/#htc-linux Zoolooc__ (n=fredsiba@nrbg-4dbfce9b.pool.einsundeins.de)
12:01.26cr2Echo31: do you have the "OK" and windows button under the navigation button ?
12:01.48Echo31cr2: yes
12:01.58cr2they also have a backlight, but it seems to me that the lcd backlight is used for them
12:02.47Echo31cr2: I can dump, but i don't know correctly the commands of haret
12:03.25Echo31cr2: i launch telnet
12:03.33cr2where is your cpld1 ?
12:04.50cr2Echo31: which address has the rndis usb ?
12:08.26Echo31cr2: 192.168.131.129 IP of my device
12:09.34*** join/#htc-linux JuNu_KN (n=chatzill@95.113.18.25)
12:09.36cr2bash: telnet: command not found
12:09.39cr2eh?
12:13.11*** join/#htc-linux JuNu_KN_ (n=chatzill@95.113.18.25)
12:15.46Echo31cr2:  my fw blocked , i am ready now .
12:17.20*** join/#htc-linux JuNu_KN__ (n=chatzill@95.113.18.25)
12:20.24*** join/#htc-linux JuNu_KN___ (n=chatzill@95.113.18.25)
12:20.42Echo31cr2: Is it the command hereafter :  V dump 0x09000000 2  for cpld2 ?
12:26.04*** join/#htc-linux cr2 (n=cr2@ip-90-187-125-182.web.vodafone.de)
12:26.25cr2Echo31: the athena address is 169.254.2.1
12:27.46Echo31cr2: i am connected to device with telnet.
12:28.12cr2oer usb or wifi ?
12:28.26Echo31cr2: via usb
12:29.25cr2ok
12:29.28cr2http://www.htc-linux.org/wiki/index.php?title=MemoryMap
12:29.34cr2the page looks a bit broken
12:30.08cr20x08000000 CPLD1
12:30.24Echo31cr2: yes, and the cpld2 starts 0x09000000 on two 2 octets (16 bits)
12:32.04cr2HaRET(1)# pd 0x08000000 0x100
12:32.05cr208000000 | 00000004 00500013 00fe0000 000a0021 | ......P.....!...
12:32.07cr208000010 | 00000000 00000000 00000000 00000000 | ................
12:32.15cr2does not look very promising
12:32.56cr2hm.
12:33.19cr2let's check
12:33.32cr2the shadow copy
12:34.27Echo31cr2: I have the same values
12:35.53cr2the "orange" charging led is on
12:36.55Echo31cr2: Yes
12:40.36*** join/#htc-linux wirelessdreamer (n=dreamer@chrobd01.vailsys.com)
12:43.04Echo31cr2: my only lit led is the orange charging led. I do what now ?
12:44.22*** join/#htc-linux xsacha-tv (n=sacha@203-214-116-29.dyn.iinet.net.au)
12:45.36cr2enable bt
12:46.41cr2HaRET(5)# pd 0x08000000 0x20
12:46.42cr208000000 | 00400034 00d00013 00ff0000 000a0021 | 4.@.........!...
12:46.48cr2was
12:46.56cr208000000 | 00000004 00500013 00fe0000 000a0021 | ......P.....!...
12:47.58cr2+wifi
12:48.02cr208000000 | 00c00034 00d0005b 00ff0000 000a0021 | 4...[.......!...
12:49.01Echo31cr2: i have same data
12:49.18Echo31cr2: ok
12:49.34cr2GPIOB3   0x0008   led related <- wifi ??
12:50.21cr2since they use shadow, i'm a bit worried
12:51.10xsacha-tvhow come the address is so nice? 0x08000000?
12:52.42cr2HaRET(13)# nledon 0
12:52.44cr2HaRET(14)# pd 0x08000000 0x10
12:52.45cr208000000 | 00e00034 00d0005b 00ff0000 000a0021 | 4...[.......!...
12:53.18cr2e=8+4+2 ?
12:54.00cr2ah.
12:54.07cr2e0=80+40+20
12:54.36Echo31cr2: nledon 0 is not reconnized by my haret
12:54.46cr2GPIOB5   0x0020   led related
12:54.47cr2GPIOB6   0x0040   led related
12:54.49cr2GPIOB7   0x0080   led related
12:54.58cr2Echo31: i use an ancient haret
12:55.07Echo31cr2: ok
12:55.08cr2Echo31: nled ?
12:55.23Echo31cr2: thanks
12:55.37cr2Echo31: it was installed there on 12.10.2007 according to wince :)
12:56.12cr2so 20 is nled (alert)
12:56.31cr240 is bt blue blink
12:56.42xsacha-tvfor my device, NLED 0-9 only work when im not charging and NLED 11-20 only work when i am charging
12:56.49cr2and 80 is wifi green blink
12:56.53dcordescr2: build done
12:56.56xsacha-tvactually 3 and 6 work when im charging too
12:57.16cr2xsacha-tv: it's all very device-dependent
12:57.24cr2dcordes: initrd ?
12:57.26dcordesit has the ppp uucp cu wireless-tools ssh etc etc. can you give me the config file?
12:57.29dcordesyea
12:57.39xsacha-tvdo i have to write an LED driver from scratch?
12:57.43cr2dcordes: which config ?
12:57.58xsacha-tvcause my LED uses one GPIO for blue, red, green, orange
12:58.06cr2xsacha-tv: led-gpio is a very standard driver
12:58.07dcordesoh and it also has tslib. the one for vodafone pppd
12:58.18cr2dcordes: hmm.
12:58.18xsacha-tvbut all 4 colours use the same gpio?
12:58.48cr2dcordes: i can copy from nc10
12:59.01cr2dcordes: some minor changes are needed
12:59.03dcordesthat would be good. so we have the known working config
12:59.09cr2yes
12:59.16cr2xsacha-tv: no, these are different leds
12:59.38cr2xsacha-tv: only the charging leds may be muxed
12:59.39xsacha-tvcause i tried led-gpio driver on it and i only get the colour green.. so i have to write my own?
12:59.49xsacha-tvyeah it is a charging led
12:59.57cr2xsacha-tv: you need to adapt to your gpios
13:00.18xsacha-tvwell it's one LED with 4 colours and one GPIO (9)
13:00.37cr2Echo31: what about gsm & gps led ?
13:00.43xsacha-tvit has funky values for each colour like 0xffd0f5
13:01.00cr2xsacha-tv: ok, then i don't have an idea
13:01.25Echo31cr2: gsm=green and gps=orange
13:01.41xsacha-tvyeah i have that too
13:01.42cr2Echo31: the bits
13:01.45xsacha-tvand blue=wifi
13:02.06cr2Echo31: i can't test without the sim
13:02.41cr2hm, i need to check umts on athe eventually
13:03.02Echo31cr2: i dump what ?
13:03.21cr2pd 0x08000000 0x10
13:03.43cr208000000 | 00f20034 00d0005b 00ff0000 000a0021
13:03.51cr2gps is yellow blink
13:04.19Echo3108000000 | 00ca0034 0090005b 00ff0000 000a0021 | 4...[.......!...
13:04.41cr2ca ? i have f2
13:04.58*** join/#htc-linux stephan_ (n=stephan@217.237.166.98)
13:05.08cr2f2=2+80+40+20+10 ?
13:05.23Echo31cr2: yes, i have a led (yellow blink)
13:05.31cr2so 10 is gps ?
13:05.49cr22 is GPIOB1   0x0002   phone power (on=1,off=0)
13:06.01cr2you have phone on ?
13:06.45Echo31cr2: yes
13:07.45cr2ca=80+40+8+2
13:07.54cr2gps off, nled off ?
13:08.12cr2then 8 is gsm green led ?
13:08.35*** join/#htc-linux fnord (n=fnord@24-151-90-116.static.nwtn.ct.charter.com)
13:08.39*** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo)
13:10.24Echo31cr2: gsm gps without bt/wifi  002a0014 00900013 00ff0020 000a0021 | ..*..... ...!...
13:10.34cr2dcordes: https://privatepaste.com/a2bvF6vLWn this is my nc10 /etc/ppp/peers/vodafone-de
13:11.04cr22a=20+8+2
13:11.58cr2should be gsm+nled
13:12.52Echo31cr2: i have green gsm and orange alert led blink
13:12.59cr2yes
13:13.17cr2Echo31: gps and gsm led are the same left led
13:13.44Echo31cr2: ok
13:13.52cr2Echo31: i charge over usb, it's slow
13:14.20cr2Echo31: can you full charge with AC, and check the green charging led ?
13:15.25cr2i'll edit the wiki
13:17.13xsacha-tvcr2: do you know about battery drivers?
13:17.33xsacha-tvmy board has 2 power management chips next to battery.. what do i need drivers for? one of those chips?
13:19.27Echo31cr2: ok, i wait the charging state
13:19.27cr2xsacha-tv: it's very device specific
13:19.27xsacha-tvhmm ok
13:20.33cr2Echo31: looks better now -> http://www.htc-linux.org/wiki/index.php?title=CPLD1
13:21.14IceBoneThat does look... neat and tidy.
13:21.56cr2Echo31: backlight power is on cpld2
13:23.32cr2Echo31: but there is also 4,80. maybe the ok/menu backlight is different from lcd.
13:26.27cr2listed as GPIOD7   0x0080   joystick bkl ?
13:27.19cr2it's together with pxa gpio
13:27.34cr20x20 in bank3
13:28.49cr2GPIO 101   00000020   backlight (power enable=1)
13:30.28Echo31cr2: ok , i follow
13:33.51cr2i may try to enable it manually
13:34.24Echo31cr2: my charging level is already 97 percent
13:35.30*** join/#htc-linux MethoS- (n=clemens@host-091-097-245-239.ewe-ip-backbone.de)
13:36.51xsacha-tvwhats a joystick? :\
13:37.01cr2<PROTECTED>
13:37.47cr2hm. lcd and ok/menu bkl is on
13:38.01cr2xsacha-tv: 4+1directional button
13:38.09xsacha-tvoh
13:38.25xsacha-tva dpad?
13:39.12cr2its on most htc devices. in one or other form
13:39.28cr2on athena it's done as a joystick.
13:45.10cr2dcordes: https://privatepaste.com/501vkYMgR1 chat script
13:45.35cr2dcordes: but i always enter the pin with cu manuall before running pppd
13:46.15cr2dcordes: the chat script should include the full htc AT init string
13:50.27cr2Echo31: what is your board id ?
13:52.38Echo31cr2: how find my board id
13:53.55cr2Echo31: pd 0x09000000 4
13:55.18Echo31cr2: 09000000 | c93fc93f
13:57.01cr2c=80+40
13:57.22cr2110=6
13:57.49cr2<PROTECTED>
13:58.21cr2c=21
13:58.59cr2GPIOG5   0x0020   1582 present, CPLD2 location (get) .
13:59.02cr2is set
13:59.43cr20xab200000   0x0a000000   0x01   CPLD2 CPLD1c 0x20 unset
13:59.44cr20xab200000   0x09000000   0x01   CPLD2 CPLD1c 0x20 set
14:01.25*** join/#htc-linux Captnoord (n=Captnoor@dc5147a47b.adsl.wanadoo.nl)
14:06.21cr2Echo31: what is qkeyled ?
14:06.34*** join/#htc-linux StarLite (n=nnscript@s55916ca6.adsl.wanadoo.nl)
14:06.36cr2it's usually the keybaord
14:07.02Captnoordor its the led of the 'q' key
14:09.16Echo31cr2: charged (green) without gsm bt wifi 08000000 | 0000000c 00d00012 00fe0000 000a0021
14:10.23cr2Echo31: 12
14:10.43cr2was 5b
14:11.00cr2b=8+2+1
14:11.53cr22=2
14:12.53cr28 is wifi pwr
14:12.58cr2seen 13
14:13.32cr21 is the red led ? 2 is the green ?
14:14.03cr2i have 13
14:15.27cr2yeah pfh 0x08000004 1 0x11
14:15.29cr2red
14:15.49cr2pfh 0x08000004 1 0x12
14:15.52cr2green
14:16.13cr2pfh 0x08000004 1 0x10
14:16.15cr2off
14:16.44cr2but what is this one ?
14:16.47cr2GPIOC2   0x0004   led related
14:17.57cr2got blinking red :)
14:19.10cr2ok, seems to be consistent.
14:19.25Echo31cr2: good
14:19.38cr2blinking red ignores red/green settings
14:19.54cr2editing wiki
14:21.12IceBoneHey, this is really fun to watch, but may I ask what you're developing right now? Just raw linux or is it device specific?
14:21.14*** join/#htc-linux JuNu_KN (n=chatzill@95.113.18.25)
14:21.21*** join/#htc-linux skodde (n=skodde@unaffiliated/skodde)
14:22.02cr2IceBone: htc athena
14:22.29cr2IceBone: the best inet appliance from htc. imho.
14:22.32IceBoneI see.
14:23.13cr2IceBone: http://wiki.xda-developers.com/index.php?pagename=HTC_Athena
14:23.16IceBoneLooks nice, but I prefer my mobile computer it in phone form. :)
14:24.19cr2that's why i call it an appliance
14:24.29IceBoneHow different are various HTC devices in regards to the hardware they use? If you develop a driver for this, can it be used as a basis for others as well?
14:24.48cr2i will prefer its vga screen to raph. vga @ 2.8" is just an overkill
14:25.05IceBoneHeh, yeah... it's tiny.
14:25.08cr2only for others in the same class
14:25.56*** join/#htc-linux fnord (n=fnord@24-151-90-116.static.nwtn.ct.charter.com)
14:25.59cr2but athena will not play sound. it's too difficult to develop
14:26.11cr2and the cams.
14:26.18IceBone:/
14:26.19cr2but the htc cams are lame anyway.
14:26.47IceBoneI don't even use it on my diamond anyway, I have a pro dslr with me at all times almost and it would be a bit silly.
14:26.48cr2but for gps and inet it's a perfect device.
14:26.55IceBoneIt's also broken. :D
14:27.02cr2yeah
14:27.10IceBoneThe colours are all weird.
14:27.22*** join/#htc-linux Zoolooc_ (n=fredsiba@nrbg-4dbfe948.pool.einsundeins.de)
14:27.36cr2the optics on phones sucks.
14:27.50cr2and will always suck
14:28.29IceBoneNot just the optics, the sensors as well. No matter how many megapixels you crap onto a tiny sensor like that, it will never perform as well as a 35mm sensor.
14:28.39IceBonecram, not crap.
14:28.51IceBoneWell, crap works too.
14:28.59cr2hm. where do you get 35mm ccd ??
14:29.29IceBoneCanon 5d (mkII), Canon 1Ds, Nikon D700, Nikon D3, D3x.
14:29.49cr2it's insane
14:30.12IceBoneI have a D300, which is a 1.5x crop, which is 23.6mm x 15.8mm. Not as big, but big enough.
14:30.56IceBoneAlso spent a few grand on quality glass.
14:31.15IceBoneAnd then you get bozos saying their 200 dollar cam is better cause it has 3 megapixels more.
14:31.42cr2http://www.astrosurf.com/re/chip.html
14:31.54cr236.9 x 36.9
14:32.07cr24096 x 4096
14:32.10cr2omg :)
14:32.37IceBoneCanon is developing a 35mm sensor with 50 megapixels...
14:32.38cr2yes, only the glass counts
14:33.01IceBoneI wish I could afford the good Nikon f/2.8 glass. :(
14:33.16cr2for $20000 ?
14:33.22IceBoneSomething like that. :D
14:33.26cr2:D
14:33.38cr2i had a nice pic somewhere
14:33.39IceBone14-24 is 1500, 24-70 is 2000, 70-200 is 2000.
14:33.48IceBoneNot AS much...
14:33.58cr2i'll grep in the logs
14:34.10IceBoneBut I got a D3 with a 400mm f/2.8 and 2x teleconverter on loan.
14:34.21IceBoneThe lens came in its own carbon fibre hard case.
14:34.30IceBoneSported a CF lens hood as well.
14:34.34IceBoneBody out of CF.
14:34.39IceBoneStill weighed 15 kg...
14:34.49cr2this one ? http://a.img-dpreview.com/news/0703/Sigma/sigma200500mm-big.jpg
14:35.10IceBoneHah, nah, that's a monster I wish I could get my hands on.
14:35.18cr2LOL
14:35.24Perkka:P
14:35.32IceBoneNo pun intended. :
14:35.32IceBone:P
14:35.38Perkkaill be off photographing streetrace in a few min
14:35.55Perkkagotta try my 300 2.8L :)
14:36.24Perkkahttp://idetorka.se/main.php?g2_itemId=3594
14:36.26Perkkamassive :D
14:37.09IceBonehttp://img.phyrefile.com/icebone/2009/05/16/crt_d3_400mm_f2.8_2x.jpg <-- my classmate with the gear. Sorry for the hu-u-uuge size.
14:38.00IceBoneBooo, Canon! :P
14:38.07PerkkaIceBone: i think i look bigger with my 300 2.8 but ig could be imagination
14:38.15Perkkait*
14:38.17cr2also nt bad
14:38.46IceBonehttp://digitalfreak.net/wp-content/uploads/2009/04/sigma_200-500_2-8.jpg
14:38.47Perkkanow i got 2.8 from 16 to 300mm :P
14:38.57IceBonePerkka: sweet
14:39.02Perkkaexept the gap between 200 and 300 than
14:39.16Perkkathere isnt much 200-300 2.8 zooms :P
14:39.35IceBoneYou don't need it anyway. Just shoot at 200 and crop a bit if 300 is too narrow.
14:39.56Perkkayea
14:39.56IceBoneWhat body do you have?
14:40.04Perkka5d+5dmk2
14:40.12Perkkaah, and 20d
14:40.27Perkkalook what i found today.. a COW http://idetorka.se/main.php?g2_itemId=3650
14:40.27IceBoneThe only thing about the 5d mk2 I don't like is the archaic AF system.
14:40.43Perkkai got my af calibrated this week
14:40.50Perkkaso its quite ok now
14:40.52IceBoneIt still has only 9 points. :P
14:40.57Perkkayea
14:41.09Perkkait's more spot on that oof now :P
14:41.37Perkkawas sad before i got it calibrated, 2/3 of the pics were oof
14:41.48IceBoneSome say it's overkill, but if you have it on a tripod and composed properly, it pays to have a bit more points so you don't have to move the cam to focus and then back.
14:41.50Perkkahmm well... gotta go, streetracephoto
14:41.58IceBoneHave fun.
14:42.05Perkkatrue
14:42.10Perkkabye
14:42.10IceBoneI have 51...
14:42.11IceBone>_>
14:42.11IceBone<_<
14:42.54IceBoneWell, that was a bit off topic...
14:50.43cr290,d0,50
14:51.45cr240+10,80+10,80+40+10
14:57.49Echo31cr2: what we do now?
14:58.46cr2im looking at the LCD power gpios now
14:59.16cr2we should not disable them at cpld init, otherwise a full ati reset is unavoidable
15:01.32*** join/#htc-linux fnord (n=fnord@24-151-90-116.static.nwtn.ct.charter.com)
15:02.04*** join/#htc-linux pe7er (n=Adium@f053195136.adsl.alicedsl.de)
15:05.15*** join/#htc-linux mickey_jaw (n=mike@78-105-123-214.zone3.bethere.co.uk)
15:08.28*** join/#htc-linux guyiom (n=guyiom@e47108.upc-e.chello.nl)
15:13.29*** join/#htc-linux skodde (n=skodde@unaffiliated/skodde)
15:14.28cr2Echo31: can you recheck the gps power bit ?
15:15.46Echo31cr2: ok   with gps=gsm
15:16.41cr2gps
15:16.46cr2not the led
15:19.03Echo31cr2: you want  that i launch gps tool ?
15:20.42cr2yes, and check the if the bit1 of +0x6 is enabled
15:20.50cr2because it see it always disabled
15:21.26cr2wince crashed :)
15:21.27Echo31cr2:     08000000 | 00100004 00900012 00fe0020 000a0021
15:21.39cr290
15:23.23*** join/#htc-linux sxe (n=sxe@ip-62-143-86-48.unitymediagroup.de)
15:23.59cr2yeah, seems so. buggy software ?
15:27.29Echo31cr2: no, the software displays the satellites and positions
15:28.13cr2ok
15:30.19cr2Echo31: why do we have FIR driver ?
15:30.34cr2i think athena does not support IR
15:31.12Echo31cr2: yes,  only bt
15:38.51cr2Echo31: light sensor ?
15:39.47*** join/#htc-linux hollo_ (n=hollo@3e6b7b2c.rev.stofanet.dk)
15:40.47Echo31cr2: I launchs the camera ?
15:42.09Echo3108000000 | 00000084 00d00012 00fe0020 000a0021
15:42.46cr2Echo31: they are not so interesting
15:43.08Echo31cr2: without camera 08000000 | 00000004 00d00012 00fe0020 000a0021
15:43.10cr2the cam is controlled over ati i2c and connected to the ati dsp. hopeless.
15:43.22Echo31cr2: 04 and 84
15:43.23cr2Echo31: 2 cams ?
15:43.35cr2the videocall
15:43.38Echo31cr2: yes
15:44.03Echo31i launchs in video call
15:44.29Echo3108000000 | 00010004 00d00012 00fe0020 000a0021
15:45.14cr280
15:46.06cr2ok.
15:46.19cr2the biggest can of worms now. battery driver
15:49.31IceBoneLots of progress today?
15:52.15cr2it's an old work, just revisited it now.
15:52.30cr2the leds are documented too
15:57.51xsacha-tvbattery is hard, eh?
15:58.17xsacha-tvcan help me with it :)
16:21.03*** join/#htc-linux MethoS- (n=clemens@host-091-097-245-239.ewe-ip-backbone.de)
16:23.31PerkkaIceBone: it was the most boring streetrace ever imaginable
16:29.24cr2what is DSSDH ?
16:38.42Echo31cr2: where do you find the word DSSDH ?
16:40.03cr2xsacha-tv: what are the 20 and 2c pxa-gpio regs ?
16:40.10cr2Echo31: misc driver
16:40.25xsacha-tv20 and 2c? what do you mean?
16:40.43xsacha-tvi2c?
16:41.03cr2gpo
16:41.09cr2gpio registers
16:41.38tmztnledset
16:42.39xsacha-tvthe bases?
16:42.59xsacha-tv#define GPIO0_BASE      ((void __iomem *)io_p2v(0x40E00000))
16:43.04cr2#define GPSR2           __REG(0x40E00020)  /* GPIO Pin Output Set Register GPIO<80:64> */
16:43.14xsacha-tvyes
16:43.19cr2#define GPCR2           __REG(0x40E0002C)  /* GPIO Pin Output Clear Register GPIO <80:64> */
16:43.51cr2ok, so it's FE
16:44.45cr2#define GPLR2           __REG(0x40E00008)  /* GPIO Pin-Level Register GPIO<80:64> */
16:45.51xsacha-tvi get 0 when i dump those 20 2C by the way
16:47.33xsacha-tvwhat are they for?
16:49.22*** join/#htc-linux IamSOG (n=IamSOG@218.20.195.220)
16:51.49tmztcr2: did you see what I pasted yesterday?
16:52.18cr2tmzt: what ?
16:52.31cr2the LCD MD/NS ?
16:52.44cr2yes, it fits into my formula
16:53.06cr2but the LCD is not interesting, because it's 8x50 only
16:53.27tmztwhat mddi chip does it use?
16:53.38tmztand what about nand?
16:53.52cr2Echo31: ok, you may do some PXA gpio tracing, but the CPLDx data is finished
16:54.08cr2tmzt: it's like pxafb. co$t saving ;)
16:54.35tmztbut we know msm has nothing like that
16:54.38cr2if you will adapt this code to 7201A....
16:54.51cr2tmzt: 8250 has it.
16:55.08Echo31cr2: ok and thanks
16:55.11tmztthe lcdc is internal?
16:55.27tmztwhy does it say mddi then?
16:55.31cr2yes
16:55.33tmztI'm confused
16:55.47cr2saves an extra mddi client chip
16:56.14cr2the lcd is hooked directly to msm
16:56.19tmztdo we know if vic is really related to video?
16:56.31cr2vic is interrupt controller
16:56.37tmztok
16:57.18cr2now i would like to know wtf BT hangs
16:57.36cr2is it some ADM misconfiguration ??
16:58.11cr2or do i need to dig deeper in the clock code.
16:58.26tmztoh, msm?
16:58.56cr2yes. tired of pxa for today :)
16:58.58tmztdoes it work at any baud rate?
16:59.15cr2i don't have brf datasheet ;)
16:59.37tmzthciattach should help there
16:59.47tmztI mean non dm modes
16:59.49cr2the 6150 had 115200 on reset
17:00.06cr2it's on the DM pins
17:00.26tmztbut g1 used it without dm
17:00.26cr2you can't use non-DM afaiU
17:00.42tmztmaybe something in pinmux?
17:00.42cr2uart1
17:01.15tmztwhy are their dm/non-dm uart pins?
17:01.25tmztthat makes no sense
17:01.38cr2because uart2DM is an addon
17:01.47cr2afaiU ;)
17:01.48tmztwhy wouldn't they use different numbers if they were hardware differences
17:02.12tmztyeah, but I would think it's like 16550, it adds dma
17:02.15cr2why pxa has SIR and FIR ?
17:02.21cr2uart2DM is like FIR on pxa
17:02.32tmztand queue management
17:02.37tmzt4mbps
17:02.44tmztbut same pins
17:02.49cr2and you can do SIR on normal uarts
17:02.56cr2the same story
17:03.16cr2FIR is on the same pins ?
17:03.29tmztthat's what I'm saying why would dm/non-dm be different pins for the same uart
17:03.35tmztI think so, stuart
17:03.54cr2no docs = no clue
17:04.10cr2it's all guesswork
17:04.18tmztI'm saying g1 used low speed until 1.5
17:04.23cr2the 7200 has uart CLK at +0xc0
17:04.28cr2and the 8250 too
17:04.29tmzton the same hardware
17:04.39cr2but when i used it on 7201A, it hanged.
17:04.58tmztwith dm?
17:05.00cr2painful disassembling showed that 7201A uart CLK is at +0xe ;)
17:05.22tmztodd
17:05.27cr2dm has its own clock
17:05.48tmztI would guess in dm mode dm clock takes over
17:05.49cr2spl and wince always setup DM
17:05.51*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
17:05.57tmztspl does?
17:05.58cr2even to read the btaddr
17:06.03cr2yes
17:06.05tmztthat could be the problem
17:06.11cr2but with a differet clock source
17:06.12tmztmaybe hboot doesn't
17:06.22cr2PLL1 vs. MODEM_AUX_something
17:06.45cr2i don't have a good understanding how the PLL1 and MODEM_AUX is setup
17:07.09cr2PLL1 may be understood (i think)
17:07.09tmztare they all the same formulas?
17:07.28cr2but MODEM_AUX is somewhere in the dark AMSS corner ;)
17:07.31tmztdo we know all the base osc's now?
17:07.49cr2TCX0 is 19.2MHz
17:08.10cr2btw, we have 66MHz for PCLK
17:08.10cr2but g1 dmesg says 64MHz
17:08.23tmztwhich pclk?
17:08.31cr2but it's just cosmetic change.
17:08.31cr2still may be important for understanding clocks
17:08.41tmztcan we find documentation on how axi works?
17:08.45cr2periferal clock
17:08.52tmztyeah, which one
17:08.52cr2i doubt it
17:09.05cr2i think there is only one
17:09.07tmztI don't think it's qualcomm stuff
17:09.22cr2no idea
17:09.33tmztsearch arm and axi
17:09.43cr2and ahb
17:09.53tmztahb?
17:11.24cr2yes
17:13.01tmztwhat is it?
17:15.45*** join/#htc-linux darkstar62 (n=darkstar@97-126-107-190.tukw.qwest.net)
17:18.53*** join/#htc-linux pH5 (n=ph5@e178226211.adsl.alicedsl.de)
17:22.34cr2hi pH5
17:23.02cr2tmzt: i don't know
17:23.06pH5hi
17:23.44cr2pH5: how to proceed with the athena ? i have sorted out all cpld bits today
17:24.13cr2pH5: there are several drivers (by Kevin2) that have nothing to do with athena, but athena needs them
17:24.23cr2can the be added to git first ?
17:24.54cr2then i'd like to verify the cpld1+cpld2 code.
17:26.18pH5cr2: if you could split that up and send patches to the mailing list, that would be a big help.
17:26.48pH5what drivers have nothing to do with athena but are needed by it??
17:27.14cr2htc-spi-kbd.c and ad7877.c
17:28.17cr2the last one was used on apache. it's TS and battery ADC
17:29.06pH5ok, I think I understand.
17:29.28pH5the ad7877 should be submitted to mainline right now, but of course I can take it into the local tree.
17:29.37tmztspi keyboard should be serio I think
17:30.11tmztif the infrastructure will support it
17:30.23pH5yeah, somebody should look at that.
17:32.47cr2i need to buy some food now. bbl
17:44.52Echo31Hi pH5. cr2 has done a good job on the CPLDs of athena.
17:45.42pH5Echo31: of course he has, what did you expect :)
17:48.38Echo31pH5: Now, how we proceed on the athena development ?
17:56.15*** join/#htc-linux skodde (n=skodde@unaffiliated/skodde)
18:08.06*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
18:12.25pH5Echo31: I'd like you or cr2 to split up the patches and send them to the mobile-linux mailing list so that I can easily take them or comment inline where needed.
18:15.17*** join/#htc-linux xsacha (n=sacha@203-214-116-29.dyn.iinet.net.au)
18:26.42Echo31pH5: Ok. But what are the parts concerned from the patch ? all the parts
18:28.05tmztcr2: San says all the answers are in the source
18:28.50cr2Echo31: don't submit the ad7877.c patch
18:29.14cr2Echo31: and start with making the diff for pxa-regs.h
18:29.25cr2tmzt: uart2DM ?
18:29.58tmztyeah, uartDM
18:30.11tmzthe said amss probably sets up dm also
18:30.22tmztI guess we don't need non-dm mode?
18:30.59cr2not used in wince, can't be tested.
18:32.38cr2tmzt: you have one point though.
18:32.59tmzt?
18:33.08tmztwhat's not used in ce?
18:33.37cr2the braindead g1 code puts all gpio alt settings into board file, instead of leaving it to the respective drivers.
18:33.48cr2uart2 is not used in wince.
18:34.11cr2i have added uart2DM alt gpios to rfkill.
18:34.13tmztalt settings are not something driver should care about
18:34.21cr2that may be not the brightest idea.
18:34.27tmztthe only affect the package, therefore board
18:34.51tmztwe should be using mfp
18:35.09cr2htc sets alt on _probe, and unsets on _remove
18:35.19cr2i think that it's the right way.
18:35.33tmztis alt used for pinmux?
18:35.55cr2how are you going to mux the uart1 (alt) and tvout ? by callbacks to board ?
18:36.15tmztthose are workarounds to the limitations of gpio api
18:36.35cr2ok, the bt alt can be hardcoded.
18:36.41tmztlove what pre does :)
18:37.07tmztomap3 has full pinmux so they just switch alt between usb and uart, no chip needed
18:37.38tmztyes, hardcode if required, but moving all alts to drivers would be a mistake
18:37.46tmztI think I misunderstood
18:38.00cr2ok
18:38.04tmztit needs a new gen api, an altfunction requester
18:38.28cr2so you think that alts belong to board init ?
18:38.32tmztso the pin numbers stay in pdata but drivers can change alt function
18:38.37tmztyes
18:38.50tmztdrivers should never be board specific
18:38.53cr2ok.
18:39.09cr2pdata
18:39.10tmztwith mfd cells they shouldn't even have hardcoded address offsets
18:39.37cr2ok, i get your point
18:39.55tmztok
18:40.00cr2but them google should not create board-trout-rfkill.c in the first place.
18:40.30cr2but use pdata for gpios,vregs and such.
18:41.52cr2abnd dex/proc_comm should be reduced to what it is: the msm pmic driver.
18:42.23tmztboard-trout-rfkill is part of the board-trout
18:42.41tmztI do think more stuff should be generic
18:42.53cr2there should be a brf63x0.c driver
18:43.12cr2which should accept gpios/vregs et al. as pdata
18:43.19tmztdon't agree with that, pmic is a chip, dex is a protocol
18:43.48cr2i could have accessed pmic directly.
18:43.51tmztbrf should be supported by hciuart
18:44.11cr2it's just qualcomm wants to hide the spi interface from mem
18:44.16cr2s/mem/me/
18:44.26tmztah
18:44.34tmztis it spi or sbi?
18:44.39cr2sbi
18:44.45tmztsbi sangerous
18:44.52tmztsbi is dangerous
18:45.05tmztmodem plls might be also
18:45.23cr2only because amss may access it in parallel
18:45.52tmztI would say because wrong address could cause interference with gsm
18:45.59Echo31cr2: pH5: want you to merge all from  pxa-regs.h  to pxa2xx-regs.h or only parts  required to compile?
18:46.02tmztwe need to stay away from that
18:46.26tmztEcho31: what needs added there?
18:46.39tmztpxa should apply to all pxa devices
18:46.49tmztwhat's missing?
18:47.01cr2tmzt: many register definitions
18:47.14tmztpm stuff?
18:47.30tmztWy: do you know of any plans in this area?
18:47.51cr2tmzt: i have not said that the concurrency with arm9 is a good thing, just that there is no technical reason for such decision.
18:48.26cr2if you want arm9 control shared hardware, the protocol should be open and documented.
18:48.26tmztI know
18:48.51tmztwe don't share hardware, we rely on amss to provide what we need
18:49.01cr2otherwise it goes completely against the gpl. spirit at least.
18:49.15cr2with undocumented unterface.
18:49.28cr2i can program for windows with the same logic.
18:49.33tmztI don't know what the real danger to gsm or cdma(w-cdma) protocols is, but we didn't write the stack
18:50.04cr2google created a mess by changing the interface.
18:50.21cr2imho, since they have broken it, they should have documented the changes.
18:50.26tmztyeah, some things didn't need it
18:50.29tmztlike gpios
18:50.44tmztnot agruing that
18:50.53tmztonly that we should stay away from sbi
18:51.15cr2ok, but again, they created a new interface, and did not document it too. just some magic numbers all over the code.
18:51.45tmztu-boot is better right?
18:51.45cr2i've learned much more from disaasembling wince code, than looking at their "free" software ;)
18:51.54tmztdid you see the ZZZZ comment?
18:52.13cr2yes
18:52.22tmztthey want to convert hsusb init back to proc comm
18:52.23cr2the g1 code does not use vbus DEX too
18:52.30cr2but wince does it :)
18:53.10cr2why should arm9 deal with usb ?
18:53.15cr2or with tvout ?
18:53.16xsacha-tvdisassembling windows battery driver right now :P pretty cool, it compensates for booting, wifi, gps by temporarily saying battery level is lower than what it is
18:53.40tmztah
18:53.47cr2let arm9 deal with gsm, and keep it away from everything else.
18:54.09cr2i wish we could strip down the amss
18:54.30cr2with all these dns lookups there and other weirdness.
18:54.40tmztI think pmic is used to change rf power
18:54.48tmztwhich cdma does very rapidly
18:55.02cr2i doubt it.
18:55.03tmztthat's qualcomm gps
18:55.18cr2there is a 7200A diagram
18:55.34tmzthey, I found that rmnet uses DATA5 and 6 on g1
18:56.00cr2gps is a just a preamplifier. all tracking is done by some DSP. do you think it#s the same mDSP as gsm ?
18:56.15tmztnot sure
18:56.23tmztI meant the dns stuff
18:56.31tmztwhat did you mean by that?
18:57.23cr2the xtra urls are hardcoded in amss
18:57.36tmztyeah
18:57.50cr2which is a userspace issue
18:57.58cr2and not the umts firmware
18:58.05tmztmakes me even more convinced there's an ip stack and ppp is somekind of proxy
18:58.22cr2in amss ? sure.
18:58.26tmztbut amms is userspace
18:58.38tmztit has oem and apps parts
18:58.40cr2amss is modem firmware
18:58.51cr2no
18:58.55tmzton this phone it is
18:59.10tmztlook at the gobi firmware, two .mdn files
18:59.12cr2apps is spl+wince
18:59.17tmztdream_kill: you here?
18:59.52tmztok, but the same amss os is used as the primary os on other devices
19:00.13cr2tmzt: apropos pxa-regs.h i've added a bunch of data into this file in hh.org CVS
19:00.37cr2ok, i get your point
19:00.44tmztdifferent drivers and different userspace applications (brew, java, broweser)
19:01.32tmztI mean for pxa we don't change upstream stuff
19:01.44cr2we should
19:01.55tmztif new regs are needed they should be handled as patches to pxa
19:02.04cr2the mainline is simply incomplete.
19:02.08tmztand they should be in the right file for the soc
19:02.10cr2yes
19:02.19tmztyeah, pm is missing for insance
19:02.27tmztWyrM is working on that
19:02.48cr2some usb regs are missing
19:02.54tmztI was concerned at the pxa2xx into pxa2xx
19:02.55tmztyes
19:03.11tmztthey go in pxa2xx-udc or ohci though
19:03.27cr2#defines ?
19:03.34tmztpxa2xx into pxa
19:03.35tmztyes
19:03.55tmztthey've been moved out of -regs
19:03.56cr2port2 is mixed
19:04.02tmztyes
19:04.12tmztapt: up2ocr?
19:04.13aptwell, up2ocr is 0x40600020, or the USB Port 2 Output Control Register, or used for udc
19:04.32cr2how to deal with that ?
19:04.40tmztit's been done
19:04.51tmztthe only missing is the up3ocr bit masks
19:05.11cr2nobody uses that
19:05.14cr2:)
19:05.14tmztinclude a different mach header
19:05.32tmztphones with msm on host do
19:05.36xsacha-tvi noticed a newer pxa2xx-udc has new usb defines
19:05.44tmztyes
19:05.51xsacha-tvUHCRH or something.. and all the boards use that now
19:06.00cr2ok
19:06.07xsacha-tvhosr reset
19:06.13xsacha-tvhost*
19:06.35xsacha-tvand i dumped my value from winmo
19:07.58tmztyes, but it seems ulpi is used instead
19:08.15tmztit's kept in reset?
19:08.34tmztlike I said, give up on usb for now
19:08.42tmztwifi will actually be easier
19:20.09xsacha-tvk
19:20.27xsacha-tvive given up on wifi cause of regression
19:21.01tmzt?
19:21.13tmztget a newer kernel
19:21.20tmztport the Ndroid patches
19:21.35tmztor use wireless-compat
19:21.52xsacha-tvtrying battery driver now. i know the charge gpio is 88, looking at the winmo driver. i cant see manufacturer in strings, only thing it says is MITsBattery
19:21.57xsacha-tvwireless-compat?
19:22.47tmzta tree with ieee80211/mac80211 backported to various kernels
19:22.57tmztporting android should be easier
19:22.58*** join/#htc-linux JuNu_KN (n=chatzill@95.113.17.247)
19:23.12tmztgetting linux working first is even better
19:23.45xsacha-tvk
19:24.10xsacha-tvby the way i see xllpi2c mentioned, does that mean i need i2c to communicate to the battery?
19:24.22tmztprobably
19:24.27tmztxllp
19:24.29tmzt?
19:24.38xsacha-tvcross platform low level library.. winmo thing
19:24.41tmztnot to battery
19:24.59tmztthat's probably w1
19:25.10tmztbut maybe to pmic
19:25.57xsacha-tvZylonite_battd, MITs_battery
19:26.10xsacha-tvMITs isnt a manufacturer is it?
19:27.29xsacha-tvhas BatteryXllpi2c... Xllpi2cRead, Xllpi2cWrite
19:28.23tmztno idea
19:28.52xsacha-tvBatteryXllpgpio, BatteryXllpmfp, sets level using gpio
19:31.05Echo31cr2: pH5: The missing parts from pxa2xx-regs.h  concerns usb host ohci (about added 20 lines)
19:31.38cr2Echo31: tmzt says you should #include uhh*something :)
19:32.37Echo31cr2: i have to create a dedicated header
19:33.18cr2tmzt: ?
19:34.09tmzt?
19:34.31tmztmach/ something
19:34.40tmztpxa2xx-udc I think
19:34.46tmztdon't have my tree here
19:35.08tmztarch/arm/mach-pxa/include/mach
19:35.20Echo31tmzt:  or regs-udc.h
19:35.26tmztjust include udc and ohci and you should have the regs
19:35.28tmztyes
19:38.58Echo31tmzt: the  DMA Controller regs  may be also used by the sound driver.
19:47.12tmztthere should be generic dma api support
19:47.34tmztbut yes, they belong somewhere
19:49.16Echo31tmzt: for this first step, i create regs-ohci.h
19:50.15Echo31tmzt: the pxa2xx-udc.h file  is already in the arch/arm/mach-pxa/include/mach
19:50.47tmztyes
19:51.44cr2Echo31: the sound is not really important right now :)
19:52.14Echo31cr2: ok
19:52.14cr2Echo31: and pxa-i2s is not used on athena
19:52.37cr2so this part is unneeded
19:55.12*** join/#htc-linux stickboy (n=anonymou@ool-457e4101.dyn.optonline.net)
20:04.01dcordescr2: where does the chat script live? how to add the password?
20:06.50cr2dcordes: it's referenced in /etc/ppp/peers/*
20:07.23cr2dcordes: i don't use it to add the passowrd., because otherwise the passowrd should be in this script
20:07.49cr2dcordes: we also need the locale keyboard map
20:08.24cr2does your loadkeys use the same syntax as a "usual" keyboard map ?
20:08.43tmztbusybox doesn't
20:08.48cr2i'm thinking about something like raph100-de.map
20:08.54tmztit should load binary ones
20:09.13tmztmicrop-ksc doesn't need kernel keymap really
20:09.25tmztbut I think maejrep used one
20:09.32tmztit returns scancodes
20:09.44cr2tmzt: yes, i rememebr it. does busybox use loadkeys ??
20:09.54tmztyes
20:09.58cr2tmzt: how should i do alt+key ?
20:10.02tmztbut not the full syntax
20:10.09tmztI use RIGHTALT
20:10.13tmztas AltGr
20:10.24tmztbut de needs it for something else right?
20:10.52cr2tmzt: i think loadkeys is done differently on busybox
20:10.59tmztdo you have sym?
20:11.06cr2tmzt: yes, it's a different keyboard layout.
20:11.12tmztyeah, it's binary I think
20:11.18cr2tmzt: i mapped Fn to ALT
20:11.35cr2and SYN to AltGr
20:11.36tmztas alt or for altgr?
20:11.40tmztok
20:11.52tmztso Fn is LEFTALT?
20:12.10tmztyoou need something else for symbols then
20:12.12cr2tmzt: i'm not sure if dcordes has added the "real" loadkyes
20:12.21cr2Fn is LEFTALT
20:12.28tmztif AltGr is for accents
20:12.37cr2for which symbols ?
20:13.04cr2tmzt: i want to replace Fn-$FOO by Alt-$FOO
20:13.24cr2there are a lot of  things done by Fn-$FOO
20:17.00*** join/#htc-linux IamSOG (n=IamSOG@218.20.195.220) [NETSPLIT VICTIM]
20:17.00*** join/#htc-linux sxe (n=sxe@ip-62-143-86-48.unitymediagroup.de) [NETSPLIT VICTIM]
20:17.00*** join/#htc-linux toer (i=tore@179.81-166-86.customer.lyse.net)
20:17.00*** join/#htc-linux rzk_ (n=rzk@daemonet.ru) [NETSPLIT VICTIM]
20:17.00*** join/#htc-linux hachiya (n=flash@mail.filmpr.com) [NETSPLIT VICTIM]
20:17.00*** join/#htc-linux thinko (n=jdoe6alp@smaug.rackdragon.com) [NETSPLIT VICTIM]
20:17.18Echo31cr2: Do you want that i removes parts on w228 or I put its commented
20:19.19cr2Echo31: remove completely
20:20.11Echo31cr2: ok
20:22.36*** join/#htc-linux sxe_ (n=sxe@ip-62-143-86-48.unitymediagroup.de)
20:22.36*** join/#htc-linux IamSOG (n=IamSOG@218.20.195.220) [NETSPLIT VICTIM]
20:22.36*** join/#htc-linux sxe (n=sxe@ip-62-143-86-48.unitymediagroup.de) [NETSPLIT VICTIM]
20:22.37*** join/#htc-linux toer (i=tore@179.81-166-86.customer.lyse.net)
20:22.37*** join/#htc-linux rzk_ (n=rzk@daemonet.ru) [NETSPLIT VICTIM]
20:22.37*** join/#htc-linux hachiya (n=flash@mail.filmpr.com) [NETSPLIT VICTIM]
20:22.37*** join/#htc-linux thinko (n=jdoe6alp@smaug.rackdragon.com) [NETSPLIT VICTIM]
20:32.12dcordescr2: I can add all of these things in openembedded
20:32.39*** join/#htc-linux wirelessdreamer (n=dreamer@chrobd01.vailsys.com)
20:34.00cr2dcordes: are you using loadkyes from busybox ?
20:35.06cr2tmzt:
20:35.10cr2<PROTECTED>
20:35.12cr2<PROTECTED>
20:35.13cr2<PROTECTED>
20:35.52dcordescr2: the /usr/bin/loadkeys in my image is no symlink to busybox
20:37.23cr2can you find out how it is compiled ?
20:37.52dcordesI'm on it
20:38.40dcordesit must be part of something, no seperate package
20:39.01dcordesmickey|bbl: here?
20:40.27tmztyay
20:40.46tmztkbd was console-tools I tink
20:41.06tmztnow it's kbd
20:42.28dcordesI have the rm work. that's why I find nothing
20:44.10tmztwhat do you eed from mickeyl?
20:44.39dcordesask him about teh loadkey
20:48.24Echo31cr2: I think  keept the usb host in htcathena.c. I keep the 'htcathena_vsfb_device' as module or I include  it in the htcathena.c?
20:48.58tmztvsfb should be generic now??????????????
20:49.02cr2remove htcathena_vsfb_device completely
20:49.03tmztsorry
20:49.34cr2tmzt: is the vsfb.c included in mainline ?
20:49.47tmztdid you see the ATAG VIDEOLFB in uboot?
20:49.53tmztnot sure
20:50.15tmztso many implementations
20:50.49cr2it will take some time to write down all the scary ati clock PLL stuff ;)
20:51.01tmztmsm?
20:51.15cr2atiw2284
20:51.26tmztok
20:53.59cr2the http://wiki.xda-developers.com/index.php?pagename=RaphaelLinux looks completely outdated
20:55.49cr2tmzt: i'll look how g1 configures alt bt
20:57.27*** join/#htc-linux dcordes_ (n=dcordes@unaffiliated/dcordes)
20:59.32cr2dcordes_: think about ts_*, bluez-utils and i2c-*
21:01.51*** join/#htc-linux cr2 (n=cr2@ip-90-187-125-182.web.vodafone.de)
21:09.42*** join/#htc-linux stickboy (n=anonymou@ool-457e4101.dyn.optonline.net)
21:12.14*** join/#htc-linux kri5 (n=kri5@cowdy.vlmc.org) [NETSPLIT VICTIM]
21:23.00*** join/#htc-linux kri5 (n=kri5@cowdy.vlmc.org) [NETSPLIT VICTIM]
21:23.37*** part/#htc-linux pe7er (n=Adium@f053195136.adsl.alicedsl.de)
21:31.24*** join/#htc-linux BHSPitLappy (n=BHSPitLa@unaffiliated/bhspitmonkey)
21:44.29*** join/#htc-linux Squarc (n=Squarc@82-217-32-29.cable.quicknet.nl)
21:45.25*** join/#htc-linux Shinto (n=John@f048103053.adsl.alicedsl.de)
21:50.41dcordes_cr2: ok didn't have bt in
22:00.24Echo31cr2: The size of my new patch is 40 ko
22:08.52cr2Echo31: pastebin
22:10.51Echo31cr2: find the patch http://fr.pastebin.ca/1476854
22:12.35cr2Echo31: please rename these GPIO22_HTCATHENA_DPR_RESET1,
22:12.43cr2i have added new names into wiki
22:13.40cr2SSP2 is keyboard, and SSP1 is battery_mobitor+touchscreen
22:14.08cr2GPIO51_HTCATHENA_DPR_AT
22:14.15cr2these are irqs
22:14.30cr2<PROTECTED>
22:14.47cr2+       /* I2C */
22:14.48cr2+       GPIO117_I2C_SCL,
22:14.50cr2+       GPIO118_I2C_SDA,
22:14.55cr2these are entered twice
22:17.37Echo31cr2:   GPIO22_HTCATHENA_DPR_RESET1 -> DPR-P9
22:18.26cr2there is DPR-XX IRQ and DPR-XX FE
22:19.04cr2IRQ is set by MSM6275 that the data is available in the RX fifo for read
22:21.17cr2the FE notifies MSM6275 that the data can be read from the TX fifo
22:21.20cr2tmzt: is it done differentlly now ?
22:21.20cr2+       /* setup Port1 GPIO pin. */
22:21.21cr2+       pxa_gpio_mode( 88 | GPIO_ALT_FN_1_IN); /* USBHPWR1 */
22:21.21cr2+       pxa_gpio_mode( 89 | GPIO_ALT_FN_2_OUT);        /* USBHPEN1 */
22:22.14cr2Echo31: you do not initialize cpld1 and 2 ?
22:22.19cr2+//     &egpio_cpld1,
22:22.20cr2+//     &egpio_cpld2,
22:23.00cr2Echo31: this is junk
22:23.00Echo31cr2: The cpld2 initialization is failed
22:23.03cr2+extern void      htcathena_cpld2_set( u_int16_t bits );
22:23.05cr2+extern void      htcathena_cpld2_clr( u_int16_t bits );
22:23.07cr2+extern u_int16_t htcathena_cpld2_get(void);
22:23.24tmztcr2: what?
22:23.28cr2Echo31: there are some changes needed for cpld init
22:23.44cr2tmzt: how it should be done with mfp &
22:23.54cr2[00:20] <cr2> +       pxa_gpio_mode( 88 | GPIO_ALT_FN_1_IN); /* USBHPWR1 */
22:23.55cr2[00:20] <cr2> +       pxa_gpio_mode( 89 | GPIO_ALT_FN_2_OUT);        /* USBHPEN1 */
22:24.00tmztlook at magician or ezx
22:25.55cr2Echo31: cpld irq names are strange
22:26.09Echo31cr2: i tried to set the cpld2 init, the boot don't start
22:28.26Echo31cr2: for cpld, i prefer that you lead
22:28.30cr2Echo31: look much better now. but the cpld part needs some major changes. i don't have the brainpower to do it now :)
22:28.38cr2ok
22:29.38cr2i need to check what pH5 has written for magician and hx4700
22:29.58Echo31cr2: for the first step ,can you
22:30.27Echo31cr2: for the first step, can i implement only cpld2
22:30.50cr2Echo31: cpld2 can be more or less cut'n'pasted from hx4700
22:31.08tmztlooks ok
22:31.13tmztthat is mfp
22:31.31tmztonly the ohci-init isn't and that works for tes5ting
22:31.59tmztnot sure if the defines changed
22:32.00Echo31where can i find ?
22:32.52Echo31where can i find the git of hx4700?
22:33.03cr2pH5/dev
22:33.21cr2bracnh
22:36.51cr2Echo31: i'll check cpld tomorrow
22:39.43cr2Echo31: you may check how to apply power to the pxa uart (also in the hx4700.c). then we will have bt and gps :)
22:41.12Echo31cr2: ok. I implement the cpld2. thanks, bye
22:41.59cr2tmzt: back to the evil 7201A sound.
22:42.57tmzthey
22:43.24cr2i'll look at the kaiser
22:53.01cr20,0,0; 1,1,1; and 2,1,1
22:53.07cr2didn't see the last one.
22:53.28cr21,1,1 should be ok.
22:56.55tmztmodem rest?
22:56.56cr2tmzt: snd_ioctl which /dev/ file is that ?
22:57.18tmztmsm-snd-control I think
22:59.01cr2why is it not used by playwav ?
23:00.01tmztplaywave is only used to play boot sound
23:00.28tmztI guess they assume the radio is in the correct state for that
23:01.08cr2hmm
23:07.44cr2msm_snd misc dev ?
23:08.21cr2is it in /sys ?
23:08.29tmztno
23:08.34tmzt'/dev
23:08.40tmztwait
23:08.41cr2do you have it ?
23:08.43tmztno idea
23:10.43*** join/#htc-linux skodde (n=skodde@unaffiliated/skodde)
23:11.53cr2117 #define RPC_ADSP_RTOS_APP_TO_MODEM_PROC 2
23:12.04cr2should be 1. did i miss it ?
23:12.17tmztoh
23:15.41cr2tmzt: how to enable pr_info() ?
23:16.30tmztdmesg -n 15 maybe
23:16.51tmztI just learned there's a sysfs entry for that as well
23:18.01cr2msm_snd should be in /dev
23:19.22tmztyes
23:23.39cr2ok. good night
23:50.43*** join/#htc-linux Guest92385 (n=fnord@24-151-90-116.static.nwtn.ct.charter.com)

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