**** BEGIN LOGGING AT Sat Feb 25 02:59:59 2012
Feb 25 07:19:25 <JViz> what's going on with the angstrom website?
Feb 25 07:59:34 <JViz> is there a good book on angstrom?
Feb 25 09:32:53 <Roland_home> Hi. Anybody knows what's happening to angstrom website?
Feb 25 12:41:12 <Crofton|work> linuxtopgo server is having issues
Feb 25 12:44:26 <Roland_home> angstrom-distribution too
Feb 25 15:50:43 <OrlandoT> Is there an SDK I can use to develop apps and device drivers for the Beaglebone Angstrom distro?
Feb 25 18:45:53 <JViz> OrlandoT: are you looking or anything in specific?
Feb 25 19:55:11 <OrlandoT> I am looking for one for the standard package/kernel that comes with the Beaglebone
Feb 25 19:55:45 <OrlandoT> so that I could develop a kernel device driver for the Beaglebone that everybody could use
Feb 25 20:19:33 <JViz> OrlandoT: i think we're both trying to do the same thing
Feb 25 20:26:57 <OrlandoT> JViz: too bad that nobody seems to be answering. I think the answer is no there is no SDK
Feb 25 20:27:39 <Jonimus> there was some stuff on openembedded, but since angstrom was the only distro still semi active there I'm not even sure how applicable it is
Feb 25 20:27:41 <OrlandoT> JViz: what exactly are you doing?
Feb 25 20:28:13 <Jonimus> the rootfs building stuff does include a gcc and such to work with
Feb 25 20:28:20 <Jonimus> but other than that I know nothing
Feb 25 20:49:49 <JViz> I am trying to get the libs and headers to cross compile my program
Feb 25 20:50:36 <JViz> I thought that if i do an angstrom build, that i would be able to get all the libs and headers
Feb 25 20:51:21 <JViz> now i'm trying to figure out how to add extra angstrom packages to my angstrom build environment
Feb 25 20:57:08 <OrlandoT> JViz: Ok I did the same, I got me an angstrom build
Feb 25 20:57:44 <OrlandoT> sadly my board usb is acting up and I still haven't been able to connect to the console
Feb 25 20:58:28 <OrlandoT> the instructions at http://beagleboard.org/static/beaglebone/a3/README.htm say to type screen /dev/beaglebone-serial 115200
Feb 25 20:58:53 <OrlandoT> but my distro (ubuntu 11.10) does not have any dev called beaglebone-serial
Feb 25 20:59:01 <OrlandoT> and the instructions do not say anything about creating it
Feb 25 21:00:08 <OrlandoT> i did "screen /dev/ttyUSB0 115200" and even "screen /dev/ttyUSB1 115200" and i cannot get any console
Feb 25 21:05:12 <JViz> OrlandoT: i had the same problem, i ended up hooking it up to the network and SSHing into it
Feb 25 21:05:20 <JViz> er
Feb 25 21:05:24 <JViz> similiar problem
Feb 25 21:05:53 <OrlandoT> that is sad to hear
Feb 25 21:06:06 <OrlandoT> I was hoping this was more stable
Feb 25 21:06:33 <JViz> it's just the usb serial chip they decided to go with
Feb 25 21:06:36 <JViz> the drivers are buggy
Feb 25 21:06:37 <Jonimus> it would be created by a udev rule
Feb 25 21:07:00 <Jonimus> the /dev/beaglebone-serial that is
Feb 25 21:07:39 <JViz> oh
Feb 25 21:07:47 <JViz> i was doing it from windows
Feb 25 21:07:56 <JViz> i couldn't get a serial connection
Feb 25 21:08:06 <JViz> i think it was because my computer wouldn't properly identify the driverse
Feb 25 21:08:22 <OrlandoT> Jonimus: to quote the documentation
Feb 25 21:08:26 <OrlandoT> "To make a pre-A5 BeagleBone show up upon every reboot, add a udev rule. Here is an example /etc/udev/rules.d/73-beaglebone.rules: "
Feb 25 21:08:44 <OrlandoT> mine is not a pre-A5 board so I skipped the step
Feb 25 21:09:03 <Jonimus> You'd still need a udev rule to get that dev entry
Feb 25 21:09:11 <OrlandoT> also quoting from the doc "For A5 boards, no drivers should need to be installed. For older boards, you'll need invoke the driver by specifying the vendor and product ID: "
Feb 25 21:09:34 <Jonimus> No drivers should be needed correct
Feb 25 21:09:50 <Jonimus> as seen by the creation of /dev/ttyUSB#
Feb 25 21:10:05 <OrlandoT> ok
Feb 25 21:10:10 <Jonimus> the udev rule would just make the link to /dev/beaglebone-serial
Feb 25 21:10:11 <OrlandoT> then should I add the rule?
Feb 25 21:10:32 <OrlandoT> or can i simply use ttyUSB0 or ttyUSB1?
Feb 25 21:10:50 <Jonimus> it would most likely need adjustment as I'd assume the example is for some specific revision and the id's may have changed
Feb 25 21:11:39 <Jonimus> but I don't own any of the beagle boards so I can't help much there
Feb 25 21:12:22 <JViz> Jonimus: How do I add packages to an
Feb 25 21:12:29 <JViz> Angstrom build?
Feb 25 21:13:20 <Jonimus> how are you getting the build?
Feb 25 21:13:40 <JViz> git clone
Feb 25 21:14:02 <JViz> and then oebb.sh
Feb 25 21:14:40 <Jonimus> well you should be able to edit the recipe or make a custom one with the things you want
Feb 25 21:14:58 <JViz> which file has the recipe?
Feb 25 21:17:29 <Jonimus> heh I haven't dug into the files in a while, but grep may be able to find it :P
Feb 25 21:17:46 <JViz> i don't know what i would be grepping for though
Feb 25 21:20:25 <Jonimus> beaglebone perhaps :P
Feb 25 21:21:37 <JViz> nah, because that's the just sent to bitbake as a cmdline var
Feb 25 21:24:03 <Jonimus> it tells bitbake what recipe to use I'd bet :P
Feb 25 21:24:45 <JViz> well yeah
Feb 25 21:24:58 <JViz> but what does it do with that? where does it store the recipe?
Feb 25 21:25:02 <Jonimus> in the git tree
Feb 25 21:25:17 <Jonimus> I don't recall where and I don't have a system with that git clone handy
Feb 25 21:27:49 <JViz> :( oh well
Feb 25 21:27:56 <JViz> i'll find it eventually
Feb 25 21:28:49 <JViz> i think it's in setup-scripts/sources/openembedded-core/meta
Feb 25 21:29:04 <JViz> but there are a lot of recipes in there
Feb 25 21:36:01 <JViz> bbl
Feb 25 21:40:08 <JViz> hm
Feb 25 21:40:23 <JViz> wouldn't it have to tell git what to get and what *not* to get?
Feb 25 21:41:22 <JViz> er,  no
Feb 25 21:41:35 <JViz> oebb must have it's own download mechanism
Feb 25 21:42:16 <Jonimus> I'm pretty sure it just grabs everything
Feb 25 21:42:29 <Jonimus> the package recipes grab the source
Feb 25 21:43:15 <JViz> all of build targets for angstrom share all of the same sources?
Feb 25 21:43:44 <Jonimus> the stuff in the git tree is just the build scripts and such
Feb 25 21:43:53 <Jonimus> known as recipes
Feb 25 21:44:26 <JViz> wouldn't you need different versions of the source files for different machines though?
Feb 25 21:45:00 <Jonimus> and there are machine specific recipes to handle that
Feb 25 21:45:44 <JViz> is that what the layers are for?
Feb 25 21:46:32 <Jonimus> Note, I'm no expert on this and I haven't actually touched angstrom in over a year
Feb 25 21:46:37 <Jonimus> I just kinda lurk :P
Feb 25 21:46:42 <JViz> ah
Feb 25 21:47:19 <Jonimus> but I had built some custom images for my iPaq h2200's
Feb 25 21:47:28 <Jonimus> hence me digging into the custom recipe stuff
Feb 25 21:47:53 <Jonimus> you should also be able to build extra packages with bitbake
Feb 25 21:48:07 <Jonimus> but I don't know if you have access to the bone's fs to manually install them
Feb 25 21:48:26 <JViz> bone's file system
Feb 25 21:48:26 <JViz> ?
Feb 25 21:48:47 <JViz> i have access to my beaglebone's fs
Feb 25 21:48:47 <Jonimus> the fs on the beaglebone that the image installs to
Feb 25 21:48:56 <Jonimus> yes that is what I was asking
Feb 25 21:49:16 <Jonimus> then you can just bitbake package iirc and throw it on there and install with opkg
Feb 25 21:50:02 <JViz> there ar already packages for it available
Feb 25 21:50:11 <JViz> i just need to get them in my build env
Feb 25 21:50:54 <JViz> i want to add them to the machine recipe
Feb 25 21:51:03 <JViz> like, the top level recipe?
Feb 25 21:51:07 <JViz> but i can't find it
Feb 25 21:51:55 <Jonimus> well what is the bitbake command run?
Feb 25 21:53:29 <JViz> MACHINE=${MACHINE} bitbake $*
Feb 25 21:53:32 <JViz> or
Feb 25 21:53:46 <JViz> bitbake $*
Feb 25 21:53:52 <JViz> i'm not the best at reading shell scripts
Feb 25 21:55:44 <Jonimus> is this in a function or what?
Feb 25 21:55:48 <OrlandoT> does anybody know how I can compile a Angstrom kernel module outside the kernel source tree? normally I would do something like make -C ~/kernel-x.x M='pwd' modules with a Makefile like obj-m := hello.o
Feb 25 21:56:07 <OrlandoT> but that is natively not cross compiled
Feb 25 21:56:31 <Crofton|work> set CROSS_COMPILE= ?
Feb 25 21:56:33 <JViz> OrlandoT: you can make bitbake compile the kernel for you
Feb 25 21:57:06 <OrlandoT> JViz: I do not wish to compile the kernel though
Feb 25 21:57:22 <OrlandoT> i just want to compile my module (kernel driver module)
Feb 25 21:57:36 <OrlandoT> and I want to do it outside the kernel tree
Feb 25 21:57:53 <Jonimus> OrlandoT: the CROSS_COMPILE arg may do what you need as Crofton|work said
Feb 25 21:57:57 <Jonimus> or try google :/
Feb 25 21:58:38 <JViz> bbl
Feb 25 21:58:57 <OrlandoT> I suppose that I already have a cross compiler since Angstrom was built with bitbake oob
Feb 25 21:59:21 <Jonimus> indeed
Feb 25 21:59:41 <OrlandoT> I just don't know where to find the cross compiler tools inside the directories that angstrom build system has
Feb 25 22:02:12 <JViz> setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/bin/armv7a-angstrom-linux-gnueabi
Feb 25 22:02:14 <Crofton|work> look in tmp/sysroots and you should find the compiler
Feb 25 22:12:35 <OrlandoT> I would have never looked in x86_64-linux directory for a cross compiler
Feb 25 22:13:30 <Crofton|work> well, that is the arch it runs on
Feb 25 22:15:01 <OrlandoT> ok found it
Feb 25 22:15:04 <OrlandoT> thanks JViz
Feb 25 22:36:30 <OrlandoT> ok I get me the command right this time
Feb 25 22:36:32 <OrlandoT> make -C ~/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/beaglebone/kernel M=`pwd` modules
Feb 25 22:36:59 <OrlandoT> that SHOULD be able to build my module but it gets a bunch of errors related to the kernel header files
Feb 25 22:37:13 <OrlandoT> can anybody compile a kernel module like this?
Feb 25 22:41:03 <OrlandoT> oops I meant
Feb 25 22:41:06 <OrlandoT> CROSS_COMPILE=arm-angstrom-linux-gnueabi make -C ~/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/beaglebone/kernel M=`pwd` modules
Feb 25 22:41:13 <OrlandoT> same results though
Feb 25 22:42:46 <OrlandoT> ok typing error again lol
Feb 25 22:42:50 <OrlandoT> command is
Feb 25 22:43:11 <OrlandoT> CROSS_COMPILE=arm-angstrom-linux-gnueabi- make -C ~/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/beaglebone/kernel M=`pwd` modules
Feb 25 22:43:35 <OrlandoT> I get cc1: error: unrecognized command line option "-m64"
Feb 25 22:43:53 <OrlandoT> cc1: error: unrecognized command line option "-mno-red-zone"
Feb 25 22:44:05 <OrlandoT> c1: error: unrecognized command line option "-mcmodel=kernel"
Feb 25 22:51:06 <OrlandoT> ok I finally got a .o but no .ko by using this command
Feb 25 22:51:11 <OrlandoT> make CROSS_COMPILE=arm-angstrom-linux-gnueabi- ARCH=arm -C ~/setup-scripts/build/tmp-angstrom_2010_x-eglibc/sysroots/beaglebone/kernel M=`pwd` modules
Feb 25 22:52:01 <OrlandoT> got this error "/bin/sh: scripts/basic/fixdep: No such file or directory"
**** ENDING LOGGING AT Sun Feb 26 02:59:58 2012