**** BEGIN LOGGING AT Mon Apr 09 02:59:58 2012 Apr 09 15:29:55 Hello, I'm a looking for a bit of help adding support for some new hardware. It's an OMAP3530 based device, the kernel source I have for it is 2.6.35.3. My question is what version should I diff from (2.6.35 or 2.6.35.3) and which recipe should I add to (linux-2.6.35.bb, create a now linux-omap recipe, create a whole new recipe altogether)? Apr 09 15:40:59 jawilson, it depends Apr 09 15:41:17 which existing recipe best fits the kernel source format you have Apr 09 15:45:02 Crofton, kernel source format? Apr 09 15:45:29 I downloaded vanilla 2.6.35.3 from kernel.org and diffed it and the output seemed fairly sane Apr 09 15:45:34 tarball, git repo, tarball + patches etc Apr 09 15:47:22 so the device is an iVeia SoM, I have the source from them as just a plain tarball Apr 09 15:48:31 is the tarball fetchable? Apr 09 15:48:54 the easy thing is make your own recipe Apr 09 15:49:11 but, reducing kernel recipe fragmentation is a good thing Apr 09 15:49:21 yeah, that's what I was hoping to do Apr 09 15:49:56 not sure if it's fetchable, I got it from a local SVN, but I'm not sure how we got it from iVeia Apr 09 15:50:16 I was wanting to follow this http://www.openembedded.org/wiki/Adding_a_new_Machine Apr 09 15:51:00 but was unsure of which version to generate the patch from and which recipe to add it to Apr 09 15:51:05 that is a bit dated since it is for oe-classic, not oe-core Apr 09 15:51:18 and, I am going afk very soon Apr 09 15:51:41 I'm still using oe-classic, have to read up on oe-core Apr 09 15:51:46 alright, well thanks Apr 09 15:52:41 good luck Apr 09 15:53:38 thanks Apr 09 19:23:21 greetings! has udev been deprecated in oe-core? Apr 09 19:25:14 xumbi: no Apr 09 19:26:53 khem: ok thanks, I'm trying out a new image built with a recent oe-core and I don't see entries under /dev/input like in my old image, thought it might be udev but it must be something else Apr 09 21:15:26 hello. Does anyone know how to force the bitbake to build from the org.openembedded.dev/sources directory, rather than going out to the URL to get the source on itial bitbake? Apr 09 21:15:37 I put the source there, but the bitbake still goes out to the internet Apr 09 21:18:07 essentially what I want to do is skip the "fetch" stage Apr 09 21:18:14 for all of my packages Apr 09 21:18:21 I have all the sources already copied locally Apr 09 21:24:52 in other words, I want to skip "do_fetch" stage Apr 09 21:36:16 hiya Apr 09 21:47:04 Michaelmt: I think with OE-Classic you need to have .md5 files for each downloaded file containing the md5sum (the hash only) for the file Apr 10 01:52:14 hmm, checking out oe-core and bitbake by themselves is annoying Apr 10 02:06:27 heh, i assume you mean the setup involved. at a minimum you need a bblayers.conf and local.conf from somewhere. easiest to set up a template repo of some sort, or use shr or angstrom's scripts. I use http://github.com/kergoth/oe-core-template myself. Apr 10 02:06:54 yeah Apr 10 02:07:56 i think it's bad that bblayers.conf is apparently required now. either 1) bblayers.conf & friends are a convenience around bbpath/bbfiles, or 2) they're the definitive setup method, and we can drop all the underlying bbpath/bbfiles manipulations in favor of more direct layer support Apr 10 02:08:21 imo anyway Apr 10 02:08:27 I am trying to avoid the submodules stuff **** ENDING LOGGING AT Tue Apr 10 03:00:00 2012