| 02:14.00 | *** join/#htc-linux apt (i=ibot@pdpc/supporter/active/TimRiker/bot/apt) |
| 02:14.00 | *** topic/#htc-linux is HTC Linux Channel: Find logs at http://apt.rikers.org/%23htc-linux/ | please check http://handhelds.org/moin/moin.cgi/HTC_2dPhones | http://wiki.xda-developers.com/index.php?pagename=Xanadux | <cr2> let's define a common setup. |
| 02:16.29 | *** join/#htc-linux apt (i=ibot@pdpc/supporter/active/TimRiker/bot/apt) |
| 02:16.29 | *** topic/#htc-linux is HTC Linux Channel: Find logs at http://apt.rikers.org/%23htc-linux/ | please check http://handhelds.org/moin/moin.cgi/HTC_2dPhones | http://wiki.xda-developers.com/index.php?pagename=Xanadux | <cr2> let's define a common setup. |
| 03:20.28 | *** join/#htc-linux xur1z (n=chris@60.234.253.91) |
| 03:20.32 | xur1z | helo |
| 04:06.42 | *** join/#htc-linux TeringTu1y (n=maarten@188-116-dyn.ipact.nl) |
| 05:17.48 | *** join/#htc-linux _law_ (n=law@mail.stiftadmont.at) |
| 05:22.48 | *** join/#htc-linux psokolovsky (n=psokolov@82.193.98.7) |
| 06:17.25 | *** join/#htc-linux rob_w (n=rob_w@p549b9d07.dip0.t-ipconnect.de) |
| 07:24.42 | *** join/#htc-linux Fossi (n=cmewes@195.177.48.115) |
| 07:25.05 | *** join/#htc-linux rmoravcik (n=rmoravci@pc-3s0zt5w2e4y0vzmhnrzq3a21zqajzfw.users.student.utc.sk) |
| 08:15.08 | *** join/#htc-linux Kmarc (n=kari@markos.biz) |
| 09:25.45 | *** join/#htc-linux pH5 (n=ph5@p5485E3E2.dip.t-dialin.net) |
| 10:13.37 | *** join/#htc-linux rob_w (n=rob_w@p549B9D07.dip0.t-ipconnect.de) |
| 10:35.40 | pH5 | cr2: I've sent the tihtc ldisc. I'd be happy if you could have a look at it and test on the blueangel if you find some time. |
| 10:49.08 | *** join/#htc-linux cyrill62 (n=cyrill62@ble59-5-82-233-205-36.fbx.proxad.net) |
| 11:00.37 | *** join/#htc-linux gw280 (n=george@vm.gwright.org.uk) |
| 11:11.11 | _law_ | whats the best (mostly working) method to boot a fs with haret? |
| 11:11.25 | _law_ | ext2 mmc partition, initrd ? |
| 11:11.44 | _law_ | nothing seams do work on the tornado |
| 11:16.59 | psokolovsky | nfs - always ;-) |
| 11:19.05 | pH5 | _law_: for mmc you need working mmc support in the kernel, for nfs usb gadget + g_ether. if you do, both methods work reliably. if you don't, I guess initrd is your only choice. |
| 11:19.28 | pH5 | s/if you do/if you have them/ |
| 11:20.12 | _law_ | pH5, g_ether should work |
| 11:20.36 | _law_ | pH5, is it right that initrd is only a cpio.gz ? |
| 11:21.00 | pH5 | _law_: initramfs. initrd could be anything. |
| 11:21.30 | _law_ | pH5, i think i cant build this with OE or? |
| 11:22.40 | pH5 | _law_: hmm I don't know, I never tried this.. |
| 11:56.14 | *** join/#htc-linux tudenbart (n=willi@xdsl-213-196-251-17.netcologne.de) |
| 12:06.54 | *** join/#htc-linux bd2 (n=cbou@89.113.85.104) |
| 13:14.51 | mndctrl | what is the GSM status on the universal.. website says something about 'Works, but issues with mic...' ? |
| 13:15.20 | mndctrl | is it usable? |
| 13:19.11 | pH5 | mndctrl: my understanding is that it works but needs fiddling with alsa mixers to enable the mic. but cr2 or goxboxlive will know better, I don't have a universal. |
| 13:19.58 | mndctrl | ah, ok.. tnx! |
| 14:20.13 | *** join/#htc-linux goxboxlive (n=goxboxli@206.80-202-161.nextgentel.com) |
| 14:37.25 | *** join/#htc-linux jeanseb (n=jeanseb@gazypan.dyndns.org) |
| 14:44.09 | cr2 | mndctrl: it is a question of the kernel-userspace API |
| 14:45.22 | cr2 | pH5: which software uses alsa controls for the phone on magician ? is there any standard list of common controls ? |
| 14:46.07 | cr2 | pH5: i've just bought an old himalaya with the half-broken lcd. so i'll be able to do the tests for it too. |
| 14:47.27 | pH5 | cr2: alsamixer ;) other than Documentation/sound/alsa/ControlNames.txt I don't know about a standard list. |
| 14:48.29 | cr2 | pH5: is there a minimal required list for openmoko ? the neo supports a gazillion of controls, i can't imagine they are all used. |
| 14:48.32 | pH5 | the gpe mixer is still oss only and openmoko doesn't even have a mixer control yet. |
| 14:48.55 | cr2 | ok, so it does not exist. |
| 14:49.30 | pH5 | cr2: right. |
| 14:50.13 | cr2 | btw, what will happen if i'll start the magician-openmoko image on the himalaya/blueangel ? |
| 14:50.31 | cr2 | with the appropriate kernel of course |
| 14:50.51 | pH5 | the neo controls are a bit strange in some places. for example the left/right amp controls are two single controls instead of one stereo control. |
| 14:51.06 | cr2 | i'm always concerned about the serial ports. |
| 14:51.11 | cr2 | lol |
| 14:51.27 | cr2 | but neo does not have stereo speakers like universal ? |
| 14:51.47 | pH5 | cr2: neo has stereo speakers. |
| 14:52.03 | cr2 | hm. interesting. |
| 14:52.14 | pH5 | don't worry about the serial ports. you can write random shit into them as long as you know how to reset the chips afterwards. |
| 14:52.34 | pH5 | cr2: they're quite loud, but the sound quality is still cheap of course. |
| 14:52.47 | pH5 | much better than the magician's 'speaker' :) |
| 14:53.17 | cr2 | yeah, but i'd prefer to have /etc/defaults/serial to export the right names. |
| 14:54.18 | pH5 | cr2: that's a very good idea. instead of splitting it over blueprobe/gsmd/whatever, have a single place that defines what the uarts are used for. |
| 14:54.20 | cr2 | mickeyl was playing with the alsamixer, so i could estimate the sound quality :) |
| 14:55.08 | cr2 | yes, it can read /proc/cpu and export the names depending on the $MACHINE |
| 14:55.11 | pH5 | I played some 20Hz-16kHz sweeps at full volume to check it out. ouch :) |
| 14:55.42 | cr2 | :) |
| 15:03.50 | *** join/#htc-linux _law_ (n=_law_@213.173.86.202) |
| 16:00.37 | *** join/#htc-linux TeringTuby (n=maarten@188-116-dyn.ipact.nl) |
| 16:04.19 | *** join/#htc-linux rob_w (n=bob@p213.54.38.2.tisdip.tiscali.de) |
| 16:12.18 | cr2 | pH5: the gsm mux proto is the same on himalaya. |
| 16:14.03 | pH5 | cr2: very good. I'm just about to pester gsmd-devel with some patches. |
| 16:19.09 | cr2 | ok. i've made some asic5 traces. |
| 16:23.08 | *** join/#htc-linux TeringTu1y (n=maarten@188-116-dyn.ipact.nl) |
| 16:31.29 | *** join/#htc-linux TeringTu2y (n=maarten@188-116-dyn.ipact.nl) |
| 16:41.51 | *** join/#htc-linux TeringTuby (n=maarten@188-116-dyn.ipact.nl) |
| 17:11.30 | *** join/#htc-linux TeringTu1y (n=maarten@188-116-dyn.ipact.nl) |
| 17:12.51 | *** join/#htc-linux TBBle (n=tbble@202.55.155.71) |
| 17:29.53 | *** join/#htc-linux drbombay[lap] (n=drbombay@pdpc/supporter/active/drbombay) |
| 17:52.27 | cr2 | pH5: what was pasic2 ? |
| 17:53.09 | pH5 | by extrapolation, the led/ds1wm chip on the blueangel. |
| 17:53.22 | cr2 | ok. thanks. |
| 17:53.24 | pH5 | on the magician it's pasic3 (in the wince code) or aic3 (printed on the chip) |
| 17:53.41 | cr2 | yes. |
| 17:55.46 | *** join/#htc-linux pleemans (n=peter@d51A5E76A.access.telenet.be) |
| 18:08.45 | cr2 | found owm irq on himalaya. |
| 18:13.00 | cr2 | the device is mostly identical to blueangel. |
| 18:14.02 | *** join/#htc-linux goxboxlive (n=goxboxli@206.80-202-161.nextgentel.com) |
| 18:16.16 | goxboxlive | hi all |
| 18:20.05 | goxboxlive | cr2: Why is such a hack we did to the pxafb so ugly? Is it because universal is the only one who take advatage of it? |
| 18:21.54 | cr2 | i'll add the LCCR4,5 and some PXA27x other registers to pxa-regs.h and the save/restore them in pxafb. |
| 18:22.22 | goxboxlive | ok souuds good, but why is it so ugly? It has nothing to do with ugly for the hardware, right? |
| 18:24.13 | cr2 | no. |
| 18:25.56 | goxboxlive | so it's only because other devices cant take advantage of it? |
| 18:26.38 | cr2 | pH5: are pasic2 irq and owm irq different ? |
| 18:26.51 | cr2 | what is the purpose of pasic2 irw ? |
| 18:30.11 | _law_ | Kevin2: i have to set mtype to 6665 (htc_tornado MACH_TORNADO TORNADO 6665) if my tornado should work... |
| 18:31.59 | *** join/#htc-linux TeringTuby (n=maarten@188-116-dyn.ipact.nl) |
| 18:33.10 | cr2 | _law_: this is braindead. where does your kernel source code from ? |
| 18:34.10 | _law_ | cr2: http://chac.le-poulpe.net/~nico/tornado/dl/ |
| 18:34.30 | cr2 | ok. so it's just a hack. |
| 18:38.39 | _law_ | cr2: k but setting mtype manual should work or? |
| 18:46.50 | *** join/#htc-linux FossiFoo (n=Fossi@e176101106.adsl.alicedsl.de) |
| 18:47.51 | goxboxlive | The zaurusd is setup with switches and not keys |
| 18:53.53 | cr2 | goxboxlive: that's why it's zaurusd. is it a binary ? |
| 18:54.49 | goxboxlive | cr2: no, i have compiled it with OE and just added universal to it |
| 18:55.25 | goxboxlive | but when starting it complaines about our kernel is missing swithces |
| 18:56.10 | cr2 | then it needs to be patched. |
| 18:57.20 | goxboxlive | ?? patched our kernel or zaurus source? |
| 18:57.40 | goxboxlive | I have addeduniversal to zaurusd source, not patching in OE |
| 18:58.36 | cr2 | i need to look at the zaurusd source. |
| 19:09.20 | goxboxlive | :-) |
| 19:27.47 | pH5 | cr2: no, afaik there is only the ds1wm irq on that chip. |
| 19:38.21 | *** join/#htc-linux SmallR2002 (n=SmallR20@88-108-221-159.dynamic.dsl.as9105.com) |
| 19:38.58 | cr2 | pH5: gpio12 is input http://wiki.xda-developers.com/index.php?pagename=HimalayaGPIO |
| 19:39.44 | cr2 | is there some "ready" signal? |
| 19:46.57 | cr2 | hm. where is this pasic3... |
| 19:58.25 | cr2 | green is LED1, red is LED0. |
| 20:24.21 | pH5 | the ds1wm has an interrupt register for several interrupts (TBE, RBF, etc.) that can be individually masked. it is generic (see mreimer's ds1wm driver). |
| 20:28.08 | pH5 | http://wiki.xda-developers.com/index.php?pagename=MagicianAIC3 has the pasic3 info. |
| 20:28.08 | cr2 | ok. i just can't find its location. |
| 20:28.35 | pH5 | But I'm missing my dump of the secondary registers. where did I put that... |
| 20:29.13 | cr2 | http://wiki.xda-developers.com/index.php?pagename=HimalayaMemoryMap |
| 20:32.05 | cr2 | blue led may be on asic5, i don't care about it right now. |
| 20:32.24 | cr2 | ah, i'm dumb. the last line. |
| 20:33.26 | cr2 | nothing there too. |
| 20:34.35 | pH5 | cr2: or it is connected to the ti bb. |
| 20:35.19 | cr2 | pH5: and the irq to asic3 ? |
| 20:35.43 | cr2 | i don't see anything useful in the battery.dll |
| 20:36.00 | cr2 | i'll look for a motherboard picture picture |
| 20:36.48 | pH5 | cr2: asic3? |
| 20:37.18 | cr2 | yes. |
| 20:37.45 | pH5 | how would I know about asic3, I only have a magician :) |
| 20:37.48 | cr2 | a9502a00 is referenced, but it's something related to the backpack pcmcia on asic5. |
| 20:38.03 | cr2 | the OWM irq is on asic3. |
| 20:38.13 | cr2 | but the asic3 OWM is not used. |
| 20:38.18 | cr2 | the same on blueangel. |
| 20:38.39 | cr2 | but on blueangel the blue led and owm are on pasic2. |
| 20:39.02 | pH5 | so the owm on pasic2 is used but the irq is chained through asic3? |
| 20:39.02 | cr2 | can't find it on himalaya. |
| 20:39.10 | cr2 | yes. |
| 20:39.22 | cr2 | don't ask me why :) |
| 20:39.44 | cr2 | on hx4700 and universal it's done in a normal way. |
| 20:39.58 | cr2 | owm on asic3 and blue led on LED2 |
| 20:40.02 | pH5 | http://www.xs4all.nl/~itsme/projects/xda/serial-protocols.html |
| 20:40.15 | cr2 | it's on wallaby. |
| 20:40.29 | cr2 | xda, not xda2. |
| 20:40.30 | pH5 | the wallaby had its leds controlled by the ti bb. maybe the blue led is still on the bb on the himalaya? |
| 20:40.49 | cr2 | himalaya is xda2. it's blueangel without wifi and keyboard. |
| 20:41.02 | cr2 | hm. don't know. |
| 20:41.13 | pH5 | hm.. it wouldn't make any sense. |
| 20:41.38 | pH5 | or wait, can you enable bluetooth without the gsm chip being enabled? |
| 20:41.49 | pH5 | blue led is only for bt on himalaya, right. |
| 20:42.59 | _law_ | hmm i think the /dev/ram0 is too small, so i cant boot any image.. does anyone know a tiny ramfs which i can use for testing |
| 20:43.06 | cr2 | yes. some bit on asic5 changes, maybe i'll check it manually. |
| 20:43.17 | _law_ | or how can i set the size of the ram? its 64mb or? |
| 20:57.40 | cr2 | ah. BP is backpack :) |
| 21:04.26 | *** join/#htc-linux goxboxlive (n=goxboxli@206.80-202-161.nextgentel.com) |
| 21:07.08 | cr2 | pH5: it's evil. the blue led is enabled by asic3 gpioa0 ;) |
| 21:08.41 | cr2 | the OWM is unreferenced in battery.dll |
| 21:08.52 | cr2 | hahaha. maybe it is not used at all. |
| 21:09.02 | cr2 | i'll search for the motherboard pictures. |
| 21:11.57 | cr2 | no. pasic2 is on the motherboard. |
| 21:12.01 | cr2 | http://forum.xda-developers.com/attachment.php?attachmentid=19821&d=1073841116 |
| 21:12.21 | cr2 | HTC AIC2 |
| 21:12.40 | cr2 | wtf? |
| 21:33.10 | *** join/#htc-linux TeringTu1y (n=maarten@188-116-dyn.ipact.nl) |
| 21:53.41 | *** join/#htc-linux TeringTuby (n=maarten@188-116-dyn.ipact.nl) |
| 21:54.08 | _law_ | i have testsed now 2 different cramfs files systems an always the /linuxrc cant be executed. i have compiled the kernel with gcc 4.x and the cramfs filesystem are build with gcc 3.3.2, could the be a problem? |
| 21:54.54 | *** join/#htc-linux Ralith (n=ralith@soggy202.drizzle.com) |
| 22:04.49 | cr2 | _law_: unlikely. |
| 22:06.10 | _law_ | hmm, so there is another problem, that no image can be executed... |
| 22:07.07 | *** join/#htc-linux alsuren (n=alsuren@host86-148-18-74.range86-148.btcentralplus.com) |
| 22:25.07 | _law_ | so i tried to whole stuff with the haret from (http://omap850.om.funpic.de/downloads/wizard/HaRET_omap.exe) with this version my kernel boots :-) |
| 22:36.52 | _law_ | is there a difference between boot and bootlinux in the default.txt ? |
| 22:48.21 | cr2 | _law_: i think it should be the same |
| 22:48.51 | _law_ | ok thank, need some sleep, n8 all |
| 22:50.51 | *** part/#htc-linux _law_ (n=_law_@213.173.86.202) |
| 23:21.17 | *** part/#htc-linux rmoravcik (n=rmoravci@pc-3s0zt5w2e4y0vzmhnrzq3a21zqajzfw.users.student.utc.sk) |
| 23:27.58 | Kevin2 | _law_: Yet another haret version, eh? :-) |
| 23:28.30 | Kevin2 | Are you saying the same kernel+initrd works on the wizard haret, and it does not work on latest mainline? |
| 23:30.29 | cr2 | Kevin2: he has already left. |
| 23:34.09 | Kevin2 | Hi cr2 |
| 23:34.35 | cr2 | hi |
| 23:34.53 | cr2 | what should we do with hermes ? |
| 23:35.39 | Kevin2 | I'm starting to think there is something wrong with the initial linux steps. I don't know what it could be though. |
| 23:36.01 | Kevin2 | The only thing I can think of is to add debugging info during the early boot and figure out where it is failing. |
| 23:39.01 | cr2 | s3c24xx_init_clocks(0) |
| 23:39.09 | cr2 | is it correct ? |
| 23:40.31 | Kevin2 | I don't know. |
| 23:40.55 | cr2 | <PROTECTED> |
| 23:40.55 | cr2 | <PROTECTED> |
| 23:41.24 | cr2 | so it's effectively s3c24xx_init_clocks(12000000) |
| 23:43.10 | cr2 | we need to come to 400MHz from that. |
| 23:47.14 | cr2 | what is the speed of rx3715 ? |
| 23:47.39 | cr2 | is runs with s3c24xx_init_clocks(16934000) |
| 23:49.28 | cr2 | rx1950 too. it has 300MHz CPU frequency. |
| 23:49.38 | cr2 | reading the CPU manual is required... |
| 23:56.08 | cr2 | <PROTECTED> |
| 23:56.08 | cr2 | <PROTECTED> |
| 23:58.42 | Kevin2 | I understand the need to get the clocks right. However, clock setup comes much later in the boot - my diagnostic output seems to halt pretty early. |
| 23:59.01 | Kevin2 | It's always possible my diagnostic stuff wasn't reliable, but it seems suspicious. |