| 00:07.21 | Pali | freemangordon: about camera problems, sailus is online here |
| 00:48.24 | *** join/#maemo-ssu jonwil (~jonwil@27-33-137-199.static.tpgi.com.au) |
| 00:52.19 | *** part/#maemo-ssu mkaindl (~mkaindl@ama-dablam.markus-kaindl.de) |
| 02:58.54 | *** join/#maemo-ssu amiconn_ (quassel@rockbox/developer/amiconn) |
| 05:27.04 | *** join/#maemo-ssu Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr) |
| 05:49.30 | *** join/#maemo-ssu Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr) |
| 05:57.05 | *** join/#maemo-ssu luf (~luf@80.188.29.62) |
| 06:07.48 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-93-219.residential.rdsnet.ro) |
| 06:14.04 | *** join/#maemo-ssu aap__ (~drew@cpe-174-101-232-161.cinci.res.rr.com) |
| 06:14.52 | *** join/#maemo-ssu Sc0rpius_ (~naikel@ec2-54-224-30-118.compute-1.amazonaws.com) |
| 06:15.46 | *** join/#maemo-ssu T_X_ (~T_X@open-mesh.org) |
| 06:18.19 | *** join/#maemo-ssu LauRoman (~LauRoman@5-14-93-219.residential.rdsnet.ro) |
| 06:21.47 | *** join/#maemo-ssu FatPhil_ (~pcarmody@87-119-183-129.tll.elisa.ee) |
| 06:21.51 | *** join/#maemo-ssu nedko (~nedko@unaffiliated/nedko) |
| 06:23.01 | *** join/#maemo-ssu sailus (~sailus@valkosipuli.retiisi.org.uk) |
| 06:53.09 | *** join/#maemo-ssu scoobertron (~tom@66.172.11.27) |
| 06:56.31 | *** join/#maemo-ssu aap (~drew@cpe-174-101-232-161.cinci.res.rr.com) |
| 06:56.44 | *** join/#maemo-ssu DrCode (~DrCode@gateway/tor-sasl/drcode) |
| 07:28.51 | *** join/#maemo-ssu DrCode (~DrCode@gateway/tor-sasl/drcode) |
| 07:37.22 | *** join/#maemo-ssu DrCode (~DrCode@gateway/tor-sasl/drcode) |
| 07:44.54 | *** join/#maemo-ssu freemangordon (~freemango@213.137.35.49) |
| 07:47.43 | *** join/#maemo-ssu dos1 (~dos@unaffiliated/dos1) |
| 08:23.48 | *** join/#maemo-ssu Martix_ (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 08:52.25 | *** join/#maemo-ssu sunny_s (~sunny_s@business-092-079-020-027.static.arcor-ip.net) |
| 09:19.36 | *** join/#maemo-ssu jonwil (~jonwil@27-33-137-199.static.tpgi.com.au) |
| 09:23.13 | *** join/#maemo-ssu DrCode (~DrCode@gateway/tor-sasl/drcode) |
| 09:30.30 | *** join/#maemo-ssu Pali (~pali@Maemo/community/contributor/Pali) |
| 09:58.09 | *** join/#maemo-ssu dos1 (~dos@unaffiliated/dos1) |
| 10:45.43 | *** join/#maemo-ssu RST38h (marat@wsip-184-180-40-182.ri.ri.cox.net) |
| 11:01.56 | *** join/#maemo-ssu sunny_s (~sunny_s@business-092-079-020-027.static.arcor-ip.net) |
| 11:12.40 | DocScrutinizer05 | FatPhil_: ((<FatPhil> Peter Ujfalusi once gave a presentation on the functionality of the TI sound core.)) would you happen to know about a keyword searchstring or even a link to that presentation? Aunt google was a bitch |
| 11:26.32 | *** join/#maemo-ssu psycho_oreos (~no@unaffiliated/tuxsavvy) |
| 11:35.33 | FatPhil_ | DocScrutinizer05: that was 100% internal, at a inter-team team-building event. |
| 11:37.12 | DocScrutinizer05 | mhm |
| 11:37.16 | DocScrutinizer05 | thanks |
| 11:39.10 | DocScrutinizer05 | FatPhil_: so what's your personal notion on this - shall we try to get audio working with twl4030 and the reference design, or should we try to get a copy of N900 (AIC34xxxx etc)? |
| 11:40.06 | DocScrutinizer05 | s/get a copy/implement a clone/ |
| 11:47.32 | DocScrutinizer05 | tlv320aix34 is ~USD10, and a lot of (re)work to change the sound we already got in GTA04 |
| 11:48.16 | *** join/#maemo-ssu ujfalusi (~ujfalusi@a91-152-162-160.elisa-laajakaista.fi) |
| 11:48.23 | DocScrutinizer05 | OTOH I think we hardly can make maemo audio work without that particular codec |
| 11:53.21 | ujfalusi | DocScrutinizer05: FatPhil_ asked me to join the channel to help with audio something. |
| 11:54.08 | DocScrutinizer05 | HEY! :-) |
| 11:54.23 | DocScrutinizer05 | hi ujfalusi! |
| 11:54.47 | DocScrutinizer05 | lemme quote myself... |
| 11:56.08 | DocScrutinizer05 | [2013-09-12 13:58:30] <DocScrutinizer05> jonwil: audio is the most annoying subject in Neo900, and not yet finalized. But most definitely will _not_ use identical chipset like N900 |
| 11:56.20 | DocScrutinizer05 | [2013-09-12 13:59:56] <DocScrutinizer05> we're still about to wonder why the heck nobody else (pandora, N900... etc) used twl4030 audio function blocks |
| 11:56.37 | DocScrutinizer05 | [2013-09-12 13:59:59] <FatPhil> Peter Ujfalusi once gave a presentation on the functionality of the TI sound core. He explained that every single possible mode of operation it had was either fundamentally flawed by design, or just plain buggy. |
| 11:57.38 | ujfalusi | Yeah, it has it's quirks for sure ;) |
| 11:57.39 | DocScrutinizer05 | ujfalusi: what are the major pitfalls we should know about with twl4030 audio? |
| 11:58.18 | DocScrutinizer05 | do you think we could get working audio for a N900-alike phone at all, when using it? |
| 11:59.28 | ujfalusi | It is working perfectly. I have added support for all the functionality in the driver, so routing to any of the output/input should be fine. |
| 11:59.52 | ujfalusi | The reason Nokia products choosen different codecs comes down to audio performance. |
| 12:00.23 | ujfalusi | The dedicated codecs have better SNR and better overal performance |
| 12:00.26 | DocScrutinizer05 | like in...? |
| 12:00.35 | DocScrutinizer05 | aah SNR |
| 12:00.53 | DocScrutinizer05 | killer argument already |
| 12:01.23 | DocScrutinizer05 | we want to use the device as mp3 player occasionally |
| 12:01.24 | ujfalusi | Like in n900 we have tlv320aic34 (?) in n9 we have tlv320dac33 (for headset only) + twl5030 (for Handsfree + earpiece + recording) |
| 12:01.40 | DocScrutinizer05 | yep, tlv320aic34 |
| 12:02.11 | jonwil | Its a pitty the interesting parts (pulseaudio-modules-nokia-* etc) are closed source |
| 12:02.23 | DocScrutinizer05 | indeed |
| 12:03.19 | DocScrutinizer05 | gives us little options to rather no choice at all regarding how to implement compatible resp working audio in hw, when we want to port fremantle |
| 12:03.52 | DocScrutinizer05 | now add to that the SNR issue |
| 12:04.45 | DocScrutinizer05 | and the generally differing feature set (buzzword digital filters in tlv320xxx) |
| 12:04.49 | ujfalusi | Not sure what's inside of that module to be honest. But if it is also fiddling with mixer controls for route selection than you need to pick the same codec as well. |
| 12:05.18 | DocScrutinizer05 | yep, that's what been my conclusion as well |
| 12:05.56 | DocScrutinizer05 | ujfalusi: we have that XPROT blob |
| 12:06.25 | DocScrutinizer05 | that nobody knows exactly what it does, possibly entangled with tlv320aic34 filters |
| 12:06.41 | DocScrutinizer05 | then we have that "magic" on kernel cmdline :-o |
| 12:07.20 | DocScrutinizer05 | snd-soc-rx51.hp_lim=42 snd-soc-tlv320aic3x.hp_dac_lim=6 |
| 12:07.35 | DocScrutinizer05 | NFC |
| 12:08.13 | DocScrutinizer05 | just feels like it won't work that nicely on a system that does not even have snd-soc-tlv320aic3x |
| 12:08.19 | ujfalusi | DocScrutinizer05: those are for speaker or ear protection. To limit the gain control so user can not set it too high |
| 12:08.29 | DocScrutinizer05 | yep |
| 12:08.59 | ujfalusi | we had similar things for n9, but it was not via cmdline but via pdat from the board file |
| 12:09.09 | jonwil | We should find out what the people doing meego/mer/nemo/etc on N900 are doing with PulseAudio these days, that might help us out |
| 12:09.16 | DocScrutinizer05 | highpass to cut off <~50Hz or whatever, dynamic compression and maybe adding harmonics to make the speakers "sound" louder, plus limiter |
| 12:09.48 | DocScrutinizer05 | jonwil: seems they ignore the problem |
| 12:10.42 | nedko | what is the problem? |
| 12:11.00 | DocScrutinizer05 | ujfalusi: XPROT even talks to dsme about "temperature" :-o |
| 12:11.32 | ujfalusi | DocScrutinizer05: yep |
| 12:11.32 | DocScrutinizer05 | nedko: audio |
| 12:12.54 | nedko | DocScrutinizer05: what is the problem with audio? |
| 12:13.03 | jonwil | the closed source pa blobs also talk to BME for something |
| 12:13.31 | DocScrutinizer05 | the general design, the quality and other flaws in twl4030, the closed blobs in PA |
| 12:14.15 | DocScrutinizer05 | jonwil: that *could* be just for yelling an alarm when battery low |
| 12:14.42 | DocScrutinizer05 | or for cell temperature, or both, or sth completely different |
| 12:14.46 | DocScrutinizer05 | :-S |
| 12:16.01 | jonwil | aha, found the ml post I made on the issue |
| 12:16.06 | jonwil | modules-nokia-voice.so is the one using it |
| 12:16.27 | DocScrutinizer05 | tzzz |
| 12:16.54 | jonwil | both that module and dsme-thermalobject-surface.so are using it only for the battery temprature |
| 12:16.56 | DocScrutinizer05 | this stuff gives me terrible headache |
| 12:17.37 | jonwil | It may be that the simple answer is to use the same hardware as the N900, keep using the binary blobs and forget about audio beyond that,,, |
| 12:18.01 | DocScrutinizer05 | prolly best approach |
| 12:18.21 | DocScrutinizer05 | the tlv320aic34 is available at digikey for $10 |
| 12:18.39 | ujfalusi | or try to get hints from former developers and have own modules replacing the blobs with similar functionality? |
| 12:19.36 | DocScrutinizer05 | hard to get help, but if we could get that would for sure be a nice alternative - even when keeping the BOM for audio |
| 12:20.56 | DocScrutinizer05 | I asked $Nokia maybe 20 times during last 4 years to at *least* releast the technical specs of XPROT |
| 12:21.10 | DocScrutinizer05 | release* |
| 12:21.25 | DocScrutinizer05 | like cutoff of highpass |
| 12:22.02 | DocScrutinizer05 | limiter threshold, or what the heck you need to describe the technical function of the blob |
| 12:22.11 | DocScrutinizer05 | and as well of the hardware |
| 12:24.25 | jonwil | Even having a list of the features the module does (i.e. "it contains algorithms for sidetone, volume limiter, high-pass filter, x,y,z") would be helpful |
| 12:24.26 | DocScrutinizer05 | we don't even know about RMS Watts of speakers |
| 12:24.43 | jonwil | Are N900 speakers easy to get on the open market? |
| 12:24.54 | DocScrutinizer05 | relatively easy, yeah |
| 12:25.19 | jonwil | ok, so we could keep the same audio chip, same speakers etc without problems |
| 12:25.27 | jonwil | if we wanted to do that |
| 12:25.37 | DocScrutinizer05 | we probably have to do that |
| 12:25.43 | *** join/#maemo-ssu oooaaaooo1 (~rootzilla@d122-109-45-144.per802.wa.optusnet.com.au) |
| 12:25.57 | jonwil | yeah unless we can get some info on the closed blobs from somewhere... |
| 12:26.00 | DocScrutinizer05 | though I already hear Nikolus shouting "not it!" |
| 12:26.26 | oooaaaooo1 | how do i know if cssu is installed? |
| 12:26.36 | oooaaaooo1 | is there a command line to check |
| 12:26.43 | DocScrutinizer05 | check "about" in settings |
| 12:28.31 | oooaaaooo1 | cool it says cssu installed |
| 12:28.37 | DocScrutinizer05 | FatPhil_: how much help from former audio developers could you possibly get? do we have a chance to free up audio? |
| 12:28.43 | oooaaaooo1 | how do i "test" it |
| 12:28.57 | DocScrutinizer05 | oooaaaooo1: enable rotation |
| 12:29.07 | DocScrutinizer05 | when you're on CSSU-Testing |
| 12:29.13 | oooaaaooo1 | <PROTECTED> |
| 12:29.42 | oooaaaooo1 | how do i enable rotation |
| 12:29.53 | jonwil | Do we know who did the pulseaudio stuff? |
| 12:30.00 | DocScrutinizer05 | then you can install rotatation lock applet (or similar name), get an icon in status area and a menu button in status menu |
| 12:30.11 | oooaaaooo1 | alrighty |
| 12:30.14 | DocScrutinizer05 | jonwil: good question |
| 12:30.58 | DocScrutinizer05 | oooaaaooo1: see |
| 12:30.59 | jonwil | the maintainer in the repo packages file is just listed as multmedia@maemo.org |
| 12:31.02 | DocScrutinizer05 | ~jrtools |
| 12:31.03 | infobot | well, jrtools is http://wiki.maemo.org/User:Joerg_rw/tools |
| 12:31.38 | DocScrutinizer05 | it has instructions on how to *block* rotation, you should be clever enough to invert those |
| 12:31.52 | DocScrutinizer05 | jonwil: great :-P |
| 12:34.06 | DocScrutinizer05 | (audio) I think cmt_speech will become another PITA to put to work on a new modem |
| 12:34.34 | jonwil | yeah that ties into the closed audio blobs I suspect :( |
| 12:34.39 | DocScrutinizer05 | we had our share of fun to make BB5 audio work with/in/under SHR |
| 12:35.25 | DocScrutinizer05 | we had sourcecode for cmt_speech cmdline tool(?), so it wasn't too hard |
| 12:36.17 | DocScrutinizer05 | the other way round is probably magnitudes harder: we know how to talk to modem but no clue about the "upstream" ABI into maemo-audio |
| 12:37.27 | jonwil | https://gitorious.org/meego-cellular/libcmtspeechdata might be interesting |
| 12:37.51 | DocScrutinizer05 | but then, I guess we could even hack that on kernel level, converting the Option audio to the waird ISI.... err *cough* |
| 12:39.09 | jonwil | https://gitorious.org/maemo-multimedia/pulseaudio-modules-meego might also help |
| 12:39.12 | DocScrutinizer05 | jonwil: "Kai Vehmanen", eh? |
| 12:39.18 | jonwil | and maybe stuff under https://gitorious.org/maemo-multimedia/ |
| 12:40.21 | DocScrutinizer05 | jonwil: sounds good, I haven't lloked into it though, thus dunno if it's sufficient to get our freemantle audio to work |
| 12:40.28 | DocScrutinizer05 | looked* |
| 12:47.25 | jonwil | I think we need to look firstly at what meego/mer/nemo/etc are using on the N900 (they may not have all the algorithms but they appear to have enough for functioning system, secondly we should look at audio code as it was when it was first released for meego (i.e. older revisions in https://gitorious.org/maemo-multimedia/pulseaudio-modules-meego and matching meego blobs) and also see if we... |
| 12:47.27 | jonwil | ...can find someone who can share info |
| 12:54.34 | jonwil | of course a nice copy of pulseaudio-nokia-0.9.15.0-49+0m5.tar.gz would be the ideal solution but that's never gonna happen :( |
| 12:57.37 | jonwil | That is probably the #1 piece of source code that I would have if I could have any one source package from the N900 :) |
| 13:08.39 | jonwil | That and the wirelessmodemapi docs for the N900 cellmo |
| 13:11.27 | Pali | "[14:07:20] <DocScrutinizer05> snd-soc-rx51.hp_lim=42 snd-soc-tlv320aic3x.hp_dac_lim=6" this cmdline is not needed anymore in last PR1.3 kernel all that values are in board rx51 files |
| 13:12.53 | Pali | "[14:13:02] <jonwil> the closed source pa blobs also talk to BME for something" closed PA blobs only asking BME battery temperature every minute |
| 13:13.30 | Pali | DocScrutinizer05 should rememeber that we already RE battery temperature ADCIN formula and we already have kernel driver for it |
| 13:18.28 | Pali | DocScrutinizer05, jonwil: Nokia moved all closed PA bits into some PA nokia algo package and after that they opened closed PA modules |
| 13:18.55 | Pali | so what is needed is to RE that one closed pa algo library |
| 13:19.07 | Pali | other sources are on gitorious |
| 13:20.55 | Pali | closed modules are: libnokia-common.so, module-nokia-audiots.so, module-nokia-algorithm-agc.so, module-nokia-algorithms.so |
| 13:21.10 | Pali | other PA modules are open (and/or) using these closed modules |
| 13:23.42 | jonwil | yeah figuring out what algorithims and other things are in those blobs would help |
| 13:25.35 | DocScrutinizer05 | great, Nokia developed a ubercool own proprietary AGC algo :-S PFFFF |
| 13:26.18 | Pali | it looks like that code which is in above libraries is somehow linked in closed fremantle modules too... |
| 13:26.31 | DocScrutinizer05 | and it has so extremely valuable precious intelectual property that they had to do it in a closed source blob |
| 13:27.19 | Pali | there is also one closed module pulseaudio-modules-nokia-parameters but somehow in lasts git commits there is source code drop :D |
| 13:27.21 | DocScrutinizer05 | ¡¡¡¡¡¡¡¡¡ (if that wasn't clear) |
| 13:27.30 | Pali | (in meego pa modules repo) |
| 13:27.41 | DocScrutinizer05 | ¡ == sarcasm tag |
| 13:30.57 | Pali | author of closed pa modules can be Jyri Sarha |
| 13:31.23 | jonwil | I note that oldest pulseaudio in meego code drop is a fair few versions newer than Fremantle version |
| 13:31.45 | jonwil | looking at main pulseaudio tree that is |
| 13:32.03 | *** join/#maemo-ssu NIN101 (~NIN@p5DD29AA0.dip0.t-ipconnect.de) |
| 13:33.12 | jonwil | Juho Hämäläinen may also be someone who would know about pulseaudio nokia stuffs |
| 13:33.16 | DocScrutinizer05 | yeah, "our" PA is not even API/ABI compatible to recent versions, so we can't recompile PA since the Nokia blobs wouldn't match anymore - or so I heard |
| 13:34.57 | DocScrutinizer05 | I bet there's an AEC (echo cancellation) cloded blob as well, somewhere |
| 13:35.10 | DocScrutinizer05 | closed* |
| 13:35.58 | jonwil | https://gitorious.org/maemo-multimedia/pulseaudio-modules-meego/commit/5ba46c1e71cfc4b309a42b0ac69fe018d5f40837 is very interesting |
| 13:36.19 | jonwil | Its close to the oldest revision in pulseaudio-modules-meego |
| 13:36.49 | jonwil | and it shows options for linking in certain algorithims that weren't opened up |
| 13:37.07 | jonwil | in this case something called "audio tuning support" |
| 13:37.15 | jonwil | and "music module DRC" |
| 13:37.24 | jonwil | and "music module STW" |
| 13:37.29 | jonwil | and "xprot" |
| 13:37.42 | jonwil | and "xprot-ambient-temprature" (which is what needs BME temp) |
| 13:38.00 | jonwil | and also "equalizers" |
| 13:38.08 | jonwil | and "AEP algorithm" |
| 13:40.24 | jonwil | bearing in mind that pulseaudio on MeeGo will have been changed a lot to talk to ofono rather than CSD |
| 13:41.16 | Pali | jonwil: not, it has support for both ofono and csd |
| 13:41.21 | jonwil | ok |
| 13:41.39 | Pali | jonwil: above repo is harmattan |
| 13:41.45 | Pali | not generic meego |
| 13:41.49 | jonwil | ok |
| 13:41.55 | jonwil | looks like there is a sidetone lib in there somewhere too |
| 13:44.00 | jonwil | it will support harmattan flavor of CSD which is quite possibly different from Fremantle flavor |
| 13:44.14 | jonwil | not that reverse engineering how pulseaudio-* talks to CSD is hard |
| 13:46.25 | kerio | why does pulseaudio have to talk to csd? |
| 13:46.29 | kerio | shouldn't it be the reverse? |
| 13:48.29 | jonwil | well module-nokia.voice on N900 listens to signal com.nokia.csd.Call.Instance.AudioConnect |
| 13:49.24 | kerio | oh, so it's not just a normal client like any other program that uses audio |
| 13:51.24 | Pali | here is some info about that closed modules: http://marc.info/?l=meego-commits&m=129651840007755 |
| 13:51.38 | Pali | because meego servers are already down we do not have anything else... |
| 13:52.01 | Pali | source code of parameters package is already in git |
| 13:52.23 | Pali | hm, I have downloaded copy of that libraries |
| 13:52.25 | jonwil | the cellular voice parts of the system need to talk to both the cellular services daemon and the system syncronization controller daemon (which handles cellular modem state) |
| 13:52.34 | Pali | so are not lost forever |
| 13:53.45 | jonwil | ok, so on the N900, the only closed-module that needs to talk to a com.nokia.* dbus interface is module-nokia-voice.so |
| 13:54.01 | jonwil | it is wired up to signal com.nokia.csd.Call.Instance.AudioConnect |
| 13:54.23 | jonwil | com.nokia.csd.Call.ServerStatus |
| 13:54.52 | jonwil | and com.nokia.phone.SSC.modem_state_changed_ind |
| 13:55.00 | jonwil | all 3 of those make sense for it to be wired up to |
| 13:55.21 | jonwil | AudioConnect is likely to tell it to activate cellular audio |
| 13:55.27 | jonwil | modem state is so it knows if the modem is up or down |
| 13:55.39 | jonwil | and server status not sure about but probably related to call state |
| 13:57.00 | jonwil | AudoConnect signal ends up in cmtspeech_state_change_call_connect |
| 13:57.03 | *** join/#maemo-ssu freemangordon_ (~freemango@213.137.35.49) |
| 13:57.41 | jonwil | ServerStatus ends up in cmtspeech_state_change_call_status |
| 13:58.17 | jonwil | modem state change ends up calling cmtspeech_protocol_state and pa_asyncmsgq_post |
| 13:58.34 | jonwil | I am currently checking out the earliest tree of pulseaudio-modules-meego to analyze |
| 14:01.13 | DocScrutinizer05 | jonwil: great analysis, please convert it into some ascii-graphics and publish it on wiki |
| 14:01.34 | jonwil | I am too tired to write wiki posts right now :P |
| 14:02.07 | DocScrutinizer05 | then throw a copy of chanlog there. so it won't get lost again |
| 14:02.21 | DocScrutinizer05 | you can edit and beautify it later |
| 14:04.49 | jonwil | great, looks like the oldest tree of pulseaudio-modules-meego is talking to the right CSD interfaces |
| 14:04.52 | jonwil | i.e. the maemo ones |
| 14:04.54 | jonwil | that helps |
| 14:06.33 | jonwil | great, that means we now have documentation of all 3 of those dbus calls I just mentioned :) |
| 14:06.40 | *** join/#maemo-ssu freemangordon (~freemango@213.137.35.49) |
| 14:07.04 | *** part/#maemo-ssu freemangordon (~freemango@213.137.35.49) |
| 14:07.33 | jonwil | or at least something about what those do |
| 14:07.43 | DocScrutinizer05 | \o/ |
| 14:08.18 | DocScrutinizer05 | AEP is very important - well the other ones as well |
| 14:11.19 | jonwil | what is AEP? |
| 14:11.41 | DocScrutinizer05 | err Audio Enhancement Processing sth |
| 14:12.16 | jonwil | so where would the echo cancellation be? |
| 14:12.59 | DocScrutinizer05 | AEP (Audio Enhancements Packag http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Architecture/Multimedia_Domain#EAP_and_AEP |
| 14:13.25 | DocScrutinizer05 | >>AEP (Audio Enhancements Package) is a full duplex speech audio enhancement package including echo cancellation, background noise suppression, DRC, AGC, etc. Both EAP and AEP are implemented as a PulseAudio module.<< |
| 14:14.01 | jonwil | ok |
| 14:14.04 | Pali | ah that graph is too compilacted |
| 14:14.36 | DocScrutinizer05 | ~wtf drc |
| 14:17.07 | jonwil | ok, so do we know what STW is? |
| 14:17.20 | jonwil | stw might be stereo widening |
| 14:18.22 | jonwil | probably something to make stereo output sound better |
| 14:19.35 | Pali | btw nemo n900 port totally dropped all closed nokia pa modules |
| 14:24.33 | DocScrutinizer05 | jonwil: stereo widening R'=R-n*L, L'=L-n*R |
| 14:25.29 | DocScrutinizer05 | or in plain english: add inverted other side channel a bit |
| 14:25.50 | DocScrutinizer05 | 0<=n<=1 |
| 14:26.19 | DocScrutinizer05 | 0= normal stereo, 1=nonsense, basically momo |
| 14:26.23 | DocScrutinizer05 | mono* |
| 14:27.50 | jonwil | seems like a few things were opened (like parameters and sidetone) then they dropped all the rest presumably as not 100% essential for working usable phone |
| 14:28.50 | DocScrutinizer05 | for a start it seems we need libcmtspeech working with new modem, and ALSA working with new audio codec exactly same way it did with old one - otherwise PED policies will fail miserably |
| 14:29.03 | jonwil | I do note that the HEAD of pulseaudio-modules-meego has files speech_src_neon_hardfp.a and speech_src_neon.a |
| 14:29.13 | DocScrutinizer05 | the rest should "just work(TM)" |
| 14:29.42 | freemangordon_ | DocScrutinizer05: camera interface is pretty much different |
| 14:29.55 | DocScrutinizer05 | errr |
| 14:30.32 | DocScrutinizer05 | sure, but that's not audio, eh? And btw camera will see *major* rework to look like N900 100% |
| 14:31.09 | freemangordon_ | sure, just saying |
| 14:31.10 | DocScrutinizer05 | down to the mux between front and back |
| 14:31.17 | freemangordon_ | BTW I meant from the SW side |
| 14:31.36 | freemangordon_ | kernel ifaces are different/non-existing |
| 14:31.46 | DocScrutinizer05 | so different between which two entites? |
| 14:32.04 | freemangordon_ | 2.6.28 and 3.x |
| 14:32.14 | DocScrutinizer05 | oh, you and your 3.x :-P |
| 14:32.31 | freemangordon_ | I don;t hink we have a choice for neo900 |
| 14:32.33 | freemangordon_ | ;) |
| 14:32.56 | freemangordon_ | well, ok |
| 14:33.11 | DocScrutinizer05 | you say this to get your beloved contemporary kernel :-> |
| 14:33.29 | freemangordon_ | :D |
| 14:33.33 | freemangordon_ | no |
| 14:34.07 | DocScrutinizer05 | I don't see why we can't build KP52 for Neo900 |
| 14:35.01 | DocScrutinizer05 | tiny adjustments to board file |
| 14:35.02 | jonwil | Camera shouldn't be a problem as its fairly well separated from the rest of the system |
| 14:35.22 | jonwil | btw http://mirror.yandex.ru/mirrors/meego/releases/1.1/non-oss/repos/armv7l/packages/armv7l/ contains the binary bits for the Meego PulseAudio blobs |
| 14:35.52 | DocScrutinizer05 | courtesy Nokia, meh! |
| 14:36.08 | jonwil | courtesy Nokia what? |
| 14:36.38 | DocScrutinizer05 | where else would meego aka stskeeps have gotten the closed blobs for meego from? |
| 14:37.19 | jonwil | yeah |
| 14:37.35 | freemangordon_ | sailus: ping |
| 14:37.36 | DocScrutinizer05 | and "meh!" because Nokia gave meego all they asked for, while maemo community not even got an answer when asking for exactly same |
| 14:44.00 | kerio | DocScrutinizer05: wait, n=1 should be no sound whatsoever |
| 14:44.17 | DocScrutinizer05 | only for mono signals |
| 14:44.32 | kerio | R' and L' are exactly the opposite |
| 14:44.44 | kerio | if you're in the middle of the speakers, there's no sound |
| 14:44.51 | DocScrutinizer05 | for any stereo component L=-R |
| 14:45.05 | DocScrutinizer05 | for n=1 |
| 14:45.35 | kerio | yeah, and that means that you get no sound :D |
| 14:46.47 | DocScrutinizer05 | basically no sound, that's right. Though sometimes this is used for karaoke, since the vocals are supposed to be mono and thus "filtered out" while instruments have larger stereo component |
| 14:47.22 | DocScrutinizer05 | and L=-R doesn't mean no sound at all |
| 14:47.34 | jonwil | If we have any contacts inside nokia that might be able to share anything at all about pulseaudio blobs, NOW is the time to exercise those contacts and do whatever we can :P |
| 14:47.50 | DocScrutinizer05 | it just means the sound is not at all located in middle between the speakers |
| 14:47.51 | kerio | well ok it's no sound if you only have one ear and that ear is in the middle of the speakers |
| 14:49.18 | DocScrutinizer05 | FatPhil_: ^^^ |
| 14:49.30 | DocScrutinizer05 | unclouded: ( jonwil ) |
| 14:49.37 | DocScrutinizer05 | ETAB |
| 14:49.48 | DocScrutinizer05 | FatPhil_: ( jonwil ) |
| 14:50.14 | DocScrutinizer05 | didn't even notice ujfalusi left channel |
| 14:51.09 | DocScrutinizer05 | kerio: in an ideal world with singularity ear, yes |
| 14:51.51 | kerio | damn real world screwing up with my maths >:( |
| 14:52.04 | DocScrutinizer05 | Van Gogh listening to a hole in the wall that is exactly in the middle of two ideal speakers, might have no sound at all |
| 14:52.13 | FatPhil_ | L-R means remove all mono components. |
| 14:52.29 | DocScrutinizer05 | exactly |
| 14:52.44 | FatPhil_ | Some high end turntables have that as an output option, so that you can balance the stylus properly |
| 14:52.59 | DocScrutinizer05 | but L=-R doesn't mean no sound |
| 14:53.39 | DocScrutinizer05 | actually a lot of incorrectly installed home stereo do L=-R |
| 14:54.23 | DocScrutinizer05 | it's not even easy to notice when you listen to such home stereo |
| 14:54.43 | DocScrutinizer05 | well, for Joe Average at least |
| 14:55.40 | FatPhil_ | It's pretty much the same as L=R, but with the cancellation/reinforcement regions moved around |
| 14:56.31 | FatPhil_ | jonwil: there are no contacts inside nokia with any connections to maemo or even meego any more |
| 14:57.14 | jonwil | After this nice discussion, I am now going to label audio as the most difficult piece of the jigsaw puzzle with cellular modem being bumped down to second most difficult |
| 14:57.15 | FatPhil_ | we all got given the boot, or moved to meltemi. And those then got given the boot! |
| 14:57.37 | jonwil | cellular modem is just a matter of dbus calls, audio is a LOT harder |
| 14:57.59 | jonwil | even if we copy nokia Audio circutry and chips and parts (speakers and microphone included) exactly |
| 15:00.01 | jonwil | camera I dont think will be a major issue |
| 15:02.16 | DocScrutinizer05 | jonwil: how can audio be any hard on an identical hw platform with an identical kernel? |
| 15:06.35 | DocScrutinizer05 | (libcmtspeech for Option) https://gitorious.org/meego-cellular/libcmtspeechdata/source/7f8f3ce357513e4849e1bf6d657980a514529c1a:doc/README-devel.txt#L62 |
| 15:07.39 | jonwil | Do we want to be 100% compatible with the closed-source upstream consumers of pulseaudio (including things like flashplayer, skype and others)? |
| 15:08.08 | jonwil | I assume we do |
| 15:09.01 | DocScrutinizer05 | sure |
| 15:09.42 | DocScrutinizer05 | absolutely |
| 15:10.45 | jonwil | In that case we will likely need to use the same pulseaudio bits the N900 is using since there is no gaurantee that whatever Harmattan is using (i.e. whatever is currently in https://gitorious.org/maemo-multimedia/pulseaudio-modules-meego/ https://gitorious.org/maemo-multimedia/pulseaudio/ etc) will be API or ABI compatible with the Maemo version |
| 15:11.20 | jonwil | Or do we have evidence showing that whats in those repos IS ABI compatible with Fremantle PulseAudio bits? |
| 15:13.37 | DocScrutinizer05 | I think we rather have indications that it is _not_ |
| 15:13.43 | jonwil | ok |
| 15:14.56 | DocScrutinizer05 | so I think it's TLV320aic34 plus other gear, in Neo900 |
| 15:15.05 | DocScrutinizer05 | or project dies |
| 15:15.18 | jonwil | The way I see it our options are: |
| 15:15.44 | jonwil | 1.Try to get code for pulseaudio-nokia on fremantle (wont happen so lets ignore this) |
| 15:17.02 | jonwil | 2.Use pulseaudio-modules-meego and other bits in those GIT repos and make them ABI compatible with Fremantle (and also port libcmtspeech to Neo900 modem). This would mean we miss out on AGC and whatever other algos are in the MeeGo Nokia blobs that were dropped |
| 15:18.02 | DocScrutinizer05 | 3. throw another ~20EUR at audio hw in Neo900 to make it clone of N900 |
| 15:18.30 | jonwil | 3.Like #2 except that we use the older versions of those git repos back when they were still using the pulseaudio-modules-nokia MeeGo blobs |
| 15:19.45 | jonwil | 4.Use the Fremantle PulseAudio bits and modify the cmtspeech kernel driver to talk the right ABI to the Fremantle pulseaudio bits but to then translate to whatever the Neo900 modem needs |
| 15:20.37 | DocScrutinizer05 | 4. it is |
| 15:20.46 | DocScrutinizer05 | https://gitorious.org/meego-cellular/libcmtspeechdata/source/7f8f3ce357513e4849e1bf6d657980a514529c1a:doc/README-devel.txt#L62 |
| 15:23.02 | DocScrutinizer05 | seems option GTM601 has a simple PCM audio that is connected to SoC via McBSP as usual |
| 15:26.16 | jonwil | or 5.Reverse engineer libcmtspeech in the Fremantle module-nokia-voice.so and turn what we have in https://gitorious.org/meego-cellular/libcmtspeechdata/ into a copy of the Fremantle bits (or at the very least, the nokiamodem specific bits) then having done that, write a fremantle-libcmtspeech-compatible backend for the Neo900 modem and use some mods/hacks/whatever to replace the relevant... |
| 15:26.17 | jonwil | ...parts of libcmtspeech in module-nokia-voice.so of Fremantle with our new compile |
| 15:26.30 | jonwil | The fact that libcmtspeech is a static library and not a .so doesn't help us :( |
| 15:33.51 | *** join/#maemo-ssu oldtopman (~oldtopman@unaffiliated/oldtopman) |
| 15:36.47 | *** join/#maemo-ssu dos1 (~dos@unaffiliated/dos1) |
| 15:38.16 | DocScrutinizer05 | it's STATIC?? |
| 15:38.27 | DocScrutinizer05 | FFS |
| 15:38.33 | jonwil | yes it is |
| 15:38.40 | jonwil | looks like Fremantle is using version 1.6.2.1 |
| 15:38.55 | jonwil | oldest we have in repo is 2.0.5 |
| 15:39.36 | DocScrutinizer05 | headdesks |
| 15:41.08 | jonwil | now you see why I said "audio is going to be hard" |
| 15:41.32 | jonwil | :) |
| 15:41.35 | DocScrutinizer05 | so what's next API stack-upwards? |
| 15:42.03 | DocScrutinizer05 | PA shit? |
| 15:42.12 | jonwil | yes |
| 15:42.18 | DocScrutinizer05 | :-(( |
| 15:43.29 | DocScrutinizer05 | well, I guess we can RE this |
| 15:44.01 | DocScrutinizer05 | prolly an extremely thin PA interface layer over a heavy libcmtspeech |
| 15:47.50 | jonwil | no its not that simple, libcmtspeech is linked into fremantle module-nokia-voice.so with a LOT of other code |
| 15:48.20 | jonwil | some of which ended up in pulseaudio-modules-meego |
| 15:48.26 | jonwil | and some of which ended up in the nokia blobs |
| 15:49.35 | DocScrutinizer05 | OMG |
| 15:49.46 | jonwil | OMG what? |
| 15:50.01 | DocScrutinizer05 | Nokia actually did *everything* to counteract RE and re-use |
| 15:50.26 | jonwil | no they did what they needed to do to make things work whilst minimizing the amount of code they needed to actually open up |
| 15:50.29 | DocScrutinizer05 | I wish speedevil's statement on this was on a infobot factoid |
| 15:52.27 | DocScrutinizer05 | yep, and when they opened up code, they made sure it depends on another glue-bit that is closed so you can't use the open stuff for anything anywhere else |
| 15:53.48 | jonwil | The closed glue no doubt contains those algorithms that Nokia considers important |
| 15:53.58 | jonwil | i.e. those which are special to them and that they dont want their competitors to see |
| 15:54.33 | DocScrutinizer05 | yes, but why did they link statically?? |
| 15:54.54 | DocScrutinizer05 | just to show *us* the finger |
| 15:55.57 | DocScrutinizer05 | and on "special to them" see at least my comment about AGC above. AGC is so silly simple, it's ridiculous to have an own algo in a blob |
| 16:01.08 | jonwil | they probably linked libcmtspeech statically because it was easier and meant one less shared library (and less code duplication) |
| 16:02.51 | jonwil | Now do you agree with me that audio is hardest part of Neo900 work (harder than cell modem, harder than GPS, harder than camera)? |
| 16:14.09 | jonwil | short of a miracle occurring our best hope is to rewrite the N900 kernel cmtspeech driver to talk to the Neo900 modem and translate whatever Nokia proprietary info is sent down as appropriate |
| 16:14.27 | *** join/#maemo-ssu amizraa (~amizraa@gateway/tor-sasl/amizraa) |
| 16:14.43 | jonwil | and even then doing that will be HARD :) |
| 16:28.32 | Pali | freemangordon: something new? |
| 16:28.48 | freemangordon_ | Pali: no :( |
| 16:29.01 | freemangordon_ | besides just enabled clock and gpio debug |
| 16:29.15 | freemangordon_ | hoping it will give me some more info |
| 16:31.19 | Pali | ok |
| 16:31.37 | freemangordon_ | nice: ssi_sst_fck_3430es2 0 0 110666666 |
| 16:31.48 | freemangordon_ | 0 0 is prepare/enable count |
| 16:31.59 | freemangordon_ | this is ssi transmit clk aiui |
| 16:32.06 | freemangordon_ | no wonder it doesn;t work |
| 16:41.00 | *** join/#maemo-ssu Vlad_on_the_road (~Vlad_on_t@ip-66.net-82-216-1.versailles2.rev.numericable.fr) |
| 16:43.44 | *** join/#maemo-ssu kerio (kerio@acehack.de) |
| 17:30.36 | *** join/#maemo-ssu xes (~xes@unaffiliated/xes) |
| 17:53.02 | *** join/#maemo-ssu bsdmaniak (~bsdmaniak@std93-20-88-120-139-80.fbx.proxad.net) |
| 18:18.23 | *** join/#maemo-ssu arcean (~arcean@aadb186.neoplus.adsl.tpnet.pl) |
| 18:23.41 | *** join/#maemo-ssu nox- (noident@freebsd/developer/nox) |
| 18:28.32 | *** join/#maemo-ssu arcean (~arcean@aadb186.neoplus.adsl.tpnet.pl) |
| 19:16.28 | *** join/#maemo-ssu freemangordon (~freemango@213.137.35.49) |
| 19:18.27 | *** join/#maemo-ssu M4rtinK (~M4rtinK@46.227.13.46) |
| 19:19.10 | *** join/#maemo-ssu Martix_ (~martix@46.227.13.46) |
| 19:21.45 | *** join/#maemo-ssu mkaindl (~mkaindl@ama-dablam.markus-kaindl.de) |
| 20:42.32 | *** join/#maemo-ssu xes_ (~xes@unaffiliated/xes) |
| 20:47.35 | *** join/#maemo-ssu xes (~xes@unaffiliated/xes) |
| 21:45.04 | *** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172) |
| 21:46.26 | freemangordon | sailus: ping |
| 21:47.09 | freemangordon | Pali: some news - seems there is a bug in clock framework, on 2.6.28 SSI clock chain is: |
| 21:47.24 | freemangordon | "/sys/kernel/debug/clock/virt_19_2m_ck/osc_sys_ck/sys_ck/dpll3_ck/dpll3_x2_ck/dpll3_m2x2_ck/corex2_fck/ssi_ssr_fck/ssi_sst_fck/" |
| 21:48.03 | freemangordon | on 3.10 it is: |
| 21:48.27 | freemangordon | well, different :) |
| 21:48.37 | freemangordon | I fixed that, but still no joy :( |
| 21:49.08 | freemangordon | Pali: any idea what notion m2x2 (in clock names) means? |
| 21:49.31 | Pali | no idea |
| 21:50.24 | Pali | freemangordon: another question: is audio working with 3.10? |
| 21:50.25 | freemangordon | I am out of ideas, I see cawake interrupts (which IMO means the modem is alive and trying to communicate) |
| 21:50.28 | freemangordon | Pali: no |
| 21:50.47 | Pali | ok |
| 21:50.55 | freemangordon | ... but I see no port interrupts |
| 21:51.07 | Pali | in 3.5 or 3.8 audio worked |
| 21:51.28 | Pali | I remember that I heard nokia welcome video |
| 21:51.28 | freemangordon | I see errors from PA |
| 21:51.49 | freemangordon | well, that means DSP was working too |
| 21:51.54 | DocScrutinizer05 | freemangordon: do you have a IRQ-handler set up for that IRQ? |
| 21:51.58 | freemangordon | yes |
| 21:52.11 | freemangordon | and I see it in /proc/interrupts |
| 21:52.17 | Pali | yes, dsp worked before 3.10 (or 3.9) before multiarch for omap3 was introduced |
| 21:52.17 | freemangordon | but with count of 0 |
| 21:52.17 | DocScrutinizer05 | is it ever executed? |
| 21:52.24 | freemangordon | no |
| 21:52.32 | DocScrutinizer05 | check your IRQ settings |
| 21:52.45 | DocScrutinizer05 | IRQ on OMAP are... weird |
| 21:53.07 | Pali | freemangordon: for audio you can try to revert my two audio patches in git tree and then manually load audio kernel modules |
| 21:53.10 | freemangordon | but cawake interrupt handler is executed |
| 21:53.10 | freemangordon | port interrupt is not connected to gpio |
| 21:53.10 | freemangordon | they are fine, it is irq 67 |
| 21:53.12 | Pali | maybe there is problem |
| 21:53.27 | freemangordon | Pali: I want SSI working :) |
| 21:53.33 | DocScrutinizer05 | e.g the IRQ dispatcher/mux needs *clock* to even notice a IRQ, unless it's a wakeup IRQ, afaik |
| 21:53.40 | Pali | I tried to migrate audio driver/configuration to new format with hotplug and module autoload support |
| 21:53.41 | Pali | ok |
| 21:54.04 | freemangordon | DocScrutinizer05: do you have SSI documentation by chance? |
| 21:54.16 | freemangordon | I hate to work blindly |
| 21:54.20 | DocScrutinizer05 | sorry nope, lost it with my last job |
| 21:54.49 | freemangordon | do the guys with gta04 have it? |
| 21:55.04 | freemangordon | I mean, SSI os a part of OMAP |
| 21:55.08 | freemangordon | *is |
| 21:55.32 | DocScrutinizer05 | had several 1000 pages of printed docu about MIPI HSI, IRQ in OMAP4 (or the lack of...), SSI, UART, whatnot else |
| 21:55.59 | freemangordon | DocScrutinizer05: BTW for sure 3.x sets MUX incorrectly for rx51 |
| 21:56.21 | DocScrutinizer05 | I'm not surprised |
| 21:56.23 | freemangordon | but this is internal IRQ, MUX config should not matter IMO |
| 21:56.38 | freemangordon | irq 67, any bell? |
| 21:56.46 | DocScrutinizer05 | right, it's internal interrupt |
| 21:56.54 | DocScrutinizer05 | nope |
| 21:57.03 | freemangordon | ssi_p1_mpu_irq0 |
| 21:57.11 | freemangordon | shit |
| 21:57.50 | DocScrutinizer05 | IroN900:~# grep "67:" /proc/interrupts |
| 21:57.51 | DocScrutinizer05 | <PROTECTED> |
| 21:58.11 | freemangordon | yep, the same with 3.10, but count is 0 |
| 21:58.56 | freemangordon | honestly, no idea where else to look at |
| 21:59.17 | freemangordon | maybe I need to set some consumer? |
| 21:59.18 | DocScrutinizer05 | hmm, 67 not listed in /sys/kernel/debug/omap_gpio |
| 21:59.35 | freemangordon | it is not gpio |
| 21:59.50 | DocScrutinizer05 | err, THAT rings a bell. Though absolutely nothing more than that |
| 22:00.02 | DocScrutinizer05 | "consumer" |
| 22:00.15 | DocScrutinizer05 | think I heard coleagues bitch about that |
| 22:00.36 | freemangordon | yep, of some power supply |
| 22:00.42 | freemangordon | but that makes no sense either, as driver seems to communicate with SSI core |
| 22:00.44 | DocScrutinizer05 | aaah right |
| 22:00.58 | freemangordon | ? |
| 22:01.11 | DocScrutinizer05 | "power supply consumer" |
| 22:01.16 | freemangordon | yep |
| 22:01.34 | freemangordon | for RAPU/GAZOO |
| 22:02.26 | freemangordon | but if cmt is not powered I won;t have cawake interrupts, right? |
| 22:03.11 | DocScrutinizer05 | consider using a different GPIO/IRQ, just for testing purposes. Like GPIO_68 cam-focus |
| 22:03.31 | freemangordon | hmm, what for? |
| 22:03.36 | DocScrutinizer05 | well, I think THAT is a given fact |
| 22:03.52 | freemangordon | for sure this is the correct IRQ, see 2.6.28 |
| 22:04.20 | DocScrutinizer05 | sure, I just thought you could press button and see if IRQ-handler jumps |
| 22:04.38 | freemangordon | 67: 0 INTC ssi_p1_mpu_irq0 |
| 22:04.57 | DocScrutinizer05 | if you can't debug that pin, just debug another one ;-) |
| 22:05.04 | freemangordon | I see in init code IRQ handler attached |
| 22:05.31 | freemangordon | oh, got it |
| 22:05.32 | freemangordon | but I think this will be just a waste of time |
| 22:06.20 | freemangordon | BTW in dsp driver there is a code laying with SSI clocks |
| 22:06.30 | freemangordon | *playing |
| 22:06.54 | DocScrutinizer05 | I could tell you a lot about "set this bit, clear that bit2 but it's useless since not applicable for the level you're working on |
| 22:07.54 | DocScrutinizer05 | and I have no clue about all those kernel macros used for IRQ and the like |
| 22:08.46 | freemangordon | in case you are interested, http://pastebin.com/ji3m5He3 |
| 22:08.51 | freemangordon | gpios |
| 22:08.58 | DocScrutinizer05 | I definitely can debug and hack a kernel driver, but I can't write one, or find the huge missing elephant |
| 22:09.34 | freemangordon | MUX config http://pastebin.com/8P1e7M18 |
| 22:09.39 | DocScrutinizer05 | I wouldn't even notice it's missing |
| 22:09.50 | freemangordon | the elephant? :) |
| 22:10.51 | freemangordon | clocks http://pastebin.com/PR4Vn5Au |
| 22:12.43 | DocScrutinizer05 | yep, the elephant. I don't know where it's supposed to show up |
| 22:13.45 | DocScrutinizer05 | but I will notice the peanut that's laying there despite it should've been eaten. Never heard it's elephant to eat it |
| 22:15.56 | DocScrutinizer05 | yay, MUCH better: http://pastebin.com/raw.php?i=PR4Vn5Au (the format) |
| 22:16.05 | *** join/#maemo-ssu Martix_ (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 22:16.16 | freemangordon | yep |
| 22:16.36 | DocScrutinizer05 | felt nausea from seasickness from http://pastebin.com/PR4Vn5Au |
| 22:17.51 | DocScrutinizer05 | wtf is "rate"? |
| 22:18.03 | DocScrutinizer05 | oh nm |
| 22:18.07 | freemangordon | Hz |
| 22:18.09 | freemangordon | frequency |
| 22:18.12 | DocScrutinizer05 | sure |
| 22:19.45 | DocScrutinizer05 | no idea |
| 22:20.17 | DocScrutinizer05 | except.... use F-Bus to get modem bootlog |
| 22:20.25 | DocScrutinizer05 | ;-) |
| 22:20.37 | freemangordon | well, the only thing I didn't play with is regulator consumers |
| 22:21.11 | DocScrutinizer05 | there are regulators in linux for BB5? |
| 22:21.12 | freemangordon | DocScrutinizer05: I am sure modem works (cawake changes) |
| 22:21.42 | freemangordon | see schematics, most of power supplies are connected to GAZOO |
| 22:21.52 | *** join/#maemo-ssu dhbiker (~dhbiker@95.87.145.172) |
| 22:22.06 | DocScrutinizer05 | sure, but gazoo I'd think is under control of BB5 firmware, not APE |
| 22:22.32 | freemangordon | yes, but power is controlled by omap (via twl) |
| 22:22.46 | DocScrutinizer05 | main modem power, yeah prolly |
| 22:23.05 | DocScrutinizer05 | some "CMT_EN" or whatever |
| 22:23.08 | freemangordon | so if linux *thinks* the regulator is not used, it shuts it down |
| 22:23.18 | freemangordon | cmt_en is a gpio |
| 22:23.28 | DocScrutinizer05 | I think it shuts whole modem down |
| 22:23.55 | DocScrutinizer05 | BB5 is a complete ARM system |
| 22:24.07 | DocScrutinizer05 | quite similar to OMAP3 |
| 22:24.18 | DocScrutinizer05 | GAZOO == GAIA |
| 22:24.22 | freemangordon | no, I mean - the hard way, by shutting the regulators down |
| 22:24.35 | freemangordon | look at p11 in schematics |
| 22:24.43 | DocScrutinizer05 | the regulators are not even connected to OMAP I'd guess |
| 22:24.46 | freemangordon | VANA,VIO, V!* etc |
| 22:24.47 | freemangordon | V18 |
| 22:24.54 | freemangordon | yes, but are controlled by omap |
| 22:25.13 | freemangordon | and this is the whole idea behind hwmod DT iiuc |
| 22:25.14 | DocScrutinizer05 | how are they controlled when not connected? per RF? |
| 22:25.19 | DocScrutinizer05 | or IrDA? |
| 22:25.21 | freemangordon | hwmod/DT |
| 22:25.48 | freemangordon | regulators are controlled by kernel via TWL |
| 22:26.08 | freemangordon | iiuc if usage count drops to 0 , the regulator is shut down |
| 22:26.18 | freemangordon | the same goes for clocks |
| 22:26.59 | DocScrutinizer05 | I can't see a single data line from OMAP to GAZOO |
| 22:27.13 | freemangordon | there is no |
| 22:27.29 | freemangordon | if we dont count gpios as data lines ofc |
| 22:27.31 | DocScrutinizer05 | then you can't control the regulators in GAZOO from OMAP |
| 22:28.10 | freemangordon | yes, but VANA,V18,VIO, etc are *inputs* to GAZOO iiuc |
| 22:28.17 | DocScrutinizer05 | they are controlled by RAPU like the regulators in GAIA are controlled by OMAP |
| 22:28.30 | DocScrutinizer05 | nope |
| 22:28.38 | freemangordon | sure? |
| 22:28.42 | DocScrutinizer05 | those are power line *outputs* from GAZOO |
| 22:28.45 | freemangordon | oh |
| 22:29.00 | freemangordon | VANA is output from GAZOO? |
| 22:29.10 | freemangordon | ok, if you say so |
| 22:29.49 | freemangordon | hmm, coorect |
| 22:29.49 | freemangordon | *correct |
| 22:30.03 | freemangordon | these are outgoing arrows |
| 22:30.27 | DocScrutinizer05 | and no VANA anywhere outside BB5 domain (except camera) |
| 22:30.45 | DocScrutinizer05 | those are the power supplies fro BB% |
| 22:30.48 | DocScrutinizer05 | 5 |
| 22:30.50 | DocScrutinizer05 | dang |
| 22:30.58 | freemangordon | ok, got it :) |
| 22:31.20 | freemangordon | hmm, well... |
| 22:31.32 | freemangordon | NFC where to look then :( |
| 22:32.40 | DocScrutinizer05 | check the single signal lines from OMAP to RAPU |
| 22:32.57 | DocScrutinizer05 | check the (one?) databus from OMAP to RAPU |
| 22:33.01 | freemangordon | I don't have HF scope here |
| 22:33.07 | DocScrutinizer05 | that's all that connects those two worlds |
| 22:33.23 | DocScrutinizer05 | is'l <10 lines |
| 22:33.27 | DocScrutinizer05 | it's |
| 22:33.38 | freemangordon | not to say I don;t want to disassemble my devel n900 |
| 22:34.13 | DocScrutinizer05 | Imeant check linux kernel what it does to those lines, compare to 2.6.28 |
| 22:34.39 | freemangordon | the same driver works with 3.5 |
| 22:34.43 | DocScrutinizer05 | strace cmt |
| 22:34.49 | DocScrutinizer05 | or libisi |
| 22:35.08 | freemangordon | DocScrutinizer05: it doesn;t work on lower layer |
| 22:35.23 | freemangordon | BOOT INFO REQ fails. Or rather receives no answer |
| 22:35.47 | freemangordon | And I think the reason is because IRQ is not triggered |
| 22:36.01 | DocScrutinizer05 | yes, maybe. but anything not working on lower layer should throw an erro on higgher layer. Great diagnose tool |
| 22:36.39 | freemangordon | well, I have the errors, something like - "timeout trying to power the modem", etc |
| 22:36.43 | DocScrutinizer05 | strace working system |
| 22:37.22 | freemangordon | no need, sscd (the one that powers the modem up) traces what it does in syslog |
| 22:37.28 | freemangordon | whne started with -d 3 |
| 22:37.37 | DocScrutinizer05 | timeout trying to power modem most likely means the APE waits for a "Hello, here I am!" from modem after doing cmt_en |
| 22:37.42 | freemangordon | yep |
| 22:38.50 | DocScrutinizer05 | you need to set up your interface prior tp powering up modem, otherwise "hello, here i am" gets lost. |
| 22:39.14 | DocScrutinizer05 | and maybe you need to send a "^Q" to make the modem start to talk at all |
| 22:39.39 | DocScrutinizer05 | ^Q == $random-init-sequence |
| 22:40.05 | DocScrutinizer05 | for coldflash bootloader it's "." afaik |
| 22:40.14 | DocScrutinizer05 | ascii 2." |
| 22:40.19 | DocScrutinizer05 | "." even |
| 22:40.26 | DocScrutinizer05 | a series of dots |
| 22:40.54 | DocScrutinizer05 | which tells bootloader that a "terminal" is attached |
| 22:41.45 | DocScrutinizer05 | for BB5 I guess you need to follow ISI specs on how to establish a communication between APE and BB5 |
| 22:42.04 | DocScrutinizer05 | wirelssmodemapi stuff |
| 22:42.44 | DocScrutinizer05 | http://www.cncmods.net/files/ |
| 22:43.40 | dos1 | wireless modem... lego? :) |
| 22:43.56 | DocScrutinizer05 | http://www.cncmods.net/files/Wireless%20Modem%20API%20G1%20V2%2010w49.zip |
| 22:44.27 | DocScrutinizer05 | initializing that ISI interface is not exactly trivial |
| 22:44.41 | freemangordon | hmm, wait, wtf? |
| 22:44.54 | freemangordon | is going to check something :) |
| 22:45.00 | jon_y | DocScrutinizer05: why are the wireless docs on a game modding site? :) |
| 22:45.08 | DocScrutinizer05 | it's not like BB5 is supposed to send some plaintext ascii "hello!" via a 192kb UART |
| 22:45.49 | DocScrutinizer05 | jon_y: that's a misconception |
| 22:46.04 | jon_y | how so? |
| 22:46.07 | DocScrutinizer05 | in reality they are on wirelessmodemapi.com |
| 22:46.18 | jon_y | oh ok, vhost |
| 22:46.36 | jon_y | well, not vhost |
| 22:46.45 | DocScrutinizer05 | if you want to call it a vhost, I guess we're fine with that :-) |
| 22:46.46 | jon_y | dns pointint to the same |
| 22:47.11 | DocScrutinizer05 | I'd call it jonwil's mirror |
| 22:47.33 | jon_y | he does CnC part time> |
| 22:47.35 | jon_y | ? |
| 22:47.45 | DocScrutinizer05 | *shrug* |
| 22:47.52 | DocScrutinizer05 | ~wtf CnC |
| 22:47.52 | jon_y | just curious how it ended up sharing |
| 22:48.02 | jon_y | Command and Conquer |
| 22:48.13 | jon_y | in this case CnC3/4 |
| 22:48.27 | DocScrutinizer05 | sounds OT |
| 22:48.27 | jon_y | the site is about game modding |
| 22:48.32 | DocScrutinizer05 | so what? |
| 22:48.46 | dos1 | jon_y: I'd guess that's his page, or he has some access to it, and just used it to store those files, nothing to see here |
| 22:48.50 | dos1 | except some cool lego stuff :) |
| 22:49.12 | jon_y | just curious how it manage to share the site together with wireless modems |
| 22:49.29 | dos1 | it's just a personal mirror |
| 22:49.38 | jon_y | probably |
| 22:49.42 | dos1 | for sure :P |
| 22:50.30 | DocScrutinizer05 | wirelessmodemapi.com is down since years |
| 22:51.43 | DocScrutinizer05 | actually I guess since decease of meego |
| 23:03.13 | *** join/#maemo-ssu Martix_ (~martix@static-84-242-103-180.net.upcbroadband.cz) |
| 23:03.30 | DocScrutinizer05 | freemangordon: the SSI input buffer may be filled, thus the "ready" signal to BB5 not set, thus BB5 not sending new stuff, thus no IRQ associated with new stuff, thus no handler ever cleaning/flushing the input buffer |
| 23:16.55 | *** join/#maemo-ssu M4rtinK (~M4rtinK@ip-89-177-124-88.net.upcbroadband.cz) |
| 23:28.47 | *** join/#maemo-ssu oldtopman (~oldtopman@unaffiliated/oldtopman) |