All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: can one lay hands on a galileo-based dev kit?
Date: Tue, 29 Apr 2014 12:50:18 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1404291249280.4250@localhost> (raw)
In-Reply-To: <535FD6BF.4040004@dynamicdevices.co.uk>

On Tue, 29 Apr 2014, Alex J Lennon wrote:

>
> On 29/04/2014 17:34, Robert P. J. Day wrote:
> >   i've just been asked to design a linux device drivers course based
> > on the arduino-compatible intel galileo processor, so my first TODO
> > item is to lay hands on a galileo-based dev kit, for which this looks
> > like the obvious choice:
> >
> > https://software.intel.com/en-us/iotdevkit
> >
> > but that page says "upcoming". does it exist? my normal go-to source
> > up here, digikey.ca, shows zero in stock. where can i lay hands on
> > one (if possible)? thanks.
>
> If it helps I had a Galileo Dev Kit delivered from RS (UK) a couple of
> days ago.
>
> http://uk.rs-online.com/web/p/processor-microcontroller-development-kits/7919611/

  ok, so that tells me it's at least available, so i should be able to
track it down online around here somewhere. good to know. now if
anyone in canada wants to weigh in and point me at the best source for
one of these things, that would be great.

  BTW, i notice that's the basic board, while this:

https://software.intel.com/en-us/iotdevkit

seems a bit more bundled. does anyone know if there is any significant
difference?

  as i mentioned earlier, a client wants a drivers course based on
this processor, so i'd also want the ability to possibly order a bunch
of them for the students as class time approaches (whenever that is).

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================


  reply	other threads:[~2014-04-29 16:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-29 16:34 can one lay hands on a galileo-based dev kit? Robert P. J. Day
2014-04-29 16:43 ` Alex J Lennon
2014-04-29 16:50   ` Robert P. J. Day [this message]
2014-04-30  2:43     ` Trevor Woerner
2014-04-30  2:46       ` Trevor Woerner
2014-05-13 13:56   ` Robert P. J. Day
2014-05-13 14:16     ` Vaduva alexandru
2014-05-13 14:20       ` Robert P. J. Day
2014-05-13 14:33     ` Alex J Lennon
2014-05-16 10:11       ` Paul Eggleton
2014-05-16 10:29         ` Alex J Lennon
2014-05-16 10:47           ` Paul Eggleton
2014-05-16 11:17             ` Alex J Lennon
2014-05-16 11:32               ` Paul Eggleton
2014-05-16 12:15                 ` Alex J Lennon
2014-05-16 11:37         ` Robert P. J. Day
2014-05-16 13:29           ` Paul Eggleton
2014-05-16 12:51         ` Robert P. J. Day
2014-05-16 13:10           ` Paul Eggleton
2014-05-16 13:58             ` Robert P. J. Day
2014-05-13 20:12     ` Alex J Lennon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.11.1404291249280.4250@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=ajlennon@dynamicdevices.co.uk \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.