**** BEGIN LOGGING AT Tue Oct 05 02:59:57 2010 Oct 05 06:28:01 has anyone used/tried displaylink on 10.10? Oct 05 07:39:28 morning Oct 05 07:51:45 lag: panda OTG port: yes it does work, but not as OTG, it is configured as device in the kernel config Oct 05 07:53:28 sebjan: So what do you make of bug 645420 Oct 05 07:53:29 Launchpad bug 645420 in linux-ti-omap4 (Ubuntu) "OTG port not enabled for OMAP4 (affects: 2) (heat: 324)" [Low,Confirmed] https://launchpad.net/bugs/645420 Oct 05 07:55:25 lag: well, I already commented on this bug: our driver is not OTG capable at the moment, this is why it is statically configured as device. It is working fine as device. Oct 05 07:55:52 lag: this will not change for 10.10. I think we shall have the driver fixed to support OTG in 11.04. Oct 05 08:01:45 sebjan: So you did Oct 05 12:49:30 sebjan: I've just read your comment on the audio bug Oct 05 13:02:51 lag: me2 Oct 05 13:02:53 heh Oct 05 13:03:21 sebjan: ogra_ac and i think the default.pa is the same as ogra_ac posted in the launchpad. Oct 05 13:03:40 cooloney, how did things go yesterday? Oct 05 13:03:43 well, at least the one you pasted before Oct 05 13:04:00 davidm, well, network is still super slow Oct 05 13:04:24 did uboot and xloader get changed? Oct 05 13:04:40 rsalveti has a package ready i think Oct 05 13:04:46 uboot doesnt need changes Oct 05 13:05:05 and i think i worked out a proper solution of the mixer settings Oct 05 13:05:15 cooloney, ogra_ac: ok, I did not check that, I retrieved the default.pa delivered from our dev team, and saw it was different from the one installed by default in the daily images, so updated it Oct 05 13:05:21 (which at least solves 50% of the audio prob) Oct 05 13:05:31 yup Oct 05 13:05:36 let's test soon :-) Oct 05 13:05:40 sebjan, we cant change default.pa Oct 05 13:05:56 I'm still unsure what progress has been made on the audio since I worked on it Oct 05 13:05:57 using that file would break audio for everyone but panda users Oct 05 13:06:21 ALSA has always worked with only the amixer settings Oct 05 13:06:22 sebjan, but i have an idea for the mixer which i'll test today Oct 05 13:06:27 ogra_ac: yep, this was just to check the drivers are able to generate some sound. This is not the final solution. Oct 05 13:06:27 Pulse has never worked Oct 05 13:06:41 The card is only reported when the other config file is used Oct 05 13:06:45 lag, alsa has never worked without modifying the default volumes Oct 05 13:06:48 What's new? What's different? Oct 05 13:06:53 Correct Oct 05 13:06:56 So what's new? Oct 05 13:07:00 sebjan: yeah, we think sound driver works, but maybe the route setting has some issue Oct 05 13:07:03 thast what the mixer settings are for :P Oct 05 13:07:18 lag, that we needed a proper way to set them Oct 05 13:07:32 I've heard lots of people talk about it being better and there are patches and improvements have been made, but I see no difference to 2 weeks ago Oct 05 13:07:34 cooloney: yes, that shall be the purpose of SDP4430.conf file to setup the proper routings Oct 05 13:07:34 which i think i found (need to test later today, its early here) Oct 05 13:07:58 ogra_ac: What are the proper way? Oct 05 13:08:03 sebjan, why cant we fix the routings in the driver Oct 05 13:08:04 I can probably do it in the kernel Oct 05 13:08:13 (which is what I'v been looking at) Oct 05 13:08:24 lag, i doubt that since it needs to be modifyable per device Oct 05 13:08:42 ogra_ac: How do you mean? Oct 05 13:08:44 lag, /usr/share/alsa/init/hda is a good example Oct 05 13:09:11 lag, blaze and panda need different volume adjustments (and later devices probably too) Oct 05 13:09:33 ogra_ac: Okay Oct 05 13:09:34 lag, the more important part is the routing Oct 05 13:09:39 ogra_ac: don't know, I did not follow up on this topic, I repeat what I understood from berco :) Oct 05 13:09:41 whioch is wrong in kernel Oct 05 13:09:48 cooloney worked on a fix for that Oct 05 13:09:53 but we havent tested Oct 05 13:09:58 (in the driver) Oct 05 13:10:00 What's the fix? Oct 05 13:10:16 switching the routing of device 0 Oct 05 13:10:23 THIS is why I needed to speak to cooloney yesterday! Oct 05 13:10:36 if we had a proper network :-) Oct 05 13:10:42 we can play sound over device 7 via speaker-test after some alsamixer setting Oct 05 13:10:42 btw, ES2.1 boots fine Oct 05 13:10:58 but pluseaudio will open device 0, which will fail Oct 05 13:10:59 ogra_ac managed - rsalveti managed Oct 05 13:11:04 and PA never runs Oct 05 13:11:14 lag, managed ? Oct 05 13:11:14 I even saw cooloney log on, only to log off again 15 mins later Oct 05 13:11:20 To get online Oct 05 13:11:31 lag, well, FSVO online Oct 05 13:11:34 comradekingu: What's device 7 currently? Oct 05 13:11:46 the network at TI is really bad Oct 05 13:11:47 FSVO? Oct 05 13:11:52 for some value of Oct 05 13:11:58 How do they manage? Oct 05 13:12:07 (you know, you use these abbreviations to not have to type so much :P) Oct 05 13:12:18 lag, i was on through 3G Oct 05 13:12:23 YMTUY Oct 05 13:12:33 shared 3g, the only one that worked Oct 05 13:12:39 That sucks! Oct 05 13:12:49 lag: oh, from the my post in the launchpad, it is here http://pastebin.ubuntu.com/503799/ Oct 05 13:12:56 lag: sorry, it should be device 9 Oct 05 13:13:23 We've been able to play sound via HDMI from the beginning Oct 05 13:13:35 and sebjan i believe your alsamixer.sh can setup the right value of all the mixer Oct 05 13:14:04 then we can play our sound over device 9 Oct 05 13:14:06 right, we just need to translate it into an alsa init file Oct 05 13:14:25 right, I think so Oct 05 13:14:27 but device 0, there is no-codec-associated Oct 05 13:14:43 pa try to open this default device 0, but failed Oct 05 13:14:54 so re-mapping the codec in the driver should fix that Oct 05 13:15:34 ogra_ac: yeah, we need to talk with audio expert from TI, this sdp4430.c ASoC driver is from their Oct 05 13:16:23 right Oct 05 13:49:41 sebjan: for your testing with modification of default.pa, you got sound from hdmi or headset? Oct 05 13:50:06 cooloney: I only tested headset Oct 05 13:52:16 sebjan: ok, got it. i will test it soon. we try to find a fix today. Oct 05 13:52:38 sebjan: i am going to push out the audio fixing patches today, since we are closed to 10.10 release Oct 05 13:52:49 sebjan: is there any other audio new fixings? Oct 05 13:53:28 ogra_ac, if we only need xloader changes I'd like to see the patch diff between ES2.0 and ES2.1 silicon so I can get a feel of what is being done Oct 05 13:53:54 cooloney: ok. I received a 1 line patch update for audio that is supposed to help for the audio record. I'll send it to you right now. However I have not been able to make audio record even with it - we are still missing something here (maybe also a routing issue?) Oct 05 13:54:41 sebjan: oh, we never try recording i think, before we fix the playback. Oct 05 13:55:09 davidm, robclark is doing last tests Oct 05 13:55:19 sebjan: ok, please post me the audio patch Oct 05 13:55:33 davidm, if we get his ok (which i expect durign the day) we are good to go Oct 05 13:55:50 davidm, and we're all actively working on the sound issues Oct 05 13:56:12 davidm, for which we need a libalsa0 upload Oct 05 13:56:22 and possibly a kernel Oct 05 13:56:34 thats the three packages we'll need today Oct 05 13:57:24 ogra_ac, I want to understand the "amount" of change between ES2.0 and ES2.1 so I can get a feel for the level of risk with releasing on 10.10 Oct 05 13:58:08 davidm, about 30-40 lines in x-loader to handle the different ram speed Oct 05 13:58:19 cooloney: I just sent the audio patch Oct 05 13:58:31 sebjan: cool, thx Oct 05 14:02:34 davidm: ogra_ac: yep, just different timmings to support ddr@400mhz Oct 05 14:03:02 so it should work without breaking other stuff Oct 05 14:03:21 but rob is giving some more tests Oct 05 14:05:52 cooloney: moving the elements in the list of DAIs could fix the missing codec on the default device. Oct 05 14:06:06 hey Oct 05 14:06:08 TI sound people would have to be consulted. Oct 05 14:06:51 does anyone know a board that has an arm processor and an ethernet interface? nothing else is needed, though its not a problem, but i need this to be as small as possible. Oct 05 14:07:05 and of course has the capability to run ubuntu oni t Oct 05 14:14:28 kornel`: Try beagleXM or Gumstix. Oct 05 14:14:40 mpoirier: cool. could you post me a patch? Oct 05 14:14:59 cooloney: I don't have a patch for that... Oct 05 14:15:04 mpoirier: we are leaving from hotel to TI office Oct 05 14:15:20 cooloney: ok hookup with me when you get on again Oct 05 14:24:17 ogra_ac: Hi! We need to modify the pre-installed images to have custom boot.scr scripts for our internal releases. How would you do this, please? Oct 05 14:24:32 by a script Oct 05 14:25:15 mopdenacker, we need to head over to the office, lets talk in a few mins Oct 05 14:26:10 ogra_ac: we could also modify the script that creates the boot.scr file for the second boot... This way users wouldn't have to make any manual change... Oct 05 14:26:26 ogra_ac: no problemo. Thanks for your answer! Oct 05 14:28:11 thnx Oct 05 14:54:44 ogra_ac, cooloney: though the kernel was changed to allow 1GB usage without crash issues, the boot.scr cmd lines still restricts to 460 + 256M Oct 05 14:55:19 sebjan, yeah, good point, Oct 05 14:55:24 sebjan, yeah, i'll change that today Oct 05 14:55:27 ogra_ac, cool Oct 05 15:09:36 ogra_ac: back to my question... Our need is to modify the script that generates boot.scr after expanding the SD card partition. What file should we modify? That's only for our internal releases. Oct 05 15:28:20 ogra_ac: Can I close my half of bug 628029? Oct 05 15:28:22 Launchpad bug 628029 in linux-ti-omap4 (Ubuntu Maverick) (and 2 other projects) "[maverick] panda omap4 does not suspend (affects: 1) (heat: 8)" [High,Confirmed] https://launchpad.net/bugs/628029 Oct 05 15:38:37 mopdenacker: If I'm not mistaken, I think you're looking for: /usr/share/initramfs-tools/scripts/local-bottom/jasper_setup Oct 05 15:51:27 lag: thanks a lot! I will take a look. Oct 05 15:51:49 mopdenacker: Any time :) Oct 05 15:53:57 sakoman: Good morning Oct 05 15:54:16 gm lag Oct 05 15:55:44 sakoman: Have you managed to find the time to push this upstream yet? Oct 05 15:55:47 sakoman: http://www.sakoman.com/cgi-bin/gitweb.cgi?p=linux-omap-2.6.git;a=commit;h=9f40ee61034576e8abdb8201c9526204680e70d5 Oct 05 15:56:13 lag, no not yet Oct 05 15:56:38 sakoman: Any view to? Oct 05 15:58:49 lag: I'll be working on a patch series over the next couple of weeks. I'll try to add it as part of that Oct 05 15:59:04 sakoman: Sounds good - thanks :) Oct 05 16:03:24 bye Oct 05 16:25:47 https://wiki.canonical.com/UbuntuPlatform/ARM/LinaroCoordinationCallMinutes Oct 05 16:42:03 is there a mean to install a specific version of a package? Using one omap4 cdimage, I have alsa-utils=1.0.23-2ubuntu1 and in a more recent img I have alsa-utils=1.0.23-2ubuntu3... Oct 05 16:42:17 I want to be able to revert as I suspect an issue with latest version Oct 05 16:42:48 apt-get install cannot find the alsa-utils-1.0.23-2ubuntu1 version... Oct 05 16:43:19 are the old packages removed from cannonical archive? Oct 05 17:09:28 berco1, ogra_ac might can help to answer that. Oct 05 17:10:13 berco1, i am working on the audio issue in kernel side Oct 05 17:10:30 cooloney: I think I found out myself :) Oct 05 17:10:38 cooloney: I found one on Launchpad https://launchpad.net/ubuntu/+source/alsa-utils/1.0.23-2ubuntu1/+build/1879590/+files/alsa-utils_1.0.23-2ubuntu1_armel.deb Oct 05 17:10:42 berco1, cool Oct 05 17:11:01 cooloney: I have one image that has audio working with that famous SDP4430.conf file Oct 05 17:11:33 cooloney: however, taking today's cdimage and putting the SDP4430.conf in it doesn't enable sound Oct 05 17:11:54 berco1, from the code in sound/soc/omap/sdp4430.c, the frondend dai-links are no codec associated, right? Oct 05 17:12:05 cooloney: I found that alsa-utils, alsa-base and pulseaudio have been upgraded Oct 05 17:12:47 berco1, so from my side, the PulseAudio will fail due to failing to open the pcm0 device which is MultiMedia of SDP4430 Oct 05 17:13:07 cooloney: I need to check with audio dev team for your question Oct 05 17:13:14 is that holding you? Oct 05 17:13:40 berco1, do you need to modify the default.pa to make the sound work? Oct 05 17:13:52 cooloney: have you tried running the amixer.sh file? Oct 05 17:14:16 cooloney: in my working setup, no default.pa change, I just use the default file Oct 05 17:14:18 berco1, yeah, i tried that. amixer.sh will set the right value Oct 05 17:14:57 berco1, cool. since modification of default.pa is not acceptable, that might make other omap4 based board sound broken Oct 05 17:15:31 berco1, sorry, need to have luch Oct 05 17:15:35 cooloney: yes. Nevertheless, I still need to understand if it is one of the s/w upgrade that breaks my setup Oct 05 17:15:36 lunch, siya Oct 05 17:15:43 see ya Oct 05 17:29:46 cooloney: get in touch with me when you get back - we'll talk about your pmc0 device. Oct 05 18:03:57 mpoirier, hey, man. I am back from lunch Oct 05 18:04:06 ok good. Oct 05 18:04:41 you are correct, the default front end in the list doesn't have a codec. Oct 05 18:04:50 actually it is set to the null-codec. Oct 05 18:05:40 mpoirier, right, that's why pulseaudio will fail to open the device. Oct 05 18:05:49 if you were to put DAI entry pertaining to the headset at the very top of DAI list, I think that devices would become your default device. Oct 05 18:06:09 that is, in theory, great... Oct 05 18:06:35 but that DAI still wouldn't have any backend associated to it, resulting in a failure to open pcm0. Oct 05 18:07:11 that's what lies at the heart of the problem. Oct 05 18:07:43 mpoirier, right. we are thinking in the same way Oct 05 18:07:47 this is a config that is left to userspace, on purpose. Oct 05 18:08:20 mpoirier, i just fixed the first frontend dai-link Oct 05 18:08:26 built the kernel and will test soon Oct 05 18:08:49 you prept it up in the list ? Oct 05 18:29:58 yay Oct 05 18:30:01 mixer defaults solved Oct 05 18:43:55 mpoirier, i found we need to debug the alsa and asoc code for a while Oct 05 18:44:30 maybe it is right that pcm0 doesn't have the codec driver associated Oct 05 18:44:55 it will be connected to a backend when we open it for operation at runtime Oct 05 18:45:06 but we failed to find one. Oct 05 18:45:12 so i am looking at this Oct 05 19:09:26 GrueMaster: http://people.canonical.com/~rsalveti/maverick/boot/es21/MLO Oct 05 19:27:57 cooloney: I'm back from lunch. Oct 05 19:29:06 I have done a lot of tracing in the soc area... Oct 05 19:29:44 hold on a sec... Oct 05 19:31:41 did you see the latest addition from ogra ? Oct 05 19:33:37 cooloney: did you see the latest finding from ogra ? Oct 05 19:34:06 cooloney: about /usr/share/alsa/init/00main ? Oct 05 19:35:58 mpoirier, yeah, but that's for alsamixer. pulseaudio need to open it in the right way Oct 05 19:36:37 cooloney: indeed, there are multiple part of the puzzle. Oct 05 19:37:07 cooloney: take a look at this: http://omappedia.org/images/c/c9/OMAP4_Audio_Phoenix.jpg Oct 05 19:37:36 cooloney: on the right hand side you have the famous DAIs. Oct 05 19:38:22 cooloney: on the left side, second square, are the "interface". Oct 05 19:39:10 cooloney: the famous PDMs. UL0, UL1, DL0...DL4 Oct 05 19:41:17 running the script omap4_amixer_config.sh will link the DAIs to the PDMs. Oct 05 19:41:55 cooloney: it is only when that relashion is established that opening pcm0 can succeed. Oct 05 19:42:13 cooloney: I spent a lot of time in there. Oct 05 19:43:25 To the best of my knowledge, SDP4030.conf under /usr/share/alsa/cards/ is supposed to do that Oct 05 19:43:47 sorry, SDP4430.conf. Oct 05 19:44:20 TI guys are all very fluent with those concepts. Oct 05 19:44:22 mpoirier:cooloney: I can support on this if you have trouble. Berco is still working on the finalization of SDP4430.conf file Oct 05 19:45:08 sguiriec: the above is a recollection of 2 weeks of soul searching in the soc subsystem. Oct 05 19:45:28 feel free to rectify anything that would not be accurate. Oct 05 19:47:54 sguiriec: am I correct when saying that PDMs and DAIs are linked in file SDP4430.conf ? Oct 05 19:48:13 mpoirier:You statement is ok. Final solution will be with SDP4430.conf file. With this file we should get ride of omap4_amixer_config.sh. Oct 05 19:48:56 cooloney: hence no changes should be required to the kernel. Oct 05 19:49:14 cooloney: at least that's the conclusion I came up with. Oct 05 19:49:43 cooloney: all the ingredient in the kernel are there and working. The scheme was meant to be generic. Oct 05 19:50:01 mpoirier: Inside OMAP4 McPDM port include part of Sigma delta. This is why code is a little bit different form standard CODEC interface Oct 05 19:50:45 sguiriec: the famous McPDMs... I'm still having a lot of fun with those. Oct 05 19:50:55 sguiriec, and mpoirier let me to report my findings here Oct 05 19:51:18 cooloney: everybody should be on the same page on your side.... Oct 05 19:51:28 speaker-test -D plughw:0,3 -t sine -c 2 Oct 05 19:51:33 will generate sound Oct 05 19:51:41 We've all talked about it in great lenght Oct 05 19:52:04 mpoirier: Liam has work to get correct board name in order to have ALSA utils to be able to load SDP4430.conf file. Now we are finalizing the content of this file in order to set correctly the audio path after board boot. Oct 05 19:52:11 also 0,7 Oct 05 19:52:44 the dynamically run time binding, looks right Oct 05 19:53:00 but device 0,0 doesn't generate any sound Oct 05 19:53:15 mpoirier:cooloney: 0 Oct 05 19:53:31 i can open it, the dmesg from driver tells me it binds to the right codec and backend Oct 05 19:53:51 ogra: https://code.edge.launchpad.net/~rsalveti/ubuntu/maverick/x-loader-omap4/es21/ Oct 05 19:54:05 cooloney: yes indeed, but your path to the PDM probably doesn't exist. Oct 05 19:54:35 mpoirier, so we need to check the bug in this binding thing Oct 05 19:55:11 mpoirier:cooleney: can you check amixer controls for DL1 Media Playback Volume? Oct 05 19:56:40 sguiriec: I'll have to fire up my board - what are you after ? Oct 05 19:57:27 mpoirier:Inside ABE you have SW volume. Just want to check that volume is well set. Oct 05 19:57:35 sguiriec, let me check this. Oct 05 19:57:53 cooloney: please, I don't have the very latest patch. Oct 05 19:59:24 sguiriec, my bad, i need to run the amixer.sh from sebjan and becor, Oct 05 19:59:49 sguiriec, i got sound from device 0,0 Oct 05 20:00:26 sguiriec: what state do you want the system to be in ? Oct 05 20:00:38 sguiriec: just after booting ? Oct 05 20:01:41 sguiriec, i will try ogra's latest alsa config method to get alsamixer works firstly Oct 05 20:01:56 sguiriec, but we need to make the pulseaudio also working Oct 05 20:02:06 mpoirier: cooloney:Until we finalise the SDP4430.conf file it is beter to run amixer.sh file (or omap4_amixer_setup). amixer.sh -a should reconfigure the audio path. Until it is not fix you will have no sound after boot Oct 05 20:02:29 sguiriec: that is well understood on my side. Oct 05 20:02:53 sguiriec: do you still want us to check DL1 Media playback ? Oct 05 20:02:59 thats nothng we can do in the image Oct 05 20:03:12 * ogra can only repeat that every time this comes up Oct 05 20:03:22 uploas deadline for maverick is in a few hours Oct 05 20:03:46 mpoirier: Yes if you have no audio on plughw:0,0 and audio on plughw:0,3 it should be linked to this control. Oct 05 20:04:17 sguiriec: I'm here to provide you data - my board is powered up. Oct 05 20:04:36 I haven't done anything to it so far, aka defautl value. Oct 05 20:04:55 do yo want the value of DL1 now or after running amixer.sh ? Oct 05 20:05:37 mpoirier: In case you have no audio it will be good to have it now and the to set up in the middle of the play Oct 05 20:06:16 sguiriec: I definitely don't have audio right now. Oct 05 20:06:33 mpoirier: Normally audio should come back if you run amixer.sh -a Oct 05 20:06:45 sguiriec: indeed. Oct 05 20:07:00 sguiriec: I'll run the script, hang on. Oct 05 20:07:19 sguiriec, amixer.sh is not a final solution for our release, i think ogra has make all the setting in his alsa init file. Oct 05 20:08:14 which isnt proper either Oct 05 20:08:24 SDP4430.conf is actually the right way to go Oct 05 20:09:32 mpoirier:cooloney:Inline with this statement. berco is working on it. Seem to have trouble with Pulse and alsa versions. Oct 05 20:10:35 sguiriec: indeed, berco was asking about older versions earlier today. Is the newer stuff broken ? Oct 05 20:11:19 mpoirier:cooloney: generation of asound.state file was not always inline with SDP4430.conf file. Newer stuff has broken it. This is why berco is asking older version Oct 05 20:13:02 mpoirier:cooloney: I was just with him before coming back to home. Now need to understand what is borken and to see if it is inside pulse or alsa. Oct 05 20:15:13 speaker-test -D plughw:0,3 -t sine -c 2 Oct 05 20:15:21 speaker-test -D plughw:0,7 -t sine -c 2 Oct 05 20:15:38 sorry, wrong console, please ignore Oct 05 20:16:25 sguiriec: numid=3,iface=MIXER,name='DL1 Voice Playback Volume' Oct 05 20:16:26 ; type=INTEGER,access=rw---R--,values=1,min=0,max=149,step=0 Oct 05 20:16:26 : values=110 Oct 05 20:16:26 | dBscale-min=-120.00dB,step=1.00dB,mute=1 Oct 05 20:16:50 sguiriec: that is after running amixer.sh Oct 05 20:17:26 sguiriec: speaker-test -D plughw:0,3 -t sine -c 2 works properly. Oct 05 20:18:54 mpoirier: this control is for voice so plughw:0,2. DL1 Media Playback Volume should be numid=1 Oct 05 20:20:09 mpoirier: this control is for Voice port (plughw:0,2). For multimedia it should be numid=1 name='DL1 Media Playback Volume' Oct 05 20:20:42 sguiriec: ok, one sec. Oct 05 20:21:46 numid=1,iface=MIXER,name='DL1 Media Playback Volume' Oct 05 20:21:46 ; type=INTEGER,access=rw---R--,values=1,min=0,max=149,step=0 Oct 05 20:21:46 : values=110 Oct 05 20:21:46 | dBscale-min=-120.00dB,step=1.00dB,mute=1 Oct 05 20:22:00 sguiriec: ^^^^^^^^ Oct 05 20:23:41 mpoirier: Ok 110 looks ok. it means -10 dB. Can you check also numid=18? Should be the next gain in the ABE chain before headset. I will recommend to set it to 120 (0 dB). Oct 05 20:24:58 sguiriec: numid=18,iface=MIXER,name='SDT DL Volume' Oct 05 20:24:58 ; type=INTEGER,access=rw---R--,values=1,min=0,max=149,step=0 Oct 05 20:24:58 : values=120 Oct 05 20:24:58 | dBscale-min=-120.00dB,step=1.00dB,mute=1 Oct 05 20:25:11 it is indeed set to 120. Oct 05 20:25:29 mpoirier: And still not sound on headset Oct 05 20:26:06 sguiriec: speaker-test -D plughw:0,3 -t sine -c 2 did work Oct 05 20:27:00 sguiriec: so does speaker-test -D plughw:0,2 -t sine -c 2 Oct 05 20:27:21 mpoirier:depend on the controls. Oct 05 20:28:07 sguiriec: we may be out of sync here... Oct 05 20:28:53 sguiriec and mpoirier, let me sync with you guys Oct 05 20:29:35 kernel driver looks ok, it uses the front end and back end for dynamically run time binding Oct 05 20:30:16 for alsamixer, we need SDP4430.conf and the script file to set it in right volumn Oct 05 20:30:54 moreover, we need to modify the default.pa of pulseaudio to make the sound works finally Oct 05 20:31:07 mpoirier:cooloney: Yes you need to have a valid root between FE and BE. SPD4430.conf should do it after the boot Oct 05 20:31:46 sguiriec: would you like me to run other tests ? Oct 05 20:32:03 mpoirrier:cooloney: for pulse I am not the good guy to comment. May be in the comming weeks. Oct 05 20:32:04 but unfortunately, ogra said, we cannot modify the default.pa, since that will break other boards with different audio configuration Oct 05 20:32:37 anyway, guys, i am going to send out the audio patches Oct 05 20:32:44 cooloney: I did not investigate the pulse front. Oct 05 20:32:52 mpoirier: Just try on plughw:0,0. Normally you should have some sound Oct 05 20:33:07 cooloney: too busy getting grey hair with PDMs and DAIs. Oct 05 20:33:13 sguiriec: ok, one sec. Oct 05 20:33:59 ogra: mpoirier: cooloney: hi! Oct 05 20:34:13 so it looks better on the audio front... Oct 05 20:34:16 mpoirier:cooloney: Just thinking that for pulse a patch has been already pull in 10.10 in order to set custom configuration on top of default.pa file. Oct 05 20:34:34 sguiriec: no this was not pulled on time for 10.10 Oct 05 20:35:05 mpoirier: cooloney: ogra: so what do we need exactly on top of the current image to get audio out of the box? are you using SDP4430.conf file or not? Oct 05 20:35:32 SDP4430.conf is not ready yet. Oct 05 20:35:37 berco is working on it. Oct 05 20:35:45 ndec: thanks nico for the info Oct 05 20:36:21 mpoirier: i saw ogra comments on the bug, with the omap4 config file. what is this file? where is it supposed to come from, e.g. which package? Oct 05 20:36:44 ndec, firstly, we need merge those audio patches Oct 05 20:37:04 ndec: I saw the comment to but havent' had time to try. Oct 05 20:37:07 cooloney: agreed, on this. stability and sound quality is much better with those patches. Oct 05 20:37:31 mpoirier: ok.. i thought you guys were talking about this in fact. Oct 05 20:38:02 ndec: no, I'm doing test for sguiriec - he's helping us. Oct 05 20:38:04 so we need ogra to explain why/how he did this change. Oct 05 20:38:23 mpoirier: ok. which tests? Oct 05 20:38:23 ndec, for the SDP4430.conf or alsamixer configs, ogra will update that Oct 05 20:39:13 ndec, that file apparently only works if you call alsactl init and requires a one line change to libasound0 Oct 05 20:39:24 (the omap4 file) Oct 05 20:39:24 ndec: sguiriec needed information, I'm providing it. Oct 05 20:39:54 sguiriec: plughw:0,0 also works. Oct 05 20:40:11 ndec: With berco we have some trouble with latest Asla/Pulse release compare to his previous FS. Oct 05 20:40:44 mpoirier: Good to see that port is working after good setting. Oct 05 20:42:08 sguiriec: educate me here a little... Oct 05 20:42:17 when doing aplay -l, Oct 05 20:42:31 sguiriec: Just here for help Oct 05 20:42:47 device 9, 11, 13, and 14 are associated with twl6040 codec. Oct 05 20:44:02 how did you do the mapping with plughw:0,0 , plughw:0,3 and plughw:0,4 ? Oct 05 20:44:32 sguiriec: 'cause those devices are not associtated with twl6040... Oct 05 20:45:36 mpoirirer: These devices are here for BE ports or to bypass ABE. Diirect access to McPDM. Oct 05 20:47:05 mpoirier: Here I think we need to update the wiki. plughw:0,0 is Multimedia port (FE port). This port can be sent on different BE ports (Headset/Handsfree) Oct 05 20:48:17 sguiriec: here's another way of asking the same question: is the output of aplay -l related to plughw:0,x ? Oct 05 20:48:18 mpoirier: mixer controls setting will enable the different paths. Oct 05 20:50:02 mpoirier: Normaly when we are using ABE we should use plughw;0.x with x up to 8. Oct 05 20:51:04 sguiriec: the ABE are accessed directly with the plughw:0,x ? Oct 05 20:51:21 mpoirier: After we should used amixer controls in order to set the path between FE to BE ports. Oct 05 20:51:53 sguiriec: let me summarise what I just learned... Oct 05 20:52:21 mpoirirer: ALSA is accessed to ABE directly with a sDMA channel to ABE. Oct 05 20:52:54 ABEs are access directly via plughw:0,x . But for this to work the path between FE and BE must be set. Correct ? Oct 05 20:54:03 mporirier: Yes otherwise ALSA will return an error Oct 05 20:54:51 sguiriec: here's another question then: Oct 05 20:55:35 sguiriec: is the path between ABEs and BEs always the same ? Oct 05 20:56:09 mpoirier: No it can be changed accoridng to the use case. Oct 05 20:57:20 sguiriec: the following has become my bedside reading: http://omappedia.org/images/c/c9/OMAP4_Audio_Phoenix.jpg Oct 05 20:58:23 sguiriec: in this case, plughw:0,0 is related to which PDM ? (UL0...DL4) Oct 05 20:58:37 sguiriec: if that question makes sense at all... Oct 05 20:58:43 mpoirier: Here you are missing the ABE part. McPDM port is a kind of TDM port manages by ABE. Oct 05 20:59:17 mpoirier: Until you do not have ABE picture your questions are normal. Oct 05 21:00:11 sguiriec: the only time I saw a ABE was in the omap4 technical reference manual. Oct 05 21:00:26 sguiriec: unless you have a better picture... Oct 05 21:00:51 mpoirier: ABE graph is making the link beetween FE port and BE port. Typicaly McPDM is a BE port. McBSP is also a other BE port used for BT or MODEM call. Oct 05 21:02:38 sguiriec: ya, I read about the McBSP but aren't much of interest in this case - correct ? Oct 05 21:02:50 mpoirier: will check if I can provide you better picture tomorrow. Normally should be ok Oct 05 21:03:32 mpoirier: For standard audio with Phoenix Audio McBSP is no interest for our use case Oct 05 21:03:56 sguiriec: ok that is the conclusion I came up with. Oct 05 21:04:44 sguiriec: i've known from the start i was missing information - anything you can get will help. Oct 05 21:06:03 mpoirier:of course. Will sync with ndec in order to help you on the topic. Quite new compare to OMAP3. Oct 05 21:07:50 sguiriec: thanks. your time and insight are well appreciated. Oct 05 21:11:16 mpoirier: I hope we will reach to good SDP4430.conf file with berco. Will try to provide ABE/Phoenix audio picture for audio system understanting Oct 05 21:11:41 ok Oct 05 21:12:13 * ogra_ac still doesnt get why device 0,0 cant just properly connect to the working default codec in the driver Oct 05 21:12:19 that would solve all our issues Oct 05 21:13:13 ogra_ac: even if it would, the FE - BE path would not be established. Oct 05 21:16:19 vincent-laptop: robclark: http://paste.ubuntu.com/506797/ an oops while restarting X11 Oct 05 21:17:13 orga_ac: SDP4430.conf should solve our problem by setting up the graph between FE and BE ports after the boot. Oct 05 21:18:57 GrueMaster: http://people.canonical.com/~rsalveti/maverick/boot/es21/MLO-sdp Oct 05 21:18:58 sguiriec, yeah Oct 05 21:19:12 * ogra_ac just commented on the bug Oct 05 21:24:49 ogra_ac: Do you have any glue on potential recent update on ALSA or pulse that can explain different behavior in the reading of .conf audio file? Oct 05 21:25:18 no, sorry, i dont, do you know between which versions it changed ? Oct 05 21:26:12 orga_ac: Can check tomorrow with berco? Do not have it from home. Oct 05 21:26:19 * ogra_ac goes to check changelogs on launchpad Oct 05 21:26:48 sguiriec, but you are use it was a version in maverick ? Oct 05 21:26:58 s/use/sure/ Oct 05 21:28:28 orga_ac:thanks, I will check the chanelogs. berco has two FS. One is working and the one is not. There are based on maverick but version are not exactly the same. changelogs should help us Oct 05 21:30:27 yep, i'm just looking Oct 05 21:30:48 one prob is though that there camein a completely new upstream version at some point Oct 05 21:33:20 robclark: http://gitorious.org/~rsalveti/pandaboard/rsalveti-x-loader/commits/omap4_panda_es2.1 Oct 05 22:46:38 vincent-laptop: robclark http://people.canonical.com/~rsalveti/maverick/boot/es21/MLO-lowvoltage Oct 05 22:46:45 with *(volatile int*)(0x4A307BA0) = 0x3A5512; Oct 05 22:58:35 grrr, really wish xvidcap would work so I could show you guys the unity-efl stuff Oct 05 23:39:53 GrueMaster: http://people.canonical.com/~rsalveti/maverick/boot/es21/u-boot-4430sdp.bin Oct 06 00:24:40 ogra_ac, around ? Oct 06 00:40:23 hey all... got a quick ??? --> if I create a custom xorg.conf in /etc/X11/ will it be used as the default? or do I need to create a new one in /usr/share/X11/xorg.conf.d? Oct 06 01:14:23 GrueMaster, ping ? Oct 06 01:14:28 ogra_ac, ping ? Oct 06 01:49:22 III: the new directories are basically for devices configureation Oct 06 02:07:28 thanks tmzt_ **** ENDING LOGGING AT Wed Oct 06 02:59:57 2010