IRC log for #htc-linux on 20090615

00:00.20tmztit might be helpful to respond to the thread talking about how similar/simple smd itself is, and how the soft irqs work
00:00.35tmztsimilar to other msm devices
00:00.46cr2is there an "accelerated" audio infrastructure in linux ? like DRI ?
00:01.13tmztthe higherlevel stuff might be an issue but the basics of smd and proc-comm should really be merged/updated
00:01.19cr2smd depends on the smem layout
00:01.26cr2which is done by oemsbl
00:01.43cr2at least on g1 and raph100 the driver is generic enough.
00:01.46tmztwe also need to cleanup htc-fb or eliminate it if possible
00:02.02tmztyeah, we should move the cdma stuff to pdata
00:02.03cr2but on raph800 / vogue it is not so generic.
00:02.44tmztagain, something like .table-format could be used
00:02.54cr2proc_comm is actually the PMIC "driver"
00:03.00cr2so it's not msm-specific too.
00:03.36tmztif it's NONE read the entries from smd-channel-data
00:03.46tmztisn't pmic on sbi?
00:05.21*** join/#htc-linux cr2 (n=cr2@ip-77-24-93-240.web.vodafone.de)
00:05.25tmzthow is it not msm specific? or you mean the register structure is similar enough to other pmics that we should treat it like a hardware driver?
00:05.36cr2disconnected ?
00:05.42tmztyes
00:05.52cr2[02:00] <cr2> is there an "accelerated" audio infrastructure in linux ? like DRI ?
00:05.53cr2[02:01] <cr2> smd depends on the smem layout
00:05.55cr2[02:01] <cr2> which is done by oemsbl
00:05.56cr2[02:01] <cr2> at least on g1 and raph100 the driver is generic enough.
00:05.58cr2[02:01] <cr2> but on raph800 / vogue it is not so generic.
00:05.59cr2[02:02] <cr2> proc_comm is actually the PMIC "driver"
00:06.01cr2[02:02] <cr2> so it's not msm-specific too.
00:06.31cr2the only non-pmic part of proc_comm is gpio
00:07.00tmzt5:38 < tmzt> we also need to cleanup htc-fb or
00:07.00tmzt<PROTECTED>
00:07.00tmzt15:39 < tmzt> yeah, we should move the cdma stuff
00:07.00tmzt<PROTECTED>
00:07.00tmzt15:39 < cr2> but on raph800 / vogue it is not so
00:07.00cr2let's start pushing and bashing google with the gpio ALT patch :)
00:07.02tmzt<PROTECTED>
00:07.05tmzt15:39 < tmzt> again, something like .table-format
00:07.07tmzt<PROTECTED>
00:07.10tmzt15:40 < cr2> proc_comm is actually the PMIC
00:07.12tmzt<PROTECTED>
00:07.15tmzt15:40 < cr2> so it's not msm-specific too.
00:07.17tmzt15:40 < tmzt> if it's NONE read the entries from
00:07.20tmzt<PROTECTED>
00:07.23tmzt15:42 < tmzt> how is it not msm specific? or you mean the register structure is similar enough to other pmics that we should treat it like a hardware
00:07.26tmzt<PROTECTED>
00:07.28tmzt15:42 < cr2> disconnected ?
00:07.31tmzt15:42 < tmzt> yes
00:07.34cr2ok
00:07.53cr2i see it throught the Lag value
00:08.03cr2got 130 sec before ;)
00:08.28cr2proc_comm mainly talks to pmic.
00:08.41cr2and there are several msm pmic chips
00:08.58cr2the DEX/proc_comm may be a good abstraction
00:09.16tmztyeah
00:09.21cr2why did they add gpio to proc_comm is unclear to me
00:09.38cr2even htc has an rpc for gpio control
00:09.40tmztbased on what viperbjk said I think all of smem is just ram, no mmio at all
00:09.59tmztthe rtos picks up changes and makes the low-level change
00:10.00cr2if they do not want to manipulate arm9 gpios directly.
00:10.21cr2smem is ram. DPRAM if you'd lkike
00:10.51tmztor csmi on omap
00:10.58cr2but all out wince htc phones manipulate arm9 gpios directly.
00:11.18tmztthe thread also mentioned dsp stuff is a more traditional mailbox implementation
00:11.29tmztand that smd is 8k queues
00:11.40cr2yes
00:12.00cr2but you need to adapt to the specific sram layout.
00:12.24tmzthow extacly?
00:12.30cr2not alwaays 8k
00:12.49cr2can be 512byte
00:12.52tmztthat was from swetland on the thread
00:12.55cr2vogue/raph800
00:13.01tmztah
00:13.03tmztok
00:13.06cr2yes, on g1 and raph100 it's 8k
00:13.27tmztwhat's 512 on cdma?
00:13.27cr2and the sram layout is the same.
00:13.37cr2so g1 smd works on raph100 as is
00:13.50cr2AT and DATA
00:13.51tmztthe table is also not complete on there
00:14.15tmztthe multiple DATA channels?
00:14.16cr2with the stream patch, though (g1=raph100+stream patch)
00:14.35tmztstream patch?
00:14.48cr2which channel is packet and which is stream
00:15.06cr2it seems that the packet channel is a g1 innovation.
00:15.11cr2maybe because of  the qmi
00:16.15cr2imho google should do a major cleanup of their code
00:16.45cr2because they created a real PITA with it even for raph100 which is very similar to g1
00:17.46cr2whether they really want to do it, is another issue
00:19.00tmztah
00:19.02cr2if i was an arm maintainer, i will not accept the current arch-msm for a lot of reasons.
00:19.08tmztyeah qmi makes sense
00:19.22tmztfor them, I wish it did for us
00:20.42cr2we know the most pitfalls now, but it is still not clear how to cleanup this mess
00:21.51cr2i have applied the bt power+reset
00:22.13cr2now the kernel freezes on stty -F /dev/ttyHS1
00:22.27cr2it must be DMOV-related
00:22.31tmzthard to debug?
00:22.46cr2i dont' see the oops on the LCD
00:22.50cr2and usb is dead
00:22.58cr2i can ping raph, though
00:22.59tmztserial :)
00:23.07cr2yeah, soldering
00:23.16tmztdon't you have a cable for one of the other projects?
00:23.21cr2or redirecting thr console to tty0
00:23.39cr2no, i need to solder the docking station
00:23.43cr2hmm.
00:23.44tmztdo you have the update thread enabled?
00:23.59cr2we may try to resolve these fb problems too
00:24.33cr2i have the standard kernel from git
00:24.47tmztenable update
00:25.00cr2<PROTECTED>
00:25.05tmztwhen I disabled it I stopped getting oops
00:25.17tmztdo you have init code now?
00:25.32cr2which init ?
00:25.40tmztwe don't need more feedback than vibra anyway
00:25.40cr2add everything to git
00:25.44tmztlcd init
00:26.02cr2we have a separate setup for android, so we can do clean things for normal kernel
00:26.21cr2no. lcd init needs power gpios
00:26.50cr2and on epson* lcds it needs the SPI codes
00:26.51tmztcan we trace those on screen off/on?
00:27.04cr2which ones ?
00:27.13tmztgpios
00:27.21cr2they are known.
00:27.25tmztshort press power button
00:27.34tmztwhy don't they work then?
00:27.43cr2'setlcd 4' in haret
00:27.48tmztand mddi writes?
00:27.55cr2because we have not added them
00:28.04cr2mddi is ok
00:28.11cr2well.
00:28.15tmztwe need it for xip/mtd anyway
00:28.30tmztmddi writes to init lcd from the client chip
00:28.38cr2i have documented what wince does for mddi setup. g1 is a bit diufferent
00:28.45cr2but it still works.
00:29.12cr2not mddi itself, but the spi to the panel
00:30.34tmztspi direct to panel?
00:30.51cr2btw, i got another oops in the bt shutdown code, which i don't understand
00:30.52cr2yes.
00:31.03tmztif we had client drivers with correct register names
00:31.19cr2no
00:31.41tmztok, so that's not client at all, that's traditional tft module
00:31.44cr2you just need to query the LCD type over epson/toshiba gpios
00:32.02cr2and send the right spi sequences
00:32.15tmztI mean instead of magic handshake sequences like on trout
00:32.17cr2instead of the g1 sequences
00:32.57cr2they are not documented (afaik) but it's known where to pick them.
00:33.36AstainHellbringwow I walk away and miss a ton of stuff here
00:34.21tmztlogs are good
00:34.26AstainHellbringyep thats for sure
00:34.49tmztdo we know what lcm is used?
00:35.01tmztwe know cdma is different for some reason
00:36.00tmztwe could find out from viperbjk on diam100
00:37.01cr2yes , there are several lcdm used
00:37.11cr2just need to be documented.
00:38.22tmztthere are usually datasheets for those, if we treat mddi client like any other lcdc we can ignore it I think
00:38.55tmztbut at least we would know what spi commands do
00:39.09cr2hmm. i doubt that you'll get the lcm datasheet
00:39.15tmztmaybe find a secret 18bit mode on cdma
00:39.19tmztwhy?
00:39.28tmztyou think mddi is part of it?
00:39.30cr2even the moko phone does not have it
00:39.36cr2no, the spi
00:39.39tmztoh
00:39.50cr2the same magic spi sequences only.
00:40.15tmztok
00:40.17cr2i'd prefer a secret 565 mode on raph100
00:40.25tmztyeah
00:40.31tmztat least for X
00:40.42cr2yes
00:40.57tmztoh, Pre uses a similar screen flipping system to android
00:41.18tmztvyres*4 and "standard" ioctl
00:41.20cr2Pre ?
00:41.26tmztPalm Pre
00:41.41cr2which cpu is that ?
00:41.49tmztCDMA phone built on omap3410
00:41.58tmztwith msm6800 baseband
00:42.00cr2omap3. ok
00:42.03tmztcame with root
00:42.23cr2msm is on dpram ?
00:42.38tmztthrough a simple code and complex usb multiplexer process
00:42.46cr2or usb like on universal and hermes ?
00:42.51tmztdon't know yet, I think usb host
00:43.08tmztmaybe with some handshaking or wakeup gpios
00:43.08cr2ok, so it'S like uni/herm
00:43.29tmztI've been asking for lsusb -v -v in #webos-internals for 3 days
00:43.44tmztcat ~roc/interrupts would be useful as well
00:43.46cr2hehe
00:43.50cr2dmesg ?
00:44.04tmztno, I have .config though
00:44.42cr2i don't know omap3 internals
00:44.45tmztthey have a wiki now
00:45.15tmztI guess it's webos-internals.org
00:45.21tmztor webos-dev.org
00:45.26cr2ok, but it's not something new.
00:45.34tmztyeah
00:45.43tmztand not msm for ap
00:46.01tmztbut we knew that a year ago
00:46.03cr2the same on athena
00:46.26cr2pxa270+msm6275
00:46.29cr2of hermes
00:46.37cr2s3c2442+msm6275
00:47.10tmztanyway, brought that up because there is some work for dri on arm which would benefit us and omap3
00:47.21tmzteven for the offscreen buffers support
00:47.25cr2ok
00:47.30tmztand 3d later
00:47.49tmztdrm
00:47.50cr2well, we need to make sound work :)
00:47.54tmztnot dri
00:47.56tmztyes
00:48.15cr2i'm also thinking about gps
00:48.19tmztdo you think tracing ioctls on g1 will help?
00:48.42cr2since rpc is working now, even for adsp, it should be possible
00:49.09cr2yes, if you can trace the libgps.so calls
00:49.09tmzthaven't got rpc to really work
00:49.15cr2it's  thumb code there ;)
00:49.33tmztthe problem on android is everything is in a few processes
00:49.39cr2but i'd like to see the smem dump first
00:49.44tmzthard to strace
00:49.56tmztcan we fix /dev/mem?
00:50.16cr2my battery comes close to its end ;)
00:50.20tmztwe should be able to open pmem by removing a few checks
00:50.21cr2fix ?
00:50.42tmztis it just disabled?
00:50.50cr2just enable it in .config
00:50.58tmztAstainHellbring: did you get /dev/mem working?
00:51.02cr2yes, even on raph in the current git
00:51.08AstainHellbringnot yet tmzt
00:51.29cr2AstainHellbring: does gps work for you on g1 ?
00:51.33tmztwe can add printks's to ioctls as well
00:52.02cr2tmzt: where do you see gps ioctls ith source code ?
00:52.18tmztI don't?
00:52.36cr2the function names are more or less the same as on wince.
00:52.52cr2somehow i think that it's easier to do it on wince
00:52.55tmztL mean generally for tracing closed libraries on android
00:53.34cr2wince driver is more readable than this thumb mess on g1
00:54.05cr2the rpcs are already in wiki
00:54.28cr2init+register some clients+pdsm_get_position
00:54.38tmztI don't see anything related to msm in git grep gps
00:54.39cr2with 28 params ;)
00:54.51cr2libgps.so is closed source.
00:55.01cr2which program uses libgps.so ?
00:55.20tmztg1 uses nmea doesn't it?
00:55.29cr2+rpc
00:55.36cr2the same as raph100
00:55.38tmztI think thatqs for updating/saving ephemeris for fast start
00:55.59cr2not only i think
00:56.50tmzttarget/product/sdk gpstest
00:56.54cr2raph100 has nmea in smd27 and sends several rpcs
00:57.04cr2i think the same is true for g1
00:57.29cr2raph800 is more complex., because it does not have nmea smd27
00:57.51cr2sdk gpstest ?
00:57.59cr2can you like the source ?
00:58.06tmztinteresting, GPS-STATUS
00:58.10tmztNONE
00:58.17tmztSESSION BEGIN
00:58.18cr2debian says i have 30min left.
00:58.23tmztSESSION END
00:58.26cr2but it guess less
00:58.29tmztENGINE ON
00:58.34tmztENGINE OFF
00:59.20cr2link ?
00:59.22tmzt..
00:59.35tmztin repo, libhardware-legacy
00:59.37AstainHellbringcr2 yes gps works on g1
00:59.46cr2ok
01:00.12cr2tmzt: we may grab the libgps.so, but it's not my method ;)
01:00.17tmztcat /dev/smd27?
01:00.45tmztGPS STATUS
01:00.52tmztsorry
01:00.53cr2hangs without any updates
01:01.00tmztGPS POSITION
01:01.16tmztMODE STANDALONE
01:01.37tmztMODE MS BASED (SUPL MS-Based Mode)
01:01.52cr2yes, you send the pdsm_get_position() rpc, and (probably) get a nmea sentence(s) in smd27
01:02.18tmztMODE MS ASSISTED (SUPL MS-Assisted mode)
01:02.56cr2tmzt: PA and PD ?
01:03.42tmzthow many fields from rpc?
01:03.48tmztflags
01:03.52tmztdouble lat
01:03.57tmztdouble long
01:04.02tmztdouble alt
01:04.04cr2tmzt: check the MSM_RPC wiki page
01:04.13tmztfloat speed
01:04.14cr228
01:04.20tmztfloat bearing
01:04.25tmztfloat accuracy
01:04.30tmzttimestamp
01:04.33tmztah
01:04.37tmztmore then
01:04.54cr2double/float need some encoding
01:05.07cr2we don't have cpu fp support
01:05.07tmztrequested frequency of fixes in seconds
01:05.27cr2=2 in wince
01:05.44tmztright
01:05.57tmztthis is c code from android
01:05.57cr21 per 2 seconds
01:06.09cr2link ?
01:06.16tmztit says you can set frquency, 0 to get a single fix
01:06.16cr2i have 5 min left :)
01:06.19tmztrepo
01:06.26tmztI have it offline
01:06.33cr2direkt link please :)
01:07.22tmztlibhardware-legacy.git
01:07.36tmzthardware/libhardwanre-legacy.git
01:08.52tmzthttp://android.git.kernel.org/?p=platform/hardware/libhardware_legacy.git;a=summary
01:08.52cr2found
01:09.09tmztthere's a 7k hardware git also, didn't know that
01:09.13tmztor forgot
01:09.34cr2gps_qemu.c ?
01:10.11cr2gpsd reimplementation
01:11.04tmzthttp://android.git.kernel.org/?p=platform/hardware/msm7k.git;a=blob;f=libaudio/AudioHardware.cpp;h=b8b8566aacabacd0230739cb342db5e8a6ffc47e;hb=donut
01:11.15tmztyeah
01:12.00tmztthat's all there is, the rest is in libgps.so
01:12.08cr2hehe
01:12.19cr2where did you get these strings ?
01:12.55tmztinclude/gps.h
01:13.10tmztinclude/hardware-legacy
01:13.37cr2do we have /dev/msm_snd ?
01:57.23*** join/#htc-linux PoohbaLT (n=BlkPoohb@c-69-141-71-249.hsd1.nj.comcast.net)
02:01.11*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
02:43.20*** join/#htc-linux BHSPitLappy (n=BHSPitLa@unaffiliated/bhspitmonkey)
03:08.57*** join/#htc-linux mrmoku|a` (n=mrmoku@ppp-93-104-63-55.dynamic.mnet-online.de)
03:34.12*** join/#htc-linux wooj (n=wooj@unaffiliated/wooj)
03:34.59*** join/#htc-linux Tinyboom_ (n=nahh@206.84-49-89.nextgentel.com)
04:27.32*** join/#htc-linux droid001 (n=mc@p4FDCC71C.dip.t-dialin.net)
04:30.25*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
04:30.26*** join/#htc-linux BHSPitMonkey (n=stephen@unaffiliated/bhspitmonkey)
04:38.23*** join/#htc-linux davidb_csh (n=davidb@flourescence.rh.rit.edu)
05:01.17*** join/#htc-linux ltxda (n=anon@unaffiliated/ltxda)
06:02.21*** join/#htc-linux kiozen (n=oeichler@p5492168F.dip0.t-ipconnect.de)
06:06.42*** join/#htc-linux Squarc (n=Squarc@82-217-32-29.cable.quicknet.nl)
06:10.54*** join/#htc-linux Tinyboom_ (n=nahh@206.84-49-89.nextgentel.com)
06:22.02*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
06:39.19*** join/#htc-linux BabelO (n=fcr@unaffiliated/babelo)
06:50.20*** join/#htc-linux pleemans (n=toi@d51A49C45.access.telenet.be)
06:50.46*** join/#htc-linux goxboxlive (n=goxboxli@237.80-202-137.nextgentel.com)
07:16.03*** join/#htc-linux Shinto (n=John@f048016163.adsl.alicedsl.de)
07:35.39*** join/#htc-linux Tinyboom_ (n=nahh@206.84-49-89.nextgentel.com)
07:48.24*** join/#htc-linux JuNu_KN (n=chatzill@p549ABD7B.dip0.t-ipconnect.de)
08:12.54*** join/#htc-linux timebomb (n=tb@f054127247.adsl.alicedsl.de)
08:20.19*** join/#htc-linux BabelO_ (n=fcr@unaffiliated/babelo)
08:24.59*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
08:35.49*** join/#htc-linux goxboxlive (n=jrs@mail2.hjellnesconsult.no)
08:51.29*** join/#htc-linux Tinyboom_ (n=nahh@206.84-49-89.nextgentel.com)
08:56.32*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
09:07.03*** join/#htc-linux timebomb (n=tb@f054127247.adsl.alicedsl.de)
09:16.37*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
09:23.11*** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz)
09:27.09*** join/#htc-linux zycho (n=zycho@dslb-088-070-242-216.pools.arcor-ip.net)
09:38.04*** join/#htc-linux zycho_ (n=zycho@dslb-088-070-242-216.pools.arcor-ip.net)
09:39.20*** join/#htc-linux IamSOG (n=IamSOG@218.19.247.28)
09:48.39*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
10:01.38*** join/#htc-linux MethoS (n=clemens@host-091-097-242-021.ewe-ip-backbone.de)
10:08.36*** join/#htc-linux Tinyboom_ (n=nahh@206.84-49-89.nextgentel.com)
10:09.48*** join/#htc-linux DJWillis (i=djwillis@82-46-19-72.cable.ubr02.bath.blueyonder.co.uk)
10:28.37*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
10:32.51*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
10:40.06*** join/#htc-linux goxboxlive (n=jrs@mail2.hjellnesconsult.no)
10:58.36*** join/#htc-linux dcordes (n=dcordes@unaffiliated/dcordes)
10:59.10tmzthttp://article.gmane.org/gmane.linux.kernel/851842
10:59.23tmztgpio-alt-func in gpiolib
11:01.40kri5hello there
11:02.25kri5does anyone is working on "android revival project" for htc blackstone support?
11:04.05*** join/#htc-linux yoyey (n=yoann@82.237.160.83)
11:05.25tmztrevival?
11:06.27tmztwe are working on rpc for sound, audio routing, gps, replacing the initial console with proper lcd init, integrating upstream work, etc.
11:06.41tmztnot sure how that applies to blak at the moment
11:07.04tmztbut without it supporting all A devices including new ones will be much harder
11:09.37*** join/#htc-linux Tinyboom_ (n=nahh@206.84-49-89.nextgentel.com)
11:11.36*** join/#htc-linux DJW|Home (i=djwillis@82-46-19-72.cable.ubr02.bath.blueyonder.co.uk)
11:16.40*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
11:24.15kri5http://forum.xda-developers.com/showthread.php?t=524898
11:24.35kri5developement for blackstone seemed to be stopped
11:24.43kri5so tuxhero initiated this
11:25.03kri5i'd like to know if there were people working on this :)
11:25.23tmzt> +       clk_enable(msm_port->clk);
11:25.23tmzt> +
11:25.23tmzt> +       msm_write(port, 0xC0, UART_MREG);
11:25.23tmzt> +       msm_write(port, 0xB2, UART_NREG);
11:25.24tmzt> +       msm_write(port, 0x7D, UART_DREG);
11:25.27tmzt> +       msm_write(port, 0x1C, UART_MNDREG);
11:25.42tmztcr2: this is in proposed upstream patch
11:25.43*** join/#htc-linux timebomb (n=tb@85.182.255.196)
11:27.47kri5tmzt: otherwise, can you indicate me where i can found some resources/tutorials/docs on how does the linux kernel works for embedded devices
11:27.52kri5i'd like to participate
11:28.02kri5i have skills on many languages
11:28.30kri5but i just don't know anything on kernel drivers devel
11:28.43kri5and less on embedded
11:33.22tmztI would suggest reading code
11:33.45tmztwhat driver are you looking to implement
11:36.26Elleois HaRET's CRC reliable when performing a ramboot as well as a boot?
11:37.14Elleoas it fail's when I use boot, but the kernel passes when doing a ramboot (tags still fail though)
11:38.39kri5tmzt: i don't care, where do you need help :)
11:38.41kri5?
11:39.28tmztElleo: ramboot is for build a .exe wit kernel/initrd built in
11:39.46tmztkri5: well, mostly research right now
11:39.59Elleoah, so ramboot doesn't use the supplied zImage at all
11:40.22tmztthere aren't too many actual drivers that need written
11:40.47tmztlook at the tree, the files in arch/arm/mach-msm
11:40.54tmztElleo: no
11:41.15Elleookay, thanks
11:41.17tmztElleo: what device/what are you trying to do?
11:41.36Elleotmzt: Acer m900, trying to add support for it
11:42.13kri5tmzt: ok i'll take a look
11:42.15tmztok
11:42.22tmztacer?
11:42.29tmztnot eten
11:42.31Elleotmzt: well, e-ten really
11:42.37Elleobut e-ten were bought by acer a while back
11:42.41Elleoso it's branded as being acer now
11:42.49tmztsame as glofiish?
11:42.55Elleoyeah
11:43.08Elleoit's the next model on from the m800
11:43.23tmzttalk to stefen_schmidt when he's here
11:43.43tmzthow far have you got?
11:44.15Elleowell I can get to the point where HaRET should hand off to the kernel
11:44.20Elleobut the kernel seems to be getting corrupted
11:44.37Elleohowever I'm having trouble a bit before that shutting down all the DMA controllers
11:44.56tmztyou can't boot at all?
11:45.19Elleoif I try and shutdown the last 2 controllers (out of 4) the system just hangs; but it sounds like I need to do something extra with those as they're secure DMA controllers
11:45.24Elleonope
11:45.29tmztis fbduringboot enabled?
11:45.42tmzthow do you know it hangs?
11:45.48tmztafter go go go?
11:46.02Elleoyeah I get output from HaRET in the frame buffer
11:46.33tmzthow do you know it's crc though, it could be something kernel
11:46.44tmztwhat display driver does it use?
11:46.54Elleoit never really starts the kernel
11:47.05Elleoat least I never get any output from earlyprintk or anything
11:47.09tmzthow do you know that?
11:47.11Elleoand it fails HaRET's CRC check
11:47.18tmztyou have serial?
11:47.23Elleowhich would seem to suggest it's getting corrupted
11:47.38tmztwhat message do you get about crc?
11:47.39kri5tmzt: for now, you're mostly trying to find out how the hardware works?
11:47.52tmztyes
11:48.20Elleotmzt: "Checking tags CRC...FAIL FAIL FAIL" "Checking kernel CRC...FAIL FAIL FAIL"
11:48.26tmztbut like I've said, I don't really know much about blak, it's state, etc.
11:48.34tmzthuh
11:48.48tmzttalk to Kevin2 is all I can really say
11:48.52Elleobut I'm wondering if it's down to a couple of the DMA controllers still being active and possible doing nasty things to the memory
11:49.05tmztdoes it get to go go go without that enabled?
11:49.20Elleotmzt: it gets beyond Go go go, this is after that
11:49.33Elleoit creates the checksum before go go go, then tests it after
11:49.35tmztthere is nothing after that
11:49.53Elleotmzt: on the framebuffer there is
11:49.54tmztlook at haret code
11:50.03tmztthere is what?
11:50.09Elleoharet does Go Go Go, then it does the machine specific shutdown stuff
11:50.17Elleothen it does the mmu trampoline
11:50.22Elleoand crc check
11:50.28Elleoand then tries to hand off to the kernel
11:50.28tmztsorry, it says "at this point we are no longer running" in the code
11:50.46tmztok, what cpu and video?
11:51.06Elleoit's a samsung s3c6410
11:51.23tmztbuitl in video?
11:51.28Elleoyeah
11:51.34tmztok
11:51.49tmztKevin2: ping
11:54.43tmztsee if he can help you when he gets here
11:54.48Elleothanks :)
12:13.30*** join/#htc-linux BabelO_ (n=fcr@unaffiliated/babelo)
12:24.04*** join/#htc-linux miknix (n=miknix@gentoo/developer/miknix)
12:30.12*** join/#htc-linux Tinyboom_ (n=nahh@206.84-49-89.nextgentel.com)
12:42.31*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
12:54.44*** join/#htc-linux timebomb (n=tb@85.182.255.196)
13:02.11*** join/#htc-linux Tinyboom_ (n=nahh@206.84-49-89.nextgentel.com)
13:10.38*** part/#htc-linux yoyey (n=yoann@82.237.160.83)
13:26.37*** join/#htc-linux syn-fin (n=alien@66.165.162.68)
13:29.30*** join/#htc-linux goxboxlive (n=goxboxli@237.80-202-137.nextgentel.com)
13:29.40*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
13:37.50*** join/#htc-linux wooj (n=wooj@unaffiliated/wooj)
13:40.58*** join/#htc-linux methril|work (n=Methril@213.27.233.98)
13:46.24*** join/#htc-linux MethoS- (n=clemens@host-091-097-243-034.ewe-ip-backbone.de)
13:55.29*** join/#htc-linux xsacha (n=sacha@123.100.137.226)
13:55.33xsachahey guys
14:02.49AstainHellbringhi
14:03.36IamSOGyo yo
14:10.16*** join/#htc-linux jpm1234 (i=82124ba8@gateway/web/ajax/mibbit.com/x-ad4c0c22f1352a42)
14:12.08*** join/#htc-linux timebomb (n=tb@85.182.255.196)
14:14.58*** join/#htc-linux sdt555 (n=titus@147.145.40.44)
14:18.30*** join/#htc-linux yoyey (n=yoann@82.237.160.83)
14:18.49*** part/#htc-linux yoyey (n=yoann@82.237.160.83)
14:20.36*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
14:22.32*** join/#htc-linux marmotta (n=skodde@unaffiliated/skodde)
14:24.50*** join/#htc-linux pleemans (n=toi@d51A49C45.access.telenet.be)
14:34.09*** join/#htc-linux melgurth (n=melgurth@abfu154.neoplus.adsl.tpnet.pl)
14:34.46*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
14:36.07*** join/#htc-linux timebomb (n=tb@85.182.255.196)
14:48.27*** join/#htc-linux j0b0 (n=jobo@5ED40048.cable.ziggo.nl)
14:51.11*** part/#htc-linux sdt555 (n=titus@147.145.40.44)
15:22.36*** join/#htc-linux solerant-dc (n=kamikaze@adsl-99-147-76-3.dsl.hstntx.sbcglobal.net)
15:26.43*** join/#htc-linux Tinyboom_ (n=nahh@206.84-49-89.nextgentel.com)
15:29.24*** join/#htc-linux onen|openBmap (n=onen@mry91-1-89-87-198-158.dsl.club-internet.fr)
15:31.01*** join/#htc-linux wooj (n=wooj@unaffiliated/wooj)
15:36.17*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
15:37.28*** join/#htc-linux pH5 (n=ph5@e178210068.adsl.alicedsl.de)
15:46.15*** join/#htc-linux yoyey (n=yoann@82.237.160.83)
15:46.46*** part/#htc-linux yoyey (n=yoann@82.237.160.83)
15:57.16*** join/#htc-linux Tinyboom_ (n=nahh@206.84-49-89.nextgentel.com)
16:14.48*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
16:23.24*** join/#htc-linux kiozen (n=oeichler@rgnb-5d87cc11.pool.einsundeins.de)
16:32.22*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
16:59.54*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
17:05.00*** join/#htc-linux Squarc (n=Squarc@82-217-32-29.cable.quicknet.nl)
17:27.26*** join/#htc-linux pH5 (n=ph5@e178222215.adsl.alicedsl.de)
17:41.01*** join/#htc-linux MLM (n=mlvdmeid@5ED0BCBD.cable.ziggo.nl)
17:44.20*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
17:52.53*** join/#htc-linux Tinyboom_ (n=nahh@206.84-49-89.nextgentel.com)
17:54.33*** join/#htc-linux chab7 (n=kvirc@fibhost-67-206-132.fibernet.bacs-net.hu)
18:08.36*** join/#htc-linux pleemans (n=toi@d54C2AAB7.access.telenet.be)
18:08.47*** part/#htc-linux high-rez (n=gus@carrera.bourg.net)
18:08.50*** join/#htc-linux high-rez (n=gus@carrera.bourg.net)
18:09.34high-rezAnyone here tried to boot up the linux kernel on a rhodium?  Anything I should be aware of when trying? :)
18:27.53*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
18:32.29*** join/#htc-linux Tinyboom_ (n=nahh@206.84-49-89.nextgentel.com)
18:35.57*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
18:38.09*** join/#htc-linux dcordes-kais (n=dcordes-@ip-90-186-29-15.web.vodafone.de)
18:38.50dcordes-kaishigh-rez you can try the latest raphael zImage
18:39.05dcordes-kaishigh-rez do you have cdma or gsm unit?
18:40.23AstainHellbringhiya dcordes-kais
18:40.35dcordes-kaishiya
18:40.55AstainHellbringwhats new in the latest raph zimage?
18:41.09dcordes-kaissomebody know how much current a typical 5400rpm 2,5" hdd pulls?
18:41.55dcordes-kaisAstainHellbring dunno, check htc-msm-2.6.27 git log. high-rez wants to boot linux on rhodijum
18:43.07AstainHellbringahh ic
18:57.43dcordes-kaisAstainHellbring do you have the rhodium too?
18:59.27*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
19:01.36pH5dcordes-kais: my old pata 5400rpm travelstar says 5V 1A on its top, I guess current models don't need as much
19:05.56AstainHellbringdcordes-kais no not yet
19:06.09AstainHellbringwaiting for one with US 3g
19:12.26*** join/#htc-linux Tinyboom_ (n=nahh@206.84-49-89.nextgentel.com)
19:16.29*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
19:23.44BabelO~x de fr verstecken, unterdrücken
19:28.05*** join/#htc-linux Tinyboom_ (n=nahh@206.84-49-89.nextgentel.com)
19:36.28*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
19:42.51*** join/#htc-linux AstainHellbring (n=AstainHe@unaffiliated/astainhellbring)
19:50.25dcordesBabelO: if you need translation help just ping
19:51.03BabelOdcordes  : thanks, it is just a bot testing, have to ask Timriker :)
19:51.15dcordesheh ok
19:51.28dcordeshow are the planes/helis ?
19:53.05dcordespH5: thanks. my new samsung says 0,85A . I was just wondering if I bought the wrong voltage regulator
19:56.39dcordesit's amazing, I thought they were pulling like 2A minimum
19:58.25pH5dcordes: still, too much to power them from the phone usb port directly :)
19:59.40dcordesit's for a DVR
20:01.10*** join/#htc-linux MLM_ (n=mlvdmeid@5ED0BCBD.cable.ziggo.nl)
20:01.35pH5I'd want my phone to be the DVR.
20:01.50BabelOdcordes i broke heli :) but i already built it again :)
20:02.03pH5wonders how long until phones with micro hdmi or displaylink outputs appear
20:02.31BabelOpH5: for you -> http://www.wowwee.com/en/products/tech/projection/cinemin/swivel
20:03.17BabelOi like rovio too :)
20:03.32*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
20:03.49high-rezHey guys, on my Raphael - the kernel stops booting at "handover: boot [htc_fb-1] -> real [tty0]" - any idea what I'm doing wrong here ?
20:04.48Squarchigh-rez: I have that also sometimes
20:04.59Squarchigh-rez: but not always..
20:05.03pH5is susceptible to rainbow effect. do pico dlps suffer from that?
20:05.58high-rezSquarc: One the kernel I built recently it always happens.  On an older kenel it only happens some times...  It appears there have been a number of advancements in the newer kernel.
20:06.32Squarccould it be some kind of interrupt/timing problem ?
20:06.54high-rezI got into a really weird menu while playing with this thing yesterday.  I think it was an engineering menu.  I had rgb gradients and said "device unlocked" and at the bottom "serial port enabled".
20:07.15high-rezSquarc: Mind if I msg you ?
20:07.21Squarcnope, not at all
20:08.12*** join/#htc-linux StarLite (n=nnscript@s55916ca6.adsl.wanadoo.nl)
20:08.35*** join/#htc-linux Tinyboom_ (n=nahh@206.84-49-89.nextgentel.com)
20:08.51*** join/#htc-linux miknix (n=miknix@81.193.83.213)
20:11.58dcordespH5: nvidia makes new arm platform which is powerful enough for 1080p hd support
20:12.12miknixis someone using htc-flasher?
20:12.28dcordesbut I don't know if the market likes handset with hdmi output yet
20:14.33pH5dcordes: maybe not, but it's a pity. with hdmi a reasonably fast phone would become a complete desktop computer replacement.
20:22.54*** join/#htc-linux WigglerAway_ (n=james@92-235-224-158.cable.ubr12.stav.blueyonder.co.uk)
20:26.46dcordesmiknix: I used it few times
20:26.52*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
20:27.07dcordespH5: true, you can use raphael tv out though :)
20:27.10miknixdcordes, it doesnt seem to work with the wizard
20:27.23miknixwizard uses old nbh roms
20:27.30miknixs/nbh/nbf/
20:28.11dcordesmiknix: do you use latest version? http://forum.xda-developers.com/showpost.php?p=2301259&postcount=25
20:28.36miknixyes, right from svn
20:28.47dcordesthen it seems like he didn't
20:29.25miknixI'm going to copy the rom into the SD
20:29.42miknixand mess with the bootloader commands to see if I can flash it
20:31.33dcordesok
20:31.53dcordesmiknix: does frameworkd work on wiz?
20:32.05tmztit's on giz-e17
20:32.30dcordesso I assume it works well?
20:32.34miknixit does
20:32.42dcordescool
20:32.50dcordesdid you have to patch heavily?
20:33.18miknixthe ebuild is from a gentoo overlay
20:33.34tmztis it working on wizard then, ogsmd?
20:33.57dcordesI mean did you have to patch the frameworkd in order to operate on wizard? or does single line modem type work?
20:34.05miknixwait a sec
20:34.11miknixe17 does work on wiz
20:34.18high-reztmzt: I'm here as well...  I've got a raphael, rhodium, several others.
20:34.57miknixthe phone framwork is in the image but I never tried it
20:38.28miknixCmd>?
20:38.28miknixPlease see XDA-Developers wiki for the list of available commands
20:38.28miknixhttp://wiki.xda-developers.com
20:38.30miknixgreat
20:55.49*** join/#htc-linux MLM (n=mlvdmeid@5ED0BCBD.cable.ziggo.nl)
20:58.08*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
21:03.19*** join/#htc-linux JuNu_KN (n=chatzill@kons-5f714611.pool.einsundeins.de)
21:07.05WigglerAway_Can someone help me understand the ram organisation on the raphael. Haret states wince reports 208MB. Device is advertised with 288MB I believe 32MB is a SMI with the ARM9. device-htcraphael.h states 89MB RAM, Kernel is parsed with mem=76MB. What's going on here?
21:09.19*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
21:37.36*** join/#htc-linux MethoS (n=clemens@host-091-097-243-034.ewe-ip-backbone.de)
22:17.27*** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz)
22:18.36*** join/#htc-linux Tinyboom_ (n=nahh@206.84-49-89.nextgentel.com)
22:21.12*** join/#htc-linux marex (n=marex@vasut.kolej.mff.cuni.cz)
22:55.40*** join/#htc-linux l33tlinuxh4x0r (n=user@adsl-144-166-112.rmo.bellsouth.net)
23:03.48*** join/#htc-linux j0b0 (n=jobo@5ED40048.cable.ziggo.nl)
23:10.19*** join/#htc-linux BHSPitMonkey (n=stephen@unaffiliated/bhspitmonkey)
23:10.45*** join/#htc-linux fish1209 (n=fish1209@unaffiliated/fish0912)
23:15.07*** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com)
23:31.15*** join/#htc-linux timebomb (n=tb@e177143253.adsl.alicedsl.de)

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