00:00.21 | tmzt | on diam? |
00:00.24 | IceBone | Si. |
00:00.25 | tmzt | which mtype are you using? |
00:01.23 | IceBone | 1805 |
00:01.37 | tmzt | which is for? |
00:02.13 | IceBone | I 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.31 | tmzt | you need to look at the default.txt |
00:02.36 | tmzt | you need to use mtype for raph100 |
00:02.42 | IceBone | I see. |
00:02.44 | tmzt | no |
00:02.45 | tmzt | diam100 |
00:02.52 | IceBone | the first line says set mtype 1805 |
00:03.18 | tmzt | htcdiamond MACH_HTCDIAMOND HTCDIAMOND 1805 |
00:04.07 | IceBone | I paste that in instead of just 1805? |
00:04.13 | tmzt | no |
00:04.26 | tmzt | set MTYPE 1805 |
00:04.39 | IceBone | I should say I'm no programmer. Most of the time I just wing it and hope for the best. |
00:04.42 | IceBone | That's what it says. |
00:05.20 | IceBone | All of them do. |
00:05.36 | tmzt | this isn't programming, it's a config file |
00:05.42 | tmzt | just open it in a text editor |
00:05.51 | IceBone | Dude... I told you I did. That's what it says. |
00:06.00 | IceBone | I downloaded several builds, tried them all. |
00:06.06 | IceBone | All default.txt files have 1805 |
00:06.26 | tmzt | I 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.56 | IceBone | Moment. |
00:07.30 | IceBone | I'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.57 | IceBone | Which 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.04 | IceBone | Which has set mtype 1805. |
00:08.24 | IceBone | I also tried this one: |
00:08.25 | IceBone | http://connect-utb.com/index.php?option=com_rokdownloads&view=file&Itemid=68&id=20:android-for-htc-touch-diamond-diam500 |
00:08.37 | IceBone | Saw it had more stuff, but the touchscreen was flipped. |
00:08.52 | IceBone | So I replaced the default.txt in that diam500 build with the diamond one from the previous build. |
00:09.04 | IceBone | It fixed the touchscreen, but everything else remained. |
00:09.26 | IceBone | Still no access to internal storage and font size didn't save in spare parts. |
00:09.52 | dcordes | gniite |
00:09.58 | IceBone | The old version didn't have those two issues. |
00:11.04 | IceBone | gnight, dcordes |
00:14.15 | IceBone | I'm not much help, am I? |
00:18.08 | *** join/#htc-linux skodde (n=skodde@unaffiliated/skodde) |
00:19.14 | tmzt | sorry, had to go |
00:20.05 | tmzt | all the builds should have kernel support for all four devices |
00:20.20 | tmzt | mtype is what tells kernel which support to use |
00:21.45 | IceBone | I see that raph is 1910, raph800 is 2039. The one I'm using is definitely 1805. |
00:22.09 | tmzt | ok |
00:22.25 | tmzt | please paste current mtype and cmdline lines |
00:22.35 | IceBone | set mtype 1805 |
00:22.42 | IceBone | set 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.59 | tmzt | is that calib for diam100? |
00:25.03 | tmzt | ok |
00:25.07 | tmzt | looks good |
00:25.14 | tmzt | remove msm sdcc |
00:25.22 | tmzt | msmsdcc id |
00:25.35 | IceBone | Remove completely or replace? |
00:26.06 | tmzt | remove |
00:26.09 | IceBone | Righto. |
00:26.12 | tmzt | not used any more |
00:27.13 | tmzt | I don't think root=/dev/ram0 is need either but it seems to be okay |
00:27.24 | IceBone | Should 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.59 | tmzt | reset is good |
00:28.10 | tmzt | I don't think it's really necessary |
00:28.21 | tmzt | it won't hurt though |
00:28.35 | IceBone | Takes 2 minutes 10 seconds to boot up wm and tf3d2... :( |
00:29.15 | tmzt | either way |
00:29.17 | IceBone | Android on the other hand takes only 40 seconds. |
00:29.20 | IceBone | "is nice" |
00:29.47 | IceBone | Do you guys have any info on HTC Sense? |
00:30.22 | tmzt | not more than what is known |
00:30.38 | tmzt | supposedly "hero" rom has some of that |
00:30.41 | IceBone | It looks very nice. |
00:30.45 | IceBone | Yeah. |
00:31.07 | IceBone | Too bad android isn't optimised for VGA. :( |
00:31.11 | IceBone | Looks so tiny on the Diamond. |
00:31.28 | tmzt | you could use it in hvga I think |
00:31.34 | tmzt | maybe |
00:31.47 | IceBone | But that would negate having a VGA screen. :P |
00:32.30 | IceBone | I'm running the sdk emulator in vga mode right now. It's insane how much bigger it is. |
00:32.51 | IceBone | Booting android. |
00:33.20 | IceBone | And it stopped on framebuffer console |
00:33.27 | tmzt | try again |
00:33.33 | tmzt | it does that randomly |
00:33.38 | IceBone | Yes, I've noticed. |
00:33.45 | IceBone | Any simpler way than red button reset? |
00:33.49 | tmzt | no |
00:33.55 | IceBone | Roger. |
00:34.35 | IceBone | How far along has this come, in your opinion? |
00:35.02 | IceBone | From start of development to stable build with all features working (or at least functioning basic phone stuff) |
00:36.04 | tmzt | mostly paying attention to kernel |
00:36.39 | tmzt | those builds aren't directly our goal in this channel |
00:36.57 | IceBone | But quite a ways off still, huh? |
00:37.11 | tmzt | we are far more interested in having a stable base for linux, including android to run |
00:37.40 | tmzt | we are working on sound today |
00:37.43 | IceBone | The most I've dabbled in linux was installing Debian sarge on my laptop. |
00:38.08 | IceBone | I still get the "Removed SD Card" notification. |
00:38.24 | tmzt | that's a userspace issue |
00:38.31 | tmzt | seems hard to solve |
00:39.04 | IceBone | Well, it worked on the old version. You must have made major changes since. |
00:39.59 | tmzt | us? |
00:40.05 | tmzt | no, 1.5 is different |
00:40.10 | IceBone | Ah, I see. |
00:40.27 | tmzt | talk to San in #android |
00:40.35 | IceBone | I'm not pointing fingers here, I'm just investigating. :) |
00:40.42 | tmzt | that's what I meant by userspace, not kernel |
00:41.18 | IceBone | Should I go ask there? |
00:42.06 | tmzt | not really |
00:42.18 | tmzt | they don't support diam |
00:42.20 | IceBone | Oh, 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.22 | IceBone | Ah. |
00:42.26 | *** join/#htc-linux maejrep (n=madcoder@c-71-225-60-178.hsd1.pa.comcast.net) |
00:42.43 | tmzt | the problem is you have a loop fs on the sdcard and are also trying to mount it |
00:42.57 | tmzt | maejrep: !!! |
00:43.15 | tmzt | busy on yb stuff? |
00:43.17 | tmzt | myb |
00:44.08 | IceBone | I 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.42 | tmzt | basically |
00:46.49 | IceBone | Well, 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.41 | tmzt | get hero orking? |
00:47.49 | tmzt | seems some people would like that |
00:47.58 | IceBone | :D |
00:48.04 | IceBone | I bet they would. |
00:48.09 | tmzt | it won't be usable without 3d |
00:48.16 | tmzt | so we need that first |
00:53.14 | cr2_ | good night |
00:53.30 | IceBone | Well, good luck with that, I'm a right-brain person, no programming out of me. |
00:58.50 | IceBone | Thanks 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.54 | tmzt | https://www.codeaurora.org/patches/quic/le/PATCH_u-boot-2009.03_1144_LCD_support_20090608.tar.gz |
02:29.03 | tmzt | https://www.codeaurora.org/patches/quic/le/PATCH_u-boot-2009.03_1147_nand_support_20090601.tar.gz |
02:29.09 | tmzt | https://www.codeaurora.org/patches/quic/le/u-boot-2009.03_PATCH_2009_05_14.patch |
02:29.14 | tmzt | NAND and LCD now |
02:32.32 | tmzt | + // Initialize the PHY |
02:32.32 | tmzt | + // ZZZZ replace this with an smem_proc_comm call??? |
02:32.33 | tmzt | + usbhs_ulpi_phy_init(); |
02:32.36 | tmzt | please don't |
02:33.41 | tmzt | + if (apps_part_start_blk == 0) |
02:33.41 | tmzt | + { |
02:33.41 | tmzt | + printf("NAND: starting block of APPS partition is unknown\n"); |
02:33.41 | tmzt | + return 0; |
02:33.41 | tmzt | + } |
02:33.43 | tmzt | + |
02:33.46 | tmzt | + /* |
02:33.49 | tmzt | + * Can't assume the user knows which block the APPS partition starts in. |
02:33.51 | tmzt | + * To boot from NAND, user should run "nboot <addr> 0 0". (offset = 0) |
02:33.54 | tmzt | + * This function will add the APPS partition offset automatically. |
02:33.56 | tmzt | + */ |
02:33.59 | tmzt | + |
02:35.50 | tmzt | +/* |
02:35.50 | tmzt | + * adm.h - Application Data Mover (ADM) definitions |
02:35.50 | tmzt | + * |
02:46.16 | tmzt | . |
02:46.17 | tmzt | +#ifdef D800_480 |
02:46.18 | tmzt | + #define DISP_W 800 |
02:46.19 | tmzt | + #define HBP 216 |
02:46.19 | tmzt | + #define HFP 40 |
02:46.21 | tmzt | + #define DISP_H 600 |
02:46.23 | tmzt | + #define VBP 27 |
02:46.26 | tmzt | + #define VFP 1 |
02:46.29 | tmzt | + #define LCD_MD_VAL_40MHZ 0x0005FFCF |
02:46.31 | tmzt | + #define LCD_NS_VAL_40MHZ 0xFFD41B49 |
02:46.34 | tmzt | +#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.15 | xsacha-tv | how do i set where my devices go in kernel? eg. /sys/class/timed_output/ ? |
07:30.51 | maejrep | xsacha-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.58 | maejrep | *class device |
07:31.24 | xsacha-tv | yeah it's a class, but how do i get it to go in to timed_output? |
07:32.24 | xsacha-tv | cause android only looks in timed_output/ |
07:32.35 | xsacha-tv | THE_DEVICE "/sys/class/timed_output/vibrator/enable" |
07:49.06 | xsacha-tv | maejrep, 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.08 | dcordes | eelo |
09:02.59 | xsacha-tv | hi |
09:03.20 | xsacha-tv | dcordes: what do i change in how i register the device? :\ |
09:05.05 | dcordes | I have no idea |
09:05.23 | dcordes | can'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.44 | xsacha-tv | yeah i could |
09:10.56 | xsacha-tv | but i sort of wanted it to work in future builds without customising each one |
09:11.14 | xsacha-tv | hang 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.49 | dcordes | JuNu_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.20 | dcordes | xsacha-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.05 | dcordes | xsacha-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.38 | xsacha-tv | up2ocr |
10:58.46 | xsacha-tv | apt, up2ocr |
10:58.46 | apt | extra, 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.27 | cr2 | +#define BATTERY_MIMIC_LEGACY_VBATT_READ_PROC 11 |
11:25.42 | Echo31 | hi cr2 |
11:28.02 | cr2 | hi Echo31 |
11:28.22 | Echo31 | cr2: When you plan to update the athena pages of http://wiki.xda-developers.com for gpio,cpld2 and cpld1 ? |
11:30.05 | cr2 | Echo31: i'll use htc-linux.org wiki |
11:30.29 | cr2 | Echo31: btw, we have 8 led gpios |
11:30.39 | cr2 | how many leds are there ? |
11:30.52 | *** join/#htc-linux Zoolooc_ (n=fredsiba@nrbg-4dbfcaa2.pool.einsundeins.de) |
11:31.39 | Echo31 | cr2: My device is HTC advantage x7500 |
11:34.55 | cr2 | mine is t-mob ameo, but i think they are more or less identical |
11:35.44 | Echo31 | cr2: I think have 3 leds (gsm, bt/wifi,alert) + 3 leds of nav button (red, green, orange) |
11:37.25 | cr2 | orange may be red+green |
11:37.49 | cr2 | what about baclklight leds for the buttons ? |
11:38.28 | cr2 | also, the bt/wifi led can be blue/green ? |
11:42.37 | Echo31 | cr2: i insert a sim card for looking the leds colour |
11:45.00 | cr2 | ok |
11:55.13 | Echo31 | cr2: 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.58 | Echo31 | cr2: if orange is different green+red, i have 8 leds |
11:57.15 | cr2 | ok, that sounds good |
11:59.26 | cr2 | Echo31: can you dump the cpld registers ? |
12:01.13 | *** join/#htc-linux Zoolooc__ (n=fredsiba@nrbg-4dbfce9b.pool.einsundeins.de) |
12:01.26 | cr2 | Echo31: do you have the "OK" and windows button under the navigation button ? |
12:01.48 | Echo31 | cr2: yes |
12:01.58 | cr2 | they also have a backlight, but it seems to me that the lcd backlight is used for them |
12:02.47 | Echo31 | cr2: I can dump, but i don't know correctly the commands of haret |
12:03.25 | Echo31 | cr2: i launch telnet |
12:03.33 | cr2 | where is your cpld1 ? |
12:04.50 | cr2 | Echo31: which address has the rndis usb ? |
12:08.26 | Echo31 | cr2: 192.168.131.129 IP of my device |
12:09.34 | *** join/#htc-linux JuNu_KN (n=chatzill@95.113.18.25) |
12:09.36 | cr2 | bash: telnet: command not found |
12:09.39 | cr2 | eh? |
12:13.11 | *** join/#htc-linux JuNu_KN_ (n=chatzill@95.113.18.25) |
12:15.46 | Echo31 | cr2: 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.42 | Echo31 | cr2: 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.25 | cr2 | Echo31: the athena address is 169.254.2.1 |
12:27.46 | Echo31 | cr2: i am connected to device with telnet. |
12:28.12 | cr2 | oer usb or wifi ? |
12:28.26 | Echo31 | cr2: via usb |
12:29.25 | cr2 | ok |
12:29.28 | cr2 | http://www.htc-linux.org/wiki/index.php?title=MemoryMap |
12:29.34 | cr2 | the page looks a bit broken |
12:30.08 | cr2 | 0x08000000 CPLD1 |
12:30.24 | Echo31 | cr2: yes, and the cpld2 starts 0x09000000 on two 2 octets (16 bits) |
12:32.04 | cr2 | HaRET(1)# pd 0x08000000 0x100 |
12:32.05 | cr2 | 08000000 | 00000004 00500013 00fe0000 000a0021 | ......P.....!... |
12:32.07 | cr2 | 08000010 | 00000000 00000000 00000000 00000000 | ................ |
12:32.15 | cr2 | does not look very promising |
12:32.56 | cr2 | hm. |
12:33.19 | cr2 | let's check |
12:33.32 | cr2 | the shadow copy |
12:34.27 | Echo31 | cr2: I have the same values |
12:35.53 | cr2 | the "orange" charging led is on |
12:36.55 | Echo31 | cr2: Yes |
12:40.36 | *** join/#htc-linux wirelessdreamer (n=dreamer@chrobd01.vailsys.com) |
12:43.04 | Echo31 | cr2: 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.36 | cr2 | enable bt |
12:46.41 | cr2 | HaRET(5)# pd 0x08000000 0x20 |
12:46.42 | cr2 | 08000000 | 00400034 00d00013 00ff0000 000a0021 | 4.@.........!... |
12:46.48 | cr2 | was |
12:46.56 | cr2 | 08000000 | 00000004 00500013 00fe0000 000a0021 | ......P.....!... |
12:47.58 | cr2 | +wifi |
12:48.02 | cr2 | 08000000 | 00c00034 00d0005b 00ff0000 000a0021 | 4...[.......!... |
12:49.01 | Echo31 | cr2: i have same data |
12:49.18 | Echo31 | cr2: ok |
12:49.34 | cr2 | GPIOB3 0x0008 led related <- wifi ?? |
12:50.21 | cr2 | since they use shadow, i'm a bit worried |
12:51.10 | xsacha-tv | how come the address is so nice? 0x08000000? |
12:52.42 | cr2 | HaRET(13)# nledon 0 |
12:52.44 | cr2 | HaRET(14)# pd 0x08000000 0x10 |
12:52.45 | cr2 | 08000000 | 00e00034 00d0005b 00ff0000 000a0021 | 4...[.......!... |
12:53.18 | cr2 | e=8+4+2 ? |
12:54.00 | cr2 | ah. |
12:54.07 | cr2 | e0=80+40+20 |
12:54.36 | Echo31 | cr2: nledon 0 is not reconnized by my haret |
12:54.46 | cr2 | GPIOB5 0x0020 led related |
12:54.47 | cr2 | GPIOB6 0x0040 led related |
12:54.49 | cr2 | GPIOB7 0x0080 led related |
12:54.58 | cr2 | Echo31: i use an ancient haret |
12:55.07 | Echo31 | cr2: ok |
12:55.08 | cr2 | Echo31: nled ? |
12:55.23 | Echo31 | cr2: thanks |
12:55.37 | cr2 | Echo31: it was installed there on 12.10.2007 according to wince :) |
12:56.12 | cr2 | so 20 is nled (alert) |
12:56.31 | cr2 | 40 is bt blue blink |
12:56.42 | xsacha-tv | for my device, NLED 0-9 only work when im not charging and NLED 11-20 only work when i am charging |
12:56.49 | cr2 | and 80 is wifi green blink |
12:56.53 | dcordes | cr2: build done |
12:56.56 | xsacha-tv | actually 3 and 6 work when im charging too |
12:57.16 | cr2 | xsacha-tv: it's all very device-dependent |
12:57.24 | cr2 | dcordes: initrd ? |
12:57.26 | dcordes | it has the ppp uucp cu wireless-tools ssh etc etc. can you give me the config file? |
12:57.29 | dcordes | yea |
12:57.39 | xsacha-tv | do i have to write an LED driver from scratch? |
12:57.43 | cr2 | dcordes: which config ? |
12:57.58 | xsacha-tv | cause my LED uses one GPIO for blue, red, green, orange |
12:58.06 | cr2 | xsacha-tv: led-gpio is a very standard driver |
12:58.07 | dcordes | oh and it also has tslib. the one for vodafone pppd |
12:58.18 | cr2 | dcordes: hmm. |
12:58.18 | xsacha-tv | but all 4 colours use the same gpio? |
12:58.48 | cr2 | dcordes: i can copy from nc10 |
12:59.01 | cr2 | dcordes: some minor changes are needed |
12:59.03 | dcordes | that would be good. so we have the known working config |
12:59.09 | cr2 | yes |
12:59.16 | cr2 | xsacha-tv: no, these are different leds |
12:59.38 | cr2 | xsacha-tv: only the charging leds may be muxed |
12:59.39 | xsacha-tv | cause i tried led-gpio driver on it and i only get the colour green.. so i have to write my own? |
12:59.49 | xsacha-tv | yeah it is a charging led |
12:59.57 | cr2 | xsacha-tv: you need to adapt to your gpios |
13:00.18 | xsacha-tv | well it's one LED with 4 colours and one GPIO (9) |
13:00.37 | cr2 | Echo31: what about gsm & gps led ? |
13:00.43 | xsacha-tv | it has funky values for each colour like 0xffd0f5 |
13:01.00 | cr2 | xsacha-tv: ok, then i don't have an idea |
13:01.25 | Echo31 | cr2: gsm=green and gps=orange |
13:01.41 | xsacha-tv | yeah i have that too |
13:01.42 | cr2 | Echo31: the bits |
13:01.45 | xsacha-tv | and blue=wifi |
13:02.06 | cr2 | Echo31: i can't test without the sim |
13:02.41 | cr2 | hm, i need to check umts on athe eventually |
13:03.02 | Echo31 | cr2: i dump what ? |
13:03.21 | cr2 | pd 0x08000000 0x10 |
13:03.43 | cr2 | 08000000 | 00f20034 00d0005b 00ff0000 000a0021 |
13:03.51 | cr2 | gps is yellow blink |
13:04.19 | Echo31 | 08000000 | 00ca0034 0090005b 00ff0000 000a0021 | 4...[.......!... |
13:04.41 | cr2 | ca ? i have f2 |
13:04.58 | *** join/#htc-linux stephan_ (n=stephan@217.237.166.98) |
13:05.08 | cr2 | f2=2+80+40+20+10 ? |
13:05.23 | Echo31 | cr2: yes, i have a led (yellow blink) |
13:05.31 | cr2 | so 10 is gps ? |
13:05.49 | cr2 | 2 is GPIOB1 0x0002 phone power (on=1,off=0) |
13:06.01 | cr2 | you have phone on ? |
13:06.45 | Echo31 | cr2: yes |
13:07.45 | cr2 | ca=80+40+8+2 |
13:07.54 | cr2 | gps off, nled off ? |
13:08.12 | cr2 | then 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.24 | Echo31 | cr2: gsm gps without bt/wifi 002a0014 00900013 00ff0020 000a0021 | ..*..... ...!... |
13:10.34 | cr2 | dcordes: https://privatepaste.com/a2bvF6vLWn this is my nc10 /etc/ppp/peers/vodafone-de |
13:11.04 | cr2 | 2a=20+8+2 |
13:11.58 | cr2 | should be gsm+nled |
13:12.52 | Echo31 | cr2: i have green gsm and orange alert led blink |
13:12.59 | cr2 | yes |
13:13.17 | cr2 | Echo31: gps and gsm led are the same left led |
13:13.44 | Echo31 | cr2: ok |
13:13.52 | cr2 | Echo31: i charge over usb, it's slow |
13:14.20 | cr2 | Echo31: can you full charge with AC, and check the green charging led ? |
13:15.25 | cr2 | i'll edit the wiki |
13:17.13 | xsacha-tv | cr2: do you know about battery drivers? |
13:17.33 | xsacha-tv | my board has 2 power management chips next to battery.. what do i need drivers for? one of those chips? |
13:19.27 | Echo31 | cr2: ok, i wait the charging state |
13:19.27 | cr2 | xsacha-tv: it's very device specific |
13:19.27 | xsacha-tv | hmm ok |
13:20.33 | cr2 | Echo31: looks better now -> http://www.htc-linux.org/wiki/index.php?title=CPLD1 |
13:21.14 | IceBone | That does look... neat and tidy. |
13:21.56 | cr2 | Echo31: backlight power is on cpld2 |
13:23.32 | cr2 | Echo31: but there is also 4,80. maybe the ok/menu backlight is different from lcd. |
13:26.27 | cr2 | listed as GPIOD7 0x0080 joystick bkl ? |
13:27.19 | cr2 | it's together with pxa gpio |
13:27.34 | cr2 | 0x20 in bank3 |
13:28.49 | cr2 | GPIO 101 00000020 backlight (power enable=1) |
13:30.28 | Echo31 | cr2: ok , i follow |
13:33.51 | cr2 | i may try to enable it manually |
13:34.24 | Echo31 | cr2: 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.51 | xsacha-tv | whats a joystick? :\ |
13:37.01 | cr2 | <PROTECTED> |
13:37.47 | cr2 | hm. lcd and ok/menu bkl is on |
13:38.01 | cr2 | xsacha-tv: 4+1directional button |
13:38.09 | xsacha-tv | oh |
13:38.25 | xsacha-tv | a dpad? |
13:39.12 | cr2 | its on most htc devices. in one or other form |
13:39.28 | cr2 | on athena it's done as a joystick. |
13:45.10 | cr2 | dcordes: https://privatepaste.com/501vkYMgR1 chat script |
13:45.35 | cr2 | dcordes: but i always enter the pin with cu manuall before running pppd |
13:46.15 | cr2 | dcordes: the chat script should include the full htc AT init string |
13:50.27 | cr2 | Echo31: what is your board id ? |
13:52.38 | Echo31 | cr2: how find my board id |
13:53.55 | cr2 | Echo31: pd 0x09000000 4 |
13:55.18 | Echo31 | cr2: 09000000 | c93fc93f |
13:57.01 | cr2 | c=80+40 |
13:57.22 | cr2 | 110=6 |
13:57.49 | cr2 | <PROTECTED> |
13:58.21 | cr2 | c=21 |
13:58.59 | cr2 | GPIOG5 0x0020 1582 present, CPLD2 location (get) . |
13:59.02 | cr2 | is set |
13:59.43 | cr2 | 0xab200000 0x0a000000 0x01 CPLD2 CPLD1c 0x20 unset |
13:59.44 | cr2 | 0xab200000 0x09000000 0x01 CPLD2 CPLD1c 0x20 set |
14:01.25 | *** join/#htc-linux Captnoord (n=Captnoor@dc5147a47b.adsl.wanadoo.nl) |
14:06.21 | cr2 | Echo31: what is qkeyled ? |
14:06.34 | *** join/#htc-linux StarLite (n=nnscript@s55916ca6.adsl.wanadoo.nl) |
14:06.36 | cr2 | it's usually the keybaord |
14:07.02 | Captnoord | or its the led of the 'q' key |
14:09.16 | Echo31 | cr2: charged (green) without gsm bt wifi 08000000 | 0000000c 00d00012 00fe0000 000a0021 |
14:10.23 | cr2 | Echo31: 12 |
14:10.43 | cr2 | was 5b |
14:11.00 | cr2 | b=8+2+1 |
14:11.53 | cr2 | 2=2 |
14:12.53 | cr2 | 8 is wifi pwr |
14:12.58 | cr2 | seen 13 |
14:13.32 | cr2 | 1 is the red led ? 2 is the green ? |
14:14.03 | cr2 | i have 13 |
14:15.27 | cr2 | yeah pfh 0x08000004 1 0x11 |
14:15.29 | cr2 | red |
14:15.49 | cr2 | pfh 0x08000004 1 0x12 |
14:15.52 | cr2 | green |
14:16.13 | cr2 | pfh 0x08000004 1 0x10 |
14:16.15 | cr2 | off |
14:16.44 | cr2 | but what is this one ? |
14:16.47 | cr2 | GPIOC2 0x0004 led related |
14:17.57 | cr2 | got blinking red :) |
14:19.10 | cr2 | ok, seems to be consistent. |
14:19.25 | Echo31 | cr2: good |
14:19.38 | cr2 | blinking red ignores red/green settings |
14:19.54 | cr2 | editing wiki |
14:21.12 | IceBone | Hey, 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.02 | cr2 | IceBone: htc athena |
14:22.29 | cr2 | IceBone: the best inet appliance from htc. imho. |
14:22.32 | IceBone | I see. |
14:23.13 | cr2 | IceBone: http://wiki.xda-developers.com/index.php?pagename=HTC_Athena |
14:23.16 | IceBone | Looks nice, but I prefer my mobile computer it in phone form. :) |
14:24.19 | cr2 | that's why i call it an appliance |
14:24.29 | IceBone | How 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.48 | cr2 | i will prefer its vga screen to raph. vga @ 2.8" is just an overkill |
14:25.05 | IceBone | Heh, yeah... it's tiny. |
14:25.08 | cr2 | only 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.59 | cr2 | but athena will not play sound. it's too difficult to develop |
14:26.11 | cr2 | and the cams. |
14:26.18 | IceBone | :/ |
14:26.19 | cr2 | but the htc cams are lame anyway. |
14:26.47 | IceBone | I 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.48 | cr2 | but for gps and inet it's a perfect device. |
14:26.55 | IceBone | It's also broken. :D |
14:27.02 | cr2 | yeah |
14:27.10 | IceBone | The colours are all weird. |
14:27.22 | *** join/#htc-linux Zoolooc_ (n=fredsiba@nrbg-4dbfe948.pool.einsundeins.de) |
14:27.36 | cr2 | the optics on phones sucks. |
14:27.50 | cr2 | and will always suck |
14:28.29 | IceBone | Not 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.39 | IceBone | cram, not crap. |
14:28.51 | IceBone | Well, crap works too. |
14:28.59 | cr2 | hm. where do you get 35mm ccd ?? |
14:29.29 | IceBone | Canon 5d (mkII), Canon 1Ds, Nikon D700, Nikon D3, D3x. |
14:29.49 | cr2 | it's insane |
14:30.12 | IceBone | I have a D300, which is a 1.5x crop, which is 23.6mm x 15.8mm. Not as big, but big enough. |
14:30.56 | IceBone | Also spent a few grand on quality glass. |
14:31.15 | IceBone | And then you get bozos saying their 200 dollar cam is better cause it has 3 megapixels more. |
14:31.42 | cr2 | http://www.astrosurf.com/re/chip.html |
14:31.54 | cr2 | 36.9 x 36.9 |
14:32.07 | cr2 | 4096 x 4096 |
14:32.10 | cr2 | omg :) |
14:32.37 | IceBone | Canon is developing a 35mm sensor with 50 megapixels... |
14:32.38 | cr2 | yes, only the glass counts |
14:33.01 | IceBone | I wish I could afford the good Nikon f/2.8 glass. :( |
14:33.16 | cr2 | for $20000 ? |
14:33.22 | IceBone | Something like that. :D |
14:33.26 | cr2 | :D |
14:33.38 | cr2 | i had a nice pic somewhere |
14:33.39 | IceBone | 14-24 is 1500, 24-70 is 2000, 70-200 is 2000. |
14:33.48 | IceBone | Not AS much... |
14:33.58 | cr2 | i'll grep in the logs |
14:34.10 | IceBone | But I got a D3 with a 400mm f/2.8 and 2x teleconverter on loan. |
14:34.21 | IceBone | The lens came in its own carbon fibre hard case. |
14:34.30 | IceBone | Sported a CF lens hood as well. |
14:34.34 | IceBone | Body out of CF. |
14:34.39 | IceBone | Still weighed 15 kg... |
14:34.49 | cr2 | this one ? http://a.img-dpreview.com/news/0703/Sigma/sigma200500mm-big.jpg |
14:35.10 | IceBone | Hah, nah, that's a monster I wish I could get my hands on. |
14:35.18 | cr2 | LOL |
14:35.24 | Perkka | :P |
14:35.32 | IceBone | No pun intended. : |
14:35.32 | IceBone | :P |
14:35.38 | Perkka | ill be off photographing streetrace in a few min |
14:35.55 | Perkka | gotta try my 300 2.8L :) |
14:36.24 | Perkka | http://idetorka.se/main.php?g2_itemId=3594 |
14:36.26 | Perkka | massive :D |
14:37.09 | IceBone | http://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.00 | IceBone | Booo, Canon! :P |
14:38.07 | Perkka | IceBone: i think i look bigger with my 300 2.8 but ig could be imagination |
14:38.15 | Perkka | it* |
14:38.17 | cr2 | also nt bad |
14:38.46 | IceBone | http://digitalfreak.net/wp-content/uploads/2009/04/sigma_200-500_2-8.jpg |
14:38.47 | Perkka | now i got 2.8 from 16 to 300mm :P |
14:38.57 | IceBone | Perkka: sweet |
14:39.02 | Perkka | exept the gap between 200 and 300 than |
14:39.16 | Perkka | there isnt much 200-300 2.8 zooms :P |
14:39.35 | IceBone | You don't need it anyway. Just shoot at 200 and crop a bit if 300 is too narrow. |
14:39.56 | Perkka | yea |
14:39.56 | IceBone | What body do you have? |
14:40.04 | Perkka | 5d+5dmk2 |
14:40.12 | Perkka | ah, and 20d |
14:40.27 | Perkka | look what i found today.. a COW http://idetorka.se/main.php?g2_itemId=3650 |
14:40.27 | IceBone | The only thing about the 5d mk2 I don't like is the archaic AF system. |
14:40.43 | Perkka | i got my af calibrated this week |
14:40.50 | Perkka | so its quite ok now |
14:40.52 | IceBone | It still has only 9 points. :P |
14:40.57 | Perkka | yea |
14:41.09 | Perkka | it's more spot on that oof now :P |
14:41.37 | Perkka | was sad before i got it calibrated, 2/3 of the pics were oof |
14:41.48 | IceBone | Some 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.50 | Perkka | hmm well... gotta go, streetracephoto |
14:41.58 | IceBone | Have fun. |
14:42.05 | Perkka | true |
14:42.10 | Perkka | bye |
14:42.10 | IceBone | I have 51... |
14:42.11 | IceBone | >_> |
14:42.11 | IceBone | <_< |
14:42.54 | IceBone | Well, that was a bit off topic... |
14:50.43 | cr2 | 90,d0,50 |
14:51.45 | cr2 | 40+10,80+10,80+40+10 |
14:57.49 | Echo31 | cr2: what we do now? |
14:58.46 | cr2 | im looking at the LCD power gpios now |
14:59.16 | cr2 | we 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.28 | cr2 | Echo31: can you recheck the gps power bit ? |
15:15.46 | Echo31 | cr2: ok with gps=gsm |
15:16.41 | cr2 | gps |
15:16.46 | cr2 | not the led |
15:19.03 | Echo31 | cr2: you want that i launch gps tool ? |
15:20.42 | cr2 | yes, and check the if the bit1 of +0x6 is enabled |
15:20.50 | cr2 | because it see it always disabled |
15:21.26 | cr2 | wince crashed :) |
15:21.27 | Echo31 | cr2: 08000000 | 00100004 00900012 00fe0020 000a0021 |
15:21.39 | cr2 | 90 |
15:23.23 | *** join/#htc-linux sxe (n=sxe@ip-62-143-86-48.unitymediagroup.de) |
15:23.59 | cr2 | yeah, seems so. buggy software ? |
15:27.29 | Echo31 | cr2: no, the software displays the satellites and positions |
15:28.13 | cr2 | ok |
15:30.19 | cr2 | Echo31: why do we have FIR driver ? |
15:30.34 | cr2 | i think athena does not support IR |
15:31.12 | Echo31 | cr2: yes, only bt |
15:38.51 | cr2 | Echo31: light sensor ? |
15:39.47 | *** join/#htc-linux hollo_ (n=hollo@3e6b7b2c.rev.stofanet.dk) |
15:40.47 | Echo31 | cr2: I launchs the camera ? |
15:42.09 | Echo31 | 08000000 | 00000084 00d00012 00fe0020 000a0021 |
15:42.46 | cr2 | Echo31: they are not so interesting |
15:43.08 | Echo31 | cr2: without camera 08000000 | 00000004 00d00012 00fe0020 000a0021 |
15:43.10 | cr2 | the cam is controlled over ati i2c and connected to the ati dsp. hopeless. |
15:43.22 | Echo31 | cr2: 04 and 84 |
15:43.23 | cr2 | Echo31: 2 cams ? |
15:43.35 | cr2 | the videocall |
15:43.38 | Echo31 | cr2: yes |
15:44.03 | Echo31 | i launchs in video call |
15:44.29 | Echo31 | 08000000 | 00010004 00d00012 00fe0020 000a0021 |
15:45.14 | cr2 | 80 |
15:46.06 | cr2 | ok. |
15:46.19 | cr2 | the biggest can of worms now. battery driver |
15:49.31 | IceBone | Lots of progress today? |
15:52.15 | cr2 | it's an old work, just revisited it now. |
15:52.30 | cr2 | the leds are documented too |
15:57.51 | xsacha-tv | battery is hard, eh? |
15:58.17 | xsacha-tv | can help me with it :) |
16:21.03 | *** join/#htc-linux MethoS- (n=clemens@host-091-097-245-239.ewe-ip-backbone.de) |
16:23.31 | Perkka | IceBone: it was the most boring streetrace ever imaginable |
16:29.24 | cr2 | what is DSSDH ? |
16:38.42 | Echo31 | cr2: where do you find the word DSSDH ? |
16:40.03 | cr2 | xsacha-tv: what are the 20 and 2c pxa-gpio regs ? |
16:40.10 | cr2 | Echo31: misc driver |
16:40.25 | xsacha-tv | 20 and 2c? what do you mean? |
16:40.43 | xsacha-tv | i2c? |
16:41.03 | cr2 | gpo |
16:41.09 | cr2 | gpio registers |
16:41.38 | tmzt | nledset |
16:42.39 | xsacha-tv | the bases? |
16:42.59 | xsacha-tv | #define GPIO0_BASE ((void __iomem *)io_p2v(0x40E00000)) |
16:43.04 | cr2 | #define GPSR2 __REG(0x40E00020) /* GPIO Pin Output Set Register GPIO<80:64> */ |
16:43.14 | xsacha-tv | yes |
16:43.19 | cr2 | #define GPCR2 __REG(0x40E0002C) /* GPIO Pin Output Clear Register GPIO <80:64> */ |
16:43.51 | cr2 | ok, so it's FE |
16:44.45 | cr2 | #define GPLR2 __REG(0x40E00008) /* GPIO Pin-Level Register GPIO<80:64> */ |
16:45.51 | xsacha-tv | i get 0 when i dump those 20 2C by the way |
16:47.33 | xsacha-tv | what are they for? |
16:49.22 | *** join/#htc-linux IamSOG (n=IamSOG@218.20.195.220) |
16:51.49 | tmzt | cr2: did you see what I pasted yesterday? |
16:52.18 | cr2 | tmzt: what ? |
16:52.31 | cr2 | the LCD MD/NS ? |
16:52.44 | cr2 | yes, it fits into my formula |
16:53.06 | cr2 | but the LCD is not interesting, because it's 8x50 only |
16:53.27 | tmzt | what mddi chip does it use? |
16:53.38 | tmzt | and what about nand? |
16:53.52 | cr2 | Echo31: ok, you may do some PXA gpio tracing, but the CPLDx data is finished |
16:54.08 | cr2 | tmzt: it's like pxafb. co$t saving ;) |
16:54.35 | tmzt | but we know msm has nothing like that |
16:54.38 | cr2 | if you will adapt this code to 7201A.... |
16:54.51 | cr2 | tmzt: 8250 has it. |
16:55.08 | Echo31 | cr2: ok and thanks |
16:55.11 | tmzt | the lcdc is internal? |
16:55.27 | tmzt | why does it say mddi then? |
16:55.31 | cr2 | yes |
16:55.33 | tmzt | I'm confused |
16:55.47 | cr2 | saves an extra mddi client chip |
16:56.14 | cr2 | the lcd is hooked directly to msm |
16:56.19 | tmzt | do we know if vic is really related to video? |
16:56.31 | cr2 | vic is interrupt controller |
16:56.37 | tmzt | ok |
16:57.18 | cr2 | now i would like to know wtf BT hangs |
16:57.36 | cr2 | is it some ADM misconfiguration ?? |
16:58.11 | cr2 | or do i need to dig deeper in the clock code. |
16:58.26 | tmzt | oh, msm? |
16:58.56 | cr2 | yes. tired of pxa for today :) |
16:58.58 | tmzt | does it work at any baud rate? |
16:59.15 | cr2 | i don't have brf datasheet ;) |
16:59.37 | tmzt | hciattach should help there |
16:59.47 | tmzt | I mean non dm modes |
16:59.49 | cr2 | the 6150 had 115200 on reset |
17:00.06 | cr2 | it's on the DM pins |
17:00.26 | tmzt | but g1 used it without dm |
17:00.26 | cr2 | you can't use non-DM afaiU |
17:00.42 | tmzt | maybe something in pinmux? |
17:00.42 | cr2 | uart1 |
17:01.15 | tmzt | why are their dm/non-dm uart pins? |
17:01.25 | tmzt | that makes no sense |
17:01.38 | cr2 | because uart2DM is an addon |
17:01.47 | cr2 | afaiU ;) |
17:01.48 | tmzt | why wouldn't they use different numbers if they were hardware differences |
17:02.12 | tmzt | yeah, but I would think it's like 16550, it adds dma |
17:02.15 | cr2 | why pxa has SIR and FIR ? |
17:02.21 | cr2 | uart2DM is like FIR on pxa |
17:02.32 | tmzt | and queue management |
17:02.37 | tmzt | 4mbps |
17:02.44 | tmzt | but same pins |
17:02.49 | cr2 | and you can do SIR on normal uarts |
17:02.56 | cr2 | the same story |
17:03.16 | cr2 | FIR is on the same pins ? |
17:03.29 | tmzt | that's what I'm saying why would dm/non-dm be different pins for the same uart |
17:03.35 | tmzt | I think so, stuart |
17:03.54 | cr2 | no docs = no clue |
17:04.10 | cr2 | it's all guesswork |
17:04.18 | tmzt | I'm saying g1 used low speed until 1.5 |
17:04.23 | cr2 | the 7200 has uart CLK at +0xc0 |
17:04.28 | cr2 | and the 8250 too |
17:04.29 | tmzt | on the same hardware |
17:04.39 | cr2 | but when i used it on 7201A, it hanged. |
17:04.58 | tmzt | with dm? |
17:05.00 | cr2 | painful disassembling showed that 7201A uart CLK is at +0xe ;) |
17:05.22 | tmzt | odd |
17:05.27 | cr2 | dm has its own clock |
17:05.48 | tmzt | I would guess in dm mode dm clock takes over |
17:05.49 | cr2 | spl and wince always setup DM |
17:05.51 | *** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be) |
17:05.57 | tmzt | spl does? |
17:05.58 | cr2 | even to read the btaddr |
17:06.03 | cr2 | yes |
17:06.05 | tmzt | that could be the problem |
17:06.11 | cr2 | but with a differet clock source |
17:06.12 | tmzt | maybe hboot doesn't |
17:06.22 | cr2 | PLL1 vs. MODEM_AUX_something |
17:06.45 | cr2 | i don't have a good understanding how the PLL1 and MODEM_AUX is setup |
17:07.09 | cr2 | PLL1 may be understood (i think) |
17:07.09 | tmzt | are they all the same formulas? |
17:07.28 | cr2 | but MODEM_AUX is somewhere in the dark AMSS corner ;) |
17:07.31 | tmzt | do we know all the base osc's now? |
17:07.49 | cr2 | TCX0 is 19.2MHz |
17:08.10 | cr2 | btw, we have 66MHz for PCLK |
17:08.10 | cr2 | but g1 dmesg says 64MHz |
17:08.23 | tmzt | which pclk? |
17:08.31 | cr2 | but it's just cosmetic change. |
17:08.31 | cr2 | still may be important for understanding clocks |
17:08.41 | tmzt | can we find documentation on how axi works? |
17:08.45 | cr2 | periferal clock |
17:08.52 | tmzt | yeah, which one |
17:08.52 | cr2 | i doubt it |
17:09.05 | cr2 | i think there is only one |
17:09.07 | tmzt | I don't think it's qualcomm stuff |
17:09.22 | cr2 | no idea |
17:09.33 | tmzt | search arm and axi |
17:09.43 | cr2 | and ahb |
17:09.53 | tmzt | ahb? |
17:11.24 | cr2 | yes |
17:13.01 | tmzt | what 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.34 | cr2 | hi pH5 |
17:23.02 | cr2 | tmzt: i don't know |
17:23.06 | pH5 | hi |
17:23.44 | cr2 | pH5: how to proceed with the athena ? i have sorted out all cpld bits today |
17:24.13 | cr2 | pH5: there are several drivers (by Kevin2) that have nothing to do with athena, but athena needs them |
17:24.23 | cr2 | can the be added to git first ? |
17:24.54 | cr2 | then i'd like to verify the cpld1+cpld2 code. |
17:26.18 | pH5 | cr2: if you could split that up and send patches to the mailing list, that would be a big help. |
17:26.48 | pH5 | what drivers have nothing to do with athena but are needed by it?? |
17:27.14 | cr2 | htc-spi-kbd.c and ad7877.c |
17:28.17 | cr2 | the last one was used on apache. it's TS and battery ADC |
17:29.06 | pH5 | ok, I think I understand. |
17:29.28 | pH5 | the ad7877 should be submitted to mainline right now, but of course I can take it into the local tree. |
17:29.37 | tmzt | spi keyboard should be serio I think |
17:30.11 | tmzt | if the infrastructure will support it |
17:30.23 | pH5 | yeah, somebody should look at that. |
17:32.47 | cr2 | i need to buy some food now. bbl |
17:44.52 | Echo31 | Hi pH5. cr2 has done a good job on the CPLDs of athena. |
17:45.42 | pH5 | Echo31: of course he has, what did you expect :) |
17:48.38 | Echo31 | pH5: 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.25 | pH5 | Echo31: 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.42 | Echo31 | pH5: Ok. But what are the parts concerned from the patch ? all the parts |
18:28.05 | tmzt | cr2: San says all the answers are in the source |
18:28.50 | cr2 | Echo31: don't submit the ad7877.c patch |
18:29.14 | cr2 | Echo31: and start with making the diff for pxa-regs.h |
18:29.25 | cr2 | tmzt: uart2DM ? |
18:29.58 | tmzt | yeah, uartDM |
18:30.11 | tmzt | he said amss probably sets up dm also |
18:30.22 | tmzt | I guess we don't need non-dm mode? |
18:30.59 | cr2 | not used in wince, can't be tested. |
18:32.38 | cr2 | tmzt: you have one point though. |
18:32.59 | tmzt | ? |
18:33.08 | tmzt | what's not used in ce? |
18:33.37 | cr2 | the braindead g1 code puts all gpio alt settings into board file, instead of leaving it to the respective drivers. |
18:33.48 | cr2 | uart2 is not used in wince. |
18:34.11 | cr2 | i have added uart2DM alt gpios to rfkill. |
18:34.13 | tmzt | alt settings are not something driver should care about |
18:34.21 | cr2 | that may be not the brightest idea. |
18:34.27 | tmzt | the only affect the package, therefore board |
18:34.51 | tmzt | we should be using mfp |
18:35.09 | cr2 | htc sets alt on _probe, and unsets on _remove |
18:35.19 | cr2 | i think that it's the right way. |
18:35.33 | tmzt | is alt used for pinmux? |
18:35.55 | cr2 | how are you going to mux the uart1 (alt) and tvout ? by callbacks to board ? |
18:36.15 | tmzt | those are workarounds to the limitations of gpio api |
18:36.35 | cr2 | ok, the bt alt can be hardcoded. |
18:36.41 | tmzt | love what pre does :) |
18:37.07 | tmzt | omap3 has full pinmux so they just switch alt between usb and uart, no chip needed |
18:37.38 | tmzt | yes, hardcode if required, but moving all alts to drivers would be a mistake |
18:37.46 | tmzt | I think I misunderstood |
18:38.00 | cr2 | ok |
18:38.04 | tmzt | it needs a new gen api, an altfunction requester |
18:38.28 | cr2 | so you think that alts belong to board init ? |
18:38.32 | tmzt | so the pin numbers stay in pdata but drivers can change alt function |
18:38.37 | tmzt | yes |
18:38.50 | tmzt | drivers should never be board specific |
18:38.53 | cr2 | ok. |
18:39.09 | cr2 | pdata |
18:39.10 | tmzt | with mfd cells they shouldn't even have hardcoded address offsets |
18:39.37 | cr2 | ok, i get your point |
18:39.55 | tmzt | ok |
18:40.00 | cr2 | but them google should not create board-trout-rfkill.c in the first place. |
18:40.30 | cr2 | but use pdata for gpios,vregs and such. |
18:41.52 | cr2 | abnd dex/proc_comm should be reduced to what it is: the msm pmic driver. |
18:42.23 | tmzt | board-trout-rfkill is part of the board-trout |
18:42.41 | tmzt | I do think more stuff should be generic |
18:42.53 | cr2 | there should be a brf63x0.c driver |
18:43.12 | cr2 | which should accept gpios/vregs et al. as pdata |
18:43.19 | tmzt | don't agree with that, pmic is a chip, dex is a protocol |
18:43.48 | cr2 | i could have accessed pmic directly. |
18:43.51 | tmzt | brf should be supported by hciuart |
18:44.11 | cr2 | it's just qualcomm wants to hide the spi interface from mem |
18:44.16 | cr2 | s/mem/me/ |
18:44.26 | tmzt | ah |
18:44.34 | tmzt | is it spi or sbi? |
18:44.39 | cr2 | sbi |
18:44.45 | tmzt | sbi sangerous |
18:44.52 | tmzt | sbi is dangerous |
18:45.05 | tmzt | modem plls might be also |
18:45.23 | cr2 | only because amss may access it in parallel |
18:45.52 | tmzt | I would say because wrong address could cause interference with gsm |
18:45.59 | Echo31 | cr2: pH5: want you to merge all from pxa-regs.h to pxa2xx-regs.h or only parts required to compile? |
18:46.02 | tmzt | we need to stay away from that |
18:46.26 | tmzt | Echo31: what needs added there? |
18:46.39 | tmzt | pxa should apply to all pxa devices |
18:46.49 | tmzt | what's missing? |
18:47.01 | cr2 | tmzt: many register definitions |
18:47.14 | tmzt | pm stuff? |
18:47.30 | tmzt | Wy: do you know of any plans in this area? |
18:47.51 | cr2 | tmzt: 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.26 | cr2 | if you want arm9 control shared hardware, the protocol should be open and documented. |
18:48.26 | tmzt | I know |
18:48.51 | tmzt | we don't share hardware, we rely on amss to provide what we need |
18:49.01 | cr2 | otherwise it goes completely against the gpl. spirit at least. |
18:49.15 | cr2 | with undocumented unterface. |
18:49.28 | cr2 | i can program for windows with the same logic. |
18:49.33 | tmzt | I don't know what the real danger to gsm or cdma(w-cdma) protocols is, but we didn't write the stack |
18:50.04 | cr2 | google created a mess by changing the interface. |
18:50.21 | cr2 | imho, since they have broken it, they should have documented the changes. |
18:50.26 | tmzt | yeah, some things didn't need it |
18:50.29 | tmzt | like gpios |
18:50.44 | tmzt | not agruing that |
18:50.53 | tmzt | only that we should stay away from sbi |
18:51.15 | cr2 | ok, but again, they created a new interface, and did not document it too. just some magic numbers all over the code. |
18:51.45 | tmzt | u-boot is better right? |
18:51.45 | cr2 | i've learned much more from disaasembling wince code, than looking at their "free" software ;) |
18:51.54 | tmzt | did you see the ZZZZ comment? |
18:52.13 | cr2 | yes |
18:52.22 | tmzt | they want to convert hsusb init back to proc comm |
18:52.23 | cr2 | the g1 code does not use vbus DEX too |
18:52.30 | cr2 | but wince does it :) |
18:53.10 | cr2 | why should arm9 deal with usb ? |
18:53.15 | cr2 | or with tvout ? |
18:53.16 | xsacha-tv | disassembling 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.40 | tmzt | ah |
18:53.47 | cr2 | let arm9 deal with gsm, and keep it away from everything else. |
18:54.09 | cr2 | i wish we could strip down the amss |
18:54.30 | cr2 | with all these dns lookups there and other weirdness. |
18:54.40 | tmzt | I think pmic is used to change rf power |
18:54.48 | tmzt | which cdma does very rapidly |
18:55.02 | cr2 | i doubt it. |
18:55.03 | tmzt | that's qualcomm gps |
18:55.18 | cr2 | there is a 7200A diagram |
18:55.34 | tmzt | hey, I found that rmnet uses DATA5 and 6 on g1 |
18:56.00 | cr2 | gps is a just a preamplifier. all tracking is done by some DSP. do you think it#s the same mDSP as gsm ? |
18:56.15 | tmzt | not sure |
18:56.23 | tmzt | I meant the dns stuff |
18:56.31 | tmzt | what did you mean by that? |
18:57.23 | cr2 | the xtra urls are hardcoded in amss |
18:57.36 | tmzt | yeah |
18:57.50 | cr2 | which is a userspace issue |
18:57.58 | cr2 | and not the umts firmware |
18:58.05 | tmzt | makes me even more convinced there's an ip stack and ppp is somekind of proxy |
18:58.22 | cr2 | in amss ? sure. |
18:58.26 | tmzt | but amms is userspace |
18:58.38 | tmzt | it has oem and apps parts |
18:58.40 | cr2 | amss is modem firmware |
18:58.51 | cr2 | no |
18:58.55 | tmzt | on this phone it is |
18:59.10 | tmzt | look at the gobi firmware, two .mdn files |
18:59.12 | cr2 | apps is spl+wince |
18:59.17 | tmzt | dream_kill: you here? |
18:59.52 | tmzt | ok, but the same amss os is used as the primary os on other devices |
19:00.13 | cr2 | tmzt: apropos pxa-regs.h i've added a bunch of data into this file in hh.org CVS |
19:00.37 | cr2 | ok, i get your point |
19:00.44 | tmzt | different drivers and different userspace applications (brew, java, broweser) |
19:01.32 | tmzt | I mean for pxa we don't change upstream stuff |
19:01.44 | cr2 | we should |
19:01.55 | tmzt | if new regs are needed they should be handled as patches to pxa |
19:02.04 | cr2 | the mainline is simply incomplete. |
19:02.08 | tmzt | and they should be in the right file for the soc |
19:02.10 | cr2 | yes |
19:02.19 | tmzt | yeah, pm is missing for insance |
19:02.27 | tmzt | WyrM is working on that |
19:02.48 | cr2 | some usb regs are missing |
19:02.54 | tmzt | I was concerned at the pxa2xx into pxa2xx |
19:02.55 | tmzt | yes |
19:03.11 | tmzt | they go in pxa2xx-udc or ohci though |
19:03.27 | cr2 | #defines ? |
19:03.34 | tmzt | pxa2xx into pxa |
19:03.35 | tmzt | yes |
19:03.55 | tmzt | they've been moved out of -regs |
19:03.56 | cr2 | port2 is mixed |
19:04.02 | tmzt | yes |
19:04.12 | tmzt | apt: up2ocr? |
19:04.13 | apt | well, up2ocr is 0x40600020, or the USB Port 2 Output Control Register, or used for udc |
19:04.32 | cr2 | how to deal with that ? |
19:04.40 | tmzt | it's been done |
19:04.51 | tmzt | the only missing is the up3ocr bit masks |
19:05.11 | cr2 | nobody uses that |
19:05.14 | cr2 | :) |
19:05.14 | tmzt | include a different mach header |
19:05.32 | tmzt | phones with msm on host do |
19:05.36 | xsacha-tv | i noticed a newer pxa2xx-udc has new usb defines |
19:05.44 | tmzt | yes |
19:05.51 | xsacha-tv | UHCRH or something.. and all the boards use that now |
19:06.00 | cr2 | ok |
19:06.07 | xsacha-tv | hosr reset |
19:06.13 | xsacha-tv | host* |
19:06.35 | xsacha-tv | and i dumped my value from winmo |
19:07.58 | tmzt | yes, but it seems ulpi is used instead |
19:08.15 | tmzt | it's kept in reset? |
19:08.34 | tmzt | like I said, give up on usb for now |
19:08.42 | tmzt | wifi will actually be easier |
19:20.09 | xsacha-tv | k |
19:20.27 | xsacha-tv | ive given up on wifi cause of regression |
19:21.01 | tmzt | ? |
19:21.13 | tmzt | get a newer kernel |
19:21.20 | tmzt | port the Ndroid patches |
19:21.35 | tmzt | or use wireless-compat |
19:21.52 | xsacha-tv | trying 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.57 | xsacha-tv | wireless-compat? |
19:22.47 | tmzt | a tree with ieee80211/mac80211 backported to various kernels |
19:22.57 | tmzt | porting android should be easier |
19:22.58 | *** join/#htc-linux JuNu_KN (n=chatzill@95.113.17.247) |
19:23.12 | tmzt | getting linux working first is even better |
19:23.45 | xsacha-tv | k |
19:24.10 | xsacha-tv | by the way i see xllpi2c mentioned, does that mean i need i2c to communicate to the battery? |
19:24.22 | tmzt | probably |
19:24.27 | tmzt | xllp |
19:24.29 | tmzt | ? |
19:24.38 | xsacha-tv | cross platform low level library.. winmo thing |
19:24.41 | tmzt | not to battery |
19:24.59 | tmzt | that's probably w1 |
19:25.10 | tmzt | but maybe to pmic |
19:25.57 | xsacha-tv | Zylonite_battd, MITs_battery |
19:26.10 | xsacha-tv | MITs isnt a manufacturer is it? |
19:27.29 | xsacha-tv | has BatteryXllpi2c... Xllpi2cRead, Xllpi2cWrite |
19:28.23 | tmzt | no idea |
19:28.52 | xsacha-tv | BatteryXllpgpio, BatteryXllpmfp, sets level using gpio |
19:31.05 | Echo31 | cr2: pH5: The missing parts from pxa2xx-regs.h concerns usb host ohci (about added 20 lines) |
19:31.38 | cr2 | Echo31: tmzt says you should #include uhh*something :) |
19:32.37 | Echo31 | cr2: i have to create a dedicated header |
19:33.18 | cr2 | tmzt: ? |
19:34.09 | tmzt | ? |
19:34.31 | tmzt | mach/ something |
19:34.40 | tmzt | pxa2xx-udc I think |
19:34.46 | tmzt | don't have my tree here |
19:35.08 | tmzt | arch/arm/mach-pxa/include/mach |
19:35.20 | Echo31 | tmzt: or regs-udc.h |
19:35.26 | tmzt | just include udc and ohci and you should have the regs |
19:35.28 | tmzt | yes |
19:38.58 | Echo31 | tmzt: the DMA Controller regs may be also used by the sound driver. |
19:47.12 | tmzt | there should be generic dma api support |
19:47.34 | tmzt | but yes, they belong somewhere |
19:49.16 | Echo31 | tmzt: for this first step, i create regs-ohci.h |
19:50.15 | Echo31 | tmzt: the pxa2xx-udc.h file is already in the arch/arm/mach-pxa/include/mach |
19:50.47 | tmzt | yes |
19:51.44 | cr2 | Echo31: the sound is not really important right now :) |
19:52.14 | Echo31 | cr2: ok |
19:52.14 | cr2 | Echo31: and pxa-i2s is not used on athena |
19:52.37 | cr2 | so this part is unneeded |
19:55.12 | *** join/#htc-linux stickboy (n=anonymou@ool-457e4101.dyn.optonline.net) |
20:04.01 | dcordes | cr2: where does the chat script live? how to add the password? |
20:06.50 | cr2 | dcordes: it's referenced in /etc/ppp/peers/* |
20:07.23 | cr2 | dcordes: i don't use it to add the passowrd., because otherwise the passowrd should be in this script |
20:07.49 | cr2 | dcordes: we also need the locale keyboard map |
20:08.24 | cr2 | does your loadkeys use the same syntax as a "usual" keyboard map ? |
20:08.43 | tmzt | busybox doesn't |
20:08.48 | cr2 | i'm thinking about something like raph100-de.map |
20:08.54 | tmzt | it should load binary ones |
20:09.13 | tmzt | microp-ksc doesn't need kernel keymap really |
20:09.25 | tmzt | but I think maejrep used one |
20:09.32 | tmzt | it returns scancodes |
20:09.44 | cr2 | tmzt: yes, i rememebr it. does busybox use loadkeys ?? |
20:09.54 | tmzt | yes |
20:09.58 | cr2 | tmzt: how should i do alt+key ? |
20:10.02 | tmzt | but not the full syntax |
20:10.09 | tmzt | I use RIGHTALT |
20:10.13 | tmzt | as AltGr |
20:10.24 | tmzt | but de needs it for something else right? |
20:10.52 | cr2 | tmzt: i think loadkeys is done differently on busybox |
20:10.59 | tmzt | do you have sym? |
20:11.06 | cr2 | tmzt: yes, it's a different keyboard layout. |
20:11.12 | tmzt | yeah, it's binary I think |
20:11.18 | cr2 | tmzt: i mapped Fn to ALT |
20:11.35 | cr2 | and SYN to AltGr |
20:11.36 | tmzt | as alt or for altgr? |
20:11.40 | tmzt | ok |
20:11.52 | tmzt | so Fn is LEFTALT? |
20:12.10 | tmzt | yoou need something else for symbols then |
20:12.12 | cr2 | tmzt: i'm not sure if dcordes has added the "real" loadkyes |
20:12.21 | cr2 | Fn is LEFTALT |
20:12.28 | tmzt | if AltGr is for accents |
20:12.37 | cr2 | for which symbols ? |
20:13.04 | cr2 | tmzt: i want to replace Fn-$FOO by Alt-$FOO |
20:13.24 | cr2 | there 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.18 | Echo31 | cr2: Do you want that i removes parts on w228 or I put its commented |
20:19.19 | cr2 | Echo31: remove completely |
20:20.11 | Echo31 | cr2: 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.12 | dcordes | cr2: I can add all of these things in openembedded |
20:32.39 | *** join/#htc-linux wirelessdreamer (n=dreamer@chrobd01.vailsys.com) |
20:34.00 | cr2 | dcordes: are you using loadkyes from busybox ? |
20:35.06 | cr2 | tmzt: |
20:35.10 | cr2 | <PROTECTED> |
20:35.12 | cr2 | <PROTECTED> |
20:35.13 | cr2 | <PROTECTED> |
20:35.52 | dcordes | cr2: the /usr/bin/loadkeys in my image is no symlink to busybox |
20:37.23 | cr2 | can you find out how it is compiled ? |
20:37.52 | dcordes | I'm on it |
20:38.40 | dcordes | it must be part of something, no seperate package |
20:39.01 | dcordes | mickey|bbl: here? |
20:40.27 | tmzt | yay |
20:40.46 | tmzt | kbd was console-tools I tink |
20:41.06 | tmzt | now it's kbd |
20:42.28 | dcordes | I have the rm work. that's why I find nothing |
20:44.10 | tmzt | what do you eed from mickeyl? |
20:44.39 | dcordes | ask him about teh loadkey |
20:48.24 | Echo31 | cr2: 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.58 | tmzt | vsfb should be generic now?????????????? |
20:49.02 | cr2 | remove htcathena_vsfb_device completely |
20:49.03 | tmzt | sorry |
20:49.34 | cr2 | tmzt: is the vsfb.c included in mainline ? |
20:49.47 | tmzt | did you see the ATAG VIDEOLFB in uboot? |
20:49.53 | tmzt | not sure |
20:50.15 | tmzt | so many implementations |
20:50.49 | cr2 | it will take some time to write down all the scary ati clock PLL stuff ;) |
20:51.01 | tmzt | msm? |
20:51.15 | cr2 | atiw2284 |
20:51.26 | tmzt | ok |
20:53.59 | cr2 | the http://wiki.xda-developers.com/index.php?pagename=RaphaelLinux looks completely outdated |
20:55.49 | cr2 | tmzt: i'll look how g1 configures alt bt |
20:57.27 | *** join/#htc-linux dcordes_ (n=dcordes@unaffiliated/dcordes) |
20:59.32 | cr2 | dcordes_: 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.41 | dcordes_ | cr2: ok didn't have bt in |
22:00.24 | Echo31 | cr2: The size of my new patch is 40 ko |
22:08.52 | cr2 | Echo31: pastebin |
22:10.51 | Echo31 | cr2: find the patch http://fr.pastebin.ca/1476854 |
22:12.35 | cr2 | Echo31: please rename these GPIO22_HTCATHENA_DPR_RESET1, |
22:12.43 | cr2 | i have added new names into wiki |
22:13.40 | cr2 | SSP2 is keyboard, and SSP1 is battery_mobitor+touchscreen |
22:14.08 | cr2 | GPIO51_HTCATHENA_DPR_AT |
22:14.15 | cr2 | these are irqs |
22:14.30 | cr2 | <PROTECTED> |
22:14.47 | cr2 | + /* I2C */ |
22:14.48 | cr2 | + GPIO117_I2C_SCL, |
22:14.50 | cr2 | + GPIO118_I2C_SDA, |
22:14.55 | cr2 | these are entered twice |
22:17.37 | Echo31 | cr2: GPIO22_HTCATHENA_DPR_RESET1 -> DPR-P9 |
22:18.26 | cr2 | there is DPR-XX IRQ and DPR-XX FE |
22:19.04 | cr2 | IRQ is set by MSM6275 that the data is available in the RX fifo for read |
22:21.17 | cr2 | the FE notifies MSM6275 that the data can be read from the TX fifo |
22:21.20 | cr2 | tmzt: is it done differentlly now ? |
22:21.20 | cr2 | + /* setup Port1 GPIO pin. */ |
22:21.21 | cr2 | + pxa_gpio_mode( 88 | GPIO_ALT_FN_1_IN); /* USBHPWR1 */ |
22:21.21 | cr2 | + pxa_gpio_mode( 89 | GPIO_ALT_FN_2_OUT); /* USBHPEN1 */ |
22:22.14 | cr2 | Echo31: you do not initialize cpld1 and 2 ? |
22:22.19 | cr2 | +// &egpio_cpld1, |
22:22.20 | cr2 | +// &egpio_cpld2, |
22:23.00 | cr2 | Echo31: this is junk |
22:23.00 | Echo31 | cr2: The cpld2 initialization is failed |
22:23.03 | cr2 | +extern void htcathena_cpld2_set( u_int16_t bits ); |
22:23.05 | cr2 | +extern void htcathena_cpld2_clr( u_int16_t bits ); |
22:23.07 | cr2 | +extern u_int16_t htcathena_cpld2_get(void); |
22:23.24 | tmzt | cr2: what? |
22:23.28 | cr2 | Echo31: there are some changes needed for cpld init |
22:23.44 | cr2 | tmzt: how it should be done with mfp & |
22:23.54 | cr2 | [00:20] <cr2> + pxa_gpio_mode( 88 | GPIO_ALT_FN_1_IN); /* USBHPWR1 */ |
22:23.55 | cr2 | [00:20] <cr2> + pxa_gpio_mode( 89 | GPIO_ALT_FN_2_OUT); /* USBHPEN1 */ |
22:24.00 | tmzt | look at magician or ezx |
22:25.55 | cr2 | Echo31: cpld irq names are strange |
22:26.09 | Echo31 | cr2: i tried to set the cpld2 init, the boot don't start |
22:28.26 | Echo31 | cr2: for cpld, i prefer that you lead |
22:28.30 | cr2 | Echo31: look much better now. but the cpld part needs some major changes. i don't have the brainpower to do it now :) |
22:28.38 | cr2 | ok |
22:29.38 | cr2 | i need to check what pH5 has written for magician and hx4700 |
22:29.58 | Echo31 | cr2: for the first step ,can you |
22:30.27 | Echo31 | cr2: for the first step, can i implement only cpld2 |
22:30.50 | cr2 | Echo31: cpld2 can be more or less cut'n'pasted from hx4700 |
22:31.08 | tmzt | looks ok |
22:31.13 | tmzt | that is mfp |
22:31.31 | tmzt | only the ohci-init isn't and that works for tes5ting |
22:31.59 | tmzt | not sure if the defines changed |
22:32.00 | Echo31 | where can i find ? |
22:32.52 | Echo31 | where can i find the git of hx4700? |
22:33.03 | cr2 | pH5/dev |
22:33.21 | cr2 | bracnh |
22:36.51 | cr2 | Echo31: i'll check cpld tomorrow |
22:39.43 | cr2 | Echo31: 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.12 | Echo31 | cr2: ok. I implement the cpld2. thanks, bye |
22:41.59 | cr2 | tmzt: back to the evil 7201A sound. |
22:42.57 | tmzt | hey |
22:43.24 | cr2 | i'll look at the kaiser |
22:53.01 | cr2 | 0,0,0; 1,1,1; and 2,1,1 |
22:53.07 | cr2 | didn't see the last one. |
22:53.28 | cr2 | 1,1,1 should be ok. |
22:56.55 | tmzt | modem rest? |
22:56.56 | cr2 | tmzt: snd_ioctl which /dev/ file is that ? |
22:57.18 | tmzt | msm-snd-control I think |
22:59.01 | cr2 | why is it not used by playwav ? |
23:00.01 | tmzt | playwave is only used to play boot sound |
23:00.28 | tmzt | I guess they assume the radio is in the correct state for that |
23:01.08 | cr2 | hmm |
23:07.44 | cr2 | msm_snd misc dev ? |
23:08.21 | cr2 | is it in /sys ? |
23:08.29 | tmzt | no |
23:08.34 | tmzt | '/dev |
23:08.40 | tmzt | wait |
23:08.41 | cr2 | do you have it ? |
23:08.43 | tmzt | no idea |
23:10.43 | *** join/#htc-linux skodde (n=skodde@unaffiliated/skodde) |
23:11.53 | cr2 | 117 #define RPC_ADSP_RTOS_APP_TO_MODEM_PROC 2 |
23:12.04 | cr2 | should be 1. did i miss it ? |
23:12.17 | tmzt | oh |
23:15.41 | cr2 | tmzt: how to enable pr_info() ? |
23:16.30 | tmzt | dmesg -n 15 maybe |
23:16.51 | tmzt | I just learned there's a sysfs entry for that as well |
23:18.01 | cr2 | msm_snd should be in /dev |
23:19.22 | tmzt | yes |
23:23.39 | cr2 | ok. good night |
23:50.43 | *** join/#htc-linux Guest92385 (n=fnord@24-151-90-116.static.nwtn.ct.charter.com) |