IRC log for #htc-linux on 20090418

00:14.43*** join/#htc-linux kri5 (n=kri5@cowdy.vlmc.org)
00:26.37*** part/#htc-linux exception13 (n=exceptio@testdrive.kgts.ru)
01:04.03*** join/#htc-linux Patrick_Bateman (n=swc@unaffiliated/swc666/x-4934821)
01:07.28*** join/#htc-linux swc|666 (n=swc@unaffiliated/swc666/x-4934821)
01:13.55*** join/#htc-linux zycho_ (n=zycho@dslb-088-070-254-107.pools.arcor-ip.net)
01:19.24*** join/#htc-linux zycho (n=zycho@dslb-088-070-254-107.pools.arcor-ip.net)
03:09.02*** join/#htc-linux mrmoku|e` (n=mrmoku@ppp-93-104-58-5.dynamic.mnet-online.de)
03:09.49*** join/#htc-linux Moult (n=Moult@60.54.42.64)
04:16.43*** join/#htc-linux exception13 (n=exceptio@testdrive.kgts.ru)
04:25.57*** join/#htc-linux _RZK333 (n=rzk@daemonet.ru)
05:33.08*** part/#htc-linux exception13 (n=exceptio@testdrive.kgts.ru)
07:01.03*** join/#htc-linux |John_A| (n=John_A@79.107.5.75)
07:05.49*** join/#htc-linux pigeon (n=pigeon@60-241-137-179.static.tpgi.com.au)
07:10.10*** join/#htc-linux AIVAnet (n=John_A@79.107.5.75) [NETSPLIT VICTIM]
07:10.10*** join/#htc-linux lordkiwi (n=root@h60088.upc-h.chello.nl) [NETSPLIT VICTIM]
07:51.22*** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo)
07:51.27*** join/#htc-linux MethoS (n=clemens@dyndsl-085-016-161-002.ewe-ip-backbone.de)
08:15.29*** join/#htc-linux lordkiwi (n=root@h60088.upc-h.chello.nl) [NETSPLIT VICTIM]
08:19.07*** join/#htc-linux SockPuppet (n=X@unaffiliated/egns)
08:22.53*** join/#htc-linux _chab7_3 (n=kvirc@fibhost-67-206-132.fibernet.bacs-net.hu)
08:58.39*** join/#htc-linux nebi_ (n=nebi@217.142.147.19)
09:04.19*** join/#htc-linux Amynecka (n=bedrunec@hellmachine.klfree.cz) [NETSPLIT VICTIM]
09:04.19*** join/#htc-linux madCoder- (n=madcoder@c-71-225-238-170.hsd1.pa.comcast.net) [NETSPLIT VICTIM]
09:04.19*** join/#htc-linux methril|fix_part (n=Methril@213.27.233.98)
09:04.19*** join/#htc-linux bodhiand (n=bodhi@89.121.200.106) [NETSPLIT VICTIM]
09:45.28*** join/#htc-linux timebomb (n=tb@d084211.adsl.hansenet.de)
10:43.06*** join/#htc-linux kiozen (n=oeichler@rgnb-5d87c9db.pool.einsundeins.de)
10:45.37*** join/#htc-linux fnord__ (n=fnord@24-151-90-116.static.nwtn.ct.charter.com)
10:59.34*** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz)
11:24.21*** join/#htc-linux cr2 (n=cr2@ip-90-186-81-17.web.vodafone.de)
11:26.17cr2~ping dcordes
11:26.18aptpong dcordes
11:26.27dcordespong
11:26.39cr2hi
11:26.45dcordeshi there
11:27.19cr2htcraphael_angstrom_defconfig
11:28.09cr2i'd like to document the nand partitions , and add nand support
11:28.28cr2but the android people should keep away from it :)
11:29.43dcordesassuming they don't want some google account info where spl is supposed to be
11:30.19cr2it needs to be clarified
11:30.37cr2druidu said that only the wince partition is visible
11:30.58cr2and the rest is shadowed by MPU
11:31.23dcordeswhat was it that provides the partition table to msm_nand ?
11:31.29cr2but the SPL can access the wifi eeprom and other goodies documented in wiki
11:32.52cr2btw, i've finally mounted my backup raid, so i'll look for the arm-related docs. where should i upload them
11:33.55cr2http://www.htc-linux.org/wiki/index.php?title=MSM_NANDID
11:34.03cr2http://wiki.xda-developers.com/index.php?pagename=MSM_NANDID
11:34.31cr2hm. sorry
11:34.33cr2http://www.htc-linux.org/wiki/index.php?title=RaphaelNAND
11:34.44dcordesok
11:35.14dcordesI proposed to create a folder in htc-linux.org for docs
11:35.34dcordeswe can then link in the wiki
11:35.43cr2ok
11:37.40cr2i suggest to create the 512K partition for the nand driver and mount it readonly.
11:37.58cr2if it will be SPL, then http://www.htc-linux.org/wiki/index.php?title=RaphaelNAND
11:38.49cr2if it will be some wince nk.exe, then it's something to think about.
11:39.44cr2because that means that the wince disables access to the upper part at boot
11:40.03cr2it is also necessary to check the
11:40.06cr2<PROTECTED>
11:40.42dcordeswhich was the case on non-A right? we were talking about "shadowed" location for the whole non wince stuff
11:40.50dcordess/location/section/
11:41.12cr2no, this table is from the A spl
11:41.18cr2A=raph100
11:45.03tmzthttp://lists.alioth.debian.org/pipermail/pkg-fso-maint/2009-April/000960.html
11:45.17tmztcan we get msm-ts support as a .config option?
11:45.29tmztdoes the experimental driver work?
11:47.12cr2tmzt: the non-android part ?
11:48.07tmztyes
11:48.25tmztthe link is for a tslib input driver for debian
11:48.57Moulthey guys just wondering
11:49.03tmzthello again
11:49.11Moultwill android one day evolve into something you can install over windows mobile?
11:49.14Moultthat'll replace it?
11:49.20tmztpossibly
11:49.38Moulteg one day google will say "hey download this file and run it on windows mobile and it'll get rid of WM and give you android"
11:49.45tmztcr2, cmonex says it's possible to replace oemsbl
11:50.06Moultif so, i hope that day comes sooner than later. i cannot wait to scrap WM
11:50.35cr2Moult: it's the goal, but we have not so much people and resources as googel ;)
11:50.41tmztdo you think the android bootloader could be used there? the one with source
11:51.10Moultcr2: well, either google or you guys come first, i don't mind either :) anything'll be better than WM
11:51.12tmztand this nand locking thing looks interesting, I'm going to read that again
11:51.16cr2tmzt: the oemsbl is even not in this flash list. i think you can reflash any part on NAND, once you will disable the MPU
11:51.35tmztbut it runs on arm9 also?
11:51.41Moultwhat's the progress so far with the OS you guys are doing?
11:51.53tmztand the parts communicate/call functions?
11:52.06tmztkernel?, Moult
11:52.24Moulttmzt: all you've got is a working kernel?
11:52.43cr2tmzt: the android botloader is too limited in scope. uboot may have been better.
11:53.23tmztbut it already has msm/amss support?
11:53.27Moultwhat about X? have you got X working on it?
11:53.38tmztwe would have to add that to uboot?
11:53.41cr2tmzt: oemsbl is mostly non-thumb code.
11:53.47tmztMoult: what device?
11:53.58Moulttry HTC Hermes?
11:54.05tmztoh
11:54.23cr2tmzt: i didn't check uboot source for a long time
11:54.27tmztXfbdev should work I think
11:54.53cr2Moult: hermes does not have an SD driver, that's the problem.
11:55.01tmztthe linwizard people are updating gpe
11:55.07tmztbut yeah, no sd
11:55.23Moultcr2: but other than that it can succesfully have your Linux OS installed on it with X?
11:55.29cr2you can run Xfbdev from initrd, but hermes has 64MB ram
11:55.39Moultand calls/sms/video calls/etc will work?
11:55.53dcordestmzt, do you know if linwizard tried framework yet?
11:55.54tmztcalls maybe with fso
11:56.02cr2Moult: somebody should check the hermes NAND with a more recent kernel
11:56.23tmztdcordes: no, don't know
11:56.26Moultoh, so it's still all hacked together?
11:56.30Moultin order to get things to work?
11:56.33tmztfoes it have extrom?
11:56.36cr2Moult: if NAND will work, it should be possible to flash linux in place of wince.
11:56.37tmztdoes
11:57.02tmztor somewhere that could be replaced without damaging ce install
11:57.04Moultcr2: you're referring to the method of replacing WM with Linux?
11:57.18tmztmaybe with raw yaffs2 on the mtd
11:57.31cr2Moult: no, NAND is your only option for storage on hermes now.
11:58.10Moulti'm sorry, can you just explain the current extent to which linux is working for htc hermes?
11:58.14dcordesI have to go. will be back later
11:58.16tmzthard reset could still recover it?
11:58.41cr2tmzt: no. you need to boot int SPL and reflash the wince image
11:59.08tmztI don't mean flash imgfs partition at all
11:59.32tmztstill boot with haret, install with usbnet/initrd
11:59.50cr2Moult: you can boot and telnet to it over usb. the keyborad works with .25 kernel from linuxtogo. the TS work afair. the rest needs some testing and minor hacking. the SD and LCD resume do not work.
11:59.50tmztmkyaffs2 on the tfat partition
12:00.06Moultcr2: TS?
12:00.09tmztcomplete linux install
12:00.12cr2touchscreen
12:00.20tmztbut you would not be able to boot
12:00.40tmztcmonex suggest replacing parts of uldr with haret
12:00.49tmztnot sure what she meant exactly
12:01.22cr2uldr=update loader.
12:01.27Moultcr2: is it not yet possible to install it such that it replaces WM? or only boot and telnet to it?
12:01.34cr2haret is wince program. what's the purpose ??
12:01.40tmztnot yet possible
12:01.49cr2Moult: only telnet.
12:02.00tmztto boot linux in place of wm without replacing spl
12:02.12cr2tmzt: uldr ~ zImage
12:02.19Moultis there another bootloader then that can replace spl?
12:02.25cr2tmzt: ok, you mean booting from spl ?
12:02.44Moultcr2: what about X, does it have a aGUI yet?
12:02.50tmztso the ce drivers for the ftl can be used
12:03.16tmztX won't fit very well in the initrd that takes up ram that it needs to run
12:03.19cr2tmzt: then it's easier to create an SD image for the older devices, or wrap the zimage+tags into .nbh
12:03.29tmztyeah
12:03.33tmzttags?
12:03.52Moultwell, a bit useless a phone that doesn't have a GUI :P
12:03.52tmztwe need a small bootloader to setup r0/r1 etc.
12:04.04cr2ah, you want to reuse the wince driver ?
12:04.11tmztbut openezx apprently has one that prepends zImage
12:04.49tmztcmonex said we could replace the uldr execuatble in a small bootable ce image with haret
12:05.01cr2tmzt: openezx is a completely different beast. it has a working bootloader with source
12:05.12tmztwhat did you mean by uldr ~ zImage
12:05.16cr2at least on a780
12:06.30tmztI know, but this is something WyrM I think to prepend a zImage and set the mtype
12:06.30cr2tmzt: zimage in place of the uldr may be nice.
12:06.30tmzts/M I/M made I/
12:06.32mickeylisn't there something like a lowlevel init when booting wm? I'd just hook there and leave flash alone forever
12:06.40tmztslow
12:06.44cr2ok, i didn't check openezx for a long time, because the only thing i'd like to check there is GPS
12:07.23tmztgne-blob is getting nice for a bootloader that can flash the phones
12:07.32cr2mickeyl: on hermes you can't use SD for boot. making NAND work is an easier option.
12:07.43mickeyloh that sucks
12:07.52tmztwe were talking about something like this for the motoq, since I have a spare one now
12:07.57mickeyli agree, for hermes it makes sense then
12:08.00mickeylnot for any other devices imo
12:08.22*** join/#htc-linux tsdogs (n=tsdogs@195.32.70.17)
12:08.25tmztand the other asic3-mmc ones
12:08.28tmztmaybe
12:08.47cr2yes, if you have working SD then SD is a better option.
12:09.15cr2tmzt: is there an asic3-mmc for the recent (sdio) kernels ?
12:09.23mickeylit's likely faster, it has more space, and it always leaves you with a working system, for several definitions of "working" ;)
12:09.54tmztcr2: don't know, I believe there was work on adapting tmio
12:09.59cr2tmzt: ATI SD != asic3-mmc, but it should be relatively easy to modify asic3-mmc into atiw288x-sd
12:10.14cr2tmzt: it's all 2+ years old.
12:11.12cr2mickeyl: using NAND saves mA's :)
12:11.38*** join/#htc-linux timebomb (n=tb@d027099.adsl.hansenet.de)
12:11.49tmztthe wm use of partition tables seems satble
12:12.03mickeylcr2: ya, that might be the only advantage for nand
12:12.20tmztit might make sense to look at a way to package the partition table as ATAG or otherwise from haret
12:12.50tmztcr2: do you know what ftl is used on msm devices in ce?
12:13.16tmztno2chem and cmonex didn't but suggested it wasn't trueffs
12:14.33cr2tmzt: trueffs was mdoc-only
12:15.18cr2tmzt: do they uses any ftl at all ?
12:15.56tmztdon't know
12:16.08tmztI see a filter driver in the registry
12:16.33tmztnot sure what it does
12:16.54cr2tmzt: sometimes they use ndis for a serial port or IR, but it's still an uart
12:17.01tmztdo you think reading partition table with haret makes sense?
12:17.14cr2tmzt: how ?
12:18.03cr2tmzt: adding the rawio call from itsutils as haret command will be a nice patch :)
12:18.24tmztyeah
12:18.41cr2and the fm radio control too.
12:19.00tmztno2chem is working on that also
12:19.07tmztbut what do you mean
12:19.16cr2tmzt: will he add it to haret ?
12:19.17tmztoh, in haret
12:19.37tmzthe's trying to use diamond rom which has it
12:19.57cr2the fm xda-dev guy posted the C api on my request
12:20.04tmzthe reports rssi of 240-255
12:20.24cr2ok
12:20.55cr2btw, i'd like to know which extusb pin is used for the antenna.
12:21.02cr2on raph et al.
12:21.34tmztthere must be a connection in the adapter to headphone jack
12:21.53tmztmine is not here and no meter either
12:22.05cr2it may be some tv/uart1 pin
12:22.51cr2damn, i need to buy the docking station and tvout cable ;)
12:23.40tmztneutv is supposed to attempt to enable tvout without detecting
12:23.44tmztnue
12:23.50tmztcheck his weblog
12:23.58cr2link ?
12:24.21tmztnuerom site
12:24.45cr2the tvout encoder is documented in wiki. we only need to find out the right MDP setup
12:25.05tmztthat's what I was wondering
12:25.17tmztwe need a mddi dumper in haret too
12:25.57tmztif this enables the encoder then the settings can be dumped
12:26.04tmztfind the site?
12:26.55cr2yes
12:27.34cr2DMOV is the DMA engine, not really the arm9-arm11 communication
12:28.00cr2all "opcodes" are located in the *.bts files
12:28.25cr2you can push them with hciattach -S *.bts texas
12:29.07cr2or even with the hcitool. if you are hardcore and use the decompiled .bts contents.
12:30.34cr2DMOV is used for the uart2DM here (uart_hs_)
12:30.41tmztyes
12:30.56cr2but to control the FM radio 115200 will be enough ;)
12:30.57tmztso bts programs dma not the bt chip?
12:31.14cr2you need dma for > 115200
12:31.31tmztthat -S is in upstream bluez 3.x right?
12:31.31cr2bts programms the chip
12:31.37cr2yes
12:31.41tmztso it would be on g1?
12:31.44cr2but you need to talk to the chip
12:31.45tmztcool
12:32.06cr2if they soldered the pins, yes.
12:32.15tmztcan you explain the opcodes in .bts then
12:32.23tmztI'm confused
12:32.31cr2wait.
12:32.50tmztI mean the -S option not fm
12:32.55tmzton g1
12:33.31cr2check hx4700
12:33.52cr2FMInit_2.bts
12:34.33cr2hmm. where is my bts decompiler...
12:36.03cr2# Description : BRF6350 2.0 FW 2.34 FM Initialization
12:36.21cr2# Compatibility: BRF6350 2.0 ROM w/ 2.0.34 Firmware
12:36.49cr2# FM ON
12:36.51cr2SEND_COMMAND: ogf=0x3f ocf=0x137 1 ->
12:36.52cr2ACTION_SEND_COMMAND: 0x01 0x37 0xfd 0x01 0x01
12:36.54cr2...
12:37.02*** join/#htc-linux utter0182 (n=dk@8afbf8ee.jrs.st-andrews.ac.uk)
12:37.03tmztis FMInit-2.bts somewhere?
12:37.11cr2SEND_COMMAND: ogf=0x3f ocf=0x135 9 ->
12:37.13cr2ACTION_SEND_COMMAND: 0x01 0x35 0xfd 0x09 0x65 0x06 0x00 0x00 0xde 0x06 0x16 0x01 0xf4
12:37.14cr2and so on
12:37.27cr2ls *.bts in \windows
12:37.48tmztogf? ocf?
12:38.16cr2FMInit_2.bts
12:38.26cr2it's BT terminology
12:38.39cr2FM_on_2_0.bts
12:38.53cr2FM_on_2_1.bts
12:39.33cr2if no2chem will write fm support for haret, it'd be nice of course :)
12:39.41tmztfm-on-2.0
12:39.44tmztyes
12:40.51cr2the api is known, and if something is missing, one can always disassemble the app.
12:40.57tmztso there's 2.0.x and 2.1.x firmware?
12:41.46tmztthe sizes are strange
12:41.56tmzt2.0 and fm-on are many k
12:42.11cr2we can't mmutrace dma
12:42.14tmzt2.1 is a 300 bytes
12:42.20tmztyeah
12:42.44cr2at least not reliably
12:43.24tmztbut if there a static buffers you could watch the memory?
12:43.30tmztdump dma regs
12:43.43tmztor dmov setup
12:43.50cr2trapping the HCI api should be easier.
12:44.45cr2if we will have uart2 support in linux, we can try to send .bts at 115200.
12:45.18cr2the spl picks the btaddr in this way.
12:45.37cr2afair also the vendor-specific ogf/ocf pair
12:47.09cr2Vendor-specific commands (OGF=0x3f):
12:47.18cr2http://wiki.xda-developers.com/index.php?pagename=UniversalBluetooth
12:47.27*** join/#htc-linux Kheops9871 (n=KoRoS@host-77-242-217-49.telecomitalia.sm)
12:48.07cr20x137 is fm on, and the 0x135 are some parameters.
12:48.52cr2fm on begins with
12:48.56cr2# FM ON
12:48.58cr2SEND_COMMAND: ogf=0x3f ocf=0x137 1 ->
12:48.59cr2ACTION_SEND_COMMAND: 0x01 0x37 0xfd 0x01 0x01
12:49.06cr2and the rest are 0x135 commands.
12:49.43tmztit would drop out of dm to send the fm commands?
12:51.20cr2#Send_HCI_VS_I2C_FM_POWER_MODE 0xFD37, 1
12:51.22cr2#Wait_HCI_Command_Complete_VS_I2C_FM_POWER_MODE_Event 5000, any, HCI_VS_I2C_FM_POWER_MODE, 0x00
12:51.33cr2it's the 0x137 command
12:51.58cr2the spl ?
12:52.20tmztsorry?
12:52.42cr2wince configures uart2DM for BT "7Mbit", and uses it.
12:53.08tmztso this like tea or si chip with interface over i2c?
12:53.28cr2internally
12:53.39tmztindividual registers have to be set?
12:53.41cr2brf6150 had i2c support too.
12:54.01cr2you talk .bts over BT, that's the "api"
12:54.16tmztorhci?
12:54.22cr2probably, but we don't have any docs.
12:54.36tmztor hci
12:54.38cr2.bts is sent with hci
12:54.46tmztyeah
12:54.51cr2so yes, hci commands.
12:55.42cr2if we will track single FM* api calls, we may correlate it with hci commands.
12:56.35tmztif we identify the i2c read/write commands
12:56.56tmztthere might already be a v4l or rockbox driver for a similar chip
12:56.58cr2it's a more difficult task.
12:57.12cr2because the i2c bus is behind the hci
12:57.34cr2you can't talk i2c directly.
12:57.53cr2otherwise it will have been trivial to trace.
13:03.23tmztyes, I mean hci commands to read/write on the i2c bus
13:04.10tmztpower mode is gpio?
13:05.04cr2brf has own gpios
13:05.26cr2there was a brf6150 .pdf diagramm
13:05.56cr2btw, you need AT@AUDIOSET=3 for FM
13:06.10cr2i think (=3), need to check
13:06.21tmztso it's handled by amss?
13:06.40*** join/#htc-linux _XD (i=t3st1fy@ircop.com)
13:06.50tmztI guerr only on ce amrr
13:08.10cr2amss handles audio swithcng
13:11.50*** join/#htc-linux StarLite (n=nnscript@s55916ca6.adsl.wanadoo.nl)
13:11.52*** join/#htc-linux cr2 (n=cr2@ip-90-186-81-17.web.vodafone.de)
13:12.02cr2yes, =3
13:28.19*** join/#htc-linux zycho (n=zycho@88.70.254.107)
13:58.49*** join/#htc-linux nebi_ (n=nebi@217.142.147.19)
14:10.21*** join/#htc-linux j0b0 (n=jobo@5ED40048.cable.ziggo.nl)
14:13.32*** join/#htc-linux j0b0 (n=jobo@5ED40048.cable.ziggo.nl)
14:14.50*** join/#htc-linux Shinto (n=John@f048159062.adsl.alicedsl.de)
14:22.02*** join/#htc-linux fnord__ (n=fnord@24-151-90-116.static.nwtn.ct.charter.com)
14:41.36*** join/#htc-linux j0b0 (n=jobo@5ED40048.cable.ziggo.nl)
14:49.12*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
14:57.10cr2hehe
14:57.35cr238400, 57600 and 115200
15:00.34dcordespossible baudrates for hci communication?
15:01.07*** join/#htc-linux Othello (i=Othello@gateway/tor/x-aa33d83e3569df28)
15:02.37cr2the uart config
15:03.17cr2i'm going through spl and writing comments. it's very helpful.
15:03.54cr2the usb part is interesting.
15:04.06dcordesnice. do you think usb host is possible?
15:04.26dcordesthat would allow for some zaurus kind of fun
15:04.42cr2it is possible.
15:04.51cr2but you need an adapter.
15:05.02cr2also for the uart1
15:05.20cr2it's going to be a maze
15:05.29dcordesright. did you receive your cable yet? what is necessary driver wise in order to make usb host work?
15:06.00cr2uart1, usb host, usb client, tvout, fm, headset...
15:06.12cr2hmm. to write the usb host driver ;)
15:07.08dcordesdo we have access to all information required in order to write the usb host driver?
15:07.30cr2tmzt: what is RAPHCONF.TXT ?
15:08.30cr2dcordes: no. g1 does not have host driver. only looking at the spl, it is possible to identify the registers that are used, and how they are used
15:21.00tmztraphconf?
15:21.34cr2yes. may be on the .nbh SD
15:22.29tmztfrom where?
15:23.00cr2read by spl
15:31.30*** join/#htc-linux MethoS (n=clemens@host-091-097-241-235.ewe-ip-backbone.de)
15:32.11cr2b1d*20
15:33.05cr2hm. pmdh
15:49.30cr2one more 0x24MB offset
15:53.42cr20xaa55fde9 ??
15:54.01cr2some fat signature ?
15:56.43cr2hm.
15:57.29cr20xe9fd header 0xaa55 at 0x200 offset
15:57.55cr2tmzt: is it the imgfs layout ?
16:00.56cr2yeah, looks like msfls50 .nb
16:01.33cr2ok, but then
16:01.36cr20x00420000   0x2400000 storage ?
16:02.04cr2is the wince
16:03.30cr2makes sense. but then you can blow away everything including spl ;)
16:04.16cr2then only oemsbl is your friend.
16:06.44cr2dcordes: now i really want to enable nand
16:08.09cr2offset c for serial ?
16:08.17tmztoh I see
16:08.38tmztso that is for a bootable goldcard?
16:09.23cr2+0x0c    UART_TF
16:09.38cr2tmzt: no, for NAND
16:10.05tmztwhat does qmat or the mkimage from eol generate?
16:10.30tmztI mean RAPHCPNF
16:12.02cr2RAPHCONF.TXT ? it's from the .nbh SD card
16:14.59cr2msm_write(port, xmit->buf[xmit->tail], UART_TF);
16:15.14cr2ok, so it was uart_write()
16:20.25cr292 #define UART_MREG               0x0028
16:20.27cr293 #define UART_NREG               0x002C
16:20.28cr294 #define UART_DREG               0x0030
16:20.30cr295 #define UART_MNDREG             0x0034
16:21.48*** join/#htc-linux dcordes (n=dcordes_@unaffiliated/dcordes)
16:23.27cr2this one goes to a separate channel
16:24.17cr2dcordes: back ?
16:24.34*** join/#htc-linux nebi_ (n=nebi@217.142.147.19)
16:26.14cr2okey, so it's possible to find the 38400, 57600 magic numbers too.
16:30.52cr2c0,b2,7d -> x9600
16:33.13cr2and 0x1c
16:33.20cr2ok, this is common.
16:33.24cr2484         msm_write(port, 0xC0, UART_MREG);
16:33.26cr2485         msm_write(port, 0xB2, UART_NREG);
16:33.27cr2486         msm_write(port, 0x7D, UART_DREG);
16:33.29cr2487         msm_write(port, 0x1C, UART_MNDREG);
16:34.25cr2dd, ff and ee
16:36.10cr2into +8
16:36.57cr242 #define UART_CSR        0x0008
16:36.59cr243 #define UART_CSR_115200 0xFF
16:37.00cr244 #define UART_CSR_57600  0xEE
16:37.02cr245 #define UART_CSR_38400  0xDD
16:37.21cr2ok. so the uart code will work.
16:37.42cr2if we will enable the uart_clk divisor...
16:40.19tmzthave you tried 2.6.29 or is this just because g1 takes the rate not individual components?
16:40.24tmztor
16:42.10cr2the code is identical
16:42.23cr2raph spl does not enable the uart clock.
16:42.34cr2it seems that it relies on oemsbl here ;)
16:43.32cr2or maybe  the M,N,D and UART_MNDREG is enough
16:43.48cr2still, g1 calls uart_clk enable
16:47.00cr2tmzt: what is the raph nand size ?
16:47.47cr2ROM capacity: 512 MB
16:48.08cr216*16*2
16:48.34*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
16:49.13cr20x20000000
16:52.22cr2interesting.
16:52.37cr2to enable the usb serial output, the vreg5 is reset.
16:53.09cr20,msleep 0x7d0, 0xb22
16:56.18cr2=0, sleep 2, =2.85V
17:07.07cr2gpio0 seems to be uart1 / h2w mux
17:08.31cr2so if you don't touch the extusb pins, and gpio0=0, then you have uart1 on extusb tvout pins.
17:19.43cr2there are several undocumented usb registers.
17:35.39no2chemhmm uart clock
17:35.48no2chemmsm_regime stuff?
17:37.02*** join/#htc-linux _XD (i=t3st1fy@ircop.com)
17:37.15no2chemi notice you don't have acpu_clk documented in raph research
17:37.34no2chemyou should look at G1 code for that
17:53.16cr2no2chem: it's not raph specific, so why bother
17:54.19cr2i'm trying to document the undocumented things, and everything raph-specific
17:56.50no2chemoh
17:56.52no2chemright
17:57.24no2chemso you have clock control functionality in linux?
17:57.59cr2partially
17:58.23cr2you mean cpu clock, or all other clocks ?
18:02.23no2chemcpu clock
18:02.35no2chem.. theres also this DVFM thing ive been trying to figure out
18:02.46no2chemapparently they have it working on the G1
18:02.55no2chemcpu clock = a11 clock
18:03.28cr2ok
18:03.48cr2i'm more worried about the peripheral clocks
18:03.59no2chemid understand why
18:04.09no2chemi guess you are still trying to get uart and stuff working
18:04.17no2chemstable, anyway
18:04.41cr2yes. uart2DM and bluetooth actually
18:04.51no2chemah
18:05.01no2chemive been messing with bluetooth uart lately..
18:05.13cr2then you can do funny stuff like FM, RDS and TMC
18:05.24no2chemthere is something weird about bluetooth on the raph800..
18:05.26no2chembluetooth uart
18:05.38cr2why ?
18:05.53no2chemwell, so the FM radio doesn't work on raph800
18:06.03no2chembut it works on the diam500... which is almost the same hardware
18:06.33no2chemfor whatever reason, in CE.... when the FM driver tries to talk to the bluetooth chip
18:06.45cr2raph500 or diam500 ?
18:06.47no2chemsending the HCI opcodes fail
18:06.50no2chemRAPH800
18:07.01no2chemit works on DIAM500 (CDMA diamond)
18:07.12cr2ok
18:07.17no2chemmaybe its a ce thing, but i used the same ROM image.. same problem
18:07.34no2chemsee, on cdma touch diamond i get this crap
18:07.34no2chem19:19:26 [D:BT] [BTU]SystemIdleTimerReset
18:07.35no2chem+sio_rs232_dm_transmit()
18:07.35no2chemsio_rs232_dm_transmit 1
18:07.35no2chem[BTU]sio_rs232_dm_transmit():send 7
18:07.36no2chemsio_rs232_dm_transmit 3
18:07.38no2chem19:19:26 [D:BT] [BTU]SystemIdleTimerReset
18:07.40no2chem3.sio_rs232_dm_transmit():uart_dm_imr=0x9
18:07.42no2chem+Tx call dmov_transfer
18:07.44no2chem-Tx call dmov_transfer
18:07.50no2chemthat i don't get on the cdma touch pro
18:07.52cr2different BT firmware ?
18:08.03no2chemsame, id hope
18:08.21cr2the same bts files ?
18:08.24no2chemyeah
18:08.32no2chemi made sure they were the same
18:08.36cr2ok
18:08.46no2chemfrom what it looks like.. dmov_transfer or whatever was failing
18:09.17no2chemso im guessing all this uart is done through the a9 maybe?.
18:09.18cr2different dma dev/channel ? weird
18:09.27cr2no
18:09.53no2chemwell
18:09.55no2chemactually
18:10.03cr2you only tell arm9 at@setaudio=3
18:10.07no2chemoh
18:10.23no2chemuart_dm has to be working though?.. because else the bt init scripts wouldn't have worked
18:10.39cr2yes
18:11.01no2chemso maybe it is a different BRF6350 firmware
18:11.16cr2maybe
18:11.17no2chemmaybe i can query the firmware version over HCI
18:11.24cr2yes
18:11.45*** join/#htc-linux DJWillis (n=djwillis@82-46-19-72.cable.ubr02.bath.blueyonder.co.uk)
18:11.46no2chemguess ill have to figure out the opcode
18:12.08no2chemdo you know if its possible to update the BRF6350 firmware? maybe it lives in nand somewhere..
18:12.21cr2i think hciaatach texas always reports the fw version
18:12.51cr2no, it lives in brf6350
18:13.05cr2but you can patch it through .bts
18:13.28cr2don't ask me how to do it though :)
18:13.30no2chemoh. so assuming im running the same bts
18:13.38no2chemthey should be functionally same yeah?..
18:13.57*** join/#htc-linux tsdogs (n=tsdogs@net203-187-146.mclink.it)
18:14.29cr2the bts patches are for a certain fw version
18:14.47no2chemoh
18:14.54cr2i don't know why htc should use a different version on raph800, but who knows
18:15.05no2chemwell, the script on the shipped raph800
18:15.10no2chemand the shipped diam500
18:15.15no2chemboth say firmware 2.11
18:15.20no2chemso im guessing they are the same.
18:15.22tmztnand on raph500?
18:15.34tmztsize
18:15.47cr2tmzt: do you have working FM ?
18:15.55tmztno
18:16.02cr2ok
18:16.05tmzthaven't tried the cabs
18:16.12no2chemthey don't work =p
18:16.24tmztjust reloaded everything again
18:16.25no2chemits a very strange problem, heh.
18:16.45no2chemmaybe the hardware isn't there, but i dont believe that =p
18:17.02tmztkeyboard issue is still here but I think it's s2u2
18:17.17cr2no2chem: the dma should not fail
18:17.19tmzttried on vzw?
18:17.41tmztI'm thinking the pcm link could be different
18:17.50tmzton cdma and gsms
18:18.23cr20xB1300150
18:18.23no2chemwell, like i said, it works fine on cdma diamond
18:18.29no2chemand its not the pcm link
18:18.34no2chemthat connects fine
18:18.35tmztI have the fm on scripts
18:18.45*** join/#htc-linux fnord__ (n=fnord@24-151-90-116.static.nwtn.ct.charter.com)
18:19.00tmztbut if it's different it could be different firmware
18:19.06tmztbut probably not
18:19.08cr20xB1300180
18:19.15no2chemit really just seems like the fm on scipts aren't working... for whatever reason
18:20.10cr2ok, so 2 usb registers are not documented in the g1 code.
18:31.32cr2hm. orr800 and 0rr200
18:31.41cr2the same 0xa00 that we see
18:32.16cr2& e00
18:32.34cr21110.0000.0000
18:32.50cr20010.0000.0000
18:33.00cr20100.0000.0000
18:33.27cr2ok, the top bit is cleaned too.
18:34.51kiozenhi cr2
18:34.56kiozendid GT compile?
18:34.56cr2hi kiozen
18:35.15cr2svn up did not show any patches
18:35.50kiozendid you try to remove the build path and to rebiuild
18:36.13cr2no. not on friday
18:37.21dcordescr2, now I'm back
18:37.21cr2kiozen: btw, even JOSM has routing plugin now :)
18:37.55cr2dcordes: i think that SPL & things are exposed in NAND too
18:38.16cr2dcordes: but i just need to build the kernel with nand support and check.
18:38.44kiozencr2: don't care, I never use routing, but I answer every request, that I wait for someone to do it
18:38.48cr2destroying spl sounds as a big fun
18:39.19kiozenstill look for a good replacement for my zire 21
18:39.33cr2kiozen: ok. i'm more interested in enhancing the geofererencer.
18:39.34kiozenlooks like all mobile phones are crap
18:39.41cr2hehe
18:40.04kiozenit's hillarious that a thing stuffed with features can't do the most simple things
18:40.18cr216/18bit color lcds like mA
18:40.30kiozenlike a decent calendar, a good address list and long term standby
18:40.37cr2blame m$
18:40.47kiozenno it's not m$
18:40.49tsdogskiozen: maybe this is of some interest http://www.gedanken.org.uk/software/routino/
18:40.58kiozeneven nokia, blackberry suck
18:41.06kiozenhi tsdogs
18:41.10tsdogshi btw
18:41.20cr2tsdogs: why there are no turn restrictions there ??
18:41.25cr2hi tsdogs
18:41.51kiozentsdogs: can you spend 15min to update translations?
18:41.57kiozenit's not much to do :)
18:42.04tsdogskiozen: ok.
18:42.35tsdogsJust drop me an e-mail when you plan to release and I'll update :)
18:42.58tsdogsI mean next time :)
18:43.17kiozenjust did a realease, but couldn't contact you, lost you mail and you wheren't in irc
18:43.28tsdogsok
18:44.13cr2tsdogs: i'll resubscribe to roadmap ML with a new e-mail
18:44.34kiozenthe blackberry curve 8900 is quite nice if they would lock that thing to just "our service and outlook only"
18:44.46tsdogscr2: good, actually only danny is working on it right now ...
18:45.00cr2ok
18:45.17cr2tsdogs: the routino is fun, because it's plain C :)
18:45.36kiozenthat's mor of a problem ;)
18:45.37cr2it's a pity there are no turn restrictions there.
18:45.38tsdogsyep
18:46.00cr2kiozen: the xml parser is done even without expat :)
18:47.13cr2tsdogs: i need to locate your polygon labeling patch, so we can submit it
18:47.45tsdogscr2: it was a hack
18:48.28tsdogsThough I have no idea if it still applies to current roadmap
18:48.34cr2tsdogs: but a really nice hack. at least the lakes finally had the names
18:49.06tsdogsthat's true, but I dubt it can go in as it is...
18:49.35cr2tsdogs: and i will probably port the postgres and grmn/shapefile buildmap code.
18:49.37cr2ok
18:50.02tsdogsthat'll be interesting
18:50.45cr2althougth the .mp parser will be better.
18:51.09cr2because preparing these shapefiles is PITA
18:51.59cr2and you can just use osm2mp.pl to create .mp
18:52.52cr2or i will modify the osm2mp.pl to create some ssplit-friendly output :)
18:57.50tsdogskiozen: http://195.32.70.240/tsdogs/openupload/www/?a=d&i=RxAn8i
18:59.22kiozentsdogs: fantastic, thanks :)
19:00.50tsdogskiozen: did you get it in german?
19:01.05kiozenI have done myself
19:01.19tsdogsno I mean was the page in German ?
19:01.23tsdogsthe web page
19:01.37kiozenno english
19:01.51tsdogshmm, your preference is english?
19:02.03tsdogsin the browser...
19:03.04dcordescr2, are you going to try nand?
19:05.20tsdogsbbl
19:14.13*** join/#htc-linux swc|666 (n=swc@unaffiliated/swc666/x-4934821)
19:15.02cr2dcordes: need to connect one more hdd where i have the linuxtogo source
19:15.27cr2dcordes: i've checked the oemsbl, it sets the 0xa00 for uart_clk
20:27.07*** join/#htc-linux Othello (i=Othello@gateway/tor/x-49c69d113707d15f)
20:52.38*** join/#htc-linux wirelessdreamer (n=dreamer@chrobd01.vailsys.com)
20:54.12wirelessdreameris power management working on raph with android or angstrom?
21:54.38*** join/#htc-linux ellisway (n=ellis@149.254.216.4)
22:24.23swc|666hopes this will be for sale soon http://www.exedamobile.com/web/index.php
22:26.30cr2swc|666: what about the screen resolution ?
22:26.36swc|666wow.. 2x8GB = add $19
22:26.37swc|666http://www.compulab.co.il/exeda/html/exeda-price.htm
22:26.39dcordesswc|666, 'Marvell PXA270 520MB CPU' 520MB, nice clock :)
22:26.52swc|666i think the specs are very nice overall
22:26.57cr2swc|666: pxa270 is good, but 128M is much less than my raph :)
22:27.02swc|666and I <3 the fact it has a qwerty
22:27.10swc|666ya 128mb ftl
22:27.27swc|666cr2, but still it is a fair trade off IMO
22:27.50cr2raph has sliding qwerty, so it can use the keyboard place for lcd.
22:28.09dcordes3Ah battery, nice
22:28.22cr2well, htc sable aka ipaq 6915 was like that with 240x240 screen.
22:28.34swc|666has a raph100
22:28.41cr2:)
22:28.56swc|666i dont like the tnetw1251 tho :/
22:29.09cr2at least it has a GPL driver
22:29.28cr2i don't like the gps receiver performance on raph100
22:29.46swc|666yea the gps sucks
22:29.48cr2because it's ultimate junk compared to sirf3.
22:30.02swc|666yep
22:30.46cr2i have 6915 too, but the 240x240 screen is too little ...
22:31.08cr2<PROTECTED>
22:31.26swc|666cr2, I bet the screen res on the Exeeda is 480 x 480
22:31.36cr2RS-232 port :D
22:31.55cr2it's not square
22:31.59swc|6662 x USB is my interest .. host + device
22:32.02cr2lookign at the screenshot
22:32.13swc|666480 x 420 maybe :p
22:32.18cr2pxa usbh, that's good.
22:32.26swc|666yep
22:32.31cr2my pna is 480x272
22:32.41cr2but pxa usbh is 1.1
22:33.10cr2this one is not 480x272
22:33.39cr2hmm. need to find out the aspect ratio from the screenshot
22:34.34swc|666nice...exeda NAVMAN Jupiter32 receiver module, Sirf-III chipset
22:35.01swc|666ah 640 x 480 VGA,
22:35.06swc|666http://www.compulab.co.il/exeda/html/exeda-datasheet.htm
22:35.59swc|666grr I wonder why they do not offer => 256mb
22:36.10cr2bah, gimp-2.6 has a different gui ;)
22:37.49swc|666really
22:38.49cr2wtf, how do i copy selection to a new window ??
22:39.40swc|666LoL
22:42.47cr2284x212pixels
22:43.04cr2i found a more brutal way to do it :)
22:43.58cr21.33962
22:44.20swc|666640x480.. basically the same as raph in landscape
22:44.33cr2480x360
22:44.57cr2yes, 640x480
22:46.10cr2but i think it's 320x240
22:47.21swc|666specs say its 640x480 vga
22:47.29swc|666http://www.compulab.co.il/exeda/html/exeda-datasheet.htm
22:47.37cr2yes, i see :)
22:47.46cr23.5" it's huge
22:47.51cr2+the keyboard.
22:48.02cr2it's more an industrial computer.
22:48.04swc|666<PROTECTED>
22:48.07swc|666yep
22:48.32cr2more like athena
22:48.49cr2also pxa270 624 +128MB ram, vga screen
22:49.14cr2but this one is gsm phone
22:49.39swc|666si
22:50.02swc|666i'm definitely going to purchase one
22:51.19cr2Connector for optional external antenna
22:51.39cr2but pxafb
22:53.07cr2Shock-resistant protection
22:54.27swc|666"Passed drop on concrete from a height of 6 feet testc" :0
22:54.42swc|666s/testc/test
22:54.50cr2wifi+minisd socket are muxed. that's not nice.
22:56.00cr2which wifi chip it uses ?
22:56.25cr2developer resources link does not work
22:56.53cr2.py
22:56.55cr2heh
22:56.57cr2http://www.compulab.co.il/exeda/html/exeda-developer.htm
22:57.27cr2Android - kernel and run-time image
22:57.29cr2wow
22:57.41cr2The requested URL /exeda/download/exeda-linux.zip was not found on this server
22:58.04cr2download is empty
23:01.14cr2lol. wince is cheap http://www.compulab.co.il/all-products/html/sw-package-price.htm
23:03.54swc|666Wi2Wi W2SW0001... based off of marvell 88W8686 :/
23:04.24cr2where is the kernel source  ?
23:04.52swc|666i dont see it anywhere yet
23:05.11swc|666only thing i can find is http://www.compulab.co.il/mediawiki/files/Linux/x270cm/linux-2.6.24-cm-x270.tar.gz
23:06.54swc|666cr2, question - was it ever determined ith the raph has usb host mode ability
23:06.55swc|666?
23:07.14swc|666s/ith/if
23:07.50swc|666i saw the patches for the vogue, but obviously != msm72xxA
23:09.17*** join/#htc-linux Moult (n=Moult@60.54.126.114)
23:11.15dcordesswc|666, you probably saw the htc-vogue branch patches that enables usb ethernet and mass storage
23:11.47dcordescr2 said host mode is possible on -A
23:11.57dcordeswe just need a driver (see today's log)
23:12.04swc|666loooks
23:12.40swc|666ah! :D
23:13.07swc|666cr2, get to coding!
23:13.09swc|666:D
23:13.30DunedanFor me working audio, wifi and bluetooth would be more important. ;-)
23:13.54dcordesmsm7xxx and msm7xxxA have a different usb chip
23:14.02swc|666well if usb host driver is in place, then an external usb wlan card is possible
23:14.09dcordesnon-A only has full speed
23:14.10swc|666i already have a power injector
23:14.38dcordesDunedan, :) how's debian?
23:14.59Dunedanwell, it works so far, including fso. But I couldn't get X working until now.
23:16.09swc|666Dunedan, which device
23:16.15Dunedanblackstone
23:16.22swc|666nice
23:16.47dcordesDunedan, did you try the uptodate fso? mickey|tv pushed some msm related patches
23:17.01cr2swc|666: tiacx driver is already there, for usb host i have found 2 unknown registers, and probably even more unknown bits in the known registers.
23:17.05Dunedandcordes: give me 10 minutes and I'll try
23:17.50cr2the usb host is used in spl to attach a miniUSB stick with RAPH*.nbh
23:18.18swc|666i c
23:18.26cr2the detection protocol is tricky, but should be doable. the usb host driver is more difficult.
23:18.29dcordesDunedan, it would be nice to have a debian with armv6-novfp binaries
23:18.57Dunedannovfp?
23:19.09cr2dcordes: can we add the vodafone ppp script to initrd ?
23:19.48dcordescr2, we could add one that is provider independent and accepts apn user pass as parameter just like the old ginge script
23:20.33cr2i don't have a pass
23:21.28dcordescr2, you can pass one anyhow
23:21.37cr2ok
23:21.48Dunedanaccess to the full ram would be also helpful :-/
23:22.12cr2Dunedan: it works on non-android
23:22.19Dunedanhow?
23:22.28DunedanI can only acces around 100MB of ram.
23:22.32dcordesDunedan, http://en.wikipedia.org/wiki/ARM_architecture#VFP
23:22.51cr2*cough* current git has it enabled.
23:23.03cr2i guess the android people are screwed.
23:23.23cr2that's why i want a non-android defconfig
23:23.35Dunedancr2: well, but shouldn't I need to configure the location via haret?
23:23.45dcordesdo you have one handy?
23:23.49cr2remove the mem=
23:23.52cr2it's enough
23:24.48Dunedandcordes: No updates for fso in debian available. But I can ask nomeata if he can push the latest fso-version into debian.
23:25.33Dunedancr2: nice. do you know since which revision it is enabled?
23:25.45cr2the non-android defconfig will be able to use nand too.
23:26.19dcordesDunedan, does the current debian package have a build from the unstable branch? afaik now there is only one branch used
23:26.32cr2http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=commitdiff;h=e202233f0b8e7156fa68f4d6bcd624f6e72514de
23:26.52cr2-#if 0
23:26.53cr2+#if 1
23:26.55cr2<PROTECTED>
23:26.59dcordescr2, can you paste the config somehwere so I can push it
23:26.59Dunedancr2: thanks
23:27.31cr2dcordes: i'll test nand, and then do a patch. probably tomorrow aka today
23:27.46dcordesok
23:28.11Dunedanhm, is this change also for blackstone, because the file is named *raphael* ...
23:28.14swc|666if you need a test rat for the raph100...
23:28.14cr2dcordes: i have a vacation for the next week.
23:28.16swc|666is here
23:28.52cr2swc|666: hehe. imvho you can destroy spl if nand goes crazy.
23:29.19swc|666:s
23:29.31cr2dcordes: btw, we need a solution for the poor 128MB sdram people.
23:29.48cr2and for the raph500 people with 64MB sram.
23:30.10dcordeswe can do it via machine type
23:30.31cr2hmm...
23:30.36cr2if it will work
23:30.44dcordesbut we lack raph500 machine type
23:30.48dcordesthere is only cdma raphael
23:31.08cr2aka raph800
23:33.11cr2the sram size is not really worth adding new mtype
23:33.20Dunedandcordes: I currently have fso 0.8.4.9-20
23:33.36Dunedan20090130
23:35.58Dunedandcordes: And why do we want armv6-novfp? Don't the devices support it?
23:36.40dcordesthe binaries run faster when they are opti
23:36.48dcordes..mized for the correct arch
23:37.23dcordesyou could benchmark a bit angstrom vs debian on the blackstone. that would be very interesting
23:37.59Dunedanbut isn't vfp an optimization?
23:38.20cr2isn't it hardware fp ?
23:38.25cr2which msm does not have ?
23:38.39DunedanThat has been my question.
23:39.00DunedanSo they don't have it and so we don't need it enabled?
23:39.16cr2the kernel does not use fp, so it's not really an issue
23:39.38cr2but the userland may profit from fp.
23:39.43cr2if your cpu has it ;)
23:41.20cr2dcordes: what is the purpose and usage pattern of GPU0 and GPU1 ? do we have a chance to use it in non-android setup ?
23:41.35cr2the ADSP and MDP are more of less clear.
23:41.46cr2s/ of/ or/
23:42.28dcordesDunedan, the fp is the one thing. the current 'official' debian arm builds are for armv4 afaik. we have armv6 so the extra instructions are not used
23:42.30cr2if not, these are 16MB more for something more useful.
23:43.07dcordesI have no idea about gpu
23:43.56dcordeswhat I do know is it would be very useful to have the full accerlation available for X
23:44.02cr2static allcation of 16MB may be good for some java stuff, but i don't really see a point right now.
23:44.36DunedanSeems like VFP should work with Debian armel: http://wiki.debian.org/ArmEabiPort
23:44.38cr2hehe. then you should disassemble the respective .so
23:45.00cr2i've already done it, and it's not fun to reimplement.
23:45.32dcordesso it would be nothing ground breaking, only more 'vram' ?
23:45.35cr2i'd simply say f*ck 3D.
23:45.41cr2unless somebody will do it.
23:46.26cr2yes, some double buffer, place for rotated images & such.
23:46.58cr2and, actually, i'd like to switch fb to 565. if it's possible with raph100 panel.
23:47.16cr2makes one more free megabyte.
23:53.40cr2default 7000 if MSM_AMSS_VERSION_WINCE
23:53.53cr2isn'T 5200 a better choice ?
23:57.47cr2<PROTECTED>
23:58.37cr2the tag can be added to haret though.
23:59.27cr264*2048=128K blocks

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