some thoughts on SAKC

Ron K. Jeffries rjeffries at
Sat Feb 27 15:09:40 EST 2010

To the extent that SAKC is used WITH a Nanonote, it could
easily be used as an extension to host computer.

Having said that, I think the idea Carlos has floated of
implementing an interface from SAKC to emulate
SDIO is *very interesting* because I can see that
being a very high bandwidth connection from
Nanonote to SAKC with the two physically side by side
to enable SAKC to "plug in" to Nanonote.

Even though SAKC will have an Xburst SOC, it does
not require a great deal of imagination to think of
interesting configurations where Nanonote does
background activitiies, and tells SAKC what it wants
done, and also does additional processing to
data pulled from SAKC that would otherwise
big down the SAKC CPU.

Having an Xburst SOC on SAKC drives it's cost
up by maybe $6. That's easily worth it.

Let's let Carlos and his talented team do their thing.
Others may wish to invest their time and energy
elsewhere. And that's OK. ;)

In any case. let's not make the mistake of attempting
to design SAKC by commitee.

Ron K. Jeffries

On Sat, Feb 27, 2010 at 11:25, Bas Wijnen <wijnen at> wrote:

> On Sat, Feb 27, 2010 at 11:36:49AM -0500, Carlos Camargo wrote:
> > SAKC is basically one NANONOTE without case, right now NANONOTE is a
> closed
> > platform, I mean, you can't interface Nano with the external world in
> easy
> > way. NANONOTE is a perfect tool for software development, and because of
> > that, we have a lot of Software developers in our lists, and just three
> > hardware developers. So, the question is: We want to attract hardware
> > developers? or the Qi target is just the SW side?
> You're saying HW people can buy a SAKC instead of a NN.  This is fine.
> We should know that this is how we see things.  Originally, the idea
> (AFAIK) was to make the SAKC an extension to the NN, not a replacement.
> As I wrote, I think the interesting part of being an extension is
> possible for much less money.
> > Projects like MilkyMist are very specialized and require a big background
> > and specific skills, rare to find. So I feel that Right now the HW side
> > needs recruit more HW developers. And SAKC will make this task. Without
> > hardware developers in our community projects like AVT2, SAKC, has no
> sense,
> > just sell NANONOTE as SW development tool. BEN NANONOTE is not useful for
> > derivated commercial products, you need a lot of interface signals/ports
> in
> > the real world. SAKC wants to fill this gap.
> So as I thought you say people use it instead of, not with, a NN.  I
> think this is indeed a much more interesting option.
> > About the Wolfgang question about special connectors:
> >
> > SAKC is a general board, we can design a lot of interfaces or "shields"
> for
> > different applications, of course, one of them will be one interface with
> > Analog outputs/inputs with special connectors. We will design daughter
> > boards for robotics, measurement, control, applications.
> Right.  That sounds good.
> Thanks,
> Bas
> Version: GnuPG v1.4.9 (GNU/Linux)
> CX4An1O51T1XdtbkDRoeP1r9CSlA6myP
> =xXmk
> _______________________________________________
> Qi Developer Mailing List
> Mail to list (members only): developer at
> Subscribe or Unsubscribe:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the discussion mailing list