**** BEGIN LOGGING AT Tue Oct 16 03:00:01 2012
Oct 16 12:57:47 <JViz> i added libusb as a dependency to my own image recipe, but i get an error saying it doesn't exist. also "bitbake libusb" works fine
Oct 16 13:05:28 <bluelightning> JViz: in the former case that's a runtime (package) name, in the latter case it's a build-time target (i.e. a recipe or PROVIDES)
Oct 16 13:05:38 <bluelightning> two different things
Oct 16 13:18:04 <JViz> ah
Oct 16 13:18:14 <JViz> thank you
Oct 16 13:24:26 <JViz> so i'm looking for ANGSTROM_EXTRA_INSTALL += ?
Oct 16 13:25:48 <bluelightning> that's a variable that angstrom images use to extend the list of packages to be installed, yes
Oct 16 13:26:00 <JViz> sweet
Oct 16 13:26:31 <JViz> there are a couple "the correct way to do things" pages that aren't actually the correct way
Oct 16 13:26:51 <bluelightning> if you mean on the OE website, most of it is catastrophically out of date
Oct 16 13:27:02 <bluelightning> something we hope to fix fairly soon
Oct 16 13:28:11 <JViz> nah, just high google hits for "make your own angstrom image" and such
Oct 16 13:28:20 <JViz> br
Oct 16 13:28:21 <JViz> brb
Oct 16 22:30:08 <JViz> this is like, the most frustrating thing ever
Oct 16 22:30:39 <JViz> ok, maybe not, but it feels like it
Oct 16 22:31:34 <bluelightning> JViz: what's up?
Oct 16 22:31:44 <JViz> i'm trying to get spidev working
Oct 16 22:32:40 <JViz> when i bitbake virtual/kernel, by default it gives me kernel version 3.2.23 and spidev as a module, but not spidev module in the modules tar
Oct 16 22:32:58 <JViz> so i opkg'd kernel-module-spidev
Oct 16 22:33:08 <JViz> that didn't work
Oct 16 22:33:23 <JViz> i noticed it downloaded a module for kernel 3.2.30, but i don't know if that matters
Oct 16 22:33:54 <JViz> i edited the defconfig in the sources to make spidev=y, so it wouldn't be a module
Oct 16 22:34:00 <JViz> still no spidev in /dev
Oct 16 22:34:43 <JViz> it's not under /sys anywhere either
Oct 16 22:35:03 <JViz> it's kind of like the kernel regressed from where i saw it last, because it used to work
Oct 16 22:35:19 <JViz> oh, let me load up my old image and see what kernel version it was
Oct 16 22:37:10 <JViz> well, it's not older than the last image i was using
Oct 16 22:37:36 <JViz> but i can't remember if i had to modify the board support files or not...
Oct 16 22:39:04 <JViz> it's /supposed/ to have spidev support now, that's what the guy who wrote the tut for editing the board support files said on the page
Oct 16 22:39:51 <JViz> i used to have to do this: http://communistcode.co.uk/blog/blogPost.php?blogPostID=1
Oct 16 22:40:13 <JViz> i'm not supposed to have to do that anymore, but spidev isn't showing up
Oct 16 22:40:28 <JViz> spi support is showing up
Oct 16 22:40:32 <JViz> just no spidev
Oct 16 22:43:00 <JViz> i think i should change the kernel version to 3.2.30, how do i do that?
Oct 16 22:43:24 <JViz> if it's going to install modules for 3.2.30, i need the version to match, don't i?
Oct 16 22:43:52 <JViz> why would it install modules for a different kernel than the one it installs by default?
Oct 16 22:48:15 <JViz> opkg is out of sync with bitbake?
Oct 16 22:56:23 <JViz> OH
Oct 16 22:56:25 <JViz> I SEE
Oct 16 23:02:16 <JViz> erm, nope
Oct 16 23:04:08 <JViz> yeah
Oct 16 23:04:10 <JViz> i see it now
Oct 16 23:04:13 <JViz> damnit
Oct 16 23:10:29 <JViz> i found the problem and it has nothing to do with angstrom
**** ENDING LOGGING AT Wed Oct 17 03:00:01 2012