https://wiki.gumstix.com/api.php?action=feedcontributions&feedformat=atom&user=BallCam 2026-04-27T05:26:19Z User contributions MediaWiki 1.25.3 https://wiki.gumstix.com/index.php?title=Slackware_14.1_On_Gumstix_Overo&diff=6086 2014-05-18T23:07:24Z

<p>BallCam: </p> <hr /> <div>=== 20 April 2014 ===<br /> <br /> Slackware 14.1 has been installed on Gumstix Overo Devices and used succesfully with their expansion boards, with a 3.5 series kernel, built with Yocto, and BitBake.<br /> <br /> Slackware packages install, and software built with &quot;configure&quot; and &quot;make&quot; also install and run.<br /> <br /> GUI Has not yet been tested. In Progress.<br /> <br /> The majority of focus will be placed on Installing, Running, and Developing Slackware 14.1 on Gumstix as Slackware 13.37 is End Of Life, and the 3.5.x Kernels built with Yocto, and provided by Gumstix support enough devices.<br /> <br /> <br /> === Prerequisites ===<br /> <br /> <br /> SD Card:<br /> Setup and Format per Gumstix Instructions.<br /> <br /> Very Important: Use the fastest SD card media you can afford. &quot;UHS Speed Class 1&quot; or &quot;Speed Class 10&quot;, minimum.<br /> Also consider using the ext4 filesystem, BUT, you will have to rebuild the kernel for that.<br /> <br /> If you go cheap on the SD Cards, like &quot;Speed Class 4&quot;, you will notice the difference. The kernel caches writes<br /> to the SD Card, and finishes them as it can. This is why it is always important to use the &quot;sync&quot; command when <br /> copying data to the SD Card. If you are trying to do any kind of video capture application, the SD card has to <br /> be fast enough to handle HD video capture. <br /> <br /> '''u-boot:'''<br /> setenv console ttyO2,115200n<br /> setenv mmcroot<br /> setenv mmcrootfstype <br /> <br /> '''kernel:'''<br /> a) Use Kernel and modules from device NAND, (They can be copied over the network, for example if an Overo<br /> is booted in a Tobi), or;<br /> b) Use Yocto and Bitbake to build a kernel, or;<br /> c) Use a pre-built image. <br /> <br /> Generally it is best to get the latest you can. The kernel used in this How To is: 3.5.7-yocto-standard<br /> <br /> '''modules:'''<br /> Don't forget the modules, however you get your kernel.<br /> <br /> '''firmware:'''<br /> You may need firmware for whateber USB WiFi device you are using.<br /> <br /> '''/etc/rc.d/ directory:'''<br /> <br /> '''/etc/rc.d/rc.M'''<br /> <br /> '''/etc/rc.d/rc.ntpd'''<br /> add the command:<br /> ntpdate -b &lt;your time server&gt; above the line<br /> that saves the kernel time to hardware, so that your system is always on time.<br /> <br /> '''/etc/inittab'''<br /> make sure the line for your login console is like so, to login to using the<br /> usb console interface (Tobi, Janus, Gallop)<br /> <br /> c1:12345:respawn:/sbin/agetty --noclear 38400 tty1 linux<br /> <br /> <br /> '''/etc/mtab'''<br /> <br /> /dev/mmcblk0p2 / ext4 rw,sync 0 0<br /> <br /> <br /> Copy Slackware ARM packages to SD Card<br /> <br /> <br /> To control module loading order, say for example, to load the camera and wifi modules last, blacklist the modules and load them in your own scripts or via /etc/rc.d/rc.local. <br /> <br /> <br /> <br /> ==== Using The Caspa / MT9V032 Sensor With Slackware 14.1 On Gumstix Overo ====<br /> <br /> Make sure to use a 3.5 series kernel built with Yocto and Bitbake per Gumstix' instructions. At least 3.5.7. When purchasing your device you may be able to request they flash the NAND with an appropriate kernel.<br /> <br /> ===== Prerequisites =====<br /> <br /> '''media-ctl''' -- Necessary to set sensor paramters.<br /> <br /> '''yavta''' &quot;Yet Another Video4Linux Test Application&quot; -- Implements Simple Image Capture Functions<br /> <br /> '''ffmpeg''' -- to &quot;transcode&quot; &quot;raw&quot; images captured by yavta, into other image or video formats.<br /> <br /> <br /> ==== Using The P54USB WiFi With Slackware 14.1 On Gumstix Overo ====<br /> <br /> This may be enabled by default in a Yocto kernel. It supports Host AP mode. Needs 5 Volts.<br /> <br /> <br /> ==== Using The rt2800usb USB WiFi With Slackware 14.1 On Gumstix Overo ====<br /> <br /> This likewise may be built in by default in a Yocto kernel. Works at both 3.6 and 5 volts.<br /> <br /> This device should work with NiMH and LiPo Battery Voltages. It supports Host AP Mode.<br /> <br /> <br /> ==== Using The LIS331 3-Axis Accelerometer With Slackware 14.1 On Gumstix Overo ====<br /> <br /> This is an I2C device. Level Shifters may be needed on the SDA and SCL lines when using this device with any other I2C Device, or to prevent intermittent operation.<br /> <br /> <br /> ==== Using The MPU-6050 3-Axis Accelerometer With Slackware 14.1 On Gumstix Overo ====<br /> <br /> This is an I2C device. Level Shifters may be needed on the SDA and SCL lines when using this device with any other I2C Device, or to prevent intermittent operation.<br /> <br /> [http://invensense.com/mems/gyro/documents/RM-MPU-6000A.pdf MPU-6050 Register Map]</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6085 2014-05-18T23:02:02Z

<p>BallCam: </p> <hr /> <div>== 8 May 2014 ==<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working with kernels 2.6.34, and 3.5.7-yocto-standard.<br /> <br /> P54 USB and rt2800usb WiFi devices work in Host Mode with hostapd. WiFi generally works in non-host mode for several devices, including libertas.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> <br /> === Prerequisites ===<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can these from Gumstix web resources, or from the NAND of the device you purchase. <br /> <br /> It is assumed that you have experience using Slackware, on some other architecture.<br /> <br /> Software will need to be installed using &quot;configure&quot; and &quot;make&quot;, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> <br /> <br /> === Basic Installation Strategy: ===<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> <br /> '''Notes:'''<br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can &quot;cross-install&quot; that is, use an x86 based PC to run &quot;installpkg to install Slackware ARM packages to an SD card to be used as the rootfs of your device for '''most''' but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do &quot;cross-install&quot; successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using &quot;installpkg&quot;. It works fine. &quot;pkgtool&quot; also works, but may not work when using the miniroot unless a few more packages from the &quot;a&quot; series are installed. <br /> <br /> <br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. '''GCC''' and '''Make''' work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> <br /> <br /> === Building Your Own Kernel: ===<br /> <br /> ==== Linux 3.5.x Kernel ====<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> <br /> <br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo:<br /> <br /> Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> <br /> <br /> ==== Linux 2.6.x Kernel ====<br /> <br /> The instructions for building a 2.6 series kernel for Gumstix can be found here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> Those instructions can be applied to kernel source obtained from Kernel.org, or Gumstix Resources.<br /> <br /> The main reason to build a 2.6 kernel is for use with Slackware ARM 13.37, and to take advantage of the<br /> kernel from Gumstix above that can be used with the Caspa. <br /> <br /> However, Since Slackware ARM 13.37 is now end of life, the focus in these wiki pages will be on Slackware ARM 14.1.<br /> <br /> <br /> <br /> === Installing Slackware ARM Packages On Overo: ===<br /> <br /> Once you have a bootable system, you can use &quot;installpkg&quot;, &quot;removepkg&quot; and &quot;pkgtool&quot; to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the &quot;a&quot; series installed. You can manually install the rest.<br /> <br /> Packages from the &quot;a&quot;, &quot;ap&quot;, &quot;d&quot;, &quot;l&quot;, &quot;n&quot; and &quot;x&quot; sets need to be installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This How To will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone with KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with &quot;removepkg&quot; or &quot;pkgtool&quot; then install from the source to get the particular version you like.<br /> <br /> <br /> <br /> === Devices Tested So Far: ===<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware:<br /> <br /> <br /> ==== Caspa Camera Unit / MT9V032 Sensor and Kernel Driver: ====<br /> <br /> <br /> ===== Using Caspa With 2.6.34 Kernel =====<br /> <br /> Start with the Gumstix User Wiki page for the Caspa, here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, follow<br /> the instructions in the Wiki Page above.<br /> <br /> <br /> ===== Using Caspa With 3.5.x Kernel =====<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from Gumstix, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work.<br /> <br /> Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its &quot;Pixel Format&quot;, or &quot;Color Space&quot; will be what is referred to as &quot;UYVY&quot;.<br /> <br /> The instructions for using &quot;yavta&quot; also work. &quot;yavta&quot; is simply: &quot;Yet Another Video4linux Test Application&quot;.<br /> <br /> Yavta will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the &quot;-pix_fmt&quot; option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the &quot;DISPLAY&quot; option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the &quot;LD_PRELOAD&quot; environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> <br /> <br /> ==== P54USB WiFi: ====<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only, works in 2.6, and 3.5 series kernels.<br /> <br /> Use this search page for devices that use the Prism 54 USB WiFi Driver<br /> <br /> http://wireless.kernel.org/en/users/Devices/USB<br /> <br /> Make sure that you have the firmware, though it is usually included<br /> in the kernel source.<br /> <br /> Make sure that the USB device that you buy is BOTH the correct<br /> Model Number, AND Revision. Manufacturers change their chipsets <br /> between revisions.<br /> <br /> <br /> ==== WRL-11713 PCDuino WiFi Dongle: ====<br /> <br /> From SparkFun.com – rt2800usb Works With HostAPD on Overo. Tested with kernel 3.5.7-yocto-standard.<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> The command:<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id <br /> <br /> Must be used to bring up the interface. <br /> <br /> Make sure to get the firmware from the [http://www.mediatek.com/en/downloads MediaTek / Ralink] website.<br /> <br /> Tested with 5 Volts and 3.6 Volts to validate for use with NiMH, or LiPo Batteries. Works with both.<br /> <br /> <br /> ==== LIS-331 Accelerometer: ====<br /> <br /> https://www.sparkfun.com/products/10345 <br /> <br /> LIS-331 Accelerometer. Works with I2C. Can be tested without Level Shifters on SDA/SCL Lines, <br /> if it is the only device using I2C, but may work intermittently if other devices like the Caspa,<br /> are using I2C, and Level Shifters are not used to set the SDA/SCL lines to 3.3 V. for this Chip.<br /> <br /> Works with i2ctools, from userspace.<br /> <br /> <br /> ==== MPU-6050 Accelerometer: ====<br /> <br /> https://www.sparkfun.com/products/11028<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Can be tested without Level Shifters on SDA/SCL Lines, <br /> if it is the only device using I2C, but may work intermittently if other devices like the Caspa,<br /> are using I2C, and Level Shifters are not used to set the SDA/SCL lines to 3.3 V. for this Chip.<br /> <br /> Works with i2ctools, from userspace.<br /> <br /> <br /> '''See The Sample Script Below.'''<br /> <br /> #!/bin/bash<br /> <br /> # Device I2C Bus Addresses<br /> MPU6050_0=0X68<br /> MPU6050_1=0X69<br /> <br /> # Initialization Register Address.<br /> PWR_MGMT_1=0x6b<br /> <br /> # Initialize Device, Select Z Axis As Clock Signal. (Register Map, p.41)<br /> INIT_SEL_Z_CLOCK=0x02<br /> i2cset -y 3 $MPU6050_0 $PWR_MGMT_1 $INIT_SEL_Z_CLOCK b<br /> i2cset -y 3 $MPU6050_1 $PWR_MGMT_1 $INIT_SEL_Z_CLOCK b<br /> <br /> # Set Max Resolution on Accelerometer and Gyro:<br /> i2cset -y 3 0x68 0x1c 0x18 b<br /> i2cset -y 3 0x69 0x1b 0x18 b<br /> <br /> # Read Bus:<br /> i2cdetect -y -r 3<br /> <br /> <br /> # Read Accelerometer 1:<br /> echo &quot;ACCEL_XOUT_H=&quot; `i2cget -y 3 $MPU6050_0 0x3b b`<br /> echo &quot;ACCEL_XOUT_L=&quot; `i2cget -y 3 $MPU6050_0 0x3c b`<br /> echo &quot;ACCEL_YOUT_H=&quot; `i2cget -y 3 $MPU6050_0 0x3d b`<br /> echo &quot;ACCEL_YOUT_L=&quot; `i2cget -y 3 $MPU6050_0 0x3e b`<br /> echo &quot;ACCEL_ZOUT_H=&quot; `i2cget -y 3 $MPU6050_0 0x3f b`<br /> echo &quot;ACCEL_ZOUT_L=&quot; `i2cget -y 3 $MPU6050_0 0x40 b`<br /> <br /> # Read Accelerometer 2:<br /> echo &quot;ACCEL_XOUT_H=&quot; `i2cget -y 3 $MPU6050_1 0x3b b`<br /> echo &quot;ACCEL_XOUT_L=&quot; `i2cget -y 3 $MPU6050_1 0x3c b`<br /> echo &quot;ACCEL_YOUT_H=&quot; `i2cget -y 3 $MPU6050_1 0x3d b`<br /> echo &quot;ACCEL_YOUT_L=&quot; `i2cget -y 3 $MPU6050_1 0x3e b`<br /> echo &quot;ACCEL_ZOUT_H=&quot; `i2cget -y 3 $MPU6050_1 0x3f b`<br /> echo &quot;ACCEL_ZOUT_L=&quot; `i2cget -y 3 $MPU6050_1 0x40 b` <br /> <br /> <br /> <br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse the Gumstix GitHub repo. Look under &quot;meta-gumstix&quot;, and &quot;linux&quot;.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6084 2014-05-09T01:20:39Z

<p>BallCam: </p> <hr /> <div>== 8 May 2014 ==<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working with kernels 2.6.34, and 3.5.7-yocto-standard.<br /> <br /> P54 USB and rt2800usb WiFi devices work in Host Mode with hostapd. WiFi generally works in non-host mode for several devices, including libertas.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> <br /> === Prerequisites ===<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can these from Gumstix web resources, or from the NAND of the device you purchase. <br /> <br /> It is assumed that you have experience using Slackware, on some other architecture.<br /> <br /> Software will need to be installed using &quot;configure&quot; and &quot;make&quot;, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> <br /> <br /> === Basic Installation Strategy: ===<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> <br /> '''Notes:'''<br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can &quot;cross-install&quot; that is, use an x86 based PC to run &quot;installpkg to install Slackware ARM packages to an SD card to be used as the rootfs of your device for '''most''' but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do &quot;cross-install&quot; successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using &quot;installpkg&quot;. It works fine. &quot;pkgtool&quot; also works, but may not work when using the miniroot unless a few more packages from the &quot;a&quot; series are installed. <br /> <br /> <br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. '''GCC''' and '''Make''' work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> <br /> <br /> === Building Your Own Kernel: ===<br /> <br /> ==== Linux 3.5.x Kernel ====<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> <br /> <br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo:<br /> <br /> Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> <br /> <br /> ==== Linux 2.6.x Kernel ====<br /> <br /> The instructions for building a 2.6 series kernel for Gumstix can be found here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> Those instructions can be applied to kernel source obtained from Kernel.org, or Gumstix Resources.<br /> <br /> The main reason to build a 2.6 kernel is for use with Slackware ARM 13.37, and to take advantage of the<br /> kernel from Gumstix above that can be used with the Caspa. <br /> <br /> However, Since Slackware ARM 13.37 is now end of life, the focus in these wiki pages will be on Slackware ARM 14.1.<br /> <br /> <br /> <br /> === Installing Slackware ARM Packages On Overo: ===<br /> <br /> Once you have a bootable system, you can use &quot;installpkg&quot;, &quot;removepkg&quot; and &quot;pkgtool&quot; to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the &quot;a&quot; series installed. You can manually install the rest.<br /> <br /> Packages from the &quot;a&quot;, &quot;ap&quot;, &quot;d&quot;, &quot;l&quot;, &quot;n&quot; and &quot;x&quot; sets need to be installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This How To will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone with KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with &quot;removepkg&quot; or &quot;pkgtool&quot; then install from the source to get the particular version you like.<br /> <br /> <br /> <br /> === Devices Tested So Far: ===<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware:<br /> <br /> <br /> ==== Caspa Camera Unit / MT9V032 Sensor and Kernel Driver: ====<br /> <br /> <br /> ===== Using Caspa With 2.6.34 Kernel =====<br /> <br /> Start with the Gumstix User Wiki page for the Caspa, here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, follow<br /> the instructions in the Wiki Page above.<br /> <br /> <br /> ===== Using Caspa With 3.5.x Kernel =====<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from Gumstix, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work.<br /> <br /> Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its &quot;Pixel Format&quot;, or &quot;Color Space&quot; will be what is referred to as &quot;UYVY&quot;.<br /> <br /> The instructions for using &quot;yavta&quot; also work. &quot;yavta&quot; is simply: &quot;Yet Another Video4linux Test Application&quot;.<br /> <br /> Yavta will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the &quot;-pix_fmt&quot; option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the &quot;DISPLAY&quot; option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the &quot;LD_PRELOAD&quot; environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> <br /> <br /> ==== P54USB WiFi: ====<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only, works in 2.6, and 3.5 series kernels.<br /> <br /> Use this search page for devices that use the Prism 54 USB WiFi Driver<br /> <br /> http://wireless.kernel.org/en/users/Devices/USB<br /> <br /> Make sure that you have the firmware, though it is usually included<br /> in the kernel source.<br /> <br /> Make sure that the USB device that you buy is BOTH the correct<br /> Model Number, AND Revision. Manufacturers change their chipsets <br /> between revisions.<br /> <br /> <br /> ==== WRL-11713 PCDuino WiFi Dongle: ====<br /> <br /> From SparkFun.com – rt2800usb Works With HostAPD on Overo. Tested with kernel 3.5.7-yocto-standard.<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> The command:<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id <br /> <br /> Must be used to bring up the interface. <br /> <br /> Make sure to get the firmware from the [http://www.mediatek.com/en/downloads MediaTek / Ralink] website.<br /> <br /> Tested with 5 Volts and 3.3 Volts.<br /> <br /> <br /> ==== LIS-331 Accelerometer: ====<br /> <br /> https://www.sparkfun.com/products/10345 <br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> Works with i2ctools, from userspace.<br /> <br /> <br /> ==== MPU-6050 Accelerometer: ====<br /> <br /> https://www.sparkfun.com/products/11028<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> Works with i2ctools, from userspace.<br /> <br /> <br /> '''See The Sample Script Below.'''<br /> <br /> #!/bin/bash<br /> <br /> # Device I2C Bus Addresses<br /> MPU6050_0=0X68<br /> MPU6050_1=0X69<br /> <br /> # Initialization Register Address.<br /> PWR_MGMT_1=0x6b<br /> <br /> # Initialize Device, Select Z Axis As Clock Signal. (Register Map, p.41)<br /> INIT_SEL_Z_CLOCK=0x02<br /> i2cset -y 3 $MPU6050_0 $PWR_MGMT_1 $INIT_SEL_Z_CLOCK b<br /> i2cset -y 3 $MPU6050_1 $PWR_MGMT_1 $INIT_SEL_Z_CLOCK b<br /> <br /> # Set Max Resolution on Accelerometer and Gyro:<br /> i2cset -y 3 0x68 0x1c 0x18 b<br /> i2cset -y 3 0x69 0x1b 0x18 b<br /> <br /> # Read Bus:<br /> i2cdetect -y -r 3<br /> <br /> <br /> # Read Accelerometer 1:<br /> echo &quot;ACCEL_XOUT_H=&quot; `i2cget -y 3 $MPU6050_0 0x3b b`<br /> echo &quot;ACCEL_XOUT_L=&quot; `i2cget -y 3 $MPU6050_0 0x3c b`<br /> echo &quot;ACCEL_YOUT_H=&quot; `i2cget -y 3 $MPU6050_0 0x3d b`<br /> echo &quot;ACCEL_YOUT_L=&quot; `i2cget -y 3 $MPU6050_0 0x3e b`<br /> echo &quot;ACCEL_ZOUT_H=&quot; `i2cget -y 3 $MPU6050_0 0x3f b`<br /> echo &quot;ACCEL_ZOUT_L=&quot; `i2cget -y 3 $MPU6050_0 0x40 b`<br /> <br /> # Read Accelerometer 2:<br /> echo &quot;ACCEL_XOUT_H=&quot; `i2cget -y 3 $MPU6050_1 0x3b b`<br /> echo &quot;ACCEL_XOUT_L=&quot; `i2cget -y 3 $MPU6050_1 0x3c b`<br /> echo &quot;ACCEL_YOUT_H=&quot; `i2cget -y 3 $MPU6050_1 0x3d b`<br /> echo &quot;ACCEL_YOUT_L=&quot; `i2cget -y 3 $MPU6050_1 0x3e b`<br /> echo &quot;ACCEL_ZOUT_H=&quot; `i2cget -y 3 $MPU6050_1 0x3f b`<br /> echo &quot;ACCEL_ZOUT_L=&quot; `i2cget -y 3 $MPU6050_1 0x40 b` <br /> <br /> <br /> <br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse the Gumstix GitHub repo. Look under &quot;meta-gumstix&quot;, and &quot;linux&quot;.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6083 2014-05-09T01:17:25Z

<p>BallCam: </p> <hr /> <div>== 20 April 2014 ==<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working with kernels 2.6.34, and 3.5.7-yocto-standard.<br /> <br /> P54 USB and rt2800usb WiFi devices work in Host Mode with hostapd. WiFi generally works in non-host mode for several devices, including libertas.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> <br /> === Prerequisites ===<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can these from Gumstix web resources, or from the NAND of the device you purchase. <br /> <br /> It is assumed that you have experience using Slackware, on some other architecture.<br /> <br /> Software will need to be installed using &quot;configure&quot; and &quot;make&quot;, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> <br /> <br /> === Basic Installation Strategy: ===<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> <br /> '''Notes:'''<br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can &quot;cross-install&quot; that is, use an x86 based PC to run &quot;installpkg to install Slackware ARM packages to an SD card to be used as the rootfs of your device for '''most''' but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do &quot;cross-install&quot; successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using &quot;installpkg&quot;. It works fine. &quot;pkgtool&quot; also works, but may not work when using the miniroot unless a few more packages from the &quot;a&quot; series are installed. <br /> <br /> <br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. '''GCC''' and '''Make''' work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> <br /> <br /> === Building Your Own Kernel ===<br /> <br /> ==== Linux 3.5.x Kernel ====<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> <br /> <br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo:<br /> <br /> Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> <br /> <br /> ==== Linux 2.6.x Kernel ====<br /> <br /> The instructions for building a 2.6 series kernel for Gumstix can be found here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> Those instructions can be applied to kernel source obtained from Kernel.org, or Gumstix Resources.<br /> <br /> The main reason to build a 2.6 kernel is for use with Slackware ARM 13.37, and to take advantage of the<br /> kernel from Gumstix above that can be used with the Caspa. <br /> <br /> However, Since Slackware ARM 13.37 is now end of life, the focus in these wiki pages will be on Slackware ARM 14.1.<br /> <br /> <br /> <br /> === Installing Slackware ARM Packages On Overo ===<br /> <br /> Once you have a bootable system, you can use &quot;installpkg&quot;, &quot;removepkg&quot; and &quot;pkgtool&quot; to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the &quot;a&quot; series installed. You can manually install the rest.<br /> <br /> Packages from the &quot;a&quot;, &quot;ap&quot;, &quot;d&quot;, &quot;l&quot;, &quot;n&quot; and &quot;x&quot; sets need to be installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This How To will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone with KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with &quot;removepkg&quot; or &quot;pkgtool&quot; then install from the source to get the particular version you like.<br /> <br /> <br /> <br /> === Devices Tested So Far ===<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware:<br /> <br /> ==== Caspa Camera Unit / MT9V032 Sensor and Kernel Driver ====<br /> <br /> <br /> ===== Using Caspa With 2.6.34 Kernel =====<br /> <br /> Start with the Gumstix User Wiki page for the Caspa, here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, follow<br /> the instructions in the Wiki Page above.<br /> <br /> <br /> ===== Using Caspa With 3.5.x Kernel =====<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from Gumstix, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work.<br /> <br /> Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its &quot;Pixel Format&quot;, or &quot;Color Space&quot; will be what is referred to as &quot;UYVY&quot;.<br /> <br /> The instructions for using &quot;yavta&quot; also work. &quot;yavta&quot; is simply: &quot;Yet Another Video4linux Test Application&quot;.<br /> <br /> Yavta will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the &quot;-pix_fmt&quot; option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the &quot;DISPLAY&quot; option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the &quot;LD_PRELOAD&quot; environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> <br /> <br /> ==== P54USB WiFi ====<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only, works in 2.6, and 3.5 series kernels.<br /> <br /> Use this search page for devices that use the Prism 54 USB WiFi Driver<br /> <br /> http://wireless.kernel.org/en/users/Devices/USB<br /> <br /> Make sure that you have the firmware, though it is usually included<br /> in the kernel source.<br /> <br /> Make sure that the USB device that you buy is BOTH the correct<br /> Model Number, AND Revision. Manufacturers change their chipsets <br /> between revisions.<br /> <br /> <br /> ==== WRL-11713 PCDuino WiFi Dongle ====<br /> <br /> From SparkFun.com – rt2800usb Works With HostAPD on Overo. Tested with kernel 3.5.7-yocto-standard.<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> The command:<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id <br /> <br /> Must be used to bring up the interface. <br /> <br /> Make sure to get the firmware from the [http://www.mediatek.com/en/downloads MediaTek / Ralink] website.<br /> <br /> Tested with 5 Volts and 3.3 Volts.<br /> <br /> <br /> ==== LIS-331 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/10345 <br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> Works with i2ctools, from userspace.<br /> <br /> <br /> ==== MPU-6050 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/11028<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> Works with i2ctools, from userspace.<br /> <br /> #!/bin/bash<br /> <br /> # Device I2C Bus Addresses<br /> MPU6050_0=0X68<br /> MPU6050_1=0X69<br /> <br /> # Initialization Register Address.<br /> PWR_MGMT_1=0x6b<br /> <br /> # Initialize Device, Select Z Axis As Clock Signal. (Register Map, p.41)<br /> INIT_SEL_Z_CLOCK=0x02<br /> i2cset -y 3 $MPU6050_0 $PWR_MGMT_1 $INIT_SEL_Z_CLOCK b<br /> i2cset -y 3 $MPU6050_1 $PWR_MGMT_1 $INIT_SEL_Z_CLOCK b<br /> <br /> # Set Max Resolution on Accelerometer and Gyro:<br /> i2cset -y 3 0x68 0x1c 0x18 b<br /> i2cset -y 3 0x69 0x1b 0x18 b<br /> <br /> # Read Bus:<br /> i2cdetect -y -r 3<br /> <br /> <br /> # Read Accelerometer 1:<br /> echo &quot;ACCEL_XOUT_H=&quot; `i2cget -y 3 $MPU6050_0 0x3b b`<br /> echo &quot;ACCEL_XOUT_L=&quot; `i2cget -y 3 $MPU6050_0 0x3c b`<br /> echo &quot;ACCEL_YOUT_H=&quot; `i2cget -y 3 $MPU6050_0 0x3d b`<br /> echo &quot;ACCEL_YOUT_L=&quot; `i2cget -y 3 $MPU6050_0 0x3e b`<br /> echo &quot;ACCEL_ZOUT_H=&quot; `i2cget -y 3 $MPU6050_0 0x3f b`<br /> echo &quot;ACCEL_ZOUT_L=&quot; `i2cget -y 3 $MPU6050_0 0x40 b`<br /> <br /> # Read Accelerometer 2:<br /> echo &quot;ACCEL_XOUT_H=&quot; `i2cget -y 3 $MPU6050_1 0x3b b`<br /> echo &quot;ACCEL_XOUT_L=&quot; `i2cget -y 3 $MPU6050_1 0x3c b`<br /> echo &quot;ACCEL_YOUT_H=&quot; `i2cget -y 3 $MPU6050_1 0x3d b`<br /> echo &quot;ACCEL_YOUT_L=&quot; `i2cget -y 3 $MPU6050_1 0x3e b`<br /> echo &quot;ACCEL_ZOUT_H=&quot; `i2cget -y 3 $MPU6050_1 0x3f b`<br /> echo &quot;ACCEL_ZOUT_L=&quot; `i2cget -y 3 $MPU6050_1 0x40 b` <br /> <br /> <br /> <br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse the Gumstix GitHub repo. Look under &quot;meta-gumstix&quot;, and &quot;linux&quot;.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6082 2014-05-09T01:05:54Z

<p>BallCam: /* Using Caspa With 2.6.34 Kernel */</p> <hr /> <div>== 20 April 2014 ==<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working with kernels 2.6.34, and 3.5.7-yocto-standard.<br /> <br /> P54 USB and rt2800usb WiFi devices work in Host Mode with hostapd. WiFi generally works in non-host mode for several devices, including libertas.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> <br /> === Prerequisites ===<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can these from Gumstix web resources, or from the NAND of the device you purchase. <br /> <br /> It is assumed that you have experience using Slackware, on some other architecture.<br /> <br /> Software will need to be installed using &quot;configure&quot; and &quot;make&quot;, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> <br /> <br /> === Basic Installation Strategy: ===<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> <br /> '''Notes:'''<br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can &quot;cross-install&quot; that is, use an x86 based PC to run &quot;installpkg to install Slackware ARM packages to an SD card to be used as the rootfs of your device for '''most''' but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do &quot;cross-install&quot; successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using &quot;installpkg&quot;. It works fine. &quot;pkgtool&quot; also works, but may not work when using the miniroot unless a few more packages from the &quot;a&quot; series are installed. <br /> <br /> <br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. '''GCC''' and '''Make''' work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> <br /> <br /> === Building Your Own Kernel ===<br /> <br /> ==== Linux 3.5.x Kernel ====<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> <br /> <br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo:<br /> <br /> Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> <br /> <br /> ==== Linux 2.6.x Kernel ====<br /> <br /> The instructions for building a 2.6 series kernel for Gumstix can be found here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> Those instructions can be applied to kernel source obtained from Kernel.org, or Gumstix Resources.<br /> <br /> The main reason to build a 2.6 kernel is for use with Slackware ARM 13.37, and to take advantage of the<br /> kernel from Gumstix above that can be used with the Caspa. <br /> <br /> However, Since Slackware ARM 13.37 is now end of life, the focus in these wiki pages will be on Slackware ARM 14.1.<br /> <br /> === Installing Slackware ARM Packages On Overo ===<br /> <br /> Once you have a bootable system, you can use &quot;installpkg&quot;, &quot;removepkg&quot; and &quot;pkgtool&quot; to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the &quot;a&quot; series installed. You can manually install the rest.<br /> <br /> Packages from the &quot;a&quot;, &quot;ap&quot;, &quot;d&quot;, &quot;l&quot;, &quot;n&quot; and &quot;x&quot; sets need to be installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This How To will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone with KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with &quot;removepkg&quot; or &quot;pkgtool&quot; then install from the source to get the particular version you like.<br /> <br /> <br /> === Devices Tested So Far ===<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware:<br /> <br /> ==== Caspa Camera Unit / MT9V032 Sensor and Kernel Driver ====<br /> <br /> ===== Using Caspa With 2.6.34 Kernel =====<br /> <br /> Start with the Gumstix User Wiki page for the Caspa, here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, follow<br /> the instructions in the Wiki Page above.<br /> <br /> ===== Using Caspa With 3.5.x Kernel =====<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from Gumstix, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work.<br /> <br /> Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its &quot;Pixel Format&quot;, or &quot;Color Space&quot; will be what is referred to as &quot;UYVY&quot;.<br /> <br /> The instructions for using &quot;yavta&quot; also work. &quot;yavta&quot; is simply: &quot;Yet Another Video4linux Test Application&quot;.<br /> <br /> Yavta will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the &quot;-pix_fmt&quot; option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the &quot;DISPLAY&quot; option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the &quot;LD_PRELOAD&quot; environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> <br /> <br /> ==== P54USB WiFi ====<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only.<br /> <br /> Use this search page for devices that use the Prism 54 USB WiFi Driver<br /> <br /> http://wireless.kernel.org/en/users/Devices/USB<br /> <br /> Make sure that you have the firmware, though it is usually included<br /> in the kernel source.<br /> <br /> Make sure that the USB device that you buy is BOTH the correct<br /> Model Number, AND Revision. Manufacturers change their chipsets <br /> between revisions.<br /> <br /> <br /> ==== WRL-11713 PCDuino WiFi Dongle ====<br /> <br /> From SparkFun.com – rt2800usb Works With HostAPD on Overo<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> This works in Kernel 3.5.x<br /> <br /> The command:<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id <br /> <br /> Must be used to bring up the interface. <br /> <br /> Make sure to get the firmware from the [http://www.mediatek.com/en/downloads MediaTek / Ralink] website.<br /> <br /> Tested with 5 Volts and 3.3 Volts.<br /> <br /> <br /> ==== LIS-331 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/10345 <br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> ==== MPU-6050 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/11028<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse the Gumstix GitHub repo. Look under &quot;meta-gumstix&quot;, and &quot;linux&quot;.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6081 2014-05-09T01:03:39Z

<p>BallCam: /* Linux 2.6.x Kernel */</p> <hr /> <div>== 20 April 2014 ==<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working with kernels 2.6.34, and 3.5.7-yocto-standard.<br /> <br /> P54 USB and rt2800usb WiFi devices work in Host Mode with hostapd. WiFi generally works in non-host mode for several devices, including libertas.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> <br /> === Prerequisites ===<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can these from Gumstix web resources, or from the NAND of the device you purchase. <br /> <br /> It is assumed that you have experience using Slackware, on some other architecture.<br /> <br /> Software will need to be installed using &quot;configure&quot; and &quot;make&quot;, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> <br /> <br /> === Basic Installation Strategy: ===<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> <br /> '''Notes:'''<br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can &quot;cross-install&quot; that is, use an x86 based PC to run &quot;installpkg to install Slackware ARM packages to an SD card to be used as the rootfs of your device for '''most''' but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do &quot;cross-install&quot; successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using &quot;installpkg&quot;. It works fine. &quot;pkgtool&quot; also works, but may not work when using the miniroot unless a few more packages from the &quot;a&quot; series are installed. <br /> <br /> <br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. '''GCC''' and '''Make''' work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> <br /> <br /> === Building Your Own Kernel ===<br /> <br /> ==== Linux 3.5.x Kernel ====<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> <br /> <br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo:<br /> <br /> Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> <br /> <br /> ==== Linux 2.6.x Kernel ====<br /> <br /> The instructions for building a 2.6 series kernel for Gumstix can be found here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> Those instructions can be applied to kernel source obtained from Kernel.org, or Gumstix Resources.<br /> <br /> The main reason to build a 2.6 kernel is for use with Slackware ARM 13.37, and to take advantage of the<br /> kernel from Gumstix above that can be used with the Caspa. <br /> <br /> However, Since Slackware ARM 13.37 is now end of life, the focus in these wiki pages will be on Slackware ARM 14.1.<br /> <br /> === Installing Slackware ARM Packages On Overo ===<br /> <br /> Once you have a bootable system, you can use &quot;installpkg&quot;, &quot;removepkg&quot; and &quot;pkgtool&quot; to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the &quot;a&quot; series installed. You can manually install the rest.<br /> <br /> Packages from the &quot;a&quot;, &quot;ap&quot;, &quot;d&quot;, &quot;l&quot;, &quot;n&quot; and &quot;x&quot; sets need to be installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This How To will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone with KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with &quot;removepkg&quot; or &quot;pkgtool&quot; then install from the source to get the particular version you like.<br /> <br /> <br /> === Devices Tested So Far ===<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware:<br /> <br /> ==== Caspa Camera Unit / MT9V032 Sensor and Kernel Driver ====<br /> <br /> ===== Using Caspa With 2.6.34 Kernel =====<br /> <br /> Start with the Gumstix User Wiki page for the Caspa, here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, the Kernel Source tree has to come from Sakoman.com<br /> <br /> At http://www.Sakoman.com, select “Download” to get to the Git repo.<br /> <br /> Under &quot;projects/&quot;, select linux.git<br /> <br /> Under the &quot;heads&quot; section, click the ellipsis at the bottom of the page to expand the list. Click on &quot;omap3-2.6.34&quot; to browse the source tree.<br /> <br /> This code can be checked out in a manner similar to the Gumstix git repo:<br /> <br /> 1) First clone the “linux.git” repo located at http://www.Sakoman.com/git/<br /> <br /> git clone git://www.Sakoman.com/git/linux.git<br /> <br /> This will create a “linux” directory.<br /> <br /> 2) Then checkout the “omap3-2.6.34” branch, from within the “linux” directory:<br /> <br /> cd linux<br /> git checkout omap3-2.6.34<br /> <br /> You can then apply the patch and defconfig to this source tree to build the kernel per the instructions on the Gumstix Wiki page for the Caspa.<br /> <br /> <br /> ===== Using Caspa With 3.5.x Kernel =====<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from Gumstix, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work.<br /> <br /> Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its &quot;Pixel Format&quot;, or &quot;Color Space&quot; will be what is referred to as &quot;UYVY&quot;.<br /> <br /> The instructions for using &quot;yavta&quot; also work. &quot;yavta&quot; is simply: &quot;Yet Another Video4linux Test Application&quot;.<br /> <br /> Yavta will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the &quot;-pix_fmt&quot; option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the &quot;DISPLAY&quot; option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the &quot;LD_PRELOAD&quot; environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> <br /> <br /> ==== P54USB WiFi ====<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only.<br /> <br /> Use this search page for devices that use the Prism 54 USB WiFi Driver<br /> <br /> http://wireless.kernel.org/en/users/Devices/USB<br /> <br /> Make sure that you have the firmware, though it is usually included<br /> in the kernel source.<br /> <br /> Make sure that the USB device that you buy is BOTH the correct<br /> Model Number, AND Revision. Manufacturers change their chipsets <br /> between revisions.<br /> <br /> <br /> ==== WRL-11713 PCDuino WiFi Dongle ====<br /> <br /> From SparkFun.com – rt2800usb Works With HostAPD on Overo<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> This works in Kernel 3.5.x<br /> <br /> The command:<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id <br /> <br /> Must be used to bring up the interface. <br /> <br /> Make sure to get the firmware from the [http://www.mediatek.com/en/downloads MediaTek / Ralink] website.<br /> <br /> Tested with 5 Volts and 3.3 Volts.<br /> <br /> <br /> ==== LIS-331 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/10345 <br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> ==== MPU-6050 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/11028<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse the Gumstix GitHub repo. Look under &quot;meta-gumstix&quot;, and &quot;linux&quot;.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6080 2014-05-09T01:00:07Z

<p>BallCam: </p> <hr /> <div>== 20 April 2014 ==<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working with kernels 2.6.34, and 3.5.7-yocto-standard.<br /> <br /> P54 USB and rt2800usb WiFi devices work in Host Mode with hostapd. WiFi generally works in non-host mode for several devices, including libertas.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> <br /> === Prerequisites ===<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can these from Gumstix web resources, or from the NAND of the device you purchase. <br /> <br /> It is assumed that you have experience using Slackware, on some other architecture.<br /> <br /> Software will need to be installed using &quot;configure&quot; and &quot;make&quot;, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> <br /> <br /> === Basic Installation Strategy: ===<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> <br /> '''Notes:'''<br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can &quot;cross-install&quot; that is, use an x86 based PC to run &quot;installpkg to install Slackware ARM packages to an SD card to be used as the rootfs of your device for '''most''' but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do &quot;cross-install&quot; successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using &quot;installpkg&quot;. It works fine. &quot;pkgtool&quot; also works, but may not work when using the miniroot unless a few more packages from the &quot;a&quot; series are installed. <br /> <br /> <br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. '''GCC''' and '''Make''' work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> <br /> <br /> === Building Your Own Kernel ===<br /> <br /> ==== Linux 3.5.x Kernel ====<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> <br /> <br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo:<br /> <br /> Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> <br /> <br /> ==== Linux 2.6.x Kernel ====<br /> <br /> The instructions for building a 2.6 series kernel for Gumstix can be found here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> Those instructions can be applied to kernel source obtained from Kernel.org, or Gumstix Resources.<br /> <br /> The main reason to build a 2.6 kernel is for Slackware ARM 13.37. However, Since Slackware ARM 13.37 is now end of life, <br /> the focus in these wiki pages will be on Slackware ARM 14.1.<br /> <br /> <br /> <br /> === Installing Slackware ARM Packages On Overo ===<br /> <br /> Once you have a bootable system, you can use &quot;installpkg&quot;, &quot;removepkg&quot; and &quot;pkgtool&quot; to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the &quot;a&quot; series installed. You can manually install the rest.<br /> <br /> Packages from the &quot;a&quot;, &quot;ap&quot;, &quot;d&quot;, &quot;l&quot;, &quot;n&quot; and &quot;x&quot; sets need to be installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This How To will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone with KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with &quot;removepkg&quot; or &quot;pkgtool&quot; then install from the source to get the particular version you like.<br /> <br /> <br /> === Devices Tested So Far ===<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware:<br /> <br /> ==== Caspa Camera Unit / MT9V032 Sensor and Kernel Driver ====<br /> <br /> ===== Using Caspa With 2.6.34 Kernel =====<br /> <br /> Start with the Gumstix User Wiki page for the Caspa, here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, the Kernel Source tree has to come from Sakoman.com<br /> <br /> At http://www.Sakoman.com, select “Download” to get to the Git repo.<br /> <br /> Under &quot;projects/&quot;, select linux.git<br /> <br /> Under the &quot;heads&quot; section, click the ellipsis at the bottom of the page to expand the list. Click on &quot;omap3-2.6.34&quot; to browse the source tree.<br /> <br /> This code can be checked out in a manner similar to the Gumstix git repo:<br /> <br /> 1) First clone the “linux.git” repo located at http://www.Sakoman.com/git/<br /> <br /> git clone git://www.Sakoman.com/git/linux.git<br /> <br /> This will create a “linux” directory.<br /> <br /> 2) Then checkout the “omap3-2.6.34” branch, from within the “linux” directory:<br /> <br /> cd linux<br /> git checkout omap3-2.6.34<br /> <br /> You can then apply the patch and defconfig to this source tree to build the kernel per the instructions on the Gumstix Wiki page for the Caspa.<br /> <br /> <br /> ===== Using Caspa With 3.5.x Kernel =====<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from Gumstix, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work.<br /> <br /> Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its &quot;Pixel Format&quot;, or &quot;Color Space&quot; will be what is referred to as &quot;UYVY&quot;.<br /> <br /> The instructions for using &quot;yavta&quot; also work. &quot;yavta&quot; is simply: &quot;Yet Another Video4linux Test Application&quot;.<br /> <br /> Yavta will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the &quot;-pix_fmt&quot; option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the &quot;DISPLAY&quot; option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the &quot;LD_PRELOAD&quot; environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> <br /> <br /> ==== P54USB WiFi ====<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only.<br /> <br /> Use this search page for devices that use the Prism 54 USB WiFi Driver<br /> <br /> http://wireless.kernel.org/en/users/Devices/USB<br /> <br /> Make sure that you have the firmware, though it is usually included<br /> in the kernel source.<br /> <br /> Make sure that the USB device that you buy is BOTH the correct<br /> Model Number, AND Revision. Manufacturers change their chipsets <br /> between revisions.<br /> <br /> <br /> ==== WRL-11713 PCDuino WiFi Dongle ====<br /> <br /> From SparkFun.com – rt2800usb Works With HostAPD on Overo<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> This works in Kernel 3.5.x<br /> <br /> The command:<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id <br /> <br /> Must be used to bring up the interface. <br /> <br /> Make sure to get the firmware from the [http://www.mediatek.com/en/downloads MediaTek / Ralink] website.<br /> <br /> Tested with 5 Volts and 3.3 Volts.<br /> <br /> <br /> ==== LIS-331 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/10345 <br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> ==== MPU-6050 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/11028<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse the Gumstix GitHub repo. Look under &quot;meta-gumstix&quot;, and &quot;linux&quot;.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_14.1_On_Gumstix_Overo&diff=6076 2014-04-24T05:05:24Z

<p>BallCam: </p> <hr /> <div>=== 20 April 2014 ===<br /> <br /> Slackware 14.1 has been installed on Gumstix Overo Devices and used succesfully with their expansion boards, with a 3.5 series kernel, built with Yocto, and BitBake.<br /> <br /> Slackware packages install, and software built with &quot;configure&quot; and &quot;make&quot; also install and run.<br /> <br /> GUI Has not yet been tested. In Progress.<br /> <br /> The majority of focus will be placed on Installing, Running, and Developing Slackware 14.1 on Gumstix as Slackware 13.37 is End Of Life, and the 3.5.x Kernels built with Yocto, and provided by Gumstix support enough devices.<br /> <br /> <br /> === Prerequisites ===<br /> <br /> <br /> SD Card:<br /> Setup and Format per Gumstix Instructions.<br /> <br /> Very Important: Use the fastest SD card media you can afford. &quot;UHS Speed Class 1&quot; or &quot;Speed Class 10&quot;, minimum.<br /> Also consider using the ext4 filesystem, BUT, you will have to rebuild the kernel for that.<br /> <br /> If you go cheap on the SD Cards, like &quot;Speed Class 4&quot;, you will notice the difference. The kernel caches writes<br /> to the SD Card, and finishes them as it can. This is why it is always important to use the &quot;sync&quot; command when <br /> copying data to the SD Card. If you are trying to do any kind of video capture application, the SD card has to <br /> be fast enough to handle HD video capture. <br /> <br /> '''u-boot:'''<br /> setenv console ttyO2,115200n<br /> setenv mmcroot<br /> setenv mmcrootfstype <br /> <br /> '''kernel:'''<br /> a) Use Kernel and modules from device NAND, (They can be copied over the network, for example if an Overo<br /> is booted in a Tobi), or;<br /> b) Use Yocto and Bitbake to build a kernel, or;<br /> c) Use a pre-built image. <br /> <br /> Generally it is best to get the latest you can. The kernel used in this How To is: 3.5.7-yocto-standard<br /> <br /> '''modules:'''<br /> Don't forget the modules, however you get your kernel.<br /> <br /> '''firmware:'''<br /> You may need firmware for whateber USB WiFi device you are using.<br /> <br /> '''/etc/rc.d/ directory:'''<br /> <br /> '''/etc/rc.d/rc.M'''<br /> <br /> '''/etc/rc.d/rc.ntpd'''<br /> add the command:<br /> ntpdate -b &lt;your time server&gt; above the line<br /> that saves the kernel time to hardware, so that your system is always on time.<br /> <br /> '''/etc/inittab'''<br /> make sure the line for your login console is like so, to login to using the<br /> usb console interface (Tobi, Janus, Gallop)<br /> <br /> c1:12345:respawn:/sbin/agetty --noclear 38400 tty1 linux<br /> <br /> <br /> '''/etc/mtab'''<br /> <br /> /dev/mmcblk0p2 / ext4 rw,sync 0 0<br /> <br /> <br /> Copy Slackware ARM packages to SD Card<br /> <br /> <br /> To control module loading order, say for example, to load the camera and wifi modules last, blacklist the modules and load them in your own scripts or via /etc/rc.d/rc.local. <br /> <br /> <br /> <br /> ==== Using The Caspa / MT9V032 Sensor With Slackware 14.1 On Gumstix Overo ====<br /> <br /> Make sure to use a 3.5 series kernel built with Yocto and Bitbake per Gumstix' instructions. At least 3.5.7. When purchasing your device you may be able to request they flash the NAND with an appropriate kernel.<br /> <br /> ===== Prerequisites =====<br /> <br /> '''media-ctl''' -- Necessary to set sensor paramters.<br /> <br /> '''yavta''' &quot;Yet Another Video4Linux Test Application&quot; -- Implements Simple Image Capture Functions<br /> <br /> '''ffmpeg''' -- to &quot;transcode&quot; &quot;raw&quot; images captured by yavta, into other image or video formats.<br /> <br /> <br /> ==== Using The P54USB WiFi With Slackware 14.1 On Gumstix Overo ====<br /> <br /> This may be enabled by default in a Yocto kernel. It supports Host AP mode. Needs 5 Volts.<br /> <br /> <br /> ==== Using The rt2800usb USB WiFi With Slackware 14.1 On Gumstix Overo ====<br /> <br /> This likewise may be built in by default in a Yocto kernel. Works at both 3.3 and 5 volts.<br /> <br /> <br /> ==== Using The LIS331 3-Axis Accelerometer With Slackware 14.1 On Gumstix Overo ====<br /> <br /> This is an I2C device. Level Shifters may be needed on the SDA and SCL lines when your system voltage is above 3.3 Volts.<br /> <br /> <br /> ==== Using The MPU-6050 3-Axis Accelerometer With Slackware 14.1 On Gumstix Overo ====<br /> <br /> This is an I2C device. Level Shifters may be needed on the SDA and SCL lines when your system voltage is above 3.3 Volts.<br /> <br /> [http://invensense.com/mems/gyro/documents/RM-MPU-6000A.pdf MPU-6050 Register Map]</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_13.37_On_Gumstix_Overo&diff=6075 2014-04-24T04:34:05Z

<p>BallCam: </p> <hr /> <div>== Slackware 13.37 On Gumstix Overo ==<br /> <br /> Slackware ARM 13.37 Is now End Of Life but there may be some interest<br /> in installing it because the 2.6 series kernel is long term stable,<br /> and because the Caspa unit works with linux 2.6.34 from Sakoman.com<br /> <br /> The focus of the Slackware on Gumstix Overo series of Howtos will be on Slackware 14.1 and later.<br /> <br /> SD Card: <br /> <br /> Setup and Format per Gumstix Instructions.<br /> <br /> '''VERY IMPORTANT:''' Use the fastest SD card media you can afford. &quot;UHS Speed Class 1&quot; or &quot;Speed Class 10&quot;, minimum.<br /> <br /> Also consider using the ext4 filesystem, BUT, you will have to rebuild the kernel for that.<br /> <br /> If you go cheap on the SD Cards, like &quot;Speed Class 4&quot;, you will notice the difference. The kernel caches writes to the SD Card, and finishes them as it can. This is why it is always important to use the &quot;sync&quot; command when copying data to the SD Card. If you are trying to do any kind of video capture application, the SD card has to be fast enough to handle HD video capture. <br /> <br /> <br /> '''u-boot:'''<br /> setenv console ttyS2,115200n -- Must Match setting in /etc/inittab Shown below.<br /> setenv mmcroot /dev/mmcblk0p2 ro -- Mount read only. /etc/rc.d/rc.M will re-mount read-write.<br /> setenv mmcrootfstype ext3 rootwait -- Default File System Type, or;<br /> setenv mmcrootfstype ext4 rootwait -- For use with ext4, BUT requires Kernel Rebuild. Must match /etc/mtab<br /> saveenv -- Save the settings.<br /> <br /> <br /> '''Kernel and Modules:'''<br /> <br /> Try Using the kernel and modules obtained from here,<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> or built per the instructions there, or use a 2.6 series kernel<br /> and modules from an Overo NAND.<br /> <br /> '''/etc/rc.d/ directory:'''<br /> <br /> '''/etc/rc.d/rc.M'''<br /> <br /> '''/etc/rc.d/rc.ntpd'''<br /> <br /> '''/etc/inittab'''<br /> <br /> # Local serial lines:<br /> s0:12345:respawn:/sbin/agetty 115200 ttyO2 ansi<br /> <br /> Must match u-boot console setting. Match terminal type, (last argument)<br /> to your terminal program. Try &quot;ansi&quot; for use with minicom.<br /> <br /> '''/etc/mtab'''<br /> <br /> /dev/mmcblk0p2 / ext4 rw,sync 0 0 -- For use with ext4, or;<br /> <br /> /dev/mmcblk0p2 / ext3 rw,sync 0 0 -- For use with ext3<br /> <br /> These settings must match the mmcrootfstype setting in u-boot.<br /> <br /> <br /> Copy Slackware ARM packages to SD Card<br /> <br /> Uninstall SSHD, OpenSSL... reinstall from source.<br /> <br /> To control module loading order, say for example, to load the<br /> camera and wifi modules last, blacklist the modules and load them<br /> in your own scripts or via /etc/rc.d/rc.local.</div>

BallCam https://wiki.gumstix.com/index.php?title=HostAPD_WiFi_Access_Point_On_Gumstix_Overo&diff=6073 2014-04-22T00:52:57Z

<p>BallCam: </p> <hr /> <div>== HostAPD WiFi Access Point On Gumstix Overo ==<br /> <br /> The Following USB WiFi devices have been used successfully with HostAPD<br /> as A WiFi Access Point using Gumstix Overo:<br /> <br /> Use This Search Page to determine which model numbers and revisions can be used<br /> with Overo.<br /> <br /> http://wireless.kernel.org/en/users/Devices/USB<br /> <br /> Both Model Number and Revision are important. Manufacturers change chipsets between revisions.<br /> <br /> Make sure to get the correct firmware, from the manufacturer, or driver developer site, if<br /> it is not already in kernel source.<br /> <br /> <br /> P54USB<br /> Tested with:<br /> <br /> DLink DWL-G122 (REV A2) -- On-Board Antenna<br /> <br /> Linksys WUSB54G Portable -- External Antenna<br /> <br /> <br /> rt2800usb<br /> Tested with WRL-11713<br /> https://www.sparkfun.com/products/11713<br /> Firmware is on Ralink website.<br /> <br /> The following Device supports hostapd by design, but has not<br /> yet been validated on Gumstix Overo:<br /> <br /> SD8787 / W2CBW0015<br /> <br /> Uses mwifiex driver<br /> <br /> This is the driver for the SD8787 / W2CBW0015 chip which is the replacement for the,<br /> SD8686 / W2CBW003 which is now EOL from the manufacturer. The SD8787 is currently used on Duovero.<br /> <br /> <br /> The following device uses a manufacturer-provided Access Point Application:<br /> <br /> SD8686 / W2CBW003 <br /> <br /> The SD8686 / W2CBW003 chip does work as an access point, BUT you must obtain the<br /> firmware and reference driver from Wi2Wi. It only works up to kernel 2.6.29 without<br /> modifying the driver to use the newer net_dev_ops API. (Which has not been done). <br /> Wi2Wi requires an NDA to download the driver.<br /> <br /> The W2CBW003 chip is now end of life from the manufacturer.</div>

BallCam https://wiki.gumstix.com/index.php?title=HostAPD_WiFi_Access_Point_On_Gumstix_Overo&diff=6072 2014-04-22T00:41:20Z

<p>BallCam: </p> <hr /> <div>The Following USB WiFi devices have been used successfully with HostAPD<br /> as A WiFi Access Point using Gumstix Overo:<br /> <br /> Use This Search Page to determine which model numbers and revisions can be used<br /> with Overo.<br /> <br /> http://wireless.kernel.org/en/users/Devices/USB<br /> <br /> Both Model Number and Revision are important. Manufacturers change chipsets between revisions.<br /> <br /> <br /> <br /> P54USB<br /> Tested with D-Link and Linksys.<br /> 5 Volts Only, needs hub or supplemental power.<br /> <br /> <br /> rt2800usb<br /> Tested with WRL-11713 <br /> <br /> <br /> The following Device supports hostapd by design, but has not<br /> yet been validated on Gumstix Overo:<br /> <br /> SD8787 / W2CBW0015<br /> <br /> uses mwifiex driver<br /> <br /> This is the driver for the SD8787 / W2CBW0015 chip which is the replacement for the,<br /> SD8686 / W2CBW003 which is now EOL from the manufacturer.<br /> <br /> <br /> The following device uses a manufacturer-provided Access Point Application:<br /> <br /> SD8686 / W2CBW003 <br /> <br /> The SD8686 / W2CBW003 chip does work as an access point, BUT you must obtain the<br /> firmware and reference driver from Wi2Wi. It only works up to kernel 2.6.29 without<br /> modifying the driver to use the newer net_dev_ops API. (Which has not been done). <br /> Wi2Wi requires an NDA to download the driver.<br /> <br /> The W2CBW003 chip is now end of life from the manufacturer.</div>

BallCam https://wiki.gumstix.com/index.php?title=HostAPD_WiFi_Access_Point_On_Gumstix_Overo&diff=6071 2014-04-22T00:25:11Z

<p>BallCam: Created page with &quot;The Following USB WiFi devices have been used successfully with HostAPD as A WiFi Access Point using Gumstix Overo: P54 USB rt2800usb The following Device supports hostapd by...&quot;</p> <hr /> <div>The Following USB WiFi devices have been used successfully with HostAPD<br /> as A WiFi Access Point using Gumstix Overo:<br /> <br /> P54 USB<br /> <br /> rt2800usb<br /> <br /> <br /> The following Device supports hostapd by design, but has not<br /> yet been validated on Gumstix Overo<br /> <br /> mwifiex <br /> This is the driver for the ___ which is the replacement for the W2CBW003 which is now <br /> EOL from the manufacturer.<br /> <br /> <br /> The following device uses a manufacturer provided Access Point Application:<br /> <br /> libertas<br /> <br /> The libertas W2CBW003 chip does work as an access point, BUT you must obtain the<br /> firmware and reference driver from Wi2Wi. It only works up to kernel 2.6.29 without<br /> modifying the driver to use the newer net_dev_ops API. (Which has not been done). <br /> Wi2Wi requires an NDA to download the driver.<br /> <br /> The libertas chip is now end of life from the manufacturer.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_13.37_On_Gumstix_Overo&diff=6070 2014-04-22T00:09:56Z

<p>BallCam: </p> <hr /> <div>== Slackware 13.37 On Gumstix Overo ==<br /> <br /> Slackware ARM 13.37 Is now End Of Life but there may be some interest<br /> in installing it because the 2.6 series kernel is long term stable,<br /> and because the Caspa unit works with linux 2.6.34 from Sakoman.com<br /> <br /> The focus of the Slackware on Gumstix Overo series of Howtos will be on Slackware 14.1 and later.<br /> <br /> SD Card: <br /> <br /> Setup and Format per Gumstix Instructions.<br /> <br /> '''VERY IMPORTANT:''' Use the fastest SD card media you can afford. &quot;UHS Speed Class 1&quot; or &quot;Speed Class 10&quot;, minimum.<br /> <br /> Also consider using the ext4 filesystem, BUT, you will have to rebuild the kernel for that.<br /> <br /> If you go cheap on the SD Cards, like &quot;Speed Class 4&quot;, you will notice the difference. The kernel caches writes to the SD Card, and finishes them as it can. This is why it is always important to use the &quot;sync&quot; command when copying data to the SD Card. If you are trying to do any kind of video capture application, the SD card has to be fast enough to handle HD video capture. <br /> <br /> <br /> u-boot: <br /> setenv console ttyS2,115200n -- Must Match setting in /etc/inittab Shown below.<br /> setenv mmcroot /dev/mmcblk0p2 ro -- Mount read only. /etc/rc.d/rc.M will re-mount read-write.<br /> setenv mmcrootfstype ext3 rootwait -- Default File System Type, or;<br /> setenv mmcrootfstype ext4 rootwait -- For use with ext4, BUT requires Kernel Rebuild. Must match /etc/mtab<br /> saveenv -- Save the settings.<br /> <br /> <br /> Kernel and Modules:<br /> <br /> Try Using the kernel and modules obtained from here,<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> or built per the instructions there, or use a 2.6 series kernel<br /> and modules from an Overo NAND.<br /> <br /> /etc/rc.d/ directory changes:<br /> <br /> /etc/rc.d/rc.M<br /> <br /> /etc/rc.d/rc.ntpd<br /> <br /> /etc/inittab<br /> <br /> # Local serial lines:<br /> s0:12345:respawn:/sbin/agetty 115200 ttyO2 ansi<br /> <br /> Must match u-boot console setting. Match terminal type, (last argument)<br /> to your terminal program. Try &quot;ansi&quot; for use with minicom.<br /> <br /> /etc/mtab<br /> <br /> /dev/mmcblk0p2 / ext4 rw,sync 0 0 -- For use with ext4, or;<br /> <br /> /dev/mmcblk0p2 / ext3 rw,sync 0 0 -- For use with ext3<br /> <br /> These settings must match the mmcrootfstype setting in u-boot.<br /> <br /> <br /> Copy Slackware ARM packages to SD Card<br /> <br /> Uninstall SSHD, OpenSSL... reinstall from source.<br /> <br /> To control module loading order, say for example, to load the<br /> camera and wifi modules last, blacklist the modules and load them<br /> in your own scripts or via /etc/rc.d/rc.local.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_13.37_On_Gumstix_Overo&diff=6069 2014-04-21T23:25:06Z

<p>BallCam: </p> <hr /> <div>== Slackware 13.37 On Gumstix Overo ==<br /> <br /> Slackware ARM 13.37 Is now End Of Life but there may be some interest<br /> in installing it because the 2.6 series kernel is long term stable,<br /> and because the Caspa unit works with linux 2.6.34 from Sakoman.com<br /> <br /> The focus of the Slackware on Gumstix Overo series of Howtos will be on Slackware 14.1 and later.<br /> <br /> SD Card: Setup and Format per Gumstix Instructions.<br /> <br /> Very Important: Use the fastest SD card media you can afford. &quot;UHS Speed Class 1&quot; or &quot;Speed Class 10&quot;, minimum. <br /> <br /> Also consider using the ext4 filesystem, BUT, you will have to rebuild the kernel for that.<br /> <br /> If you go cheap on the SD Cards, like &quot;Speed Class 4&quot;, you will notice the difference. The kernel caches writes to the SD Card, and finishes them as it can. This is why it is always important to use the &quot;sync&quot; command when copying data to the SD Card. If you are trying to do any kind of video capture application, the SD card has to be fast enough to handle HD video capture. <br /> <br /> <br /> u-boot: <br /> setenv console ttyS2,115200n -- Must Match setting in /etc/inittab Shown below.<br /> setenv mmcroot -- Mount read only. rc.M will re-mount read-write.<br /> setenv mmcrootfstype <br /> setenv mmcrootfstype <br /> <br /> <br /> Kernel and Modules:<br /> <br /> Try Using the kernel and modules obtained from here,<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> or built per the instructions there, or use a 2.6 series kernel<br /> and modules from an Overo NAND.<br /> <br /> /etc/rc.d/ directory changes:<br /> <br /> /etc/rc.d/rc.M<br /> <br /> /etc/rc.d/rc.ntpd<br /> <br /> /etc/inittab<br /> <br /> # Local serial lines:<br /> s0:12345:respawn:/sbin/agetty 115200 ttyO2 ansi<br /> <br /> Must match u-boot console setting. Match terminal type, (last argument)<br /> to your terminal program. Try &quot;ansi&quot; for use with minicom.<br /> <br /> /etc/mtab<br /> <br /> Copy Slackware ARM packages to SD Card<br /> <br /> Uninstall SSHD, OpenSSL... reinstall from source.<br /> <br /> To control module loading order, say for example, to load the<br /> camera and wifi modules last, blacklist the modules and load them<br /> in your own scripts or via /etc/rc.d/rc.local.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_14.1_On_Gumstix_Overo&diff=6068 2014-04-21T23:05:25Z

<p>BallCam: </p> <hr /> <div>=== 20 April 2014 ===<br /> <br /> Slackware 14.1 has been installed on Gumstix Overo Devices and used succesfully with their expansion boards, with a 3.5 series kernel, built with Yocto, and BitBake.<br /> <br /> Slackware packages install, and software built with &quot;configure&quot; and &quot;make&quot; also install and run.<br /> <br /> GUI Has not yet been tested. In Progress.<br /> <br /> The majority of focus will be placed on Installing, Running, and Developing Slackware 14.1 on Gumstix as Slackware 13.37 is End Of Life, and the 3.5.x Kernels built with Yocto, and provided by Gumstix support enough devices.<br /> <br /> <br /> === Prerequisites ===<br /> <br /> <br /> SD Card:<br /> Setup and Format per Gumstix Instructions.<br /> <br /> Very Important: Use the fastest SD card media you can afford. &quot;UHS Speed Class 1&quot; or &quot;Speed Class 10&quot;, minimum.<br /> Also consider using the ext4 filesystem, BUT, you will have to rebuild the kernel for that.<br /> <br /> If you go cheap on the SD Cards, like &quot;Speed Class 4&quot;, you will notice the difference. The kernel caches writes<br /> to the SD Card, and finishes them as it can. This is why it is always important to use the &quot;sync&quot; command when <br /> copying data to the SD Card. If you are trying to do any kind of video capture application, the SD card has to <br /> be fast enough to handle HD video capture. <br /> <br /> u-boot:<br /> setenv console ttyO2,115200n<br /> setenv mmcroot<br /> setenv mmcrootfstype <br /> <br /> kernel:<br /> a) Use Kernel and modules from device NAND, (They can be copied over the network, for example if an Overo<br /> is booted in a Tobi), or;<br /> b) Use Yocto and Bitbake to build a kernel, or;<br /> c) Use a pre-built image. <br /> <br /> Generally it is best to get the latest you can. The kernel used in this How To is: 3.5.7-yocto-standard<br /> <br /> modules:<br /> Don't forget the modules, however you get your kernel.<br /> <br /> firmware:<br /> You may need firmware for whateber USB WiFi device you are using.<br /> <br /> /etc/rc.d/ directory changes:<br /> <br /> /etc/rc.d/rc.M<br /> <br /> /etc/rc.d/rc.ntpd<br /> add the command:<br /> ntpdate -b &lt;your time server&gt; above the line<br /> that saves the kernel time to hardware, so that your system is always on time.<br /> <br /> /etc/inittab<br /> make sure the line for your login console is like so, to login to using the<br /> usb console interface (Tobi, Janus, Gallop)<br /> <br /> c1:12345:respawn:/sbin/agetty --noclear 38400 tty1 linux<br /> <br /> <br /> /etc/mtab<br /> <br /> /dev/mmcblk0p2 / ext4 rw,sync 0 0<br /> <br /> <br /> Copy Slackware ARM packages to SD Card<br /> <br /> <br /> To control module loading order, say for example, to load the camera and wifi modules last, blacklist the modules and load them in your own scripts or via /etc/rc.d/rc.local. <br /> <br /> <br /> <br /> ==== Using The Caspa / MT9V032 Sensor With Slackware 14.1 On Gumstix Overo ====<br /> <br /> Make sure to use a 3.5 series kernel built with Yocto and Bitbake per Gumstix' instructions. At least 3.5.7. When purchasing your device you may be able to request they flash the NAND with an appropriate kernel.<br /> <br /> ===== Prerequisites =====<br /> <br /> media-ctl tool -- Necessary to set sensor paramters.<br /> <br /> yavta &quot;Yet Another Video4Linux Test Application&quot; -- Implements Simple Image Capture Functions<br /> <br /> ffmpeg -- to &quot;transcode&quot; &quot;raw&quot; images captured by yavta, into other image or video formats.<br /> <br /> <br /> ==== Using The P54USB WiFi With Slackware 14.1 On Gumstix Overo ====<br /> <br /> This may be enabled by default in a Yocto kernel. It supports Host AP mode. Needs 5 Volts.<br /> <br /> <br /> ==== Using The rt2800usb USB WiFi With Slackware 14.1 On Gumstix Overo ====<br /> <br /> This likewise may be built in by default in a Yocto kernel. Works at both 3.3 and 5 volts.<br /> <br /> <br /> ==== Using The LIS331 3-Axis Accelerometer With Slackware 14.1 On Gumstix Overo ====<br /> <br /> This is an I2C device. Level Shifters may be needed on the SDA and SCL lines when your system voltage is above 3.3 Volts.<br /> <br /> <br /> ==== Using The MPU-6050 3-Axis Accelerometer With Slackware 14.1 On Gumstix Overo ====<br /> <br /> This is an I2C device. Level Shifters may be needed on the SDA and SCL lines when your system voltage is above 3.3 Volts.<br /> <br /> [http://invensense.com/mems/gyro/documents/RM-MPU-6000A.pdf MPU-6050 Register Map]</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_13.37_On_Gumstix_Overo&diff=6067 2014-04-21T22:47:07Z

<p>BallCam: </p> <hr /> <div>== Slackware 13.37 On Gumstix Overo ==<br /> <br /> Slackware ARM 13.37 Is now End Of Life but there may be some interest<br /> in installing it because the 2.6 series kernel is long term stable,<br /> and because the Caspa unit works with linux 2.6.34 from Sakoman.com<br /> <br /> The focus of the Slackware on Gumstix Overo series of Howtos will be on Slackware 14.1 and later.<br /> <br /> SD Card:<br /> <br /> u-boot:<br /> <br /> kernel:<br /> <br /> modules: <br /> <br /> /etc/rc.d/ directory changes:<br /> <br /> /etc/rc.d/rc.M<br /> <br /> /etc/rc.d/rc.ntpd<br /> <br /> /etc/inittab<br /> <br /> /etc/mtab<br /> <br /> Copy Slackware ARM packages to SD Card<br /> <br /> Uninstall SSHD, OpenSSL... reinstall from source.<br /> <br /> To control module loading order, say for example, to load the<br /> camera and wifi modules last, blacklist the modules and load them<br /> in your own scripts or via /etc/rc.d/rc.local.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_14.1_On_Gumstix_Overo&diff=6066 2014-04-21T22:46:05Z

<p>BallCam: </p> <hr /> <div>=== 20 April 2014 ===<br /> <br /> Slackware 14.1 has been installed on Gumstix Overo Devices and used succesfully with their expansion boards, with a 3.5 series kernel, built with Yocto, and BitBake.<br /> <br /> Slackware packages install, and software built with &quot;configure&quot; and &quot;make&quot; also install and run.<br /> <br /> GUI Has not yet been tested. In Progress.<br /> <br /> The majority of focus will be placed on Installing, Running, and Developing Slackware 14.1 on Gumstix as Slackware 13.37 is End Of Life, and the 3.5.x Kernels built with Yocto, and provided by Gumstix support enough devices.<br /> <br /> <br /> === Prerequisites ===<br /> <br /> <br /> SD Card:<br /> Setup and Format per Gumstix Instructions.<br /> <br /> Very Important: Use the fastest SD card media you can afford. &quot;UHS Speed Class 1&quot; or &quot;Speed Class 10&quot;, minimum.<br /> Also consider using the ext4 filesystem, BUT, you will have to rebuild the kernel for that.<br /> <br /> If you go cheap on the SD Cards, like &quot;Speed Class 4&quot;, you will notice the difference. The kernel caches writes<br /> to the SD Card, and finishes them as it can. This is why it is always important to use the &quot;sync&quot; command when <br /> copying data to the SD Card. If you are trying to do any kind of video capture application, the SD card has to <br /> be fast enough to handle HD video capture. <br /> <br /> u-boot:<br /> setenv console ttyO2,115200n<br /> setenv mmcroot<br /> setenv mmcrootfstype <br /> <br /> kernel:<br /> a) Use Kernel and modules from device NAND, (They can be copied over the network, for example if an Overo<br /> is booted in a Tobi), or;<br /> b) Use Yocto and Bitbake to build a kernel, or;<br /> c) Use a pre-built image. <br /> <br /> Generally it is best to get the latest you can. The kernel used in this How To is: 3.5.7-yocto-standard<br /> <br /> modules:<br /> Don't forget the modules, however you get your kernel.<br /> <br /> firmware:<br /> You may need firmware for whateber USB WiFi device you are using.<br /> <br /> /etc/rc.d/ directory changes:<br /> <br /> /etc/rc.d/rc.M<br /> <br /> /etc/rc.d/rc.ntpd<br /> add the command:<br /> ntpdate -b &lt;your time server&gt; above the line<br /> that saves the kernel time to hardware, so that your system is always on time.<br /> <br /> /etc/inittab<br /> make sure the line for your login console is like so, to login to using the<br /> usb console interface (Tobi, Janus, Gallop)<br /> <br /> c1:12345:respawn:/sbin/agetty --noclear 38400 tty1 linux<br /> <br /> <br /> /etc/mtab<br /> <br /> /dev/mmcblk0p2 / ext4 rw,sync 0 0<br /> <br /> <br /> Copy Slackware ARM packages to SD Card<br /> <br /> <br /> To control module loading order, say for example, to load the camera and wifi modules last, blacklist the modules and load them in your own scripts or via /etc/rc.d/rc.local. <br /> <br /> <br /> <br /> ==== Using The Caspa / MT9V032 Sensor With Slackware 14.1 On Gumstix Overo ====<br /> <br /> Make sure to use a 3.5 series kernel built with Yocto and Bitbake per Gumstix' instructions. At least 3.5.7. When purchasing your device you may be able to request they flash the NAND with an appropriate kernel.<br /> <br /> ==== Using The P54USB WiFi With Slackware 14.1 On Gumstix Overo ====<br /> <br /> This may be enabled by default in a Yocto kernel. It supports Hot AP mode. Needs 5 Volts.<br /> <br /> ==== Using The rt2800usb USB WiFi With Slackware 14.1 On Gumstix Overo ====<br /> <br /> This likewise may be built in by default in a Yocto kernel. Works at both 3.3 and 5 volts.<br /> <br /> ==== Using The LIS331 3-Axis Accelerometer With Slackware 14.1 On Gumstix Overo ====<br /> <br /> This is an I2C device. Level Shifters may be needed on the SDA and SCL lines when your system voltage is above 3.3 Volts.<br /> <br /> ==== Using The MPU-6050 3-Axis Accelerometer With Slackware 14.1 On Gumstix Overo ====<br /> <br /> This is an I2C device. Level Shifters may be needed on the SDA and SCL lines when your system voltage is above 3.3 Volts.<br /> Sources</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_14.1_On_Gumstix_Overo&diff=6065 2014-04-21T22:22:18Z

<p>BallCam: </p> <hr /> <div>=== 20 April 2014 ===<br /> <br /> Slackware 14.1 has been installed on Gumstix Overo Devices and used succesfully with their expansion boards, with a 3.5 series kernel, built with Yocto, and BitBake.<br /> <br /> Slackware packages install, and software built with &quot;configure&quot; and &quot;make&quot; also install and run.<br /> <br /> GUI Has not yet been tested. In Progress.<br /> <br /> The majority of focus will be placed on Installing, Running, and Developing Slackware 14.1 on Gumstix as Slackware 13.37 is End Of Life, and the 3.5.x Kernels built with Yocto, and provided by Gumstix support enough devices.<br /> <br /> ==== Using The Caspa / MT9V032 Sensor With Slackware 14.1 On Gumstix Overo ====<br /> <br /> Make sure to use a 3.5 series kernel built with Yocto and Bitbake per Gumstix' instructions. At least 3.5.7. When purchasing your device you may be able to request they flash the NAND with an appropriate kernel.<br /> <br /> ==== Using The P54USB WiFi With Slackware 14.1 On Gumstix Overo ====<br /> <br /> This may be enabled by default in a Yocto kernel. It supports Hot AP mode. Needs 5 Volts.<br /> <br /> ==== Using The rt2800usb USB WiFi With Slackware 14.1 On Gumstix Overo ====<br /> <br /> This likewise may be built in by default in a Yocto kernel. Works at both 3.3 and 5 volts.<br /> <br /> ==== Using The LIS331 3-Axis Accelerometer With Slackware 14.1 On Gumstix Overo ====<br /> <br /> This is an I2C device. Level Shifters may be needed on the SDA and SCL lines when your system voltage is above 3.3 Volts.<br /> <br /> ==== Using The MPU-6050 3-Axis Accelerometer With Slackware 14.1 On Gumstix Overo ====<br /> <br /> This is an I2C device. Level Shifters may be needed on the SDA and SCL lines when your system voltage is above 3.3 Volts.<br /> Sources</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_14.1_On_Gumstix_Overo&diff=6064 2014-04-21T21:59:10Z

<p>BallCam: </p> <hr /> <div>=== 20 April 2014 ===<br /> <br /> Slackware 14.1 has been installed on Gumstix Overo Devices and used succesfully with their expansion boards, with a 3.5 series kernel, built with Yocto, and BitBake.<br /> <br /> Slackware packages install, and software built with &quot;configure&quot; and &quot;make&quot; also install and run.<br /> <br /> GUI Has not yet been tested. In Progress.<br /> <br /> The majority of focus will be placed on Installing, Running, and Developing Slackware 14.1 on Gumstix as Slackware 13.37 is End Of Life, and the 3.5.x Kernels built with Yocto, and provided by Gumstix support enough devices.<br /> <br /> Using The Caspa / MT9V032 Sensor With Slackware 14.1 On Gumstix Overo<br /> <br /> Make sure to use a 3.5 series kernel built with Yocto and Bitbake per Gumstix' instructions. At least 3.5.7. When purchasing your device you may be able to request they flash the NAND with an appropriate kernel.<br /> <br /> Using The P54USB WiFi With Slackware 14.1 On Gumstix Overo<br /> <br /> This may be enabled by default in a Yocto kernel. It supports Hot AP mode. Needs 5 Volts.<br /> <br /> Using The rt2800usb USB WiFi With Slackware 14.1 On Gumstix Overo <br /> <br /> This likewise may be built in by default in a Yocto kernel. Works at both 3.3 and 5 volts.<br /> <br /> Using The LIS331 3-Axis Accelerometer With Slackware 14.1 On Gumstix Overo<br /> <br /> This is an I2C device. Level Shifters may be needed on the SDA and SCL lines when your system voltage is above 3.3 Volts.<br /> <br /> Using The MPU-6050 3-Axis Accelerometer With Slackware 14.1 On Gumstix Overo<br /> <br /> This is an I2C device. Level Shifters may be needed on the SDA and SCL lines when your system voltage is above 3.3 Volts.<br /> Sources</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_14.1_On_Gumstix_Overo&diff=6063 2014-04-21T21:58:42Z

<p>BallCam: </p> <hr /> <div>=== 20 April 2014= ====<br /> <br /> Slackware 14.1 has been installed on Gumstix Overo Devices and used succesfully with their expansion boards, with a 3.5 series kernel, built with Yocto, and BitBake.<br /> <br /> Slackware packages install, and software built with &quot;configure&quot; and &quot;make&quot; also install and run.<br /> <br /> GUI Has not yet been tested. In Progress.<br /> <br /> The majority of focus will be placed on Installing, Running, and Developing Slackware 14.1 on Gumstix as Slackware 13.37 is End Of Life, and the 3.5.x Kernels built with Yocto, and provided by Gumstix support enough devices.<br /> <br /> Using The Caspa / MT9V032 Sensor With Slackware 14.1 On Gumstix Overo<br /> <br /> Make sure to use a 3.5 series kernel built with Yocto and Bitbake per Gumstix' instructions. At least 3.5.7. When purchasing your device you may be able to request they flash the NAND with an appropriate kernel.<br /> <br /> Using The P54USB WiFi With Slackware 14.1 On Gumstix Overo<br /> <br /> This may be enabled by default in a Yocto kernel. It supports Hot AP mode. Needs 5 Volts.<br /> <br /> Using The rt2800usb USB WiFi With Slackware 14.1 On Gumstix Overo <br /> <br /> This likewise may be built in by default in a Yocto kernel. Works at both 3.3 and 5 volts.<br /> <br /> Using The LIS331 3-Axis Accelerometer With Slackware 14.1 On Gumstix Overo<br /> <br /> This is an I2C device. Level Shifters may be needed on the SDA and SCL lines when your system voltage is above 3.3 Volts.<br /> <br /> Using The MPU-6050 3-Axis Accelerometer With Slackware 14.1 On Gumstix Overo<br /> <br /> This is an I2C device. Level Shifters may be needed on the SDA and SCL lines when your system voltage is above 3.3 Volts.<br /> Sources</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_13.37_On_Gumstix_Overo&diff=6062 2014-04-21T21:56:56Z

<p>BallCam: </p> <hr /> <div>== Slackware 13.37 On Gumstix Overo ==<br /> <br /> Slackware ARM 13.37 Is now End Of Life but there may be some interest<br /> in installing it because the 2.6 series kernel is long term stable,<br /> and because the Caspa unit works with linux 2.6.34 from Sakoman.com<br /> <br /> The focus of the Slackware on Gumstix Overo series of Howtos will be on Slackware 14.1 and later.<br /> <br /> SD Card:<br /> <br /> u-boot:<br /> <br /> kernel:<br /> <br /> modules: <br /> <br /> /etc/rc.d/ directory changes:<br /> <br /> /etc/rc.d/rc.M<br /> <br /> /etc/rc.d/rc.ntpd<br /> <br /> <br /> /etc/mtab<br /> <br /> Copy Slackware ARM packages to SD Card<br /> <br /> Uninstall SSHD, OpenSSL... reinstall from source.<br /> <br /> To control module loading order, say for example, to load the<br /> camera and wifi modules last, blacklist the modules and load them<br /> in your own scripts or via /etc/rc.d/rc.local.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6061 2014-04-21T21:44:56Z

<p>BallCam: </p> <hr /> <div>== 20 April 2014 ==<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working with kernels 2.6.34, and 3.5.7-yocto-standard.<br /> <br /> P54 USB and rt2800usb WiFi devices work in Host Mode with hostapd. WiFi generally works in non-host mode for several devices, including libertas.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> <br /> === Prerequisites ===<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can these from Gumstix web resources, or from the NAND of the device you purchase. <br /> <br /> It is assumed that you have experience using Slackware, on some other architecture.<br /> <br /> Software will need to be installed using &quot;configure&quot; and &quot;make&quot;, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> <br /> <br /> === Basic Installation Strategy: ===<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> <br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can &quot;cross-install&quot; that is, use an x86 based PC to run &quot;installpkg to install Slackware ARM packages to an SD card used as the rootfs of your device for most but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do &quot;cross-install&quot; successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using &quot;installpkg&quot;. It works fine. &quot;pkgtool&quot; also works, but may not work when using the miniroot unless a few more packages are installed. The miniroot has some but not all the &quot;a&quot; series packages installed.<br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. GCC and Make work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> <br /> <br /> === Building Your Own Kernel ===<br /> <br /> ==== Linux 3.5.x Kernel ====<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> <br /> <br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo:<br /> <br /> Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> <br /> <br /> ==== Linux 2.6.x Kernel ====<br /> <br /> The instructions for building a 2.6 series kernel for Gumstix can be found here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> Those instructions can be applied to kernel source obtained from Kernel.org, or Gumstix Resources.<br /> <br /> The main reason to build a 2.6 kernel is for Slackware ARM 13.37. However, Since Slackware ARM 13.37 is now end of life, <br /> the focus in these wiki pages will be on Slackware ARM 14.1.<br /> <br /> <br /> <br /> === Installing Slackware ARM Packages On Overo ===<br /> <br /> Once you have a bootable system, you can use &quot;installpkg&quot;, &quot;removepkg&quot; and &quot;pkgtool&quot; to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the &quot;a&quot; series installed. You can manually install the rest.<br /> <br /> Packages from the &quot;a&quot;, &quot;ap&quot;, &quot;d&quot;, &quot;l&quot;, &quot;n&quot; and &quot;x&quot; sets need to be installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This How To will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone with KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with &quot;removepkg&quot; or &quot;pkgtool&quot; then install from the source to get the particular version you like.<br /> <br /> <br /> === Devices Tested So Far ===<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware:<br /> <br /> ==== Caspa Camera Unit / MT9V032 Sensor and Kernel Driver ====<br /> <br /> ===== Using Caspa With 2.6.34 Kernel =====<br /> <br /> Start with the Gumstix User Wiki page for the Caspa, here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, the Kernel Source tree has to come from Sakoman.com<br /> <br /> At http://www.Sakoman.com, select “Download” to get to the Git repo.<br /> <br /> Under &quot;projects/&quot;, select linux.git<br /> <br /> Under the &quot;heads&quot; section, click the ellipsis at the bottom of the page to expand the list. Click on &quot;omap3-2.6.34&quot; to browse the source tree.<br /> <br /> This code can be checked out in a manner similar to the Gumstix git repo:<br /> <br /> 1) First clone the “linux.git” repo located at http://www.Sakoman.com/git/<br /> <br /> git clone git://www.Sakoman.com/git/linux.git<br /> <br /> This will create a “linux” directory.<br /> <br /> 2) Then checkout the “omap3-2.6.34” branch, from within the “linux” directory:<br /> <br /> cd linux<br /> git checkout omap3-2.6.34<br /> <br /> You can then apply the patch and defconfig to this source tree to build the kernel per the instructions on the Gumstix Wiki page for the Caspa.<br /> <br /> <br /> ===== Using Caspa With 3.5.x Kernel =====<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from Gumstix, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work.<br /> <br /> Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its &quot;Pixel Format&quot;, or &quot;Color Space&quot; will be what is referred to as &quot;UYVY&quot;.<br /> <br /> The instructions for using &quot;yavta&quot; also work. &quot;yavta&quot; is simply: &quot;Yet Another Video4linux Test Application&quot;.<br /> <br /> Yavta will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the &quot;-pix_fmt&quot; option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the &quot;DISPLAY&quot; option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the &quot;LD_PRELOAD&quot; environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> <br /> <br /> ==== P54USB WiFi ====<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only.<br /> <br /> Use this search page for devices that use the Prism 54 USB WiFi Driver<br /> <br /> http://wireless.kernel.org/en/users/Devices/USB<br /> <br /> Make sure that you have the firmware, though it is usually included<br /> in the kernel source.<br /> <br /> Make sure that the USB device that you buy is BOTH the correct<br /> Model Number, AND Revision. Manufacturers change their chipsets <br /> between revisions.<br /> <br /> <br /> ==== WRL-11713 PCDuino WiFi Dongle ====<br /> <br /> From SparkFun.com – rt2800usb Works With HostAPD on Overo<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> This works in Kernel 3.5.x<br /> <br /> The command:<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id <br /> <br /> Must be used to bring up the interface. <br /> <br /> Make sure to get the firmware from the [http://www.mediatek.com/en/downloads MediaTek / Ralink] website.<br /> <br /> Tested with 5 Volts and 3.3 Volts.<br /> <br /> <br /> ==== LIS-331 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/10345 <br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> ==== MPU-6050 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/11028<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse the Gumstix GitHub repo. Look under &quot;meta-gumstix&quot;, and &quot;linux&quot;.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6060 2014-04-21T21:43:41Z

<p>BallCam: </p> <hr /> <div>== 20 April 2014 ==<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working with kernels 2.6.34, and 3.5.7-yocto-standard.<br /> <br /> P54 USB and rt2800usb WiFi devices work in Host Mode with hostapd. WiFi generally works in non-host mode for several devices, including libertas.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> <br /> === Prerequisites ===<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can these from Gumstix web resources, or from the NAND of the device you purchase. <br /> <br /> It is assumed that you have experience using Slackware, on some other architecture.<br /> <br /> Software will need to be installed using &quot;configure&quot; and &quot;make&quot;, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> <br /> <br /> === Basic Installation Strategy: ===<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> <br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can &quot;cross-install&quot; that is, use an x86 based PC to run &quot;installpkg to install Slackware ARM packages to an SD card used as the rootfs of your device for most but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do &quot;cross-install&quot; successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using &quot;installpkg&quot;. It works fine. &quot;pkgtool&quot; also works, but may not work when using the miniroot unless a few more packages are installed. The miniroot has some but not all the &quot;a&quot; series packages installed.<br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. GCC and Make work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> <br /> <br /> === Building Your Own Kernel ===<br /> <br /> ==== Linux 3.5.x Kernel ====<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> <br /> <br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo:<br /> <br /> Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> <br /> <br /> ==== Linux 2.6.x Kernel ====<br /> <br /> The instructions for building a 2.6 series kernel for Gumstix can be found here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> Those instructions can be applied to kernel source obtained from Kernel.org, or Gumstix Resources.<br /> <br /> The main reason to build a 2.6 kernel is for Slackware ARM 13.37. However, Since Slackware ARM 13.37 is now end of life, <br /> the focus in these wiki pages will be on Slackware ARM 14.1.<br /> <br /> <br /> <br /> === Installing Slackware ARM Packages On Overo ===<br /> <br /> Once you have a bootable system, you can use &quot;installpkg&quot;, &quot;removepkg&quot; and &quot;pkgtool&quot; to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the &quot;a&quot; series installed. You can manually install the rest.<br /> <br /> Packages from the &quot;a&quot;, &quot;ap&quot;, &quot;d&quot;, &quot;l&quot;, &quot;n&quot; and &quot;x&quot; sets need to be installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This How To will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone with KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with &quot;removepkg&quot; or &quot;pkgtool&quot; then install from the source to get the particular version you like.<br /> <br /> <br /> === Devices Tested So Far ===<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware:<br /> <br /> ==== Caspa Camera Unit / MT9V032 Sensor and Kernel Driver ====<br /> <br /> ===== Using Caspa With 2.6.34 Kernel =====<br /> <br /> Start with the Gumstix User Wiki page for the Caspa, here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, the Kernel Source tree has to come from Sakoman.com<br /> <br /> At http://www.Sakoman.com, select “Download” to get to the Git repo.<br /> <br /> Under &quot;projects/&quot;, select linux.git<br /> <br /> Under the &quot;heads&quot; section, click the ellipsis at the bottom of the page to expand the list. Click on &quot;omap3-2.6.34&quot; to browse the source tree.<br /> <br /> This code can be checked out in a manner similar to the Gumstix git repo:<br /> <br /> 1) First clone the “linux.git” repo located at http://www.Sakoman.com/git/<br /> <br /> git clone git://www.Sakoman.com/git/linux.git<br /> <br /> This will create a “linux” directory.<br /> <br /> 2) Then checkout the “omap3-2.6.34” branch, from within the “linux” directory:<br /> <br /> cd linux<br /> git checkout omap3-2.6.34<br /> <br /> You can then apply the patch and defconfig to this source tree to build the kernel per the instructions on the Gumstix Wiki page for the Caspa.<br /> <br /> <br /> ===== Using Caspa With 3.5.x Kernel =====<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from Gumstix, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work.<br /> <br /> Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its &quot;Pixel Format&quot;, or &quot;Color Space&quot; will be what is referred to as &quot;UYVY&quot;.<br /> <br /> The instructions for using &quot;yavta&quot; also work. &quot;yavta&quot; is simply: &quot;Yet Another Video4linux Test Application&quot;.<br /> <br /> Yavta will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the &quot;-pix_fmt&quot; option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the &quot;DISPLAY&quot; option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the &quot;LD_PRELOAD&quot; environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> <br /> <br /> ==== P54USB WiFi ====<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only.<br /> <br /> Use this search page for devices that use the Prism 54 USB WiFi Driver<br /> <br /> http://wireless.kernel.org/en/users/Devices/USB<br /> <br /> Make sure that you have the firmware, though it is usually included<br /> in the kernel source.<br /> <br /> Make sure that the USB device that you buy is BOTH the correct<br /> Model Number, AND Revision. Manufacturers change their chipsets <br /> between revisions.<br /> <br /> <br /> ==== WRL-11713 PCDuino WiFi Dongle ====<br /> <br /> From SparkFun.com – rt2800usb Works With HostAPD on Overo<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> This works in Kernel 3.5.x<br /> <br /> The command:<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id <br /> <br /> Must be used to bring up the interface. <br /> <br /> Make sure to get the firmware from the [http://www.mediatek.com/en/downloads MediaTek / Ralink website]<br /> <br /> Tested with 5 Volts and 3.3 Volts.<br /> <br /> <br /> ==== LIS-331 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/10345 <br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> ==== MPU-6050 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/11028<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse the Gumstix GitHub repo. Look under &quot;meta-gumstix&quot;, and &quot;linux&quot;.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6059 2014-04-21T21:42:52Z

<p>BallCam: /* WRL-11713 PCDuino WiFi Dongle */</p> <hr /> <div>== 20 April 2014 ==<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working with kernels 2.6.34, and 3.5.7-yocto-standard.<br /> <br /> P54 USB and rt2800usb WiFi devices work in Host Mode with hostapd. WiFi generally works in non-host mode for several devices, including libertas.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> <br /> === Prerequisites ===<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can these from Gumstix web resources, or from the NAND of the device you purchase. <br /> <br /> It is assumed that you have experience using Slackware, on some other architecture.<br /> <br /> Software will need to be installed using &quot;configure&quot; and &quot;make&quot;, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> <br /> <br /> === Basic Installation Strategy: ===<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> <br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can &quot;cross-install&quot; that is, use an x86 based PC to run &quot;installpkg to install Slackware ARM packages to an SD card used as the rootfs of your device for most but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do &quot;cross-install&quot; successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using &quot;installpkg&quot;. It works fine. &quot;pkgtool&quot; also works, but may not work when using the miniroot unless a few more packages are installed. The miniroot has some but not all the &quot;a&quot; series packages installed.<br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. GCC and Make work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> <br /> <br /> === Building Your Own Kernel ===<br /> <br /> ==== Linux 3.5.x Kernel ====<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> <br /> <br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo:<br /> <br /> Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> <br /> <br /> ==== Linux 2.6.x Kernel ====<br /> <br /> The instructions for building a 2.6 series kernel for Gumstix can be found here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> Those instructions can be applied to kernel source obtained from Kernel.org, or Gumstix Resources.<br /> <br /> The main reason to build a 2.6 kernel is for Slackware ARM 13.37. However, Since Slackware ARM 13.37 is now end of life, <br /> the focus in these wiki pages will be on Slackware ARM 14.1.<br /> <br /> <br /> <br /> === Installing Slackware ARM Packages On Overo ===<br /> <br /> Once you have a bootable system, you can use &quot;installpkg&quot;, &quot;removepkg&quot; and &quot;pkgtool&quot; to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the &quot;a&quot; series installed. You can manually install the rest.<br /> <br /> Packages from the &quot;a&quot;, &quot;ap&quot;, &quot;d&quot;, &quot;l&quot;, &quot;n&quot; and &quot;x&quot; sets need to be installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This How To will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone with KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with &quot;removepkg&quot; or &quot;pkgtool&quot; then install from the source to get the particular version you like.<br /> <br /> <br /> === Devices Tested So Far ===<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware:<br /> <br /> ==== Caspa Camera Unit / MT9V032 Sensor and Kernel Driver ====<br /> <br /> ===== Using Caspa With 2.6.34 Kernel =====<br /> <br /> Start with the Gumstix User Wiki page for the Caspa, here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, the Kernel Source tree has to come from Sakoman.com<br /> <br /> At http://www.Sakoman.com, select “Download” to get to the Git repo.<br /> <br /> Under &quot;projects/&quot;, select linux.git<br /> <br /> Under the &quot;heads&quot; section, click the ellipsis at the bottom of the page to expand the list. Click on &quot;omap3-2.6.34&quot; to browse the source tree.<br /> <br /> This code can be checked out in a manner similar to the Gumstix git repo:<br /> <br /> 1) First clone the “linux.git” repo located at http://www.Sakoman.com/git/<br /> <br /> git clone git://www.Sakoman.com/git/linux.git<br /> <br /> This will create a “linux” directory.<br /> <br /> 2) Then checkout the “omap3-2.6.34” branch, from within the “linux” directory:<br /> <br /> cd linux<br /> git checkout omap3-2.6.34<br /> <br /> You can then apply the patch and defconfig to this source tree to build the kernel per the instructions on the Gumstix Wiki page for the Caspa.<br /> <br /> <br /> ===== Using Caspa With 3.5.x Kernel =====<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from Gumstix, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work.<br /> <br /> Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its &quot;Pixel Format&quot;, or &quot;Color Space&quot; will be what is referred to as &quot;UYVY&quot;.<br /> <br /> The instructions for using &quot;yavta&quot; also work. &quot;yavta&quot; is simply: &quot;Yet Another Video4linux Test Application&quot;.<br /> <br /> Yavta will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the &quot;-pix_fmt&quot; option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the &quot;DISPLAY&quot; option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the &quot;LD_PRELOAD&quot; environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> <br /> <br /> ==== P54USB WiFi ====<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only.<br /> <br /> Use this search page for devices that use the Prism 54 USB WiFi Driver<br /> <br /> http://wireless.kernel.org/en/users/Devices/USB<br /> <br /> Make sure that you have the firmware, though it is usually included<br /> in the kernel source.<br /> <br /> Make sure that the USB device that you buy is BOTH the correct<br /> Model Number, AND Revision. Manufacturers change their chipsets <br /> between revisions.<br /> <br /> <br /> ==== WRL-11713 PCDuino WiFi Dongle ====<br /> <br /> From SparkFun.com – rt2800usb Works With HostAPD on Overo<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> This works in Kernel 3.5.x<br /> <br /> The command:<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id <br /> <br /> Must be used to bring up the interface. <br /> <br /> Make sure to get the firmware from the [http://www.mediatek.com/en/downloads MediaTek / Ralink website]<br /> <br /> Tested with 5 Volts and 3.3 Volts.<br /> <br /> ==== LIS-331 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/10345 <br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> ==== MPU-6050 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/11028<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse the Gumstix GitHub repo. Look under &quot;meta-gumstix&quot;, and &quot;linux&quot;.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6058 2014-04-21T21:42:27Z

<p>BallCam: /* WRL-11713 PCDuino WiFi Dongle */</p> <hr /> <div>== 20 April 2014 ==<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working with kernels 2.6.34, and 3.5.7-yocto-standard.<br /> <br /> P54 USB and rt2800usb WiFi devices work in Host Mode with hostapd. WiFi generally works in non-host mode for several devices, including libertas.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> <br /> === Prerequisites ===<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can these from Gumstix web resources, or from the NAND of the device you purchase. <br /> <br /> It is assumed that you have experience using Slackware, on some other architecture.<br /> <br /> Software will need to be installed using &quot;configure&quot; and &quot;make&quot;, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> <br /> <br /> === Basic Installation Strategy: ===<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> <br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can &quot;cross-install&quot; that is, use an x86 based PC to run &quot;installpkg to install Slackware ARM packages to an SD card used as the rootfs of your device for most but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do &quot;cross-install&quot; successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using &quot;installpkg&quot;. It works fine. &quot;pkgtool&quot; also works, but may not work when using the miniroot unless a few more packages are installed. The miniroot has some but not all the &quot;a&quot; series packages installed.<br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. GCC and Make work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> <br /> <br /> === Building Your Own Kernel ===<br /> <br /> ==== Linux 3.5.x Kernel ====<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> <br /> <br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo:<br /> <br /> Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> <br /> <br /> ==== Linux 2.6.x Kernel ====<br /> <br /> The instructions for building a 2.6 series kernel for Gumstix can be found here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> Those instructions can be applied to kernel source obtained from Kernel.org, or Gumstix Resources.<br /> <br /> The main reason to build a 2.6 kernel is for Slackware ARM 13.37. However, Since Slackware ARM 13.37 is now end of life, <br /> the focus in these wiki pages will be on Slackware ARM 14.1.<br /> <br /> <br /> <br /> === Installing Slackware ARM Packages On Overo ===<br /> <br /> Once you have a bootable system, you can use &quot;installpkg&quot;, &quot;removepkg&quot; and &quot;pkgtool&quot; to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the &quot;a&quot; series installed. You can manually install the rest.<br /> <br /> Packages from the &quot;a&quot;, &quot;ap&quot;, &quot;d&quot;, &quot;l&quot;, &quot;n&quot; and &quot;x&quot; sets need to be installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This How To will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone with KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with &quot;removepkg&quot; or &quot;pkgtool&quot; then install from the source to get the particular version you like.<br /> <br /> <br /> === Devices Tested So Far ===<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware:<br /> <br /> ==== Caspa Camera Unit / MT9V032 Sensor and Kernel Driver ====<br /> <br /> ===== Using Caspa With 2.6.34 Kernel =====<br /> <br /> Start with the Gumstix User Wiki page for the Caspa, here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, the Kernel Source tree has to come from Sakoman.com<br /> <br /> At http://www.Sakoman.com, select “Download” to get to the Git repo.<br /> <br /> Under &quot;projects/&quot;, select linux.git<br /> <br /> Under the &quot;heads&quot; section, click the ellipsis at the bottom of the page to expand the list. Click on &quot;omap3-2.6.34&quot; to browse the source tree.<br /> <br /> This code can be checked out in a manner similar to the Gumstix git repo:<br /> <br /> 1) First clone the “linux.git” repo located at http://www.Sakoman.com/git/<br /> <br /> git clone git://www.Sakoman.com/git/linux.git<br /> <br /> This will create a “linux” directory.<br /> <br /> 2) Then checkout the “omap3-2.6.34” branch, from within the “linux” directory:<br /> <br /> cd linux<br /> git checkout omap3-2.6.34<br /> <br /> You can then apply the patch and defconfig to this source tree to build the kernel per the instructions on the Gumstix Wiki page for the Caspa.<br /> <br /> <br /> ===== Using Caspa With 3.5.x Kernel =====<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from Gumstix, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work.<br /> <br /> Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its &quot;Pixel Format&quot;, or &quot;Color Space&quot; will be what is referred to as &quot;UYVY&quot;.<br /> <br /> The instructions for using &quot;yavta&quot; also work. &quot;yavta&quot; is simply: &quot;Yet Another Video4linux Test Application&quot;.<br /> <br /> Yavta will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the &quot;-pix_fmt&quot; option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the &quot;DISPLAY&quot; option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the &quot;LD_PRELOAD&quot; environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> <br /> <br /> ==== P54USB WiFi ====<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only.<br /> <br /> Use this search page for devices that use the Prism 54 USB WiFi Driver<br /> <br /> http://wireless.kernel.org/en/users/Devices/USB<br /> <br /> Make sure that you have the firmware, though it is usually included<br /> in the kernel source.<br /> <br /> Make sure that the USB device that you buy is BOTH the correct<br /> Model Number, AND Revision. Manufacturers change their chipsets <br /> between revisions.<br /> <br /> <br /> ==== WRL-11713 PCDuino WiFi Dongle ====<br /> <br /> From SparkFun.com – rt2800usb Works With HostAPD on Overo<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> This works in Kernel 3.5.x<br /> <br /> The command:<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id <br /> <br /> Must be used to bring up the interface. Make sure to get the firmware from the [http://www.mediatek.com/en/downloads MediaTek / Ralink website]<br /> <br /> Tested with 5 Volts and 3.3 Volts.<br /> <br /> ==== LIS-331 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/10345 <br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> ==== MPU-6050 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/11028<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse the Gumstix GitHub repo. Look under &quot;meta-gumstix&quot;, and &quot;linux&quot;.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6057 2014-04-21T21:41:32Z

<p>BallCam: </p> <hr /> <div>== 20 April 2014 ==<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working with kernels 2.6.34, and 3.5.7-yocto-standard.<br /> <br /> P54 USB and rt2800usb WiFi devices work in Host Mode with hostapd. WiFi generally works in non-host mode for several devices, including libertas.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> <br /> === Prerequisites ===<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can these from Gumstix web resources, or from the NAND of the device you purchase. <br /> <br /> It is assumed that you have experience using Slackware, on some other architecture.<br /> <br /> Software will need to be installed using &quot;configure&quot; and &quot;make&quot;, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> <br /> <br /> === Basic Installation Strategy: ===<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> <br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can &quot;cross-install&quot; that is, use an x86 based PC to run &quot;installpkg to install Slackware ARM packages to an SD card used as the rootfs of your device for most but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do &quot;cross-install&quot; successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using &quot;installpkg&quot;. It works fine. &quot;pkgtool&quot; also works, but may not work when using the miniroot unless a few more packages are installed. The miniroot has some but not all the &quot;a&quot; series packages installed.<br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. GCC and Make work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> <br /> <br /> === Building Your Own Kernel ===<br /> <br /> ==== Linux 3.5.x Kernel ====<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> <br /> <br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo:<br /> <br /> Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> <br /> <br /> ==== Linux 2.6.x Kernel ====<br /> <br /> The instructions for building a 2.6 series kernel for Gumstix can be found here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> Those instructions can be applied to kernel source obtained from Kernel.org, or Gumstix Resources.<br /> <br /> The main reason to build a 2.6 kernel is for Slackware ARM 13.37. However, Since Slackware ARM 13.37 is now end of life, <br /> the focus in these wiki pages will be on Slackware ARM 14.1.<br /> <br /> <br /> <br /> === Installing Slackware ARM Packages On Overo ===<br /> <br /> Once you have a bootable system, you can use &quot;installpkg&quot;, &quot;removepkg&quot; and &quot;pkgtool&quot; to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the &quot;a&quot; series installed. You can manually install the rest.<br /> <br /> Packages from the &quot;a&quot;, &quot;ap&quot;, &quot;d&quot;, &quot;l&quot;, &quot;n&quot; and &quot;x&quot; sets need to be installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This How To will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone with KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with &quot;removepkg&quot; or &quot;pkgtool&quot; then install from the source to get the particular version you like.<br /> <br /> <br /> === Devices Tested So Far ===<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware:<br /> <br /> ==== Caspa Camera Unit / MT9V032 Sensor and Kernel Driver ====<br /> <br /> ===== Using Caspa With 2.6.34 Kernel =====<br /> <br /> Start with the Gumstix User Wiki page for the Caspa, here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, the Kernel Source tree has to come from Sakoman.com<br /> <br /> At http://www.Sakoman.com, select “Download” to get to the Git repo.<br /> <br /> Under &quot;projects/&quot;, select linux.git<br /> <br /> Under the &quot;heads&quot; section, click the ellipsis at the bottom of the page to expand the list. Click on &quot;omap3-2.6.34&quot; to browse the source tree.<br /> <br /> This code can be checked out in a manner similar to the Gumstix git repo:<br /> <br /> 1) First clone the “linux.git” repo located at http://www.Sakoman.com/git/<br /> <br /> git clone git://www.Sakoman.com/git/linux.git<br /> <br /> This will create a “linux” directory.<br /> <br /> 2) Then checkout the “omap3-2.6.34” branch, from within the “linux” directory:<br /> <br /> cd linux<br /> git checkout omap3-2.6.34<br /> <br /> You can then apply the patch and defconfig to this source tree to build the kernel per the instructions on the Gumstix Wiki page for the Caspa.<br /> <br /> <br /> ===== Using Caspa With 3.5.x Kernel =====<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from Gumstix, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work.<br /> <br /> Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its &quot;Pixel Format&quot;, or &quot;Color Space&quot; will be what is referred to as &quot;UYVY&quot;.<br /> <br /> The instructions for using &quot;yavta&quot; also work. &quot;yavta&quot; is simply: &quot;Yet Another Video4linux Test Application&quot;.<br /> <br /> Yavta will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the &quot;-pix_fmt&quot; option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the &quot;DISPLAY&quot; option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the &quot;LD_PRELOAD&quot; environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> <br /> <br /> ==== P54USB WiFi ====<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only.<br /> <br /> Use this search page for devices that use the Prism 54 USB WiFi Driver<br /> <br /> http://wireless.kernel.org/en/users/Devices/USB<br /> <br /> Make sure that you have the firmware, though it is usually included<br /> in the kernel source.<br /> <br /> Make sure that the USB device that you buy is BOTH the correct<br /> Model Number, AND Revision. Manufacturers change their chipsets <br /> between revisions.<br /> <br /> <br /> ==== WRL-11713 PCDuino WiFi Dongle ====<br /> <br /> From SparkFun.com – rt2800usb Works With HostAPD on Overo<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> This works in Kernel 3.5.x<br /> <br /> The command:<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id <br /> <br /> Must be used to bring up the interface. Make sure to get the firmware from the [http://www.mediatek.com/en/downloads MediaTek / Ralink website]<br /> Tested with 5 Volts and 3.3 Volts.<br /> <br /> <br /> <br /> ==== LIS-331 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/10345 <br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> ==== MPU-6050 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/11028<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse the Gumstix GitHub repo. Look under &quot;meta-gumstix&quot;, and &quot;linux&quot;.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6056 2014-04-21T21:01:02Z

<p>BallCam: </p> <hr /> <div>== 20 April 2014 ==<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working with kernels 2.6.34, and 3.5.7-yocto-standard.<br /> <br /> P54 USB and rt2800usb WiFi devices work in Host Mode with hostapd. WiFi generally works in non-host mode for several devices, including libertas.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> <br /> === Prerequisites ===<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can these from Gumstix web resources, or from the NAND of the device you purchase. <br /> <br /> It is assumed that you have experience using Slackware, on some other architecture.<br /> <br /> Software will need to be installed using &quot;configure&quot; and &quot;make&quot;, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> <br /> <br /> === Basic Installation Strategy: ===<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> <br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can &quot;cross-install&quot; that is, use an x86 based PC to run &quot;installpkg to install Slackware ARM packages to an SD card used as the rootfs of your device for most but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do &quot;cross-install&quot; successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using &quot;installpkg&quot;. It works fine. &quot;pkgtool&quot; also works, but may not work when using the miniroot unless a few more packages are installed. The miniroot has some but not all the &quot;a&quot; series packages installed.<br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. GCC and Make work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> <br /> <br /> === Building Your Own Kernel ===<br /> <br /> ==== Linux 3.5.x Kernel ====<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> <br /> <br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo:<br /> <br /> Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> <br /> <br /> ==== Linux 2.6.x Kernel ====<br /> <br /> The instructions for building a 2.6 series kernel for Gumstix can be found here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> Those instructions can be applied to kernel source obtained from Kernel.org, or Gumstix Resources.<br /> <br /> The main reason to build a 2.6 kernel is for Slackware ARM 13.37. However, Since Slackware ARM 13.37 is now end of life, <br /> the focus in these wiki pages will be on Slackware ARM 14.1.<br /> <br /> <br /> <br /> === Installing Slackware ARM Packages Overo ===<br /> <br /> Once you have a bootable system, you can use “installpkg”, “removepkg” and “pkgtool” to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the “a” series installed. You can manually install the rest.<br /> <br /> In the installed system images that will be published for 13.37 and 14.1, packages from the “a”, “ap”, “d”, “l”, “n” and “x” sets are installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This HowTo will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone on KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with &quot;removepkg&quot; or &quot;pkgtool&quot; then install from the source to get the particular version you like.<br /> <br /> <br /> === Devices Tested So Far ===<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware:<br /> <br /> ==== Caspa Camera Unit / MT9V032 Sensor and Kernel Driver ====<br /> <br /> ===== Using Caspa With 2.6.34 Kernel =====<br /> <br /> Start with the Gumstix User Wiki page for the Caspa, here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, the Kernel Source tree has to come from Sakoman.com<br /> <br /> At http://www.Sakoman.com, select “Download” to get to the Git repo.<br /> <br /> Under &quot;projects/&quot;, select linux.git<br /> <br /> Under the &quot;heads&quot; section, click the ellipsis at the bottom of the page to expand the list. Click on &quot;omap3-2.6.34&quot; to browse the source tree.<br /> <br /> This code can be checked out in a manner similar to the Gumstix git repo:<br /> <br /> 1) First clone the “linux.git” repo located at http://www.Sakoman.com/git/<br /> <br /> git clone git://www.Sakoman.com/git/linux.git<br /> <br /> This will create a “linux” directory.<br /> <br /> 2) Then checkout the “omap3-2.6.34” branch, from within the “linux” directory:<br /> <br /> cd linux<br /> git checkout omap3-2.6.34<br /> <br /> You can then apply the patch and defconfig to this source tree to build the kernel per the instructions on the Gumstix Wiki page for the Caspa.<br /> <br /> <br /> ===== Using Caspa With 3.5.x Kernel =====<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from Gumstix, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work.<br /> <br /> Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its &quot;Pixel Format&quot;, or &quot;Color Space&quot; will be what is referred to as &quot;UYVY&quot;.<br /> <br /> The instructions for using &quot;yavta&quot; also work. &quot;yavta&quot; is simply: &quot;Yet Another Video4linux Test Application&quot;.<br /> <br /> Yavta will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the &quot;-pix_fmt&quot; option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the &quot;DISPLAY&quot; option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the &quot;LD_PRELOAD&quot; environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> <br /> <br /> ==== P54USB WiFi ====<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only.<br /> <br /> Use this search page for devices that use the Prism 54 USB WiFi Driver<br /> <br /> http://wireless.kernel.org/en/users/Devices/USB<br /> <br /> Make sure that you have the firmware, though it is usually included<br /> in the kernel source.<br /> <br /> Make sure that the USB device that you buy is BOTH the correct<br /> Model Number, AND Revision. Manufacturers change their chipsets <br /> between revisions.<br /> <br /> <br /> ==== WRL-11713 PCDuino WiFi Dongle ====<br /> <br /> From SparkFun.com – rt2800usb Works With HostAPD on Overo<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> This works in Kernel 3.5.x<br /> <br /> The command:<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id <br /> <br /> Must be used to bring up the interface. Make sure to get the firmware from the Ralink website.<br /> Tested with 5 Volts and 3.3 Volts.<br /> <br /> <br /> ==== LIS-331 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/10345 <br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> ==== MPU-6050 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/11028<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse the Gumstix GitHub repo. Look under &quot;meta-gumstix&quot;, and &quot;linux&quot;.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6055 2014-04-21T20:58:55Z

<p>BallCam: /* P54USB WiFi */</p> <hr /> <div>== 20 April 2014 ==<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working with kernels 2.6.34, and 3.5.7-yocto-standard.<br /> <br /> P54 USB and rt2800usb WiFi devices work in Host Mode with hostapd. WiFi generally works in non-host mode for several devices, including libertas.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> <br /> === Prerequisites ===<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can these from Gumstix web resources, or from the NAND of the device you purchase. <br /> <br /> It is assumed that you have experience using Slackware, on some other architecture.<br /> <br /> Software will need to be installed using &quot;configure&quot; and &quot;make&quot;, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> <br /> <br /> === Basic Installation Strategy: ===<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> <br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can &quot;cross-install&quot; that is, use an x86 based PC to run &quot;installpkg to install Slackware ARM packages to an SD card used as the rootfs of your device for most but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do &quot;cross-install&quot; successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using &quot;installpkg&quot;. It works fine. &quot;pkgtool&quot; also works, but may not work when using the miniroot unless a few more packages are installed. The miniroot has some but not all the &quot;a&quot; series packages installed.<br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. GCC and Make work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> <br /> <br /> === Building Your Own Kernel ===<br /> <br /> ==== Linux 3.5.x Kernel ====<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> <br /> <br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo:<br /> <br /> Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> <br /> <br /> ==== Linux 2.6.x Kernel ====<br /> <br /> The instructions for building a 2.6 series kernel for Gumstix can be found here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> Those instructions can be applied to kernel source obtained from Kernel.org, or Gumstix Resources.<br /> <br /> The main reason to build a 2.6 kernel is for Slackware ARM 13.37. However, Since Slackware ARM 13.37 is now end of life, <br /> the focus in these wiki pages will be on Slackware ARM 14.1.<br /> <br /> <br /> <br /> === Installing Slackware ARM Packages Overo ===<br /> <br /> Once you have a bootable system, you can use “installpkg”, “removepkg” and “pkgtool” to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the “a” series installed. You can manually install the rest.<br /> <br /> In the installed system images that will be published for 13.37 and 14.1, packages from the “a”, “ap”, “d”, “l”, “n” and “x” sets are installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This HowTo will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone on KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with &quot;removepkg&quot; or &quot;pkgtool&quot; then install from the source to get the particular version you like.<br /> <br /> <br /> === Devices Tested So Far ===<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware:<br /> <br /> ==== Caspa Camera Unit / MT9V032 Sensor and Kernel Driver ====<br /> <br /> ===== Using Caspa With 2.6.34 Kernel =====<br /> <br /> Start with the Gumstix User Wiki page for the Caspa, here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, the Kernel Source tree has to come from Sakoman.com<br /> <br /> At http://www.Sakoman.com, select “Download” to get to the Git repo.<br /> <br /> Under &quot;projects/&quot;, select linux.git<br /> <br /> Under the &quot;heads&quot; section, click the ellipsis at the bottom of the page to expand the list. Click on &quot;omap3-2.6.34&quot; to browse the source tree.<br /> <br /> This code can be checked out in a manner similar to the Gumstix git repo:<br /> <br /> 1) First clone the “linux.git” repo located at http://www.Sakoman.com/git/<br /> <br /> git clone git://www.Sakoman.com/git/linux.git<br /> <br /> This will create a “linux” directory.<br /> <br /> 2) Then checkout the “omap3-2.6.34” branch, from within the “linux” directory:<br /> <br /> cd linux<br /> git checkout omap3-2.6.34<br /> <br /> You can then apply the patch and defconfig to this source tree to build the kernel per the instructions on the Gumstix Wiki page for the Caspa.<br /> <br /> <br /> ===== Using Caspa With 3.5.x Kernel =====<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from Gumstix, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work.<br /> <br /> Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its &quot;Pixel Format&quot;, or &quot;Color Space&quot; will be what is referred to as &quot;UYVY&quot;.<br /> <br /> The instructions for using &quot;yavta&quot; also work. &quot;yavta&quot; is simply: &quot;Yet Another Video4linux Test Application&quot;.<br /> <br /> Yavta will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the &quot;-pix_fmt&quot; option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the &quot;DISPLAY&quot; option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the &quot;LD_PRELOAD&quot; environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> <br /> <br /> ==== P54USB WiFi ====<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only.<br /> <br /> Use this search page for devices that use the Prism 54 USB WiFi Driver<br /> <br /> http://wireless.kernel.org/en/users/Devices/USB<br /> <br /> Make sure that you have the firmware, though it is usually included<br /> in the kernel source.<br /> <br /> Make sure that the USB device that you buy is BOTH the correct<br /> Model Number, AND Revision. Manufacturers change their chipsets <br /> between revisions.<br /> <br /> ==== WRL-11713 PCDuino WiFi Dongle ====<br /> <br /> From SparkFun.com – rt2800usb Works With HostAPD on Overo<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> This works in Kernel 3.5.x<br /> <br /> The command:<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id <br /> <br /> Must be used to bring up the interface. Make sure to get the firmware from the Ralink website.<br /> Tested with 5 Volts and 3.3 Volts.<br /> <br /> ==== LIS-331 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/10345 <br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> ==== MPU-6050 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/11028<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse the Gumstix GitHub repo. Look under &quot;meta-gumstix&quot;, and &quot;linux&quot;.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6054 2014-04-21T20:25:47Z

<p>BallCam: /* WRL-11713 PCDuino WiFi Dongle */</p> <hr /> <div>== 20 April 2014 ==<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working with kernels 2.6.34, and 3.5.7-yocto-standard.<br /> <br /> P54 USB and rt2800usb WiFi devices work in Host Mode with hostapd. WiFi generally works in non-host mode for several devices, including libertas.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> <br /> === Prerequisites ===<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can these from Gumstix web resources, or from the NAND of the device you purchase. <br /> <br /> It is assumed that you have experience using Slackware, on some other architecture.<br /> <br /> Software will need to be installed using &quot;configure&quot; and &quot;make&quot;, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> <br /> <br /> === Basic Installation Strategy: ===<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> <br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can &quot;cross-install&quot; that is, use an x86 based PC to run &quot;installpkg to install Slackware ARM packages to an SD card used as the rootfs of your device for most but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do &quot;cross-install&quot; successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using &quot;installpkg&quot;. It works fine. &quot;pkgtool&quot; also works, but may not work when using the miniroot unless a few more packages are installed. The miniroot has some but not all the &quot;a&quot; series packages installed.<br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. GCC and Make work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> <br /> <br /> === Building Your Own Kernel ===<br /> <br /> ==== Linux 3.5.x Kernel ====<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> <br /> <br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo:<br /> <br /> Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> <br /> <br /> ==== Linux 2.6.x Kernel ====<br /> <br /> The instructions for building a 2.6 series kernel for Gumstix can be found here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> Those instructions can be applied to kernel source obtained from Kernel.org, or Gumstix Resources.<br /> <br /> The main reason to build a 2.6 kernel is for Slackware ARM 13.37. However, Since Slackware ARM 13.37 is now end of life, <br /> the focus in these wiki pages will be on Slackware ARM 14.1.<br /> <br /> <br /> <br /> === Installing Slackware ARM Packages Overo ===<br /> <br /> Once you have a bootable system, you can use “installpkg”, “removepkg” and “pkgtool” to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the “a” series installed. You can manually install the rest.<br /> <br /> In the installed system images that will be published for 13.37 and 14.1, packages from the “a”, “ap”, “d”, “l”, “n” and “x” sets are installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This HowTo will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone on KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with &quot;removepkg&quot; or &quot;pkgtool&quot; then install from the source to get the particular version you like.<br /> <br /> <br /> === Devices Tested So Far ===<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware:<br /> <br /> ==== Caspa Camera Unit / MT9V032 Sensor and Kernel Driver ====<br /> <br /> ===== Using Caspa With 2.6.34 Kernel =====<br /> <br /> Start with the Gumstix User Wiki page for the Caspa, here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, the Kernel Source tree has to come from Sakoman.com<br /> <br /> At http://www.Sakoman.com, select “Download” to get to the Git repo.<br /> <br /> Under &quot;projects/&quot;, select linux.git<br /> <br /> Under the &quot;heads&quot; section, click the ellipsis at the bottom of the page to expand the list. Click on &quot;omap3-2.6.34&quot; to browse the source tree.<br /> <br /> This code can be checked out in a manner similar to the Gumstix git repo:<br /> <br /> 1) First clone the “linux.git” repo located at http://www.Sakoman.com/git/<br /> <br /> git clone git://www.Sakoman.com/git/linux.git<br /> <br /> This will create a “linux” directory.<br /> <br /> 2) Then checkout the “omap3-2.6.34” branch, from within the “linux” directory:<br /> <br /> cd linux<br /> git checkout omap3-2.6.34<br /> <br /> You can then apply the patch and defconfig to this source tree to build the kernel per the instructions on the Gumstix Wiki page for the Caspa.<br /> <br /> <br /> ===== Using Caspa With 3.5.x Kernel =====<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from Gumstix, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work.<br /> <br /> Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its &quot;Pixel Format&quot;, or &quot;Color Space&quot; will be what is referred to as &quot;UYVY&quot;.<br /> <br /> The instructions for using &quot;yavta&quot; also work. &quot;yavta&quot; is simply: &quot;Yet Another Video4linux Test Application&quot;.<br /> <br /> Yavta will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the &quot;-pix_fmt&quot; option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the &quot;DISPLAY&quot; option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the &quot;LD_PRELOAD&quot; environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> <br /> <br /> ==== P54USB WiFi ====<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only.<br /> <br /> <br /> ==== WRL-11713 PCDuino WiFi Dongle ====<br /> <br /> From SparkFun.com – rt2800usb Works With HostAPD on Overo<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> This works in Kernel 3.5.x<br /> <br /> The command:<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id <br /> <br /> Must be used to bring up the interface. Make sure to get the firmware from the Ralink website.<br /> Tested with 5 Volts and 3.3 Volts.<br /> <br /> ==== LIS-331 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/10345 <br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> ==== MPU-6050 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/11028<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse the Gumstix GitHub repo. Look under &quot;meta-gumstix&quot;, and &quot;linux&quot;.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6053 2014-04-21T20:23:58Z

<p>BallCam: /* WRL-11713 PCDuino WiFi Dongle */</p> <hr /> <div>== 20 April 2014 ==<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working with kernels 2.6.34, and 3.5.7-yocto-standard.<br /> <br /> P54 USB and rt2800usb WiFi devices work in Host Mode with hostapd. WiFi generally works in non-host mode for several devices, including libertas.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> <br /> === Prerequisites ===<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can these from Gumstix web resources, or from the NAND of the device you purchase. <br /> <br /> It is assumed that you have experience using Slackware, on some other architecture.<br /> <br /> Software will need to be installed using &quot;configure&quot; and &quot;make&quot;, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> <br /> <br /> === Basic Installation Strategy: ===<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> <br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can &quot;cross-install&quot; that is, use an x86 based PC to run &quot;installpkg to install Slackware ARM packages to an SD card used as the rootfs of your device for most but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do &quot;cross-install&quot; successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using &quot;installpkg&quot;. It works fine. &quot;pkgtool&quot; also works, but may not work when using the miniroot unless a few more packages are installed. The miniroot has some but not all the &quot;a&quot; series packages installed.<br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. GCC and Make work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> <br /> <br /> === Building Your Own Kernel ===<br /> <br /> ==== Linux 3.5.x Kernel ====<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> <br /> <br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo:<br /> <br /> Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> <br /> <br /> ==== Linux 2.6.x Kernel ====<br /> <br /> The instructions for building a 2.6 series kernel for Gumstix can be found here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> Those instructions can be applied to kernel source obtained from Kernel.org, or Gumstix Resources.<br /> <br /> The main reason to build a 2.6 kernel is for Slackware ARM 13.37. However, Since Slackware ARM 13.37 is now end of life, <br /> the focus in these wiki pages will be on Slackware ARM 14.1.<br /> <br /> <br /> <br /> === Installing Slackware ARM Packages Overo ===<br /> <br /> Once you have a bootable system, you can use “installpkg”, “removepkg” and “pkgtool” to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the “a” series installed. You can manually install the rest.<br /> <br /> In the installed system images that will be published for 13.37 and 14.1, packages from the “a”, “ap”, “d”, “l”, “n” and “x” sets are installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This HowTo will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone on KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with &quot;removepkg&quot; or &quot;pkgtool&quot; then install from the source to get the particular version you like.<br /> <br /> <br /> === Devices Tested So Far ===<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware:<br /> <br /> ==== Caspa Camera Unit / MT9V032 Sensor and Kernel Driver ====<br /> <br /> ===== Using Caspa With 2.6.34 Kernel =====<br /> <br /> Start with the Gumstix User Wiki page for the Caspa, here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, the Kernel Source tree has to come from Sakoman.com<br /> <br /> At http://www.Sakoman.com, select “Download” to get to the Git repo.<br /> <br /> Under &quot;projects/&quot;, select linux.git<br /> <br /> Under the &quot;heads&quot; section, click the ellipsis at the bottom of the page to expand the list. Click on &quot;omap3-2.6.34&quot; to browse the source tree.<br /> <br /> This code can be checked out in a manner similar to the Gumstix git repo:<br /> <br /> 1) First clone the “linux.git” repo located at http://www.Sakoman.com/git/<br /> <br /> git clone git://www.Sakoman.com/git/linux.git<br /> <br /> This will create a “linux” directory.<br /> <br /> 2) Then checkout the “omap3-2.6.34” branch, from within the “linux” directory:<br /> <br /> cd linux<br /> git checkout omap3-2.6.34<br /> <br /> You can then apply the patch and defconfig to this source tree to build the kernel per the instructions on the Gumstix Wiki page for the Caspa.<br /> <br /> <br /> ===== Using Caspa With 3.5.x Kernel =====<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from Gumstix, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work.<br /> <br /> Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its &quot;Pixel Format&quot;, or &quot;Color Space&quot; will be what is referred to as &quot;UYVY&quot;.<br /> <br /> The instructions for using &quot;yavta&quot; also work. &quot;yavta&quot; is simply: &quot;Yet Another Video4linux Test Application&quot;.<br /> <br /> Yavta will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the &quot;-pix_fmt&quot; option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the &quot;DISPLAY&quot; option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the &quot;LD_PRELOAD&quot; environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> <br /> <br /> ==== P54USB WiFi ====<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only.<br /> <br /> <br /> ==== WRL-11713 PCDuino WiFi Dongle ====<br /> <br /> From SparkFun.com – rt2800usb<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> This works in Kernel 3.5.x<br /> <br /> The command:<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id <br /> <br /> Must be used to bring up the interface. Make sure to get the firmware from the Ralink website.<br /> Tested with 5 Volts and 3.3 Volts.<br /> <br /> ==== LIS-331 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/10345 <br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> ==== MPU-6050 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/11028<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse the Gumstix GitHub repo. Look under &quot;meta-gumstix&quot;, and &quot;linux&quot;.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6052 2014-04-21T20:21:33Z

<p>BallCam: </p> <hr /> <div>== 20 April 2014 ==<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working with kernels 2.6.34, and 3.5.7-yocto-standard.<br /> <br /> P54 USB and rt2800usb WiFi devices work in Host Mode with hostapd. WiFi generally works in non-host mode for several devices, including libertas.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> <br /> === Prerequisites ===<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can these from Gumstix web resources, or from the NAND of the device you purchase. <br /> <br /> It is assumed that you have experience using Slackware, on some other architecture.<br /> <br /> Software will need to be installed using &quot;configure&quot; and &quot;make&quot;, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> <br /> <br /> === Basic Installation Strategy: ===<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> <br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can &quot;cross-install&quot; that is, use an x86 based PC to run &quot;installpkg to install Slackware ARM packages to an SD card used as the rootfs of your device for most but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do &quot;cross-install&quot; successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using &quot;installpkg&quot;. It works fine. &quot;pkgtool&quot; also works, but may not work when using the miniroot unless a few more packages are installed. The miniroot has some but not all the &quot;a&quot; series packages installed.<br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. GCC and Make work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> <br /> <br /> === Building Your Own Kernel ===<br /> <br /> ==== Linux 3.5.x Kernel ====<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> <br /> <br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo:<br /> <br /> Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> <br /> <br /> ==== Linux 2.6.x Kernel ====<br /> <br /> The instructions for building a 2.6 series kernel for Gumstix can be found here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> Those instructions can be applied to kernel source obtained from Kernel.org, or Gumstix Resources.<br /> <br /> The main reason to build a 2.6 kernel is for Slackware ARM 13.37. However, Since Slackware ARM 13.37 is now end of life, <br /> the focus in these wiki pages will be on Slackware ARM 14.1.<br /> <br /> <br /> <br /> === Installing Slackware ARM Packages Overo ===<br /> <br /> Once you have a bootable system, you can use “installpkg”, “removepkg” and “pkgtool” to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the “a” series installed. You can manually install the rest.<br /> <br /> In the installed system images that will be published for 13.37 and 14.1, packages from the “a”, “ap”, “d”, “l”, “n” and “x” sets are installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This HowTo will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone on KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with &quot;removepkg&quot; or &quot;pkgtool&quot; then install from the source to get the particular version you like.<br /> <br /> <br /> === Devices Tested So Far ===<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware:<br /> <br /> ==== Caspa Camera Unit / MT9V032 Sensor and Kernel Driver ====<br /> <br /> ===== Using Caspa With 2.6.34 Kernel =====<br /> <br /> Start with the Gumstix User Wiki page for the Caspa, here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, the Kernel Source tree has to come from Sakoman.com<br /> <br /> At http://www.Sakoman.com, select “Download” to get to the Git repo.<br /> <br /> Under &quot;projects/&quot;, select linux.git<br /> <br /> Under the &quot;heads&quot; section, click the ellipsis at the bottom of the page to expand the list. Click on &quot;omap3-2.6.34&quot; to browse the source tree.<br /> <br /> This code can be checked out in a manner similar to the Gumstix git repo:<br /> <br /> 1) First clone the “linux.git” repo located at http://www.Sakoman.com/git/<br /> <br /> git clone git://www.Sakoman.com/git/linux.git<br /> <br /> This will create a “linux” directory.<br /> <br /> 2) Then checkout the “omap3-2.6.34” branch, from within the “linux” directory:<br /> <br /> cd linux<br /> git checkout omap3-2.6.34<br /> <br /> You can then apply the patch and defconfig to this source tree to build the kernel per the instructions on the Gumstix Wiki page for the Caspa.<br /> <br /> <br /> ===== Using Caspa With 3.5.x Kernel =====<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from Gumstix, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work.<br /> <br /> Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its &quot;Pixel Format&quot;, or &quot;Color Space&quot; will be what is referred to as &quot;UYVY&quot;.<br /> <br /> The instructions for using &quot;yavta&quot; also work. &quot;yavta&quot; is simply: &quot;Yet Another Video4linux Test Application&quot;.<br /> <br /> Yavta will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the &quot;-pix_fmt&quot; option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the &quot;DISPLAY&quot; option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the &quot;LD_PRELOAD&quot; environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> <br /> <br /> ==== P54USB WiFi ====<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only.<br /> <br /> <br /> ==== WRL-11713 PCDuino WiFi Dongle ====<br /> <br /> From SparkFun.com – rt2800usb<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> This works in Kernel 3.5.x<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id <br /> <br /> Must be used to bring up the interface. Make sure to get the firmware from the Ralink website.<br /> Tested with 5 Volts and 3.3 Volts.<br /> <br /> <br /> ==== LIS-331 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/10345 <br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> ==== MPU-6050 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/11028<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse the Gumstix GitHub repo. Look under &quot;meta-gumstix&quot;, and &quot;linux&quot;.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6051 2014-04-21T20:20:03Z

<p>BallCam: </p> <hr /> <div>== 20 April 2014 ==<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working with kernels 2.6.34, and 3.5.7-yocto-standard.<br /> <br /> P54 USB and rt2800usb WiFi devices work in Host Mode with hostapd. WiFi generally works in non-host mode for several devices, including libertas.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> <br /> === Prerequisites ===<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can these from Gumstix web resources, or from the NAND of the device you purchase. <br /> <br /> It is assumed that you have experience using Slackware, on some other architecture.<br /> <br /> Software will need to be installed using &quot;configure&quot; and &quot;make&quot;, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> <br /> <br /> === Basic Installation Strategy: ===<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> <br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can &quot;cross-install&quot; that is, use an x86 based PC to run &quot;installpkg to install Slackware ARM packages to an SD card used as the rootfs of your device for most but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do &quot;cross-install&quot; successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using &quot;installpkg&quot;. It works fine. &quot;pkgtool&quot; also works, but may not work when using the miniroot unless a few more packages are installed. The miniroot has some but not all the &quot;a&quot; series packages installed.<br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. GCC and Make work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> <br /> <br /> === Building Your Own Kernel ===<br /> <br /> ==== 3.5.x Series ====<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> <br /> <br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo:<br /> <br /> Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> <br /> <br /> ==== 2.6.x Series ====<br /> <br /> The instructions for building a 2.6 series kernel for Gumstix can be found here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> Those instructions can be applied to kernel source obtained from Kernel.org, or Gumstix Resources.<br /> <br /> The main reason to build a 2.6 kernel is for Slackware ARM 13.37. However, Since Slackware ARM 13.37 is now end of life, <br /> the focus in these wiki pages will be on Slackware ARM 14.1.<br /> <br /> <br /> <br /> === Installing Slackware ARM Packages Overo ===<br /> <br /> Once you have a bootable system, you can use “installpkg”, “removepkg” and “pkgtool” to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the “a” series installed. You can manually install the rest.<br /> <br /> In the installed system images that will be published for 13.37 and 14.1, packages from the “a”, “ap”, “d”, “l”, “n” and “x” sets are installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This HowTo will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone on KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with &quot;removepkg&quot; or &quot;pkgtool&quot; then install from the source to get the particular version you like.<br /> <br /> <br /> === Devices Tested So Far ===<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware:<br /> <br /> ==== Caspa Camera Unit / MT9V032 Sensor and Kernel Driver ====<br /> <br /> ===== Using Caspa With 2.6.34 Kernel =====<br /> <br /> Start with the Gumstix User Wiki page for the Caspa, here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, the Kernel Source tree has to come from Sakoman.com<br /> <br /> At http://www.Sakoman.com, select “Download” to get to the Git repo.<br /> <br /> Under &quot;projects/&quot;, select linux.git<br /> <br /> Under the &quot;heads&quot; section, click the ellipsis at the bottom of the page to expand the list. Click on &quot;omap3-2.6.34&quot; to browse the source tree.<br /> <br /> This code can be checked out in a manner similar to the Gumstix git repo:<br /> <br /> 1) First clone the “linux.git” repo located at http://www.Sakoman.com/git/<br /> <br /> git clone git://www.Sakoman.com/git/linux.git<br /> <br /> This will create a “linux” directory.<br /> <br /> 2) Then checkout the “omap3-2.6.34” branch, from within the “linux” directory:<br /> <br /> cd linux<br /> git checkout omap3-2.6.34<br /> <br /> You can then apply the patch and defconfig to this source tree to build the kernel per the instructions on the Gumstix Wiki page for the Caspa.<br /> <br /> <br /> ===== Using Caspa With 3.5.x Kernel =====<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from Gumstix, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work.<br /> <br /> Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its &quot;Pixel Format&quot;, or &quot;Color Space&quot; will be what is referred to as &quot;UYVY&quot;.<br /> <br /> The instructions for using &quot;yavta&quot; also work. &quot;yavta&quot; is simply: &quot;Yet Another Video4linux Test Application&quot;.<br /> <br /> Yavta will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the &quot;-pix_fmt&quot; option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the &quot;DISPLAY&quot; option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the &quot;LD_PRELOAD&quot; environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> <br /> <br /> ==== P54USB WiFi ====<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only.<br /> <br /> <br /> ==== WRL-11713 PCDuino WiFi Dongle ====<br /> <br /> From SparkFun.com – rt2800usb<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> This works in Kernel 3.5.x<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id <br /> <br /> Must be used to bring up the interface. Make sure to get the firmware from the Ralink website.<br /> Tested with 5 Volts and 3.3 Volts.<br /> <br /> <br /> ==== LIS-331 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/10345 <br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> ==== MPU-6050 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/11028<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse the Gumstix GitHub repo. Look under &quot;meta-gumstix&quot;, and &quot;linux&quot;.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6050 2014-04-21T20:16:00Z

<p>BallCam: </p> <hr /> <div>== 20 April 2014 ==<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working with kernels 2.6.34, and 3.5.7-yocto-standard.<br /> <br /> P54 USB and rt2800usb WiFi devices work in Host Mode with hostapd. WiFi generally works in non-host mode for several devices, including libertas.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> <br /> === Prerequisites ===<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can these from Gumstix web resources, or from the NAND of the device you purchase. <br /> <br /> It is assumed that you have experience using Slackware, on some other architecture.<br /> <br /> Software will need to be installed using &quot;configure&quot; and &quot;make&quot;, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> <br /> <br /> === Basic Installation Strategy: ===<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> <br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can &quot;cross-install&quot; that is, use an x86 based PC to run &quot;installpkg to install Slackware ARM packages to an SD card used as the rootfs of your device for most but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do &quot;cross-install&quot; successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using &quot;installpkg&quot;. It works fine. &quot;pkgtool&quot; also works, but may not work when using the miniroot unless a few more packages are installed. The miniroot has some but not all the &quot;a&quot; series packages installed.<br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. GCC and Make work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> <br /> <br /> === Building Your Own Kernel ===<br /> <br /> ==== 3.5.x Series ====<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> <br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo<br /> <br /> 1) Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> <br /> <br /> ==== 2.6.x Series ====<br /> <br /> The instructions for building a 2.6 series kernel for Gumstix can be found here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> Those instructions can be applied to kernel source obtained from Kernel.org, or Gumstix Resources.<br /> <br /> The main reason to build a 2.6 kernel is for Slackware ARM 13.37. However, Since Slackware ARM 13.37 is now end of life, <br /> the focus in these wiki pages will be on Slackware ARM 14.1.<br /> <br /> <br /> <br /> === Installing Slackware ARM Packages Overo ===<br /> <br /> Once you have a bootable system, you can use “installpkg”, “removepkg” and “pkgtool” to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the “a” series installed. You can manually install the rest.<br /> <br /> In the installed system images that will be published for 13.37 and 14.1, packages from the “a”, “ap”, “d”, “l”, “n” and “x” sets are installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This HowTo will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone on KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with &quot;removepkg&quot; or &quot;pkgtool&quot; then install from the source to get the particular version you like.<br /> <br /> <br /> === Devices Tested So Far ===<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware:<br /> <br /> ==== Caspa Camera Unit / MT9V032 Sensor and Kernel Driver ====<br /> <br /> ===== Using Caspa With 2.6.34 Kernel =====<br /> <br /> Start with the Gumstix User Wiki page for the Caspa, here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, the Kernel Source tree has to come from Sakoman.com<br /> <br /> At http://www.Sakoman.com, select “Download” to get to the Git repo.<br /> <br /> Under &quot;projects/&quot;, select linux.git<br /> <br /> Under the &quot;heads&quot; section, click the ellipsis at the bottom of the page to expand the list. Click on &quot;omap3-2.6.34&quot; to browse the source tree.<br /> <br /> This code can be checked out in a manner similar to the Gumstix git repo:<br /> <br /> 1) First clone the “linux.git” repo located at http://www.Sakoman.com/git/<br /> <br /> git clone git://www.Sakoman.com/git/linux.git<br /> <br /> This will create a “linux” directory.<br /> <br /> 2) Then checkout the “omap3-2.6.34” branch, from within the “linux” directory:<br /> <br /> cd linux<br /> git checkout omap3-2.6.34<br /> <br /> You can then apply the patch and defconfig to this source tree to build the kernel per the instructions on the Gumstix Wiki page for the Caspa.<br /> <br /> <br /> ===== Using Caspa With 3.5.x Kernel =====<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from Gumstix, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work.<br /> <br /> Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its &quot;Pixel Format&quot;, or &quot;Color Space&quot; will be what is referred to as &quot;UYVY&quot;.<br /> <br /> The instructions for using &quot;yavta&quot; also work. &quot;yavta&quot; is simply: &quot;Yet Another Video4linux Test Application&quot;.<br /> <br /> Yavta will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the &quot;-pix_fmt&quot; option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the &quot;DISPLAY&quot; option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the &quot;LD_PRELOAD&quot; environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> <br /> <br /> ==== P54USB WiFi ====<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only.<br /> <br /> <br /> ==== WRL-11713 PCDuino WiFi Dongle ====<br /> <br /> From SparkFun.com – rt2800usb<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> This works in Kernel 3.5.x<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id <br /> <br /> Must be used to bring up the interface. Make sure to get the firmware from the Ralink website.<br /> Tested with 5 Volts and 3.3 Volts.<br /> <br /> <br /> ==== LIS-331 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/10345 <br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> ==== MPU-6050 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/11028<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse the Gumstix GitHub repo. Look under &quot;meta-gumstix&quot;, and &quot;linux&quot;.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6049 2014-04-21T20:14:05Z

<p>BallCam: /* Devices Tested So Far */</p> <hr /> <div>== 20 April 2014 ==<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working with kernels 2.6.34, and 3.5.7-yocto-standard.<br /> <br /> P54 USB and rt2800usb WiFi devices work in Host Mode with hostapd. WiFi generally works in non-host mode for several devices, including libertas.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> <br /> === Prerequisites ===<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can these from Gumstix web resources, or from the NAND of the device you purchase. <br /> <br /> It is assumed that you have experience using Slackware, on some other architecture.<br /> <br /> Software will need to be installed using &quot;configure&quot; and &quot;make&quot;, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> <br /> <br /> === Basic Installation Strategy: ===<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> <br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can &quot;cross-install&quot; that is, use an x86 based PC to run &quot;installpkg to install Slackware ARM packages to an SD card used as the rootfs of your device for most but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do &quot;cross-install&quot; successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using &quot;installpkg&quot;. It works fine. &quot;pkgtool&quot; also works, but may not work when using the miniroot unless a few more packages are installed. The miniroot has some but not all the &quot;a&quot; series packages installed.<br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. GCC and Make work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> <br /> <br /> === Building Your Own Kernel ===<br /> <br /> ==== 3.5.x Series ====<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> <br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo<br /> <br /> 1) Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> <br /> <br /> ==== 2.6.x Series ====<br /> <br /> The instructions for building a 2.6 series kernel for Gumstix can be found here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> Those instructions can be applied to kernel source obtained from Kernel.org, or Gumstix Resources.<br /> <br /> The main reason to build a 2.6 kernel is for Slackware ARM 13.37. However, Since Slackware ARM 13.37 is now end of life, <br /> the focus in these wiki pages will be on Slackware ARM 14.1.<br /> <br /> <br /> <br /> === Installing Slackware ARM Packages Overo ===<br /> <br /> Once you have a bootable system, you can use “installpkg”, “removepkg” and “pkgtool” to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the “a” series installed. You can manually install the rest.<br /> <br /> In the installed system images that will be published for 13.37 and 14.1, packages from the “a”, “ap”, “d”, “l”, “n” and “x” sets are installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This HowTo will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone on KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with &quot;removepkg&quot; or &quot;pkgtool&quot; then install from the source to get the particular version you like.<br /> <br /> <br /> === Devices Tested So Far ===<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware:<br /> <br /> ==== Caspa Camera Unit / MT9V032 Sensor and Kernel Driver ====<br /> <br /> ===== Using Caspa With 2.6.34 Kernel =====<br /> <br /> Start with the Gumstix User Wiki page for the Caspa, here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, the Kernel Source tree has to come from Sakoman.com<br /> <br /> At http://www.Sakoman.com, select “Download” to get to the Git repo.<br /> <br /> Under &quot;projects/&quot;, select linux.git<br /> <br /> Under the &quot;heads&quot; section, click the ellipsis at the bottom of the page to expand the list. Click on &quot;omap3-2.6.34&quot; to browse the source tree.<br /> <br /> This code can be checked out in a manner similar to the Gumstix git repo:<br /> <br /> 1) First clone the “linux.git” repo located at http://www.Sakoman.com/git/<br /> <br /> git clone git://www.Sakoman.com/git/linux.git<br /> <br /> This will create a “linux” directory.<br /> <br /> 2) Then checkout the “omap3-2.6.34” branch, from within the “linux” directory:<br /> <br /> cd linux<br /> git checkout omap3-2.6.34<br /> <br /> You can then apply the patch and defconfig to this source tree to build the kernel per the instructions on the Gumstix Wiki page for the Caspa.<br /> <br /> <br /> ===== Using Caspa With 3.5.x Kernel =====<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from Gumstix, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work.<br /> <br /> Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its &quot;Pixel Format&quot;, or &quot;Color Space&quot; will be what is referred to as &quot;UYVY&quot;.<br /> <br /> The instructions for using &quot;yavta&quot; also work. &quot;yavta&quot; is simply: &quot;Yet Another Video4linux Test Application&quot;.<br /> <br /> Yavta will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the &quot;-pix_fmt&quot; option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the &quot;DISPLAY&quot; option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the &quot;LD_PRELOAD&quot; environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> <br /> <br /> ==== P54USB WiFi ====<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only.<br /> <br /> <br /> ==== WRL-11713 PCDuino WiFi Dongle ====<br /> <br /> From SparkFun.com – rt2800usb<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> This works in Kernel 3.5.x<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id <br /> <br /> Must be used to bring up the interface. Make sure to get the firmware from the Ralink website.<br /> Tested with 5 Volts and 3.3 Volts.<br /> <br /> <br /> ==== LIS-331 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/10345 <br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> ==== MPU-6050 Accelerometer ====<br /> <br /> https://www.sparkfun.com/products/11028<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse the Gumstix GitHub repo. Look under &quot;meta-gumstix&quot;, and &quot;linux&quot;.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6048 2014-04-21T19:52:59Z

<p>BallCam: </p> <hr /> <div>== 20 April 2014 ==<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working with kernels 2.6.34, and 3.5.7-yocto-standard.<br /> <br /> P54 USB and rt2800usb WiFi devices work in Host Mode with hostapd. WiFi generally works in non-host mode for several devices, including libertas.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> <br /> === Prerequisites ===<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can these from Gumstix web resources, or from the NAND of the device you purchase. <br /> <br /> It is assumed that you have experience using Slackware, on some other architecture.<br /> <br /> Software will need to be installed using &quot;configure&quot; and &quot;make&quot;, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> <br /> <br /> === Basic Installation Strategy: ===<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> <br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can &quot;cross-install&quot; that is, use an x86 based PC to run &quot;installpkg to install Slackware ARM packages to an SD card used as the rootfs of your device for most but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do &quot;cross-install&quot; successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using &quot;installpkg&quot;. It works fine. &quot;pkgtool&quot; also works, but may not work when using the miniroot unless a few more packages are installed. The miniroot has some but not all the &quot;a&quot; series packages installed.<br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. GCC and Make work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> <br /> <br /> === Building Your Own Kernel ===<br /> <br /> ==== 3.5.x Series ====<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> <br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo<br /> <br /> 1) Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> <br /> <br /> ==== 2.6.x Series ====<br /> <br /> The instructions for building a 2.6 series kernel for Gumstix can be found here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> Those instructions can be applied to kernel source obtained from Kernel.org, or Gumstix Resources.<br /> <br /> The main reason to build a 2.6 kernel is for Slackware ARM 13.37. However, Since Slackware ARM 13.37 is now end of life, <br /> the focus in these wiki pages will be on Slackware ARM 14.1.<br /> <br /> <br /> <br /> === Installing Slackware ARM Packages Overo ===<br /> <br /> Once you have a bootable system, you can use “installpkg”, “removepkg” and “pkgtool” to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the “a” series installed. You can manually install the rest.<br /> <br /> In the installed system images that will be published for 13.37 and 14.1, packages from the “a”, “ap”, “d”, “l”, “n” and “x” sets are installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This HowTo will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone on KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with &quot;removepkg&quot; or &quot;pkgtool&quot; then install from the source to get the particular version you like.<br /> <br /> <br /> === Devices Tested So Far ===<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware.<br /> ==== Caspa Camera Unit / MT9V032 Sensor and Kernel Driver ====<br /> <br /> ===== Using Caspa With 2.6.34 Kernel =====<br /> <br /> Start with the Gumstix User Wiki page here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, the Kernel Source tree has to come from Sakoman.com<br /> <br /> At http://www.Sakoman.com, select “Download” to get to the Git repo.<br /> <br /> Under &quot;projects/&quot;, select linux.git<br /> <br /> Under the &quot;heads&quot; section, click the ellipsis at the bottom of the page to expand the list. Click on &quot;omap3-2.6.34&quot; to browse the source tree.<br /> <br /> This code can be checked out in a manner similar to the Gumstix git repo:<br /> <br /> 1) First clone the “linux.git” repo located at http://www.sakoman.com/git/<br /> <br /> git clone git://www.sakoman.com/git/linux.git<br /> <br /> This will create a “linux” directory.<br /> <br /> 2) Then checkout the “omap3-2.6.34” branch, from within the “linux” directory:<br /> <br /> cd linux<br /> git checkout omap3-2.6.34<br /> <br /> You can then apply the patch and defconfig to this source tree to build the kernel per the instructions on the Gumstix Wiki page for the Caspa.<br /> <br /> <br /> ===== Using Caspa With 3.5.x Kernel =====<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from them, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work. <br /> Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its &quot;Pixel Format&quot;, or &quot;Color Space&quot; will be what is referred to as UYVY.<br /> <br /> The instructions for using “yavta” also work. “yavta” is simply: “Yet Another Video4linux Test Application”<br /> <br /> This program will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the ”-pix_fmt” option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the “DISPLAY” option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the “LD_PRELOAD” environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> ==== P54USB WiFi ====<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only.<br /> <br /> ==== WRL-11713 PCDuino WiFi Dongle ====<br /> <br /> From SparkFun.com – rt2800usb<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> This works in Kernel 3.5.x<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id <br /> <br /> Must be used to bring up the interface. Make sure to get the firmware from the Ralink website.<br /> Tested with 5 Volts and 3.3 Volts.<br /> <br /> ==== LIS-331 Accelerometer ====<br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> ==== MPU-6050 Accelerometer ====<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> Resources will be posted here:<br /> <br /> http://slackware.org.uk/slackwarearm/people/ballcam/<br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse their GitHub repo. Look under “meta-gumstix”, and “linux”.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6047 2014-04-21T19:11:04Z

<p>BallCam: </p> <hr /> <div>== 20 April 2014 ==<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working with kernels 2.6.34, and 3.5.7-yocto-standard.<br /> <br /> P54 USB and rt2800usb WiFi devices work in Host Mode with hostapd. WiFi generally works in non-host mode for several devices, including libertas.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> <br /> === Prerequisites ===<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can these from Gumstix web resources, or from the NAND of the device you purchase. <br /> <br /> It is assumed that you have experience using Slackware, on some other architecture.<br /> <br /> Software will need to be installed using &quot;configure&quot; and &quot;make&quot;, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> <br /> <br /> === Basic Installation Strategy: ===<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> <br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can &quot;cross-install&quot; that is, use an x86 based PC to run &quot;installpkg to install Slackware ARM packages to an SD card used as the rootfs of your device for most but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do &quot;cross-install&quot; successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using &quot;installpkg&quot;. It works fine. &quot;pkgtool&quot; also works, but may not work when using the miniroot unless a few more packages are installed. The miniroot has some but not all the &quot;a&quot; series packages installed.<br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. GCC and Make work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> <br /> <br /> === Building Your Own Kernel ===<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> <br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo<br /> <br /> 1) Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> Once you have a bootable system, you can use “installpkg”, “removepkg” and “pkgtool” to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the “a” series installed. You can manually install the rest.<br /> <br /> In the installed system images that will be published for 13.37 and 14.1, packages from the “a”, “ap”, “d”, “l”, “n” and “x” sets are installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This HowTo will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone on KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with &quot;removepkg&quot; or &quot;pkgtool&quot; then install from the source to get the particular version you like.<br /> <br /> === Devices Tested So Far ===<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware.<br /> ==== Caspa Camera Unit / MT9V032 Sensor and Kernel Driver ====<br /> <br /> ===== Using Caspa With 2.6.34 Kernel =====<br /> <br /> Start with the Gumstix User Wiki page here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, the Kernel Source tree has to come from Sakoman.com<br /> <br /> At http://www.Sakoman.com, select “Download” to get to the Git repo.<br /> <br /> Under &quot;projects/&quot;, select linux.git<br /> <br /> Under the &quot;heads&quot; section, click the ellipsis at the bottom of the page to expand the list. Click on &quot;omap3-2.6.34&quot; to browse the source tree.<br /> <br /> This code can be checked out in a manner similar to the Gumstix git repo:<br /> <br /> 1) First clone the “linux.git” repo located at http://www.sakoman.com/git/<br /> <br /> git clone git://www.sakoman.com/git/linux.git<br /> <br /> This will create a “linux” directory.<br /> <br /> 2) Then checkout the “omap3-2.6.34” branch, from within the “linux” directory:<br /> <br /> cd linux<br /> git checkout omap3-2.6.34<br /> <br /> You can then apply the patch and defconfig to this source tree to build the kernel per the instructions on the Gumstix Wiki page for the Caspa.<br /> <br /> <br /> ===== Using Caspa With 3.5.x Kernel =====<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from them, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work. <br /> Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its &quot;Pixel Format&quot;, or &quot;Color Space&quot; will be what is referred to as UYVY.<br /> <br /> The instructions for using “yavta” also work. “yavta” is simply: “Yet Another Video4linux Test Application”<br /> <br /> This program will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the ”-pix_fmt” option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the “DISPLAY” option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the “LD_PRELOAD” environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> ==== P54USB WiFi ====<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only.<br /> <br /> ==== WRL-11713 PCDuino WiFi Dongle ====<br /> <br /> From SparkFun.com – rt2800usb<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> This works in Kernel 3.5.x<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id <br /> <br /> Must be used to bring up the interface. Make sure to get the firmware from the Ralink website.<br /> Tested with 5 Volts and 3.3 Volts.<br /> <br /> ==== LIS-331 Accelerometer ====<br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> ==== MPU-6050 Accelerometer ====<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> Resources will be posted here:<br /> <br /> http://slackware.org.uk/slackwarearm/people/ballcam/<br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse their GitHub repo. Look under “meta-gumstix”, and “linux”.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6046 2014-04-21T19:01:43Z

<p>BallCam: </p> <hr /> <div>== 20 April 2014 ==<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working along with at least one USB WiFi device in Host Mode with hostapd. WiFi generally works in non-host mode for several devices.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> Prerequisites<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can obtain each of these from their website, or from the NAND of the device. As this work progresses, pre-built Kernels and modules will be posted here.<br /> <br /> Likewise it is assumed that you have experience with Slackware, on some other Architecture.<br /> <br /> Software will need to be installed using &quot;configure&quot; and &quot;make&quot;, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> <br /> === Basic Installation Strategy: ===<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> <br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can “cross-install” that is, use an x86 based PC to run “installpkg” to install Slackware ARM packages to an SD card used as the rootfs of your device for most but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do “cross-install” successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using “installpkg”. It works fine. “pkgtool” also works, but may not work when using the miniroot unless a few more packages are installed. The miniroot has some but not all the “a” series packages installed.<br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. GCC and Make work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> <br /> <br /> === Building Your Own Kernel ===<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> <br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo<br /> <br /> 1) Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> Once you have a bootable system, you can use “installpkg”, “removepkg” and “pkgtool” to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the “a” series installed. You can manually install the rest.<br /> <br /> In the installed system images that will be published for 13.37 and 14.1, packages from the “a”, “ap”, “d”, “l”, “n” and “x” sets are installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This HowTo will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone on KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with &quot;removepkg&quot; or &quot;pkgtool&quot; then install from the source to get the particular version you like.<br /> <br /> === Devices Tested So Far ===<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware.<br /> ==== Caspa Camera Unit / MT9V032 Sensor and Kernel Driver ====<br /> <br /> ===== Using Caspa With 2.6.34 Kernel =====<br /> <br /> Start with the Gumstix User Wiki page here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, the Kernel Source tree has to come from Sakoman.com<br /> <br /> At http://www.Sakoman.com, select “Download” to get to the Git repo.<br /> <br /> Under &quot;projects/&quot;, select linux.git<br /> <br /> Under the &quot;heads&quot; section, click the ellipsis at the bottom of the page to expand the list. Click on &quot;omap3-2.6.34&quot; to browse the source tree.<br /> <br /> This code can be checked out in a manner similar to the Gumstix git repo:<br /> <br /> 1) First clone the “linux.git” repo located at http://www.sakoman.com/git/<br /> <br /> git clone git://www.sakoman.com/git/linux.git<br /> <br /> This will create a “linux” directory.<br /> <br /> 2) Then checkout the “omap3-2.6.34” branch, from within the “linux” directory:<br /> <br /> cd linux<br /> git checkout omap3-2.6.34<br /> <br /> You can then apply the patch and defconfig to this source tree to build the kernel per the instructions on the Gumstix Wiki page for the Caspa.<br /> <br /> <br /> ===== Using Caspa With 3.5.x Kernel =====<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from them, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work. <br /> Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its &quot;Pixel Format&quot;, or &quot;Color Space&quot; will be what is referred to as UYVY.<br /> <br /> The instructions for using “yavta” also work. “yavta” is simply: “Yet Another Video4linux Test Application”<br /> <br /> This program will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the ”-pix_fmt” option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the “DISPLAY” option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the “LD_PRELOAD” environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> ==== P54USB WiFi ====<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only.<br /> <br /> ==== WRL-11713 PCDuino WiFi Dongle ====<br /> <br /> From SparkFun.com – rt2800usb<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> This works in Kernel 3.5.x<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id <br /> <br /> Must be used to bring up the interface. Make sure to get the firmware from the Ralink website.<br /> Tested with 5 Volts and 3.3 Volts.<br /> <br /> ==== LIS-331 Accelerometer ====<br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> ==== MPU-6050 Accelerometer ====<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> Resources will be posted here:<br /> <br /> http://slackware.org.uk/slackwarearm/people/ballcam/<br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse their GitHub repo. Look under “meta-gumstix”, and “linux”.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6045 2014-04-21T18:48:24Z

<p>BallCam: </p> <hr /> <div>20 April 2014<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working along with at least one USB WiFi device in Host Mode with hostapd. WiFi generally works in non-host mode for several devices.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> Prerequisites<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can obtain each of these from their website, or from the NAND of the device. As this work progresses, pre-built Kernels and modules will be posted here.<br /> <br /> Likewise it is assumed that you have experience with Slackware, on some other Architecture.<br /> <br /> Software will need to be installed using &quot;configure&quot; and &quot;make&quot;, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> <br /> Basic Installation Strategy:<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can “cross-install” that is, use an x86 based PC to run “installpkg” to install Slackware ARM packages to an SD card used as the rootfs of your device for most but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do “cross-install” successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using “installpkg”. It works fine. “pkgtool” also works, but may not work when using the miniroot unless a few more packages are installed. The miniroot has some but not all the “a” series packages installed.<br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. GCC and Make work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> Building Your Own Kernel<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> <br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo<br /> <br /> 1) Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> Once you have a bootable system, you can use “installpkg”, “removepkg” and “pkgtool” to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the “a” series installed. You can manually install the rest.<br /> <br /> In the installed system images that will be published for 13.37 and 14.1, packages from the “a”, “ap”, “d”, “l”, “n” and “x” sets are installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This HowTo will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone on KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with &quot;removepkg&quot; or &quot;pkgtool&quot; then install from the source to get the particular version you like.<br /> <br /> Devices Tested So Far<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware.<br /> Caspa Camera Unit / MT9V032 Sensor and Kernel Driver<br /> <br /> 2.6.34 Kernel<br /> <br /> Start with the Gumstix User Wiki page here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, the Kernel Source tree has to come from Sakoman.com<br /> <br /> At http://www.Sakoman.com, select “Download” to get to the Git repo.<br /> <br /> Under &quot;projects/&quot;, select linux.git<br /> <br /> Under the &quot;heads&quot; section, click the ellipsis at the bottom of the page to expand the list. Click on &quot;omap3-2.6.34&quot; to browse the source tree.<br /> <br /> This code can be checked out in a manner similar to the Gumstix git repo:<br /> <br /> 1) First clone the “linux.git” repo located at http://www.sakoman.com/git/<br /> <br /> git clone git://www.sakoman.com/git/linux.git<br /> <br /> This will create a “linux” directory.<br /> <br /> 2) Then checkout the “omap3-2.6.34” branch, from within the “linux” directory:<br /> <br /> cd linux<br /> <br /> git checkout omap3-2.6.34<br /> <br /> You can then apply the patch and defconfig to this source tree to build the kernel per the instructions on the Gumstix Wiki page for the Caspa.<br /> <br /> 3.5.x Kernel<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from them, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work. <br /> Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its &quot;Pixel Format&quot;, or &quot;Color Space&quot; will be what is referred to as UYVY.<br /> <br /> The instructions for using “yavta” also work. “yavta” is simply: “Yet Another Video4linux Test Application”<br /> <br /> This program will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the ”-pix_fmt” option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the “DISPLAY” option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the “LD_PRELOAD” environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> P54USB WiFi<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only.<br /> WRL-11713 PCDuino WiFi Dongle<br /> <br /> From SparkFun.com – rt2800usb<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> This works in Kernel 3.5.x<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id must be used to bring up the interface. Make sure to get the firmware from the Ralink website.<br /> <br /> Tested with 5 Volts and 3.3 Volts.<br /> LIS-331 Accelerometer<br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> MPU-6050 Accelerometer<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> Resources will be posted here:<br /> <br /> http://slackware.org.uk/slackwarearm/people/ballcam/<br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse their GitHub repo. Look under “meta-gumstix”, and “linux”.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6044 2014-04-21T18:41:42Z

<p>BallCam: </p> <hr /> <div>20 April 2014<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working along with at least one USB WiFi device in Host Mode with hostapd. WiFi generally works in non-host mode for several devices.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> Prerequisites<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, <br /> or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can obtain each of these from their website, or from the NAND of the device. As this work progresses, pre-built Kernels and modules will be posted here.<br /> <br /> Likewise it is assumed that you have experience with Slackware, on some other Architecture.<br /> <br /> Software will need to be installed using “configure” and “make”, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> Basic Installation Strategy:<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can “cross-install” that is, use an x86 based PC to run “installpkg” to install Slackware ARM packages to an SD card used as the rootfs of your device for most but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do “cross-install” successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using “installpkg”. It works fine. “pkgtool” also works, but may not work when using the miniroot unless a few more packages are installed. The miniroot has some but not all the “a” series packages installed.<br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. GCC and Make work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> Building Your Own Kernel<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo<br /> <br /> 1) Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> Once you have a bootable system, you can use “installpkg”, “removepkg” and “pkgtool” to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the “a” series installed. You can manually install the rest.<br /> <br /> In the installed system images that will be published for 13.37 and 14.1, packages from the “a”, “ap”, “d”, “l”, “n” and “x” sets are installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This HowTo will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone on KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with “removepkg” or “pkgtool” then install from the source to get the particular version you like.<br /> Devices Tested So Far<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware.<br /> Caspa Camera Unit / MT9V032 Sensor and Kernel Driver<br /> 2.6.34 Kernel<br /> <br /> Start with the Gumstix User Wiki page here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, the Kernel Source tree has to come from Sakoman.com<br /> <br /> At http://www.Sakoman.com, select “Download” to get to the Git repo.<br /> <br /> Under “projects/”, select linux.git<br /> <br /> Under the “heads” section, click the ellipsis at the bottom of the page to expand the list. Click on “omap3-2.6.34” to browse the source tree.<br /> <br /> This code can be checked out in a manner similar to the Gumstix git repo:<br /> <br /> 1) First clone the “linux.git” repo located at http://www.sakoman.com/git/<br /> <br /> git clone git://www.sakoman.com/git/linux.git<br /> <br /> This will create a “linux” directory.<br /> <br /> 2) Then checkout the “omap3-2.6.34” branch, from within the “linux” directory:<br /> <br /> cd linux<br /> <br /> git checkout omap3-2.6.34<br /> <br /> You can then apply the patch and defconfig to this source tree to build the kernel per the instructions on the Gumstix Wiki page for the Caspa.<br /> 3.5.x Kernel<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from them, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work. Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its “Pixel Format”, or “Color Space” will be what is referred to as UYVY.<br /> <br /> The instructions for using “yavta” also work. “yavta” is simply: “Yet Another Video4linux Test Application”<br /> <br /> This program will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the ”-pix_fmt” option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the “DISPLAY” option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the “LD_PRELOAD” environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> P54USB WiFi<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only.<br /> WRL-11713 PCDuino WiFi Dongle<br /> <br /> From SparkFun.com – rt2800usb<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> This works in Kernel 3.5.x<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id must be used to bring up the interface. Make sure to get the firmware from the Ralink website.<br /> <br /> Tested with 5 Volts and 3.3 Volts.<br /> LIS-331 Accelerometer<br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> MPU-6050 Accelerometer<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> Resources will be posted here:<br /> <br /> http://slackware.org.uk/slackwarearm/people/ballcam/<br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse their GitHub repo. Look under “meta-gumstix”, and “linux”.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_On_Gumstix_Overo&diff=6043 2014-04-21T18:40:22Z

<p>BallCam: Created page with &quot;20 April 2014 Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more. The Caspa ca...&quot;</p> <hr /> <div>20 April 2014<br /> <br /> Both Slackware 13.37 and 14.1 have been successfully installed on Gumstix Overo Products, and used for application development, web service and more.<br /> <br /> The Caspa camera unit is working along with at least one USB WiFi device in Host Mode with hostapd. WiFi generally works in non-host mode for several devices.<br /> <br /> This is a preliminary report. How To actually accomplish all of the above will be posted here in this work in progress.<br /> Prerequisites<br /> <br /> In order to take full advantage of Slackware on Gumstix, at the current time, you will need to know how to build your own Kernel for Gumstix products, or at least obtain a pre-built one from them, and install it on an SD card. Likewise for the Kernel modules.<br /> <br /> You can obtain each of these from their website, or from the NAND of the device. As this work progresses, pre-built Kernels and modules will be posted here.<br /> <br /> Likewise it is assumed that you have experience with Slackware, on some other Architecture.<br /> <br /> Software will need to be installed using “configure” and “make”, but so far lots of software tested installs just fine as such. That information will likewise be posted here.<br /> Basic Installation Strategy:<br /> <br /> 1) Use a 2.6 series kernel for Slackware 13.37.<br /> <br /> 2) Use a 3.x Series kernel for Slackware 14.1<br /> <br /> 3) Set u-boot variables as needed. (console, mmcroot, mmcrootfstype)<br /> <br /> 4) Modify scripts under /etc/rc.d for fastest boot. This and the Kernel is where most of the changes are made to get Slackware working on Gumstix.<br /> <br /> 5) Arrange module loading for best stability (mt9v032, Wifi).<br /> <br /> 6) Re-Compile kernel to meet your particular setup.<br /> <br /> The Kernel and Modules from Gumstix distros, or that is used in NAND, can be used to boot a Slackware install.<br /> <br /> The miniroot that is provided by Slackware works with Gumstix Kernel and Modules.<br /> <br /> You can “cross-install” that is, use an x86 based PC to run “installpkg” to install Slackware ARM packages to an SD card used as the rootfs of your device for most but not all Slackware Packages.<br /> <br /> Some Slackware packages run scripts that call binaries that will not work because of CPU mismatch. The Slackware packages that only run shell commands, or just extract the files, do “cross-install” successfully.<br /> <br /> You can install Slackware packages when booted into your Gumstix Device, using “installpkg”. It works fine. “pkgtool” also works, but may not work when using the miniroot unless a few more packages are installed. The miniroot has some but not all the “a” series packages installed.<br /> <br /> After Slackware is installed on a Gumstix Overo, it can be used very much like Slackware on any PC. GCC and Make work to install software, you can run Apache, Asterisk, FFMPEG and more.<br /> Building Your Own Kernel<br /> <br /> The instructions for building a 3.5 series kernel for Gumstix Overo, using the Yocto Project, are Here:<br /> <br /> https://github.com/gumstix/Gumstix-YoctoProject-Repo<br /> <br /> An overview of the BitBake Setup for Gumstix is here:<br /> <br /> http://gumstix.org/software-development/yocto-project.html<br /> Getting The Kernel Source For Building Custom Kernels on Gumstix Overo<br /> <br /> 1) Use the Yocto Setup explained above. Its not too difficult.<br /> <br /> Probably the most important things to know are:<br /> <br /> a) Do not use it as root.<br /> <br /> b) Make your life easy. Set up a separate user account to build using the yocto project. Yocto relies on a custom-set environment. When a repo is set up in a directory, if the directory name is changed it will break build scripts. Figure out a naming convention to manage multiple “repo” downloads. Running bitbake will notify you of any missing dependencies that you may need to install. They can be installed from source on your build system, or possibly installed form Slackware Packages.<br /> <br /> c) Under your build directory is a conf directory where you can place an empty “sanity.conf” file to tell the build system that you passed.<br /> <br /> After you run BitBake to build a kernel, the patched kernel source will be under the build directory. The patches themselves will also be there. Look under the build/work directory for various source used. The kernel source that is used to build the kernel can be found under:<br /> <br /> build/tmp/sysroots/overo/usr/src/kernel<br /> <br /> Look for the kernel's .config file. You can use the source under this directory to cross-compile using your own setup to build bootable kernels like those used in the Gumstix NAND, but with your own customizations.<br /> <br /> The kernel source under this directory has the patches from under the build/work directory applied.<br /> <br /> Once you have a bootable system, you can use “installpkg”, “removepkg” and “pkgtool” to install individual packages.<br /> <br /> The miniroot currently published does not have all the packages from the “a” series installed. You can manually install the rest.<br /> <br /> In the installed system images that will be published for 13.37 and 14.1, packages from the “a”, “ap”, “d”, “l”, “n” and “x” sets are installed.<br /> <br /> Kernel source is obtained as per above, and packages for emacs, faq, KDE Tex, TCL and Games can be installed if you like.<br /> <br /> This HowTo will attempt at least to use the X Windows system, but not with KDE. FVWM and XFCE will be attempted. Best of luck to anyone on KDE.<br /> <br /> As you use your Slackware on a Gumstix Overo Based Device to build code natively, you may have to install various library dependencies from source. If there is a Slackware package for the same library, you can uninstall that package with “removepkg” or “pkgtool” then install from the source to get the particular version you like.<br /> Devices Tested So Far<br /> <br /> Below is a short list of devices tested with a Gumstix Overo based system running Slackware.<br /> Caspa Camera Unit / MT9V032 Sensor and Kernel Driver<br /> 2.6.34 Kernel<br /> <br /> Start with the Gumstix User Wiki page here:<br /> <br /> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards<br /> <br /> This setup works with FFMPEG, using /dev/video0.<br /> <br /> In order to build the 2.6.34 kernel from source for use with the Caspa, the Kernel Source tree has to come from Sakoman.com<br /> <br /> At http://www.Sakoman.com, select “Download” to get to the Git repo.<br /> <br /> Under “projects/”, select linux.git<br /> <br /> Under the “heads” section, click the ellipsis at the bottom of the page to expand the list. Click on “omap3-2.6.34” to browse the source tree.<br /> <br /> This code can be checked out in a manner similar to the Gumstix git repo:<br /> <br /> 1) First clone the “linux.git” repo located at http://www.sakoman.com/git/<br /> <br /> git clone git://www.sakoman.com/git/linux.git<br /> <br /> This will create a “linux” directory.<br /> <br /> 2) Then checkout the “omap3-2.6.34” branch, from within the “linux” directory:<br /> <br /> cd linux<br /> <br /> git checkout omap3-2.6.34<br /> <br /> You can then apply the patch and defconfig to this source tree to build the kernel per the instructions on the Gumstix Wiki page for the Caspa.<br /> 3.5.x Kernel<br /> <br /> Use Yocto per the Gumstix Instructions, or if you have a very recent device from them, it may have a 3.5.x Kernel in NAND.<br /> <br /> The Instructions posted on the various forums regarding using media-ctl do work. Basically and most important is to understand that /dev/video6 is the device to get your video from, and that its “Pixel Format”, or “Color Space” will be what is referred to as UYVY.<br /> <br /> The instructions for using “yavta” also work. “yavta” is simply: “Yet Another Video4linux Test Application”<br /> <br /> This program will capture an image successfully from the Caspa and save it as a raw UYVY image. FFMPEG can then be used to convert this to other formats. use the ”-pix_fmt” option to ffmpeg.<br /> <br /> MPlayer also works to play live video. If you are using a graphical desktop, it should work as in any other. You can use the HDMI on a Gumstix Tobi to drive your monitor.<br /> <br /> You can also export the display of MPLayer across a network, make sure to export the “DISPLAY” option correctly, and use “xhost +” on your desktop.<br /> <br /> MPlayer may show black video the first time it is called for some reason, but it does ultimately display live streaming video.<br /> <br /> You may need to set the “LD_PRELOAD” environment variable in the MPLayer command line. See the various forums on the Internet regarding this.<br /> P54USB WiFi<br /> <br /> P54USB WiFi – Prism54 USB Wifi Dongle. Works with HostAPD. 5 Volts Only.<br /> WRL-11713 PCDuino WiFi Dongle<br /> <br /> From SparkFun.com – rt2800usb<br /> <br /> https://www.sparkfun.com/products/11713<br /> <br /> This works in Kernel 3.5.x<br /> <br /> echo '148f 5370' &gt; /sys/bus/usb/drivers/rt2800usb/new_id must be used to bring up the interface. Make sure to get the firmware from the Ralink website.<br /> <br /> Tested with 5 Volts and 3.3 Volts.<br /> LIS-331 Accelerometer<br /> <br /> LIS-331 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> MPU-6050 Accelerometer<br /> <br /> MPU-6050 Accelerometer. Works with I2C. Typically 3.3 Volts, or 5 Volts with level shifters on SDA/SCL lines.<br /> <br /> Resources will be posted here:<br /> <br /> http://slackware.org.uk/slackwarearm/people/ballcam/<br /> <br /> Gumstix publishes its Kernel source here:<br /> <br /> http://gumstix.org/access-source-code.html<br /> <br /> You can also browse their GitHub repo. Look under “meta-gumstix”, and “linux”.</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_14.1_On_Gumstix_Overo&diff=6042 2014-04-21T18:38:55Z

<p>BallCam: </p> <hr /> <div> 20 April 2014<br /> <br /> Slackware 14.1 has been installed on Gumstix Overo Devices and used succesfully with their expansion boards, with a 3.5 series kernel, built with Yocto, and BitBake.<br /> <br /> Slackware packages install, and software built with &quot;configure&quot; and &quot;make&quot; also install and run.<br /> <br /> GUI Has not yet been tested. In Progress.<br /> <br /> The majority of focus will be placed on Installing, Running, and Developing Slackware 14.1 on Gumstix as Slackware 13.37 is End Of Life, and the 3.5.x Kernels built with Yocto, and provided by Gumstix support enough devices.<br /> Using The Caspa / MT9V032 Sensor With Slackware 14.1 On Gumstix Overo<br /> <br /> Make sure to use a 3.5 series kernel built with Yocto and Bitbake per Gumstix' instructions. At least 3.5.7. When purchasing your device you may be able to request they flash the NAND with an appropriate kernel.<br /> Using The P54USB WiFi With Slackware 14.1 On Gumstix Overo<br /> <br /> This may be enabled by default in a Yocto kernel. It supports Hot AP mode. Needs 5 Volts.<br /> Using The rt2800usb USB WiFi With Slackware 14.1 On Gumstix Overo <br /> <br /> This likewise may be built in by default in a Yocto kernel. Works at both 3.3 and 5 volts.<br /> Using The LIS331 3-Axis Accelerometer With Slackware 14.1 On Gumstix Overo<br /> <br /> This is an I2C device. Level Shifters may be needed on the SDA and SCL lines when your system voltage is above 3.3 Volts.<br /> Using The MPU-6050 3-Axis Accelerometer With Slackware 14.1 On Gumstix Overo<br /> <br /> This is an I2C device. Level Shifters may be needed on the SDA and SCL lines when your system voltage is above 3.3 Volts.<br /> Sources</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_14.1_On_Gumstix_Overo&diff=6041 2014-04-21T18:37:27Z

<p>BallCam: Created page with &quot; 20 April 2014 Slackware 14.1 has been installed on Gumstix Overo Devices and used succesfully with their expansion boards, with a 3.5 series kernel, built with Yocto...&quot;</p> <hr /> <div> 20 April 2014<br /> <br /> Slackware 14.1 has been installed on Gumstix Overo Devices and used succesfully with their expansion boards, with a 3.5 series kernel, built with Yocto, and BitBake.<br /> <br /> Slackware packages install, and software built with &quot;configure&quot; and &quot;make&quot; also install and run.<br /> <br /> GUI Has not yet been tested. In Progress.<br /> <br /> The majority of focus will be placed on Installing, Running, and Developing Slackware 14.1 on Gumstix as Slackware 13.37 is End Of Life, and the 3.5.x Kernels built with Yocto, and provided by Gumstix support enough devices.<br /> Using The Caspa / MT9V032 Sensor With Slackware 14.1 On Gumstix Overo<br /> <br /> Make sure to use a 3.5 series kernel built with Yocto and Bitbake per Gumstix' instructions. At least 3.5.7. When purchasing your device you may be able to request they flash the NAND with an appropriate kernel.<br /> Using The P54USB WiFi With Slackware 14.1 On Gumstix Overo<br /> <br /> This may be enabled by default in a Yocto kernel. It supports Hot AP mode. Needs 5 Volts.<br /> Using The rt2800usb USB WiFi With Slackware 14.1 On Gumstix Overo <br /> <br /> This likewise may be built in by default in a Yocto kernel. Works at both 3.3 and 5 volts.<br /> Using The LIS331 3-Axis Accelerometer With Slackware 14.1 On Gumstix Overo<br /> <br /> This is an I2C device. Level Shifters may be needed on the SDA and SCL lines when your system voltage is above 3.3 Volts.<br /> Using The MPU-6050 3-Axis Accelerometer With Slackware 14.1 On Gumstix Overo<br /> <br /> This is an I2C device. Level Shifters may be needed on the SDA and SCL lines when your system voltage is above 3.3 Volts.<br /> Sources</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_13.37_On_Gumstix_Overo&diff=6039 2014-04-21T18:36:18Z

<p>BallCam: moved Slacware 13.37 On Gumstix Overo to Slackware 13.37 On Gumstix Overo</p> <hr /> <div>== Slackware 13.37 On Gumstix Overo ==<br /> <br /> Slackware ARM 13.37 Is now End Of Life but there may be some interest<br /> in installing it because the 2.6 series kernel is long term stable,<br /> and because the Caspa unit works with 2.6.34 from Sakoman.com</div>

BallCam https://wiki.gumstix.com/index.php?title=Slacware_13.37_On_Gumstix_Overo&diff=6040 2014-04-21T18:36:18Z

<p>BallCam: moved Slacware 13.37 On Gumstix Overo to Slackware 13.37 On Gumstix Overo</p> <hr /> <div>#REDIRECT [[Slackware 13.37 On Gumstix Overo]]</div>

BallCam https://wiki.gumstix.com/index.php?title=Slackware_13.37_On_Gumstix_Overo&diff=6038 2014-04-21T18:34:16Z

<p>BallCam: Created page with &quot;== Slackware 13.37 On Gumstix Overo == Slackware ARM 13.37 Is now End Of Life but there may be some interest in installing it because the 2.6 series kernel is long term stable,...&quot;</p> <hr /> <div>== Slackware 13.37 On Gumstix Overo ==<br /> <br /> Slackware ARM 13.37 Is now End Of Life but there may be some interest<br /> in installing it because the 2.6 series kernel is long term stable,<br /> and because the Caspa unit works with 2.6.34 from Sakoman.com</div>

BallCam