IRC log for #htc-linux on 20081214

00:02.35rolkToo bad. No memory accesses via that big vm sections to that clk area when I unplug/ replug usb.
00:03.07rolkMaybe I just should try a simple search pattern :)
00:03.16rolkTomorrow, that is.
00:03.32rolkCheers, I'm getting some needed sleep.
00:04.05Bally3night rolk.. and thaks for the great efforts mate :)
00:04.42Bally3night all
00:04.55imfloflonight all
00:15.01*** join/#htc-linux chab7 (n=kvirc@212.92.4.114)
00:18.13*** join/#htc-linux nashpa (n=dliviu@dliviu.plus.com)
00:21.46swetlandtmzt: it's fsusb that we don't have any docs for
00:22.24tmzt_otg?
00:22.35swetlandwhich is an issue for 7200 which doesn't have the hsusb controller and only has fsusb
00:22.50tmzt_oh
00:23.03tmzt_this is a 7200 (polaris)
00:23.06swetlandyeah, the hsusb controller is otg capable, has a ehci host controller
00:23.33tmzt_it gets data aborts on any access to hsusb, which is nicely explained by it not having one
00:23.45swetlandyup, pure 7200 *only* has a fsusb controller and we never got docs for that part due to the company it was licensed from having gpl issues
00:25.17tmzt_16:25 < rolk> Then I get an "Unhandled fault: external abort on linefetch".  This is on the line "while((readl(USB_ULPI_VIEWPORT) & ULPI_RUN)  && (--timeout)) {"
00:27.02tmzt_16:56 < rolk> A number of writes to the memory-mapped io region that starts  with the MSM_HSUSB_PHYS address seem to, well, not cause a bus  error or page fault. In the usb_reset() function, I see the  following 'succeed':
00:27.06tmzt_16:57 < rolk> I/* RESET */
00:27.08tmzt_16:57 < rolk> Iwritel(2, USB_USBCMD);
00:27.11tmzt_16:57 < rolk> I/* INCR4 BURST mode */
00:27.24tmzt_16:57 < rolk> Iwritel(0x01, USB_SBUSCFG);
00:27.24tmzt_16:57 < rolk> Iwritel(0x12, USB_USBMODE);
00:27.24tmzt_16:58 < rolk> I/* select ULPI phy */
00:27.24tmzt_16:58 < rolk> Iwritel(0x80000000, USB_PORTSC);
00:27.24tmzt_16:58 < rolk> Iwritel(ui->dma, USB_ENDPOINTLISTADDR);
00:27.27tmzt_16:59 < tmzt_> so, you have printk's after those before the abort messages?
00:27.29tmzt_16:59 < rolk> My best guess is that the controller is not properly clocked.
00:27.32tmzt_16:59 < rolk> Yes, I have.
00:29.31tmzt_16:56 < rolk> A number of writes to the memory-mapped io region that starts  with the MSM_HSUSB_PHYS address seem to, well, not cause a bus  error or page fault. In the usb_reset() function, I see the  following 'succeed':
00:29.36tmzt_16:57 < rolk> I/* RESET */
00:29.38tmzt_16:57 < rolk> Iwritel(2, USB_USBCMD);
00:29.41tmzt_16:57 < rolk> I/* INCR4 BURST mode */
00:29.43tmzt_16:57 < rolk> Iwritel(0x01, USB_SBUSCFG);
00:29.46tmzt_16:57 < rolk> Iwritel(0x12, USB_USBMODE);
00:29.49tmzt_16:58 < rolk> I/* select ULPI phy */
00:29.51tmzt_16:58 < rolk> Iwritel(0x80000000, USB_PORTSC);
00:29.54tmzt_16:58 < rolk> Iwritel(ui->dma, USB_ENDPOINTLISTADDR);
00:29.56tmzt_16:59 < tmzt_> so, you have printk's after those before the abort messages?
00:29.59tmzt_16:59 < rolk> My best guess is that the controller is not properly clocked.
00:30.01tmzt_16:59 < rolk> Yes, I have.
00:30.04tmzt_.
00:30.06tmzt_16:56 < rolk> A number of writes to the memory-mapped io region that starts  with the MSM_HSUSB_PHYS address seem to, well, not cause a bus  error or page fault. In the usb_reset() function, I see the  following 'succeed':
00:30.11tmzt_16:57 < rolk> I/* RESET */
00:30.13tmzt_16:57 < rolk> Iwritel(2, USB_USBCMD);
00:30.16tmzt_16:57 < rolk> I/* INCR4 BURST mode */
00:30.18tmzt_16:57 < rolk> Iwritel(0x01, USB_SBUSCFG);
00:30.21tmzt_16:57 < rolk> Iwritel(0x12, USB_USBMODE);
00:30.23tmzt_16:58 < rolk> I/* select ULPI phy */
00:30.26tmzt_16:58 < rolk> Iwritel(0x80000000, USB_PORTSC);
00:30.28tmzt_16:58 < rolk> Iwritel(ui->dma, USB_ENDPOINTLISTADDR);
00:30.31tmzt_16:59 < tmzt_> so, you have printk's after those before the abort messages?
00:30.34tmzt_16:59 < rolk> My best guess is that the controller is not properly clocked.
00:30.36tmzt_16:59 < rolk> Yes, I have.
00:30.39tmzt_.
00:30.42tmzt_19:14 < rolk> I have a pdump from that area with usb plugged in:
00:30.44tmzt_19:14 < rolk> a8600000 | 2015fe2f 001b81d0 00000019 00000011 | /.. ............
00:30.47tmzt_19:14 < rolk> a8600010 | 00000001 00000055 00000000 00118000 | ....U...........
00:30.50tmzt_19:14 < rolk> and one with usb unplugged (a few seconds apart):
00:30.53tmzt_19:15 < rolk> a8600000 | 2015fc2f 001b83d0 00000019 00000011 | /.. ............
00:30.56tmzt_19:15 < rolk> a8600010 | 00000001 00000055 00000000 00118000 | ....U...........
01:12.51*** join/#htc-linux wasabi (n=wasabi@ubuntu/member/wasabi)
01:18.34*** join/#htc-linux ImCoKeMaN (n=imcokema@pool-98-111-118-30.hrbgpa.fios.verizon.net)
02:22.02*** join/#htc-linux snadge (n=snadge@starbug.ugh.net.au)
02:25.27*** join/#htc-linux Kensan (n=ken@gw.ptr-80-238-176-225.customer.ch.netstream.com)
02:34.07*** join/#htc-linux divinebovine (n=rtaylor@S01060016b6b53675.vf.shawcable.net)
03:14.24*** join/#htc-linux divinebovine (n=rtaylor@S01060016b6b53675.vf.shawcable.net)
04:05.03*** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz)
04:08.10*** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz)
04:15.25*** join/#htc-linux ionstorm (n=ion@ip68-228-225-247.ph.ph.cox.net)
04:18.40*** join/#htc-linux Xeon3D (n=xeon3d@89.152.18.153)
06:11.55maejrephmm, looks like cr2 had some useful results with the raph800 spl :x
06:12.02maejrepI had a feeling they would be substantially different
06:19.44parmasterand they weren't?
06:21.38parmasteror were?
06:45.44*** join/#htc-linux cr2 (n=konversa@crpl6.physik.uni-wuppertal.de)
06:47.38cr2rolk: you should add the CKEN tracing description for 0xa8600000 register, like it is done for the PXA CKEN in *pxa.py
06:48.37cr2the 0x200 bit is not in the wiki (?), it may be the usb clock
06:49.03cr2but these are only clock enable bits, you also need to find the divisor(s) location
06:49.13cr2check the raphale wiki for MSM_CLK
06:49.47cr2ok, leaving now :)
07:31.25maejrepparmaster, were
07:32.16maejrep<cr2> raph800 seems to be a substantially different device
07:32.16maejrep<cr2> from raph100
07:33.55parmasterthe raph100 is coming along nicely though isn't it?
07:35.21maejrepSeems that way .. I think now they're working on SD
07:35.31maejrepbut my raph800 doesn't boot with latest git :)
07:44.08*** join/#htc-linux lavender-t (n=jerrey@c-24-17-204-47.hsd1.wa.comcast.net)
07:45.36parmasteri'll have to pick up a T7272 then
07:50.21parmasteri'm having to back to an even earlier revision of gomunicator on the BA to be able to make calls
07:50.46parmasterits from 3 years ago
07:55.06lavender-tls
07:55.46lavender-toops wrong window ... :) but good morning/evening folks ...
07:57.30lavender-tanyone has a pointer how the sd clk A0/A4 are calculated ?
07:59.56*** join/#htc-linux marmotta (n=skodde@unaffiliated/skodde)
08:09.41*** join/#htc-linux lupine_85 (n=lupine_8@work.lupine.me.uk)
08:36.39*** join/#htc-linux lavender-t (n=jerrey@c-24-17-204-47.hsd1.wa.comcast.net)
08:45.31*** join/#htc-linux ChanServ (ChanServ@services.)
08:45.32*** join/#htc-linux ponicg (n=ponicg@ool-182d907a.dyn.optonline.net) [NETSPLIT VICTIM]
08:45.32*** join/#htc-linux infernix (i=nix@unaffiliated/infernix) [NETSPLIT VICTIM]
08:45.33*** join/#htc-linux mrmg (n=mrmg@spc1-bror4-0-0-cust383.asfd.broadband.ntl.com) [NETSPLIT VICTIM]
08:45.33*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring) [NETSPLIT VICTIM]
08:45.33*** join/#htc-linux nashpa (n=dliviu@dliviu.plus.com) [NETSPLIT VICTIM]
08:45.33*** mode/#htc-linux [+o ChanServ] by irc.freenode.net
08:45.40*** join/#htc-linux LunohoD (n=alex@e180068218.adsl.alicedsl.de) [NETSPLIT VICTIM]
08:51.23*** join/#htc-linux ionstorm (n=ion@ip68-228-225-247.ph.ph.cox.net) [NETSPLIT VICTIM]
08:51.23*** join/#htc-linux the_sys0p (n=the_sys0@cpe-75-85-249-111.bak.res.rr.com) [NETSPLIT VICTIM]
08:51.23*** join/#htc-linux zhobbs (n=zach@2.136.33.65.cfl.res.rr.com) [NETSPLIT VICTIM]
08:51.23*** join/#htc-linux defiant (n=add@p0pc0rn.eu) [NETSPLIT VICTIM]
08:51.23*** join/#htc-linux ecze (n=ecze@eczema.ecze.com) [NETSPLIT VICTIM]
08:51.41*** join/#htc-linux _ecze (n=ecze@eczema.ecze.com)
08:52.43*** join/#htc-linux ionstorm (n=ion@ip68-228-225-247.ph.ph.cox.net)
08:54.21*** join/#htc-linux rolk (n=rolk@ip5457417f.direct-adsl.nl)
08:56.58*** join/#htc-linux the_sys0p` (n=the_sys0@cpe-75-85-249-111.bak.res.rr.com)
09:03.14*** join/#htc-linux imfloflo (n=imfloflo@cap31-6-88-180-73-121.fbx.proxad.net)
09:06.34*** join/#htc-linux dj-d (i=dj-d@port0161-afl-adsl.cwjamaica.com)
09:07.22dj-dis there any cam fix for the htc-tilt
09:07.23dj-d?
09:12.27tmzt_kaiser?
09:12.47tmzt_don't know try the forums
09:22.34*** join/#htc-linux metter (n=metter@190.88.202.62.cust.bluewin.ch)
09:24.32*** join/#htc-linux goxboxlive (n=goxboxli@24.84-48-212.nextgentel.com)
10:12.33*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
10:14.34*** join/#htc-linux Uncle_CM (n=Uncle@ip-62-143-189-51.unitymediagroup.de)
10:26.50*** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo)
10:26.50*** join/#htc-linux Zoolooc (n=fredsiba@nrbg-4dbfc988.pool.einsundeins.de)
10:41.37*** join/#htc-linux pishuri (n=pishuri@194.230.146.209)
10:55.44*** join/#htc-linux rolk (n=rolk@ip5457417f.direct-adsl.nl)
11:19.35*** join/#htc-linux sebii (n=sebastia@adsl-89-217-147-30.adslplus.ch)
11:28.42*** join/#htc-linux metter (n=metter@190.88.202.62.cust.bluewin.ch)
11:32.16*** join/#htc-linux pishuri_ (n=pishuri@194.230.146.29)
11:47.45*** part/#htc-linux sebii (n=sebastia@adsl-89-217-147-30.adslplus.ch)
11:53.41*** part/#htc-linux pishuri_ (n=pishuri@194.230.146.29)
11:53.43*** join/#htc-linux pishuri_ (n=pishuri@194.230.146.29)
12:03.37goxboxlivehi BabelO
12:04.15goxboxlivei need some help. Do you remember how i change the led color on on leds? AFAIR i coulld do that without any recompilation right?
12:09.00BabelOgoxboxlive: hi, it is just done over sysfs
12:09.14BabelOgoxboxlive: /sys/class/leds
12:09.20BabelOfor each led you have a trigger
12:09.33BabelOthat say on which event led is linked
12:12.31goxboxliveBabelO: thx. i am trying this with a Squeezebox. My hifi componenets uses Blue led, while my squeezebox uses white when it is OK, and Blue when it's not conected to a music server. So i would like to just switch the colors so it look nice in my hfi rack :-)
12:15.07BabelOgoxboxlive: your box use deezer :) cool
12:15.33goxboxliveBabelO: what is deezer?
12:15.52goxboxlivefound it'
12:15.55BabelOgoxboxlive: http://www.deezer.com free online music
12:16.22goxboxliveand it uses last.fm
12:16.52*** join/#htc-linux Othello (i=Othello@gateway/tor/x-cef34a05b39e2e00)
12:18.15BabelOgoxboxlive: i don't like last.fm
12:19.30goxboxliveok, i havnet used it much, because the bitrate of the songs sucks. But it's ok to just check out a song if you like it and then go to the store and buy the cd.
12:20.07BabelOgoxboxlive: ok, deezer is same but with more common song
12:20.22goxboxliveok, i hve to check it out :-)
12:36.59*** join/#htc-linux kiozen (n=oeichler@rgnb-5d87d6f5.pool.einsundeins.de)
12:40.49*** join/#htc-linux Uncle_CM (n=Uncle@ip-62-143-189-51.unitymediagroup.de)
12:54.44*** join/#htc-linux BabelO (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
13:26.41*** join/#htc-linux rolk (n=robert@ip5457417f.direct-adsl.nl)
13:37.19*** join/#htc-linux tsdogs (n=tsdogs@net203-187-146.mclink.it)
13:46.15*** join/#htc-linux BabelO (n=fcr@lun34-2-82-238-28-28.fbx.proxad.net)
13:55.58*** join/#htc-linux stefan_schmidt (n=stefan@p5B03636E.dip.t-dialin.net)
14:11.11*** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz)
14:20.51*** join/#htc-linux lavender-t (n=jerrey@c-24-17-204-47.hsd1.wa.comcast.net)
14:31.42*** join/#htc-linux Moku (n=John@f054177242.adsl.alicedsl.de)
14:36.07*** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz)
14:36.23*** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz)
15:13.18rolkSomeone here interested in the Polaris/Kaiser USB device mode?
15:14.21dcordes_rolk, usb would be very useful.
15:14.50rolkDid you follow the discussion last night?
15:15.14dcordes_partly
15:15.43rolkI have something to add to the results of last night.
15:16.13dcordes_what did you find?
15:16.18rolkI was having 'external aborts' on read-access to ULPI_VIEWPORT register (that would be the interface to the external PHY).
15:16.35rolkI have tried read-accessing that same register while in WinMob,
15:16.43rolkand Haret reports no exception.
15:16.49rolkIt reads '00000000'.
15:17.37rolkThis means that there is definitely something wrong with the clock going to that USB device controller.
15:18.00rolkI enabled the clock (I think it is bit 9 in MSM_CLK_CTL).
15:18.11rolkBut someone mentioned setting the dividers properly.
15:19.15rolkFrom the Kaiser memory map, it seems that for the clocks with bits 7 and 8, the dividers are at +A0, +A4, +A8 and +AC. So, perhaps the dividers for the USB device controller block may be at +B0 and following.
15:19.55rolkI've made a dump of that area, and will check (not right now) whether the area when booting Linux is significantly different.
15:19.57dcordes_hm I can double check things on the kaiser if that helps
15:20.43rolkThe thing that worries me a bit is that someone mentioned that the MSM7200 only has a full speed controller. While the MSM7201 has a high speed controller.
15:20.59dcordes_7201A
15:21.12rolkThis probably also means that there are subtle or less subtle differences in the device controller registers.
15:21.27dcordes_swetland said that no? I thought the 7200 has hsusb all the time..
15:22.16NetRipperyes swetland said that
15:22.21rolkWhen I hook it up to a PC, it always reports the Polaris as a full speed device. This doesn't mean that it cannot do high speed, it could be a hs controller that is forced into fs mode.
15:23.04NetRipperin windows mobile, kaiser also is full speed, not high speed
15:23.16NetRipperi get low transfer rates when transferring files
15:23.28NetRipperas opposed to my raphael, which is clearly high speed
15:23.35rolkDamn. I'd really could use an MSM7200 programmers manual. Damn Broadcom for sueing Qualcomm.
15:24.23NetRipperswetland probably knows what he's talking about, being one of the trout developers
15:24.33NetRipper:)
15:26.23*** join/#htc-linux baz_ (n=baz@78-105-175-81.zone3.bethere.co.uk)
15:27.11rolkI heard that Qualcomm removed the detailed manuals for its chips from their websites when Broadcom filed a lawsuit against them for infringing some patents.
15:27.28NetRipperas far as i know they've never been up
15:27.44NetRipperbut i dont know details
15:29.13dcordes_no, there have never been such manuals. rolk maybe you mean the pdf brochures with the schematic?
15:30.19rolkNo. I don't know whether Qualcomm ever had them on their website (for the MSM*), but they used to have downloadable 'user manuals', just like Samsung has for its S3C2443 SoC.
15:30.58rolkA full description of the internal structure, busses and peripherals, with register layouts and all you'd need to implement a kernel for it.
15:31.44rolkBut I do know Qualcomm used to have (more) detailed manuals for their chips. Now you can only get them under NDA, I suppose.
15:33.35dcordes_didn't hear about that before
15:41.33rolkdcordes: do you know how I can monitor writes/reads to a range of physical addresses using Haret? I've seen an example of TRACE, but it adds one address to a watch list. I think I'm going to need to monitor a range of about 8K...
15:42.13*** join/#htc-linux STASON99 (n=stason-x@Border-R1.g-service.ru)
15:44.30dcordes_rolk, can't you put the base address and the offset?
15:45.39rolkI'd like to monitor what happens to the address range 0xa9800000 - 0xa9802000 when I plug in a usb cable and hook up the device to a PC.
15:46.18rolkAccording to the KaiserResearch wiki page, that would be the memory mapped I/O range for the USB controller.
15:50.13*** join/#htc-linux Bally3 (n=chatzill@cpc1-blac6-0-0-cust618.manc.cable.ntl.com)
15:51.57*** join/#htc-linux BHSPitLappy (n=BHSPitLa@unaffiliated/bhspitmonkey)
16:15.15*** join/#htc-linux TrinityDied (n=TrinityD@212-198-144-81.rev.numericable.fr)
16:18.43*** join/#htc-linux Xime (n=xime@dag94-3-82-233-170-230.fbx.proxad.net)
16:38.01AstainHellbringmorning
16:41.23*** join/#htc-linux ALoGeNoFF (n=QUAKEIII@43.Red-88-23-200.staticIP.rima-tde.net)
17:01.32*** join/#htc-linux Shinto (n=John@f048074102.adsl.alicedsl.de)
17:07.33*** join/#htc-linux LunohoD_ (n=alex@e180077185.adsl.alicedsl.de)
17:26.23AstainHellbringwhats new?
17:28.15*** join/#htc-linux stefan_schmidt (n=stefan@p5B033D71.dip.t-dialin.net)
17:59.14*** join/#htc-linux dcordes (n=dcordes@unaffiliated/dcordes)
18:05.44*** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo)
18:10.30dcordesrolk, were you able to get the traces?
18:26.11AstainHellbringwhatcha need traces of dcordes?
18:26.51dcordesrolk had a problem researching usb things on the polaris
18:27.31AstainHellbringahh ic
18:28.10AstainHellbringanything i can do to help with progress on raph800?
18:43.17*** join/#htc-linux rolk (n=rolk@ip5457417f.direct-adsl.nl)
18:43.36rolkdcordes: you there?
18:44.55dcordesrolk, yes
18:45.22rolkI saw your question but had to run. So, yes, I'm busy with those traces.
18:45.48rolkI have to learn Haret as I go, I do not quite understand the results I'm getting.
19:09.03*** join/#htc-linux chab7 (n=kvirc@212.92.4.114)
19:31.07*** join/#htc-linux TheOther (n=nahh@178.80-202-153.nextgentel.com)
19:35.19*** join/#htc-linux pishuri (n=pishuri@194.230.146.132)
19:43.07imfloflohttp://elinux.org/Android_on_OMAP
20:01.12*** join/#htc-linux Moku (n=John@g227130038.adsl.alicedsl.de)
20:08.15*** join/#htc-linux maejrep (n=madcoder@c-71-225-238-170.hsd1.pa.comcast.net)
20:21.20dcordes~seen dwaradzyn
20:21.22aptdwaradzyn <n=chatzill@chello089079197022.chello.pl> was last seen on IRC in channel #htc-linux, 1d 3h 9m 12s ago, saying: 'bbl'.
20:24.25*** join/#htc-linux tekkdrone (n=tekkdron@72.183.115.231)
20:27.34*** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz)
20:41.10*** join/#htc-linux rmoravcik (n=rmoravci@ip-89-102-255-171.karneval.cz)
20:48.04imfloflo~seen Bally3
20:48.06aptbally3 <n=chatzill@cpc1-blac6-0-0-cust618.manc.cable.ntl.com> was last seen on IRC in channel #htc-linux, 20h 43m 24s ago, saying: 'night all'.
21:07.24*** join/#htc-linux ionstorm (n=ion@ip68-228-225-247.ph.ph.cox.net)
21:21.18rolkOk. For those interested in the research into the USB device controller on Kaiser/Polaris.
21:22.29rolkI've done a comparision between the MSM_CLK_CTL_BASE registers (up to +0x100) with USB cable attached, both in WinMob and android-msm-htc-2.6.25.
21:23.03rolkThe content of these registers is the same, except for the ones at offset 0, 4 and 0x54.
21:23.47rolk0x54 is the backlight register, apparently, and it is switched low on my Polaris when USB cable is disconnected.
21:24.17rolkThe difference in the MSM_CLK_CTL_BASE+0x0 register is only in the 0x00000200 bit.
21:24.45rolkI suspect that is the USB controller clock enable, and I have added that to the clock.c
21:25.07rolkUnfortunately, this does not yet enable access to the USB controller.
21:25.23rolkI'm out of ideas.
21:31.26tmzt_http://electronicdesign.com/Articles/Index.cfm?AD=1&ArticleID=15784
21:32.57*** join/#htc-linux kimhoon (n=kimhoon@s559116c1.adsl.wanadoo.nl)
21:39.23tmzt_rolk: is it possible the fsusb and full-speed portion of hsusb or somewhat compatible?
21:42.48*** join/#htc-linux Bally3 (n=chatzill@cpc1-blac6-0-0-cust618.manc.cable.ntl.com)
21:43.27*** join/#htc-linux ionstorm (n=ion@ip68-228-225-247.ph.ph.cox.net)
21:45.29*** join/#htc-linux Guimli (n=guimli@ecu69-1-82-231-127-213.fbx.proxad.net)
21:47.43tmzt_http://www.mentor.com/products/ip/usb/usb20otg/phy_interfaces.cfm
21:47.59dcordeswe need usb support so our provider get more ARPU
21:48.18tmzt_yes, dcordes, think like a phone company
21:48.36tmzt_one that hasn't figured out how to own PSP sales yet
21:49.51tmzt_so if there's no HSUSB there's no ULPI???
21:50.42tmzt_http://www.intel.com/technology/usb/download/2_0_xcvr_macrocell_1_05.pdf
21:53.15tmzt_http://www.youtube.com/v/AWDurQrRt-Y&hl=en&fs=1
21:53.24tmzt_http://www.youtube.com/v/RcDqyEyC_HY&hl=en&fs=1
21:53.35tmzt_http://www.youtube.com/v/V0sOaIo6724&hl=en&fs=1
22:01.08dcordestmzt_, I wouldn't try that with my x1
22:01.23tmzt_not suggesting that
22:01.31tmzt_trying to find if the phy is seperate
22:01.52tmzt_http://www.pdacenter.ru/razborka/razbor-htc-touch-diamond/
22:02.00dcordeswhat's phy?
22:02.13tmzt_physical interface/transceiver
22:02.32tmzt_you have an x1 now?
22:02.41dcordesno
22:03.48dcordesso phy is the device that produces the signals on usb +/- pins?
22:04.01tmzt_yes
22:04.06dcordesI would like an x1 though
22:07.42rolktmzt: Thing is, I can read the ULPI_VIEWPORT register when in WinMob.
22:07.56rolkAnd when usb cable is attached.
22:08.20rolkWhen usb cable is unplugged, I can't read the same register. Haret reports an exception
22:08.33rolkjust like I get when trying to access that register from linux.
22:08.48rolkI think there is a PHY allright.
22:08.56rolkI also think I have enabled the clock.
22:09.34rolkAnd since the divider stuff is for SD card in the range MSM_CLK_CTL_BASE+0 ... +0x100, I expect that too for USB.
22:10.54rolkAs nothing changes in that area when plugging/unplugging, except for the backlight register and the clock enable bits, and I have that situation replicated in linux, and I still have no access to those registers, I suspect I  need to do more than that, but I can't imagine what.
22:30.37tekkdronetmzt_ did dzo ever release is libreference source?
22:30.42tekkdronehis*
22:31.01tmzt_tekkdrone: don't know, haven't heard from him
22:31.42tmzt_dcordes: do you know?
22:31.45tekkdroneI've got pxa27x-udc + the adb gadet up, and I have an adb shell to my apache for ez debugging
22:32.03tekkdroneand ttyS0 spits out AT commands, and I"m able to request network time
22:33.21tmzt_nice
22:33.25dcordestekkdrone, I know he sent them to people who ask for them. but don't know about release
22:33.31tekkdroneright on
22:34.01tekkdroneI'm at a loss as to where to head next, logcat is showing libref seg'ing out fairly quickly
22:34.15tekkdroneI diddled around with some links and ended up with a funk 10.64.64.64 address
22:34.22tekkdronefunky*
22:35.17dcordesI think the vogue libreference.ril used by dzo is based on the omap one with sources available
22:35.28tekkdroneI have noooo idea what I'm doing regarding the ppp configuration, is there a good place to find more reference?
22:35.38tmzt_<PROTECTED>
22:35.41tekkdroneI'm  pretty much using dzo's setupmodem and toggle, etc
22:35.45tmzt_what carrier is this?
22:35.47tekkdronevzq
22:35.50tekkdronevzw*
22:36.03tmzt_ok, just use vzw:vzw assuming you have the pda plan
22:36.24tekkdroneI do, i was using the olllllld info, number@vzw3g.com
22:36.29tekkdronehmmm
22:37.13tmzt_don't use that for pdas
22:37.35tmzt_doesn't work without a full plan on the other phones anyway
22:37.40tekkdroneright on
22:38.05tekkdronebooting android now so I can hop on the shell and fiddle a bit
22:47.59*** join/#htc-linux Tinyboom (n=nahh@178.80-202-153.nextgentel.com)
23:21.38*** join/#htc-linux br1ck (n=br1ck@xdslcy157.osnanet.de)
23:23.58*** join/#htc-linux fnord__ (n=fnord@24-151-90-116.static.nwtn.ct.charter.com)
23:44.51NetRipperdcordes, check forum, last post of jobo
23:50.48*** join/#htc-linux holycow (n=rtaylor@S01060016b6b53675.vf.shawcable.net)
23:51.57tmzt_he says X works?
23:53.00tmzt_http://members.home.nl/j0b0/zImage-mdptest-jobo (raph800)
23:56.55*** join/#htc-linux datachaos (n=datachao@189.27.166.151.adsl.gvt.net.br)

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