Robert: So far great work. It's overall working very well.
That being said, I have a pair of questions: #1 I'm trying to use the camera cape with the board, and I get the following error message when I try to read from it using openCV: VIDIOC_REQBUFS: Cannot allocate memory. I believe this has something to do with the dd for the camera, but I'm not sure if it is something that requires mods to the dd or just a change in configuration. #2 I'm assuming this is by design, but when i try to read from the camera using gstreamer, I get a package not found error. It seems as if gstreamer isn't in this package, yet I aloso run into problems when I try to do an apt-get in that it can not be located. This may very well be by design and I just haven't overcome the issues. Thanks again for your hard work on this codebase. Walt On Wednesday, January 22, 2014 6:38:23 PM UTC-6, RobertCNelson wrote: > > On Wed, Jan 22, 2014 at 5:06 PM, Louis McCarthy > <[email protected]<javascript:>> > wrote: > > Wow, Robert, you have been busy today! I was going to comment on > > xinput-calibrate, but you made a commit about 15 minutes before I did a > > clone, then I was trying to deal with touchscreen jitter and saw your > patch > > of 3.8.13-bone37....thanks for your work. I will test those out as soon > as I > > can get them built :) > > Oh we got lucky on xinput-calibrate, i was starting to look up writing > lightdm scripts, when i just hooked up the one found in their repo and > rebooted.. It worked, so ship it. ;) > > > On the capemgr front......I am looking into ways to get the dtbo files > > accessible at boot time. > > Option 1) Get capemgr to find /lib/firmware on startup > > Option 2) Put dtbo files into boot partition > > Couples issues, > > The *.dtbo's already compiled under /lib/firmware should work via the > uEnv.txt *_enable call.. > The kernel .config, build firmware in kernel is enabled. > We are using an initrd. (helps hide the lack of rtc problem for rootfs > and allows us to us uuid's for the eMMC, aka allowing single/multi mmc > card combinations..) > > So, any modifications to any of the existing /lib/firmware/*.dtbo file > will be ignored, as the kernel has it built-in. > > Any additions to /lib/firmware/*.dtbo are ignored as they are too late > on boot (uEnv.txt *_enable call) and are not in the initrd. > > So.. I "think" we can fix the problem, by making sure all *.dtbo's > (including new ones from users) are re-pulled into the initrd when > it's regenerated. Here's the current initrd.img update routine. > > if [ ! -f /boot/initrd.img-$(uname -r) ] ; then > update-initramfs -c -k $(uname -r) > else > update-initramfs -u -k $(uname -r) > fi > cp -v /boot/initrd.img-$(uname -r) /boot/uboot/initrd.img > > I'm guessing we just have to add the *.dtbo to one of the /etc/xyz > files that update-initramfs utilizes.. > > Regards, > > -- > Robert Nelson > http://www.rcn-ee.com/ > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
