**** BEGIN LOGGING AT Wed Nov 02 02:59:57 2011
Nov 02 04:22:36 <adriano87> how do i integrate bluetooth into my yocto image build?
Nov 02 04:28:42 <sgw> adriano87: we support the bluez4 recipes in meta/recipes-connctivity
Nov 02 04:31:15 <adriano87> yes i have built an image which includes that package but when i run the image, i get "Can't open HCI socket: Address family not supported by protocol". seems like the kernel module is not running for HCI. but i have configured it in the menuconfig
Nov 02 04:32:06 <sgw> adriano87: when the kernel boots does your device get recognized?  What hardware are you working with?
Nov 02 04:33:31 <adriano87> i have a bluegiga wt11 running on a mpc8315e.
Nov 02 04:34:39 <adriano87> sgw: no the device is not recognized.
Nov 02 04:37:12 <sgw> adriano87: the mpc8315 is one of the devices we support, is the bluegiga wt11 an add-on?
Nov 02 04:37:35 <adriano87> yes it is an addon.
Nov 02 04:39:42 <adriano87> sgw: connected thru mini pci-e
Nov 02 04:40:17 <sgw> hmm, we may not have tested that config, I can check with the Kernel team tomorrow morning, you might file a bug in the BSP category
Nov 02 04:43:13 <adriano87> sgw: ok thanks. in the build/tmp/deploy/images/ folder, i can see the uImage.bin, the uImage.dtb and the rootfs. but what is in the modules...tar.gz?
Nov 02 04:54:50 <sgw> adriano87: all the kernel modules, maybe that's it you don't have all the modules installed on your image?
Nov 02 04:55:30 <sgw> adriano87: can you confirm the wt11 module is installed on your image?
Nov 02 05:05:20 <adriano87> sgw: is there a wt11 module? as i understand, it uses the hci drivers?
Nov 02 05:14:37 <adriano87> sgw: thanks for your support. i will continue to figure this out as much first.
Nov 02 06:56:21 <MadSpark> adriano87, have you configured wt11 to use usb as host transport? do you see it with lsusb?
Nov 02 06:57:06 <MadSpark> adriano87, after you see it on usb bus all you need is btusb module
Nov 02 07:44:36 <RP__> morning all
Nov 02 07:49:16 <JaMa|Off> morning
Nov 02 08:32:13 <loo> http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/commit/?h=tzanussi/emgd-1.8-fixes&id=9639c9ceb8b412d861920c9585f9ca6297e290f3
Nov 02 08:33:11 <loo> i hav build failed due to emgd-driver-bin_1.8.bb this receipe
Nov 02 08:33:22 <loo> so i wanna apply that patch but not sure how
Nov 02 08:33:26 <loo> can anyone help me
Nov 02 08:38:58 <loo> anyone noe how i can apply the patch into the meta-intel/meta-crownbay?
Nov 02 08:46:26 <JaMa|Off> RP__: hi, did you forgot to git push or is something wrong?
Nov 02 08:47:17 <loo> git push?
Nov 02 08:48:01 <loo> i nid their patch
Nov 02 08:48:47 <loo> not pushing to upstream source
Nov 02 08:49:39 <JaMa|wrk> that question was for RP
Nov 02 08:50:05 <loo> oh
Nov 02 08:50:36 <loo> do u have idea wat can i do for my situation?
Nov 02 08:53:41 <JaMa|wrk> git cherry-pick 9639c9ceb8b412d861920c9585f9ca6297e290f3
Nov 02 08:56:41 <RP__> JaMa|wrk: I just got distracted - pushed now
Nov 02 08:56:54 <JaMa|wrk> ok, thanks
Nov 02 08:57:39 <RP__> loo: You can download the patch and apply it with patch manually?
Nov 02 08:58:26 <RP__> loo: On the line in the interface where it says "commit9639c9ceb8b412d861920c9585f9ca6297e290f3 (patch) (side-by-side diff)", click patch, then save the file. You can then apply with "patch -p1 < savedfile"
Nov 02 08:58:38 <RP__> loo: That is one approach, there are others depending on your situation
Nov 02 11:08:42 <JaMa|wrk> yup writing warning to ML now
Nov 02 11:08:44 <RP__> two steps forward, one step back :/
Nov 02 11:08:44 * RP__ hopes the gettext change helps people's build performance
Nov 02 11:08:44 <JaMa|wrk> RP__: can you apply patch for chown in postinst now, or should we wait for proper fix for #1711 ?
Nov 02 11:08:45 <RP__> JaMa|wrk: I really don't want to hack around this, I want people to get it fixed properly... :/
Nov 02 11:08:45 <JaMa|wrk> ok
Nov 02 11:08:45 <RP__> JaMa|wrk: We've at least reduced it to on device upgrades of existing devices at this point, I know that doesn't help you much :(
Nov 02 11:08:45 <JaMa|wrk> "fixed" in shr branch
Nov 02 11:08:46 <JaMa|wrk> as my users want telephony to work :)
Nov 02 11:08:46 <JaMa|wrk> which is kind of usefull on phone
Nov 02 14:52:49 <bluelightning> otavio: are you around?
Nov 02 17:23:45 <otavio> hi there
Nov 02 17:37:19 <otavio> sgw: there?
Nov 02 17:37:30 <otavio> sgw: is you how will give a talk on LinuxCon>
Nov 02 17:37:32 <otavio> sgw: ?
Nov 02 17:37:43 <otavio> sgw: Brazil I meant ;)
Nov 02 17:39:33 <sgw> otavio: yes, I will be at LinuxCon Brazil and giving a talk on the Yocto Project
Nov 02 17:40:14 <otavio> sgw: nice :)
Nov 02 17:40:32 <otavio> sgw: I ought to be there too :) hopefully heh
Nov 02 17:40:58 <sgw> that would be great and it would be good to meet you and maybe other people using Yocto/OE in Brazil
Nov 02 17:41:38 <otavio> sgw: it ought to be easy for you to know me as I use a power wheelchair .. so shouldn't have many handicapped people over there ;)
Nov 02 17:42:17 <otavio> sgw: et least, there weren't others wheelchair users previous years heh
Nov 02 17:44:04 <otavio> I'd like to discuss about sstage regarding native libraries ... it seems there's some illness on it and I'd like to talk about it with someone that knows about it (no knowledge about it from my side)
Nov 02 17:44:15 <otavio> Who should I talk to?
Nov 02 17:44:56 <sgw> otavio: do you mean sstate?
Nov 02 17:45:26 <sgw> otavio: RP__ might be best to chat with about sstate issues.
Nov 02 17:47:42 <RP__> otavio: Is this the problem where X links against Y, Y rebuilds and yet X gets run?
Nov 02 17:47:50 <RP__> and then X can't find Y
Nov 02 17:55:48 <otavio> RP__: no
Nov 02 17:56:04 <otavio> RP__: basically libs that builds native into lib64 aren't put in sstate
Nov 02 17:57:07 <RP__> otavio: I don't understand
Nov 02 17:57:32 <otavio> RP__: try to add bbextend native to libcap and build it in amd64 host
Nov 02 17:59:30 <RP__> otavio: It it builds for "lib64" instead of "lib" you need to patch the source to use lib
Nov 02 17:59:42 <RP__> otavio: It should use what is in libdir
Nov 02 17:59:47 <RP__> ${libdir}
Nov 02 18:00:01 <otavio> RP__: why not add lib64 in sstate?
Nov 02 18:00:28 <RP__> otavio: because the system knows to look in ${libdir} not some random directory
Nov 02 18:00:47 <RP__> otavio: We're not changing half the system to look in multiple places
Nov 02 18:00:56 <RP__> and its not a sstate problem
Nov 02 18:16:46 <otavio> RP__: so you think this is source problem?
Nov 02 18:36:55 <Crofton|work> I would like to point out the error for a checksum failure is extremely ahrd to find and all the crap
Nov 02 18:37:20 <kergoth> i noticed that the other day too. the log is useless, its one line buried way above it all
Nov 02 18:39:09 <Crofton|work> I have a bbfile that I update the url,then fix checksums, and this makes it painfully hard
Nov 02 18:39:29 <Crofton|work> it is bad anough due to upstreams inseane file naming methhod
Nov 02 18:42:21 <Crofton|work> and it looks like I ned to do it twice to get both chacksums
Nov 02 18:42:27 <Crofton|work> I suppose we should file a bug
Nov 02 18:46:11 <bluelightning> Crofton|work: I think there is a bug for that already... zenlinux (Scott G) is working on the general case for not printing huge backtraces on errors
Nov 02 18:46:44 <bluelightning> also, I thought incandescant already fixed the run-twice-to-get-checksums issue
Nov 02 18:47:00 <bluelightning> (guess it depends on what version of bitbake you are using)
Nov 02 18:47:05 <hrw> long time ago in OE tmp/checksums.ini was generated in such case
Nov 02 18:47:27 <incandescant> my patch is in bitbake upstream and poky, but it's still amid noise
Nov 02 18:47:37 <incandescant> run-twice is definitely fixed
Nov 02 18:48:08 * bluelightning -> home
Nov 02 18:48:15 <bluelightning> night all
Nov 02 18:50:15 <Crofton|work> I am starting to get caught back up
Nov 02 20:42:04 <Crofton|work> anyone know what happened to pythons unittest module
Nov 02 21:20:53 <Crofton|work> bluelightning, http://pastebin.com/p2aE7vmh
Nov 02 21:21:12 <Crofton|work> looks like I am picking a qt x86 header file doing a build for arm
Nov 02 21:21:33 <Crofton|work> not sure if it is our cmake (autofoo build and oe-clssix worked this am)
Nov 02 21:21:56 <JaMa|off> Crofton|work: was it part of python recipe or extra recipe for unittest?
Nov 02 21:22:34 <Crofton|work> bascially the python-unittest package wasn't found
Nov 02 21:22:48 <Crofton|work> I dropped it for now, but will need to go back and find out where it went
Nov 02 21:22:59 <Crofton|work> looks like unittest is in the python 2.7 manifest
Nov 02 21:23:00 <Crofton|work> bbiab
Nov 02 21:29:59 <JaMa|off> ah could be another build issue in python-2.7.2, but I never used python-unittest so I didn't notice it
Nov 02 21:31:26 <Crofton|work> I'll hunt some more
Nov 02 21:31:35 <Crofton|work> now falling a real blocker with qt :)
Nov 02 21:37:22 <dvhart> I'm getting ncurses qa_configure failures as it appears to be looking at the host for widec (widechar I imagine?) support
Nov 02 21:37:27 <dvhart> s this an indication that I need to beef up my eglibc module listing?
Nov 02 21:37:35 <JaMa|off> Crofton|work: for some reason manifest didn't pick unittest files so they all ended in python-misc
Nov 02 21:37:55 <Crofton|work> ah thanks
Nov 02 21:38:10 <JaMa|off> Crofton|work: FILES_${PN}-unittest="${libdir}/python2.7/unittest.* should be FILES_${PN}-unittest="${libdir}/python2.7/unittest/
Nov 02 21:38:31 <Crofton|work> oops
Nov 02 21:38:37 <Crofton|work> will yuo osend in a fix?
Nov 02 21:38:59 <Crofton|work> I am not in a hurry (yet)
Nov 02 21:39:09 <Crofton|work> as in, you have been doing python work?
Nov 02 21:39:37 <JaMa|off> yup I'll send it
Nov 02 21:39:42 <Crofton|work> ok, thanks
Nov 02 21:40:01 <Crofton|work> do you think that might have happened to other packages?
Nov 02 21:47:21 <JaMa|off> yes ie 2to3 is also broken
Nov 02 21:48:28 <Crofton|work> :)
Nov 02 21:48:41 <Crofton|work> ok, why is qt in the x86 sysroot ....
Nov 02 21:48:53 <JaMa|off> and even after moving unittest and 2to3 from python-misc there is still 150 files which doesn't belong to any python subpackage
Nov 02 21:49:36 <JaMa|off> well 86 if I don't count .pyo files
Nov 02 22:39:27 <juan____> hi
Nov 02 22:40:06 <juan____> i built yocto image "bitbake core-image-sato-sdk"
Nov 02 22:40:21 <juan____> the build appeared to be successful (no errors)
Nov 02 22:41:15 <juan____> i then imaged the 1.7GB core-image-sato-sdk-fri2-noemgd-20111102144406.hddimg  to a 4GB USB drive
Nov 02 22:41:41 <juan____> when i try to boot with the 4GB usb drive, i get boot prompt
Nov 02 22:42:00 <juan____> but it says it cannot find kernel image vmlinuz
Nov 02 22:43:04 <juan____> it says "Invalid or corrupt kernel image"
Nov 02 22:44:20 <juan____> oddly, when i plug the 4GB USB drive into a Linux system, i see "initrd", "ldlinux.sys", "rootfs.img", syslinux.cfg", and "vmlinuz" files
Nov 02 22:49:36 <juan____> hi
Nov 02 22:49:52 <juan____> i built yocto image "bitbake core-image-sato-sdk"
Nov 02 22:50:02 <juan____> the build appeared to be successful (no errors)
Nov 02 22:50:11 <juan____> i then imaged the 1.7GB core-image-sato-sdk-fri2-noemgd-20111102144406.hddimg  to a 4GB USB drive
Nov 02 22:50:39 <juan____> when i boot with the 4GB usb drive, i get boot prompt
Nov 02 22:50:55 <juan____> but it says "Invalid or corrupt kernel image"
Nov 02 22:51:31 <juan____> oddly, when i plug the 4GB USB drive into a Linux system, i see "initrd", "ldlinux.sys", "rootfs.img", syslinux.cfg", and "vmlinuz" files
Nov 02 22:52:09 <juan____> and they're files that are non-empty
Nov 02 22:52:20 <juan____> e.g., vmlinuz is size 4.1MB
Nov 02 22:52:32 <juan____> rootfs.img is size 1.7GB
Nov 02 22:52:45 <juan____> initrd is size 6.3M
Nov 02 23:08:11 <JaMa|off> Crofton|work: patch for unittest on oe-core ML
Nov 02 23:08:55 <Crofton|work> thanks
Nov 02 23:09:03 <Crofton|work> I'll try in the monring
Nov 02 23:09:07 <Crofton|work> I need to have a life
Nov 02 23:09:28 * Crofton|work realizes JaMa|off is hours later in his day
Nov 02 23:13:58 <Guest52883> juan____: you might want to look at the README.hardware in the top-level poky
Nov 02 23:15:25 <Crofton|work> what was the git visualizatio  tool running in the yocto booth
Nov 02 23:15:45 <Guest52883> juan____: the section starting with "  If the device fails to boot with "Boot error" displayed, it is likely the BIOS
Nov 02 23:15:45 <Guest52883>   cannot understand the physical layout of the disk (or rather it expects a
Nov 02 23:15:45 <Guest52883>   particular layout and cannot handle anything else). There are two possible
Nov 02 23:15:45 <Guest52883>   solutions to this problem:
Nov 02 23:21:03 <JaMa|off> Crofton|work: yup 0:14 AM here :)
Nov 02 23:22:57 <Crofton|work> gource btw
Nov 02 23:23:21 <dvhart> yes, gource
Nov 02 23:23:30 * dvhart is rendering another version as we speak
Nov 02 23:28:15 <Crofton|work> dvhart, so I could save a file and upload it to youtube from gorce?
Nov 02 23:28:37 <dvhart> Crofton, yes, I pipe it through ffmpeg and encode to webm
Nov 02 23:28:41 <dvhart> youtube seems happy with that
Nov 02 23:28:49 <dvhart> I can send you my script if you like
Nov 02 23:29:25 <Crofton> that would be great
Nov 02 23:29:38 <dvhart> how much ffmpeg fiddling you'll have to do depends on your distro and version
Nov 02 23:29:51 <Crofton> I ahve destroyed productivty at a customer site, because they are mesmerized :)
Nov 02 23:30:02 <dvhart> Crofton, my nick to email hash is broken... can you msg me your email addr
Nov 02 23:30:06 <dvhart> Crofton, hehe, it is addictive
Nov 02 23:36:24 <dvhart> sent
Nov 02 23:36:34 <Crofton|work> thanks
Nov 02 23:36:42 <Crofton|work> I need to play with this some
Nov 02 23:36:48 <Crofton|work> I want to do an OE movie also
Nov 02 23:37:06 <Crofton|work> I started watching kergoth build oe, but I need to run
Nov 02 23:39:36 <JaMa|off> Crofton|work: iirc hrw had such movie about 1-1,5 year ago
Nov 02 23:40:59 <JaMa|off> Crofton|work: maybe you can find the link on ML and maybe it still works :) and iirc his version was more clear
Nov 02 23:41:31 <Crofton|work> I'll talk with him about making one
**** ENDING LOGGING AT Thu Nov 03 02:59:59 2011