00:00.20 | tmzt | it might be helpful to respond to the thread talking about how similar/simple smd itself is, and how the soft irqs work |
00:00.35 | tmzt | similar to other msm devices |
00:00.46 | cr2 | is there an "accelerated" audio infrastructure in linux ? like DRI ? |
00:01.13 | tmzt | the higherlevel stuff might be an issue but the basics of smd and proc-comm should really be merged/updated |
00:01.19 | cr2 | smd depends on the smem layout |
00:01.26 | cr2 | which is done by oemsbl |
00:01.43 | cr2 | at least on g1 and raph100 the driver is generic enough. |
00:01.46 | tmzt | we also need to cleanup htc-fb or eliminate it if possible |
00:02.02 | tmzt | yeah, we should move the cdma stuff to pdata |
00:02.03 | cr2 | but on raph800 / vogue it is not so generic. |
00:02.44 | tmzt | again, something like .table-format could be used |
00:02.54 | cr2 | proc_comm is actually the PMIC "driver" |
00:03.00 | cr2 | so it's not msm-specific too. |
00:03.36 | tmzt | if it's NONE read the entries from smd-channel-data |
00:03.46 | tmzt | isn't pmic on sbi? |
00:05.21 | *** join/#htc-linux cr2 (n=cr2@ip-77-24-93-240.web.vodafone.de) |
00:05.25 | 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 driver? |
00:05.36 | cr2 | disconnected ? |
00:05.42 | tmzt | yes |
00:05.52 | cr2 | [02:00] <cr2> is there an "accelerated" audio infrastructure in linux ? like DRI ? |
00:05.53 | cr2 | [02:01] <cr2> smd depends on the smem layout |
00:05.55 | cr2 | [02:01] <cr2> which is done by oemsbl |
00:05.56 | cr2 | [02:01] <cr2> at least on g1 and raph100 the driver is generic enough. |
00:05.58 | cr2 | [02:01] <cr2> but on raph800 / vogue it is not so generic. |
00:05.59 | cr2 | [02:02] <cr2> proc_comm is actually the PMIC "driver" |
00:06.01 | cr2 | [02:02] <cr2> so it's not msm-specific too. |
00:06.31 | cr2 | the only non-pmic part of proc_comm is gpio |
00:07.00 | tmzt | 5:38 < tmzt> we also need to cleanup htc-fb or |
00:07.00 | tmzt | <PROTECTED> |
00:07.00 | tmzt | 15:39 < tmzt> yeah, we should move the cdma stuff |
00:07.00 | tmzt | <PROTECTED> |
00:07.00 | tmzt | 15:39 < cr2> but on raph800 / vogue it is not so |
00:07.00 | cr2 | let's start pushing and bashing google with the gpio ALT patch :) |
00:07.02 | tmzt | <PROTECTED> |
00:07.05 | tmzt | 15:39 < tmzt> again, something like .table-format |
00:07.07 | tmzt | <PROTECTED> |
00:07.10 | tmzt | 15:40 < cr2> proc_comm is actually the PMIC |
00:07.12 | tmzt | <PROTECTED> |
00:07.15 | tmzt | 15:40 < cr2> so it's not msm-specific too. |
00:07.17 | tmzt | 15:40 < tmzt> if it's NONE read the entries from |
00:07.20 | tmzt | <PROTECTED> |
00:07.23 | tmzt | 15: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.26 | tmzt | <PROTECTED> |
00:07.28 | tmzt | 15:42 < cr2> disconnected ? |
00:07.31 | tmzt | 15:42 < tmzt> yes |
00:07.34 | cr2 | ok |
00:07.53 | cr2 | i see it throught the Lag value |
00:08.03 | cr2 | got 130 sec before ;) |
00:08.28 | cr2 | proc_comm mainly talks to pmic. |
00:08.41 | cr2 | and there are several msm pmic chips |
00:08.58 | cr2 | the DEX/proc_comm may be a good abstraction |
00:09.16 | tmzt | yeah |
00:09.21 | cr2 | why did they add gpio to proc_comm is unclear to me |
00:09.38 | cr2 | even htc has an rpc for gpio control |
00:09.40 | tmzt | based on what viperbjk said I think all of smem is just ram, no mmio at all |
00:09.59 | tmzt | the rtos picks up changes and makes the low-level change |
00:10.00 | cr2 | if they do not want to manipulate arm9 gpios directly. |
00:10.21 | cr2 | smem is ram. DPRAM if you'd lkike |
00:10.51 | tmzt | or csmi on omap |
00:10.58 | cr2 | but all out wince htc phones manipulate arm9 gpios directly. |
00:11.18 | tmzt | the thread also mentioned dsp stuff is a more traditional mailbox implementation |
00:11.29 | tmzt | and that smd is 8k queues |
00:11.40 | cr2 | yes |
00:12.00 | cr2 | but you need to adapt to the specific sram layout. |
00:12.24 | tmzt | how extacly? |
00:12.30 | cr2 | not alwaays 8k |
00:12.49 | cr2 | can be 512byte |
00:12.52 | tmzt | that was from swetland on the thread |
00:12.55 | cr2 | vogue/raph800 |
00:13.01 | tmzt | ah |
00:13.03 | tmzt | ok |
00:13.06 | cr2 | yes, on g1 and raph100 it's 8k |
00:13.27 | tmzt | what's 512 on cdma? |
00:13.27 | cr2 | and the sram layout is the same. |
00:13.37 | cr2 | so g1 smd works on raph100 as is |
00:13.50 | cr2 | AT and DATA |
00:13.51 | tmzt | the table is also not complete on there |
00:14.15 | tmzt | the multiple DATA channels? |
00:14.16 | cr2 | with the stream patch, though (g1=raph100+stream patch) |
00:14.35 | tmzt | stream patch? |
00:14.48 | cr2 | which channel is packet and which is stream |
00:15.06 | cr2 | it seems that the packet channel is a g1 innovation. |
00:15.11 | cr2 | maybe because of the qmi |
00:16.15 | cr2 | imho google should do a major cleanup of their code |
00:16.45 | cr2 | because they created a real PITA with it even for raph100 which is very similar to g1 |
00:17.46 | cr2 | whether they really want to do it, is another issue |
00:19.00 | tmzt | ah |
00:19.02 | cr2 | if i was an arm maintainer, i will not accept the current arch-msm for a lot of reasons. |
00:19.08 | tmzt | yeah qmi makes sense |
00:19.22 | tmzt | for them, I wish it did for us |
00:20.42 | cr2 | we know the most pitfalls now, but it is still not clear how to cleanup this mess |
00:21.51 | cr2 | i have applied the bt power+reset |
00:22.13 | cr2 | now the kernel freezes on stty -F /dev/ttyHS1 |
00:22.27 | cr2 | it must be DMOV-related |
00:22.31 | tmzt | hard to debug? |
00:22.46 | cr2 | i dont' see the oops on the LCD |
00:22.50 | cr2 | and usb is dead |
00:22.58 | cr2 | i can ping raph, though |
00:22.59 | tmzt | serial :) |
00:23.07 | cr2 | yeah, soldering |
00:23.16 | tmzt | don't you have a cable for one of the other projects? |
00:23.21 | cr2 | or redirecting thr console to tty0 |
00:23.39 | cr2 | no, i need to solder the docking station |
00:23.43 | cr2 | hmm. |
00:23.44 | tmzt | do you have the update thread enabled? |
00:23.59 | cr2 | we may try to resolve these fb problems too |
00:24.33 | cr2 | i have the standard kernel from git |
00:24.47 | tmzt | enable update |
00:25.00 | cr2 | <PROTECTED> |
00:25.05 | tmzt | when I disabled it I stopped getting oops |
00:25.17 | tmzt | do you have init code now? |
00:25.32 | cr2 | which init ? |
00:25.40 | tmzt | we don't need more feedback than vibra anyway |
00:25.40 | cr2 | add everything to git |
00:25.44 | tmzt | lcd init |
00:26.02 | cr2 | we have a separate setup for android, so we can do clean things for normal kernel |
00:26.21 | cr2 | no. lcd init needs power gpios |
00:26.50 | cr2 | and on epson* lcds it needs the SPI codes |
00:26.51 | tmzt | can we trace those on screen off/on? |
00:27.04 | cr2 | which ones ? |
00:27.13 | tmzt | gpios |
00:27.21 | cr2 | they are known. |
00:27.25 | tmzt | short press power button |
00:27.34 | tmzt | why don't they work then? |
00:27.43 | cr2 | 'setlcd 4' in haret |
00:27.48 | tmzt | and mddi writes? |
00:27.55 | cr2 | because we have not added them |
00:28.04 | cr2 | mddi is ok |
00:28.11 | cr2 | well. |
00:28.15 | tmzt | we need it for xip/mtd anyway |
00:28.30 | tmzt | mddi writes to init lcd from the client chip |
00:28.38 | cr2 | i have documented what wince does for mddi setup. g1 is a bit diufferent |
00:28.45 | cr2 | but it still works. |
00:29.12 | cr2 | not mddi itself, but the spi to the panel |
00:30.34 | tmzt | spi direct to panel? |
00:30.51 | cr2 | btw, i got another oops in the bt shutdown code, which i don't understand |
00:30.52 | cr2 | yes. |
00:31.03 | tmzt | if we had client drivers with correct register names |
00:31.19 | cr2 | no |
00:31.41 | tmzt | ok, so that's not client at all, that's traditional tft module |
00:31.44 | cr2 | you just need to query the LCD type over epson/toshiba gpios |
00:32.02 | cr2 | and send the right spi sequences |
00:32.15 | tmzt | I mean instead of magic handshake sequences like on trout |
00:32.17 | cr2 | instead of the g1 sequences |
00:32.57 | cr2 | they are not documented (afaik) but it's known where to pick them. |
00:33.36 | AstainHellbring | wow I walk away and miss a ton of stuff here |
00:34.21 | tmzt | logs are good |
00:34.26 | AstainHellbring | yep thats for sure |
00:34.49 | tmzt | do we know what lcm is used? |
00:35.01 | tmzt | we know cdma is different for some reason |
00:36.00 | tmzt | we could find out from viperbjk on diam100 |
00:37.01 | cr2 | yes , there are several lcdm used |
00:37.11 | cr2 | just need to be documented. |
00:38.22 | tmzt | there are usually datasheets for those, if we treat mddi client like any other lcdc we can ignore it I think |
00:38.55 | tmzt | but at least we would know what spi commands do |
00:39.09 | cr2 | hmm. i doubt that you'll get the lcm datasheet |
00:39.15 | tmzt | maybe find a secret 18bit mode on cdma |
00:39.19 | tmzt | why? |
00:39.28 | tmzt | you think mddi is part of it? |
00:39.30 | cr2 | even the moko phone does not have it |
00:39.36 | cr2 | no, the spi |
00:39.39 | tmzt | oh |
00:39.50 | cr2 | the same magic spi sequences only. |
00:40.15 | tmzt | ok |
00:40.17 | cr2 | i'd prefer a secret 565 mode on raph100 |
00:40.25 | tmzt | yeah |
00:40.31 | tmzt | at least for X |
00:40.42 | cr2 | yes |
00:40.57 | tmzt | oh, Pre uses a similar screen flipping system to android |
00:41.18 | tmzt | vyres*4 and "standard" ioctl |
00:41.20 | cr2 | Pre ? |
00:41.26 | tmzt | Palm Pre |
00:41.41 | cr2 | which cpu is that ? |
00:41.49 | tmzt | CDMA phone built on omap3410 |
00:41.58 | tmzt | with msm6800 baseband |
00:42.00 | cr2 | omap3. ok |
00:42.03 | tmzt | came with root |
00:42.23 | cr2 | msm is on dpram ? |
00:42.38 | tmzt | through a simple code and complex usb multiplexer process |
00:42.46 | cr2 | or usb like on universal and hermes ? |
00:42.51 | tmzt | don't know yet, I think usb host |
00:43.08 | tmzt | maybe with some handshaking or wakeup gpios |
00:43.08 | cr2 | ok, so it'S like uni/herm |
00:43.29 | tmzt | I've been asking for lsusb -v -v in #webos-internals for 3 days |
00:43.44 | tmzt | cat ~roc/interrupts would be useful as well |
00:43.46 | cr2 | hehe |
00:43.50 | cr2 | dmesg ? |
00:44.04 | tmzt | no, I have .config though |
00:44.42 | cr2 | i don't know omap3 internals |
00:44.45 | tmzt | they have a wiki now |
00:45.15 | tmzt | I guess it's webos-internals.org |
00:45.21 | tmzt | or webos-dev.org |
00:45.26 | cr2 | ok, but it's not something new. |
00:45.34 | tmzt | yeah |
00:45.43 | tmzt | and not msm for ap |
00:46.01 | tmzt | but we knew that a year ago |
00:46.03 | cr2 | the same on athena |
00:46.26 | cr2 | pxa270+msm6275 |
00:46.29 | cr2 | of hermes |
00:46.37 | cr2 | s3c2442+msm6275 |
00:47.10 | tmzt | anyway, brought that up because there is some work for dri on arm which would benefit us and omap3 |
00:47.21 | tmzt | even for the offscreen buffers support |
00:47.25 | cr2 | ok |
00:47.30 | tmzt | and 3d later |
00:47.49 | tmzt | drm |
00:47.50 | cr2 | well, we need to make sound work :) |
00:47.54 | tmzt | not dri |
00:47.56 | tmzt | yes |
00:48.15 | cr2 | i'm also thinking about gps |
00:48.19 | tmzt | do you think tracing ioctls on g1 will help? |
00:48.42 | cr2 | since rpc is working now, even for adsp, it should be possible |
00:49.09 | cr2 | yes, if you can trace the libgps.so calls |
00:49.09 | tmzt | haven't got rpc to really work |
00:49.15 | cr2 | it's thumb code there ;) |
00:49.33 | tmzt | the problem on android is everything is in a few processes |
00:49.39 | cr2 | but i'd like to see the smem dump first |
00:49.44 | tmzt | hard to strace |
00:49.56 | tmzt | can we fix /dev/mem? |
00:50.16 | cr2 | my battery comes close to its end ;) |
00:50.20 | tmzt | we should be able to open pmem by removing a few checks |
00:50.21 | cr2 | fix ? |
00:50.42 | tmzt | is it just disabled? |
00:50.50 | cr2 | just enable it in .config |
00:50.58 | tmzt | AstainHellbring: did you get /dev/mem working? |
00:51.02 | cr2 | yes, even on raph in the current git |
00:51.08 | AstainHellbring | not yet tmzt |
00:51.29 | cr2 | AstainHellbring: does gps work for you on g1 ? |
00:51.33 | tmzt | we can add printks's to ioctls as well |
00:52.02 | cr2 | tmzt: where do you see gps ioctls ith source code ? |
00:52.18 | tmzt | I don't? |
00:52.36 | cr2 | the function names are more or less the same as on wince. |
00:52.52 | cr2 | somehow i think that it's easier to do it on wince |
00:52.55 | tmzt | L mean generally for tracing closed libraries on android |
00:53.34 | cr2 | wince driver is more readable than this thumb mess on g1 |
00:54.05 | cr2 | the rpcs are already in wiki |
00:54.28 | cr2 | init+register some clients+pdsm_get_position |
00:54.38 | tmzt | I don't see anything related to msm in git grep gps |
00:54.39 | cr2 | with 28 params ;) |
00:54.51 | cr2 | libgps.so is closed source. |
00:55.01 | cr2 | which program uses libgps.so ? |
00:55.20 | tmzt | g1 uses nmea doesn't it? |
00:55.29 | cr2 | +rpc |
00:55.36 | cr2 | the same as raph100 |
00:55.38 | tmzt | I think thatqs for updating/saving ephemeris for fast start |
00:55.59 | cr2 | not only i think |
00:56.50 | tmzt | target/product/sdk gpstest |
00:56.54 | cr2 | raph100 has nmea in smd27 and sends several rpcs |
00:57.04 | cr2 | i think the same is true for g1 |
00:57.29 | cr2 | raph800 is more complex., because it does not have nmea smd27 |
00:57.51 | cr2 | sdk gpstest ? |
00:57.59 | cr2 | can you like the source ? |
00:58.06 | tmzt | interesting, GPS-STATUS |
00:58.10 | tmzt | NONE |
00:58.17 | tmzt | SESSION BEGIN |
00:58.18 | cr2 | debian says i have 30min left. |
00:58.23 | tmzt | SESSION END |
00:58.26 | cr2 | but it guess less |
00:58.29 | tmzt | ENGINE ON |
00:58.34 | tmzt | ENGINE OFF |
00:59.20 | cr2 | link ? |
00:59.22 | tmzt | .. |
00:59.35 | tmzt | in repo, libhardware-legacy |
00:59.37 | AstainHellbring | cr2 yes gps works on g1 |
00:59.46 | cr2 | ok |
01:00.12 | cr2 | tmzt: we may grab the libgps.so, but it's not my method ;) |
01:00.17 | tmzt | cat /dev/smd27? |
01:00.45 | tmzt | GPS STATUS |
01:00.52 | tmzt | sorry |
01:00.53 | cr2 | hangs without any updates |
01:01.00 | tmzt | GPS POSITION |
01:01.16 | tmzt | MODE STANDALONE |
01:01.37 | tmzt | MODE MS BASED (SUPL MS-Based Mode) |
01:01.52 | cr2 | yes, you send the pdsm_get_position() rpc, and (probably) get a nmea sentence(s) in smd27 |
01:02.18 | tmzt | MODE MS ASSISTED (SUPL MS-Assisted mode) |
01:02.56 | cr2 | tmzt: PA and PD ? |
01:03.42 | tmzt | how many fields from rpc? |
01:03.48 | tmzt | flags |
01:03.52 | tmzt | double lat |
01:03.57 | tmzt | double long |
01:04.02 | tmzt | double alt |
01:04.04 | cr2 | tmzt: check the MSM_RPC wiki page |
01:04.13 | tmzt | float speed |
01:04.14 | cr2 | 28 |
01:04.20 | tmzt | float bearing |
01:04.25 | tmzt | float accuracy |
01:04.30 | tmzt | timestamp |
01:04.33 | tmzt | ah |
01:04.37 | tmzt | more then |
01:04.54 | cr2 | double/float need some encoding |
01:05.07 | cr2 | we don't have cpu fp support |
01:05.07 | tmzt | requested frequency of fixes in seconds |
01:05.27 | cr2 | =2 in wince |
01:05.44 | tmzt | right |
01:05.57 | tmzt | this is c code from android |
01:05.57 | cr2 | 1 per 2 seconds |
01:06.09 | cr2 | link ? |
01:06.16 | tmzt | it says you can set frquency, 0 to get a single fix |
01:06.16 | cr2 | i have 5 min left :) |
01:06.19 | tmzt | repo |
01:06.26 | tmzt | I have it offline |
01:06.33 | cr2 | direkt link please :) |
01:07.22 | tmzt | libhardware-legacy.git |
01:07.36 | tmzt | hardware/libhardwanre-legacy.git |
01:08.52 | tmzt | http://android.git.kernel.org/?p=platform/hardware/libhardware_legacy.git;a=summary |
01:08.52 | cr2 | found |
01:09.09 | tmzt | there's a 7k hardware git also, didn't know that |
01:09.13 | tmzt | or forgot |
01:09.34 | cr2 | gps_qemu.c ? |
01:10.11 | cr2 | gpsd reimplementation |
01:11.04 | tmzt | http://android.git.kernel.org/?p=platform/hardware/msm7k.git;a=blob;f=libaudio/AudioHardware.cpp;h=b8b8566aacabacd0230739cb342db5e8a6ffc47e;hb=donut |
01:11.15 | tmzt | yeah |
01:12.00 | tmzt | that's all there is, the rest is in libgps.so |
01:12.08 | cr2 | hehe |
01:12.19 | cr2 | where did you get these strings ? |
01:12.55 | tmzt | include/gps.h |
01:13.10 | tmzt | include/hardware-legacy |
01:13.37 | cr2 | do 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.10 | tmzt | http://article.gmane.org/gmane.linux.kernel/851842 |
10:59.23 | tmzt | gpio-alt-func in gpiolib |
11:01.40 | kri5 | hello there |
11:02.25 | kri5 | does 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.25 | tmzt | revival? |
11:06.27 | tmzt | we are working on rpc for sound, audio routing, gps, replacing the initial console with proper lcd init, integrating upstream work, etc. |
11:06.41 | tmzt | not sure how that applies to blak at the moment |
11:07.04 | tmzt | but 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.15 | kri5 | http://forum.xda-developers.com/showthread.php?t=524898 |
11:24.35 | kri5 | developement for blackstone seemed to be stopped |
11:24.43 | kri5 | so tuxhero initiated this |
11:25.03 | kri5 | i'd like to know if there were people working on this :) |
11:25.23 | tmzt | > + clk_enable(msm_port->clk); |
11:25.23 | tmzt | > + |
11:25.23 | tmzt | > + msm_write(port, 0xC0, UART_MREG); |
11:25.23 | tmzt | > + msm_write(port, 0xB2, UART_NREG); |
11:25.24 | tmzt | > + msm_write(port, 0x7D, UART_DREG); |
11:25.27 | tmzt | > + msm_write(port, 0x1C, UART_MNDREG); |
11:25.42 | tmzt | cr2: this is in proposed upstream patch |
11:25.43 | *** join/#htc-linux timebomb (n=tb@85.182.255.196) |
11:27.47 | kri5 | tmzt: 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.52 | kri5 | i'd like to participate |
11:28.02 | kri5 | i have skills on many languages |
11:28.30 | kri5 | but i just don't know anything on kernel drivers devel |
11:28.43 | kri5 | and less on embedded |
11:33.22 | tmzt | I would suggest reading code |
11:33.45 | tmzt | what driver are you looking to implement |
11:36.26 | Elleo | is HaRET's CRC reliable when performing a ramboot as well as a boot? |
11:37.14 | Elleo | as it fail's when I use boot, but the kernel passes when doing a ramboot (tags still fail though) |
11:38.39 | kri5 | tmzt: i don't care, where do you need help :) |
11:38.41 | kri5 | ? |
11:39.28 | tmzt | Elleo: ramboot is for build a .exe wit kernel/initrd built in |
11:39.46 | tmzt | kri5: well, mostly research right now |
11:39.59 | Elleo | ah, so ramboot doesn't use the supplied zImage at all |
11:40.22 | tmzt | there aren't too many actual drivers that need written |
11:40.47 | tmzt | look at the tree, the files in arch/arm/mach-msm |
11:40.54 | tmzt | Elleo: no |
11:41.15 | Elleo | okay, thanks |
11:41.17 | tmzt | Elleo: what device/what are you trying to do? |
11:41.36 | Elleo | tmzt: Acer m900, trying to add support for it |
11:42.13 | kri5 | tmzt: ok i'll take a look |
11:42.15 | tmzt | ok |
11:42.22 | tmzt | acer? |
11:42.29 | tmzt | not eten |
11:42.31 | Elleo | tmzt: well, e-ten really |
11:42.37 | Elleo | but e-ten were bought by acer a while back |
11:42.41 | Elleo | so it's branded as being acer now |
11:42.49 | tmzt | same as glofiish? |
11:42.55 | Elleo | yeah |
11:43.08 | Elleo | it's the next model on from the m800 |
11:43.23 | tmzt | talk to stefen_schmidt when he's here |
11:43.43 | tmzt | how far have you got? |
11:44.15 | Elleo | well I can get to the point where HaRET should hand off to the kernel |
11:44.20 | Elleo | but the kernel seems to be getting corrupted |
11:44.37 | Elleo | however I'm having trouble a bit before that shutting down all the DMA controllers |
11:44.56 | tmzt | you can't boot at all? |
11:45.19 | Elleo | if 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.24 | Elleo | nope |
11:45.29 | tmzt | is fbduringboot enabled? |
11:45.42 | tmzt | how do you know it hangs? |
11:45.48 | tmzt | after go go go? |
11:46.02 | Elleo | yeah I get output from HaRET in the frame buffer |
11:46.33 | tmzt | how do you know it's crc though, it could be something kernel |
11:46.44 | tmzt | what display driver does it use? |
11:46.54 | Elleo | it never really starts the kernel |
11:47.05 | Elleo | at least I never get any output from earlyprintk or anything |
11:47.09 | tmzt | how do you know that? |
11:47.11 | Elleo | and it fails HaRET's CRC check |
11:47.18 | tmzt | you have serial? |
11:47.23 | Elleo | which would seem to suggest it's getting corrupted |
11:47.38 | tmzt | what message do you get about crc? |
11:47.39 | kri5 | tmzt: for now, you're mostly trying to find out how the hardware works? |
11:47.52 | tmzt | yes |
11:48.20 | Elleo | tmzt: "Checking tags CRC...FAIL FAIL FAIL" "Checking kernel CRC...FAIL FAIL FAIL" |
11:48.26 | tmzt | but like I've said, I don't really know much about blak, it's state, etc. |
11:48.34 | tmzt | huh |
11:48.48 | tmzt | talk to Kevin2 is all I can really say |
11:48.52 | Elleo | but 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.05 | tmzt | does it get to go go go without that enabled? |
11:49.20 | Elleo | tmzt: it gets beyond Go go go, this is after that |
11:49.33 | Elleo | it creates the checksum before go go go, then tests it after |
11:49.35 | tmzt | there is nothing after that |
11:49.53 | Elleo | tmzt: on the framebuffer there is |
11:49.54 | tmzt | look at haret code |
11:50.03 | tmzt | there is what? |
11:50.09 | Elleo | haret does Go Go Go, then it does the machine specific shutdown stuff |
11:50.17 | Elleo | then it does the mmu trampoline |
11:50.22 | Elleo | and crc check |
11:50.28 | Elleo | and then tries to hand off to the kernel |
11:50.28 | tmzt | sorry, it says "at this point we are no longer running" in the code |
11:50.46 | tmzt | ok, what cpu and video? |
11:51.06 | Elleo | it's a samsung s3c6410 |
11:51.23 | tmzt | buitl in video? |
11:51.28 | Elleo | yeah |
11:51.34 | tmzt | ok |
11:51.49 | tmzt | Kevin2: ping |
11:54.43 | tmzt | see if he can help you when he gets here |
11:54.48 | Elleo | thanks :) |
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.33 | xsacha | hey guys |
14:02.49 | AstainHellbring | hi |
14:03.36 | IamSOG | yo 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.34 | high-rez | Anyone 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.50 | dcordes-kais | high-rez you can try the latest raphael zImage |
18:39.05 | dcordes-kais | high-rez do you have cdma or gsm unit? |
18:40.23 | AstainHellbring | hiya dcordes-kais |
18:40.35 | dcordes-kais | hiya |
18:40.55 | AstainHellbring | whats new in the latest raph zimage? |
18:41.09 | dcordes-kais | somebody know how much current a typical 5400rpm 2,5" hdd pulls? |
18:41.55 | dcordes-kais | AstainHellbring dunno, check htc-msm-2.6.27 git log. high-rez wants to boot linux on rhodijum |
18:43.07 | AstainHellbring | ahh ic |
18:57.43 | dcordes-kais | AstainHellbring do you have the rhodium too? |
18:59.27 | *** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com) |
19:01.36 | pH5 | dcordes-kais: my old pata 5400rpm travelstar says 5V 1A on its top, I guess current models don't need as much |
19:05.56 | AstainHellbring | dcordes-kais no not yet |
19:06.09 | AstainHellbring | waiting 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.44 | BabelO | ~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.25 | dcordes | BabelO: if you need translation help just ping |
19:51.03 | BabelO | dcordes : thanks, it is just a bot testing, have to ask Timriker :) |
19:51.15 | dcordes | heh ok |
19:51.28 | dcordes | how are the planes/helis ? |
19:53.05 | dcordes | pH5: thanks. my new samsung says 0,85A . I was just wondering if I bought the wrong voltage regulator |
19:56.39 | dcordes | it's amazing, I thought they were pulling like 2A minimum |
19:58.25 | pH5 | dcordes: still, too much to power them from the phone usb port directly :) |
19:59.40 | dcordes | it's for a DVR |
20:01.10 | *** join/#htc-linux MLM_ (n=mlvdmeid@5ED0BCBD.cable.ziggo.nl) |
20:01.35 | pH5 | I'd want my phone to be the DVR. |
20:01.50 | BabelO | dcordes i broke heli :) but i already built it again :) |
20:02.03 | pH5 | wonders how long until phones with micro hdmi or displaylink outputs appear |
20:02.31 | BabelO | pH5: for you -> http://www.wowwee.com/en/products/tech/projection/cinemin/swivel |
20:03.17 | BabelO | i like rovio too :) |
20:03.32 | *** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com) |
20:03.49 | high-rez | Hey 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.48 | Squarc | high-rez: I have that also sometimes |
20:04.59 | Squarc | high-rez: but not always.. |
20:05.03 | pH5 | is susceptible to rainbow effect. do pico dlps suffer from that? |
20:05.58 | high-rez | Squarc: 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.32 | Squarc | could it be some kind of interrupt/timing problem ? |
20:06.54 | high-rez | I 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.15 | high-rez | Squarc: Mind if I msg you ? |
20:07.21 | Squarc | nope, 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.58 | dcordes | pH5: nvidia makes new arm platform which is powerful enough for 1080p hd support |
20:12.12 | miknix | is someone using htc-flasher? |
20:12.28 | dcordes | but I don't know if the market likes handset with hdmi output yet |
20:14.33 | pH5 | dcordes: 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.46 | dcordes | miknix: I used it few times |
20:26.52 | *** join/#htc-linux Tinyboom (n=nahh@206.84-49-89.nextgentel.com) |
20:27.07 | dcordes | pH5: true, you can use raphael tv out though :) |
20:27.10 | miknix | dcordes, it doesnt seem to work with the wizard |
20:27.23 | miknix | wizard uses old nbh roms |
20:27.30 | miknix | s/nbh/nbf/ |
20:28.11 | dcordes | miknix: do you use latest version? http://forum.xda-developers.com/showpost.php?p=2301259&postcount=25 |
20:28.36 | miknix | yes, right from svn |
20:28.47 | dcordes | then it seems like he didn't |
20:29.25 | miknix | I'm going to copy the rom into the SD |
20:29.42 | miknix | and mess with the bootloader commands to see if I can flash it |
20:31.33 | dcordes | ok |
20:31.53 | dcordes | miknix: does frameworkd work on wiz? |
20:32.05 | tmzt | it's on giz-e17 |
20:32.30 | dcordes | so I assume it works well? |
20:32.34 | miknix | it does |
20:32.42 | dcordes | cool |
20:32.50 | dcordes | did you have to patch heavily? |
20:33.18 | miknix | the ebuild is from a gentoo overlay |
20:33.34 | tmzt | is it working on wizard then, ogsmd? |
20:33.57 | dcordes | I mean did you have to patch the frameworkd in order to operate on wizard? or does single line modem type work? |
20:34.05 | miknix | wait a sec |
20:34.11 | miknix | e17 does work on wiz |
20:34.18 | high-rez | tmzt: I'm here as well... I've got a raphael, rhodium, several others. |
20:34.57 | miknix | the phone framwork is in the image but I never tried it |
20:38.28 | miknix | Cmd>? |
20:38.28 | miknix | Please see XDA-Developers wiki for the list of available commands |
20:38.28 | miknix | http://wiki.xda-developers.com |
20:38.30 | miknix | great |
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.05 | WigglerAway_ | 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) |