In response to BugByte in this thread, here's a new forum thread for the discussion of a shopping list of what people want by default on a SheevaPlug distribution intended mainly for cars.
Bunch of bluetooth stuff
fbd (fusion brain daemon)
Oh, yeah, FBD makes me think:
When obdgpslogger is compiled, be sure to compile it with lots of optional stuff enabled. I have a general policy that features that add dependencies are off by default. For example, DBus support is off by default, but you need it if you want to use FBD with it.
Perhaps I should just change it to enable features if it finds them on your system. Hrm
I can start making ARM packages and repo if someone is willing to do the work of setting up the build server to crosscompile. That will essentially give you fbd, wifiproximity, obdgpslogger, etc. I've already got obdgpslogger to build with all the dbus stuff enabled.
Well, cross-compiler environments... Freely downloadable from plugcomputing. I described how to set it up here: http://www.mp3car.com/vbulletin/obdi...ml#post1321541
To cross-compile obdgpslogger for the Sheeva using cmake, I have this toolchain file [in the svn checkout]: http://svn.icculus.org/obdgpslogger/...ke?view=markup
But since cross-compiling is historically a bit obtuse at times, I can think of two other good solutions;
One, use an actual plug as the build server. I'm too busy futzing on mine to offer it up as a server for others to use, though :-/
Two, use qemu and emulate it. I've done this myself, and it's not as bad as you might expect. There's resources on ubuntu's forums for setting up a complete qemu vm: https://wiki.ubuntu.com/ARM/RootfsFromScratch which also links to https://launchpad.net/project-rootstock
Because cross-compiling is a pita, here's a picture of Nikki:
Along with WiFi proximity how about a USB WiFi dongle should be able to be plugged in and recognized.
Maybe a webcam driver or are they too hardware specific?
So, this distro would have the following capabilities:
1. OBDII via FTDIO and OBDGPSLOGGER
2. Fusion Brain daemon to allow control of the Fusion brain relay board
3. Requested: USB WiFi dongle support
4. Proposed: Webcam driver
i think we should be bumping out our own kernels. This would solve the fdti issue and the wifi issue. I picked up a $30 belkin wifi dongle at walmart that advertised only support for windows. I slapped it in my LinuxICE2 system and I had wifi instantly. This is how it should work with the sheva also. Plug it in, and forget about it.
scratchbox may be an option. Also an arm qemu virtual machine may also be an option.
Okay, I want to make this happen but am an idiot in Linux. I know a lot more than I use to, but can someone help me out here a little? I need to know:
1. Is there a step-by-step guide on how to build your own distro?
2. I have a plug and can compile one on the plug but my other computer is a Mac. I can run either OSX or Windows on it if necessary. How do I build a distro on those OS' to flash onto the Sheeva?
3. What are the exact packages I should add to the distro (and where are they located) that comes with the Sheeva to allow:
- Fusion Brain
- WiFi proximity
- LAMP? (or is this more appropriate to install later?)
(did I leave anything off?)
I've installed a lot of packages like FTP, MAN, PHP and so forth on my plug. Is it appropriate to put those in a distro or add them later? I suspect the disadvantage is that you bloat the distro. However, I'd like to have some of the basic functionality in place when you install it.
I really need to get this working as I'm stalled on my iPhone project until I get FTDI in place. The whole point of the Sheeva is to have it interface with the world and control it from the iPhone via the web server on the plug.
What I did, is I installed the copy of debian available here: http://www.cyrius.com/debian/kirkwoo...ug/unpack.html
It was pretty easy when following those directions. After installing, you get a solid operating system without much installed, but it has USB serial (FTDI) support built in.