**** BEGIN LOGGING AT Wed Jul 06 02:59:57 2011
Jul 06 08:58:54 <RP__> morning all
Jul 06 10:06:50 <Crofton> gm
Jul 06 16:40:55 <bluelightning> I see we have OLDEST_KERNEL = "2.4.0" in conf/bitbake.conf, is this something we should change?
Jul 06 16:41:23 <bluelightning> seems to be something we pass into eglibc's configure
Jul 06 16:57:03 <RP__> bluelightning: summary, yes
Jul 06 16:57:11 <RP__> bluelightning: might get some speedups :)
Jul 06 16:57:31 <bluelightning> RP__: you want a patch?
Jul 06 16:57:41 <RP__> bluelightning: go for it
Jul 06 16:57:55 <bluelightning> ok
Jul 06 17:08:00 <dvhart> bluelightning, yeah, we have already removed 2.4 support from kernel.bbclass
Jul 06 17:08:35 <bluelightning> indeed... just one more piece to clean up, there may be yet more lurking :)
Jul 06 17:22:00 <jefferai> dvhart: hey there
Jul 06 17:25:26 <dvhart> hey jefferai !
Jul 06 17:25:27 <jefferai> dvhart: with the angstrom distribution that came with the board, not everything was working but I do know that USB was -- or at least, it saw the Ethernet device, and it didn't constantly have those issues with displaying to the monitor
Jul 06 17:25:48 <jefferai> btw -- someone should steal Narcissus from the Angstrom people :-)
Jul 06 17:25:56 <dvhart> what is Narcissus?
Jul 06 17:26:04 <jefferai> the Angstrom Online Image Builder
Jul 06 17:26:10 <jefferai> http://www.angstrom-distribution.org/builder/
Jul 06 17:26:13 <jefferai> it's pretty nice
Jul 06 17:26:25 <jefferai> might be easier than whoever it was that was working on something from scratch
Jul 06 17:26:31 <dvhart> hehe, /me points incandescant and pidge at jefferai ^
Jul 06 17:26:33 <jefferai> of course I haven't actually tried building anything with it yet :-)
Jul 06 17:26:42 <jefferai> (narcissus is open source)
Jul 06 17:27:50 <dvhart> there is some image builder effort going on within the Yocto Project. Both incandescant and pidge (amongst others) are involved. Both from a desktop UI and a web UI point of view.
Jul 06 17:28:21 <dvhart> the Yocto project supports multiple platforms, integrates multiple layers, and has several image types - this complicates the builder UI considerably
Jul 06 17:28:31 <dvhart> but we all agree, something like that would be very useful
Jul 06 17:28:40 <dvhart> jefferai, remind me which rev you're building for?
Jul 06 17:29:18 <jefferai> rev C
Jul 06 17:29:29 <dvhart> right
Jul 06 17:29:51 <dvhart> I don't know where sgw is with the x-load and u-boot patches robert suggested
Jul 06 17:30:01 <dvhart> I'm just now back from jul4 vacation
Jul 06 17:30:19 <dvhart> but those changes may have an impact on the revC
Jul 06 17:30:25 <sgw> dvhart: xload is in and I have a uboot patch
Jul 06 17:30:59 <dvhart> sgw, cool - jefferai once uboot fix is in, I'd be interested to see if the behavior persists
Jul 06 17:31:02 <sgw> but I just found a QA Warning for LDFLAGS with gnuhash stuff
Jul 06 17:31:18 <sgw> dvhart: o I am re-working that
Jul 06 17:33:32 <jefferai> sgw/dvhart: ok, I'll wait on those
Jul 06 17:33:39 <jefferai> can one of you ping me when I should try updating?
Jul 06 17:34:32 <sgw> dvhart: would u-boot-mkimage ever be used on the target? Is it just a native tool?
Jul 06 17:35:05 <dvhart> jefferai, will do
Jul 06 17:35:39 <jefferai> thanks!
Jul 06 17:36:09 <dvhart> sgw, well, it is more likely to be used on the host, but you *could* build on the target for the target I suppose
Jul 06 17:36:21 <dvhart> sgw, do we package gcc to be run on the target?
Jul 06 17:36:35 <sgw> yes for sdk
Jul 06 17:36:51 <sgw> so I guess it reasonable to package this for the target also, just verifing
Jul 06 17:36:58 <dvhart> I _think_ so
Jul 06 17:37:04 <dvhart> I haven't used it explicitly
Jul 06 17:58:13 <sgw> dvhart, jefferai: uboot patch sent, RP will get it when he does (or when I get a consolidated pull together later today).
Jul 06 17:58:28 <dvhart> ack
Jul 06 17:59:41 <incandescant> the problem with naricissus is that afaik it's a fairly static script that gets called with certain paraemters set from a web form
Jul 06 18:00:41 <ka6sox> incandescant, looks like it...its pretty "canned"
Jul 06 18:01:10 * incandescant nods
Jul 06 18:01:30 <incandescant> it's a nice tool, it's just not flexible enough for our desires
Jul 06 18:02:16 <ka6sox> one thing, for example, is the lack of version control as to which packages you want pinned at which version
Jul 06 18:02:51 <ka6sox> so you always, it seems, get the latest out of the repo.
Jul 06 18:03:32 <jefferai> dvhart: sgw: sorry, by "sent" do you mean sent to a mailing list, or pushed up to the repo, or...?
Jul 06 18:03:47 <dvhart> jefferai, on the mailing list awaiting merge
Jul 06 18:03:53 <dvhart> jefferai, I'll poke you when it hits master
Jul 06 18:03:59 <jefferai> ah, ok
Jul 06 18:04:05 <jefferai> I guess it's not one of the mailing lists I joined
Jul 06 18:04:09 <jefferai> or it hasn't come through yet :-)
Jul 06 18:13:53 <bluelightning> re narcissus, narcissus doesn't actually act as a frontend to bitbake, it mostly just assembles images from pre-built packages
Jul 06 18:14:39 <incandescant> bluelightning, oh yeah, that too :-)
Jul 06 18:17:17 <bluelightning> so, I'm setting up a temporary bsp to test something
Jul 06 18:17:25 <bluelightning> if I've set PREFERRED_PROVIDER_virtual/kernel = "linux-yocto"
Jul 06 18:17:32 <bluelightning> why am I getting linux-dummy?
Jul 06 18:18:53 <bluelightning> hmm, maybe I'm missing some bbappends
Jul 06 18:27:05 <bluelightning> yes, missing a lot of kernel config stuff... nvm
**** ENDING LOGGING AT Thu Jul 07 02:59:56 2011