**** BEGIN LOGGING AT Wed Sep 07 02:59:57 2011 **** BEGIN LOGGING AT Wed Sep 07 04:07:22 2011 Sep 07 08:23:21 RP__: ping Sep 07 10:52:39 where do I tell bitbake to look for extra meta respositories I have created in the root directory? Sep 07 10:54:10 e.g. poky/meta-custom/recipes-custom/myProg/myProg_0.1.bb Sep 07 10:54:56 Snafflehog: conf/bblayers.conf under your build dir Sep 07 10:56:34 perfect, got it. thanks! Sep 07 14:14:17 i have a really stupid question, i'm somewhat familiar with socs in general but if i build an arm image with yocto, will it work with older arm socs likes arm4 and later ones too? from what i've understood arm architechture should have the same commands work for all Sep 07 14:22:38 ukas, most of what's compiled is shared between the same architecture, for instance armv4t stuff is common between all armv4t SOC Sep 07 14:30:10 hi ..... I was looking at routerstationpro.conf file just wanna confirm that r we not building bootloader with this machine? Sep 07 14:35:42 I havn't built the rsp lately.. but before we used the bootloader it came with Sep 07 14:35:57 replacing redboot with something else is too dangerous w/o a jtag programmer Sep 07 14:44:23 fray: so u used the pre installed bootloader .... hmmmmm Sep 07 14:44:39 yes.. the instructions for the RSP use it and explain how to load the images into flash Sep 07 14:44:41 no plans to add support in u-boot? Sep 07 14:44:56 not through Yocto.. the RSP is simply an off-the-shelf demo board.. Sep 07 14:44:57 Noor: what's wrong with redboot out of curiosity? Sep 07 14:45:11 if someone else wants to take over support of the RSP within Yocto, they would be free to change out the bootloader Sep 07 14:45:29 bluelightning RedBoot kinda sucks.. ;) (u-boot has it's problems but they're better understood) Sep 07 14:46:23 bluelightning: nothing ....... in our office we have a debug strategy to support u-boot ... we are resoving issues in debugging u-boot with our debugger Sep 07 14:46:31 fray: perhaps I didn't demand much of it... once I got to know how to use it I found it OK for basic tasks Sep 07 14:46:48 Noor, it all comes down to supporting people who have just bought a board from MIPS.. Sep 07 14:47:01 so for mips its bit difficult to change the bootloader ..... so just looking up any thing in u-boot so that we can use it for MIPS Sep 07 14:47:03 they won't be getting a jtag debugger/programmer for it.. so if they screw up the bootloader they'll end up with a brick Sep 07 14:47:07 fray: then again, I used to have to put up with CRL's bootldr which was quite basic by comparison, so maybe I don't have high standards when it comes to bootloaders :) Sep 07 14:47:21 bluelightning: heh Sep 07 14:47:52 so basic it didn't even understand the backspace character... Sep 07 14:47:52 I'm not against u-boot for the RSP, it's just not work we've done.. Sep 07 14:56:45 may I know the name of redboot recipe? .... grepped redboot in yocto but did not find anything Sep 07 15:02:03 Noor: we don't build it, we just use the one on the board... Sep 07 15:02:10 (factory one) Sep 07 15:03:17 oooohhhhh I misunderstood the initial comment Sep 07 15:04:40 BTW as far as I know we dont have redboot recipe in yocto/oe-core .... am i right? Sep 07 15:07:06 Noor: that's correct AFAIK Sep 07 15:07:28 I'm not sure OE classic even has it... Sep 07 15:10:33 bluelightning: yeah it does not exit even there ... just couple of utilities to config redboot from userspace .... dont know what it is Sep 07 15:11:01 anyways thanks for clearing my confusion about routerstationpro Sep 07 15:15:00 Oh heck, the environment handling in bitbake is totally broken :( Sep 07 15:18:34 Noor: no problem :) Sep 07 15:18:37 RP__: ? Sep 07 15:19:36 bluelightning: BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE FOO" FOO=1 bitbake quilt-native -c devshell Sep 07 15:19:46 bluelightning: shows FOO=1. It should not do that Sep 07 15:21:26 RP__: is it the fact that something in BB_ENV_EXTRAWHITE ends up in the shell or that you can modify BB_ENV_EXTRAWHITE externally that concerns you? Sep 07 15:21:43 bluelightning: that it ends up in the shell with no export Sep 07 19:27:28 hi Sep 07 19:28:28 using oe-core with angstrom setup scripts, I compiled a qt4e-demo-image for qemuarm and got a workign result. Then I added a layer containing an armv5 machine (arm926ejs based as qemuarm) and launched the same build. I was expecting a very fast build as only the kernel is different, but in the end I see that all the tasks are executed again and the packages are compiled one more time. Is that an expected behaviour ? Is that because I ad Sep 07 19:28:58 following Tartarus' advice on #oe I ran diffsigs on one package and got that : http://pastebin.com/st5td74e Sep 07 19:29:13 it seems only the MACHINE valude changed but all the packages get compiled again Sep 07 20:43:13 ericben: looking, so of us have been at lunch Sep 07 20:43:55 ericben: seems your pastebin timed out! Sep 07 21:12:36 * RP__ returns **** ENDING LOGGING AT Thu Sep 08 02:59:57 2011