I can't speak for anyone else, but personally I just need an extra
channel to converse with the robostix, so integration with the existing
robostix code would be just fine for me. Murphy's Law says that
someone is going to want them separately if you put them both in the
same binary though. :-)
There's been a couple of posts here (and on the wiki forum) about NSSP and SPI but as far as I can tell nobody has gotten them working yet.
On 8/30/05, Nate W <email@example.com> wrote:
> Has anyone had success for far writing to NSSP and reading on the Robostix?
> I'm about to try, but I'm not even sure where to start - like which /dev
> file is NSSP? :-)
Well, there may or may not be one :)
The NSSP driver required to talk to the robostix could be quite
different from other devices which might connect to NSSP.
Let me take a look at what's required on the gumstix side. I know the
AVR side is pretty straight forward. I'm taking a 6 day weekend so I
should have some time to squeeze in something.
Is there need for such a driver when not using the robostix? If a
driver doesn't already exist on the gumstix side, I can either make a
standalone one or incorporate it into the robstix_drv one that already
Vancouver, BC, Canada
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
gumstix-users mailing list