I agree with Tim. There's no use creating a hype and then let it die.
I have been able to find a bit more though: meta-intel-edison - Layer for the Intel Edison Development Platform
The setup script pulls in poky and the meta-intel-iot-middleware - Shared middleware recipes for Intel IoT platforms layer, which in pulls mraa from github intel-iot-devkit/mraa: Low Level Skeleton L... - GitHub.
The kernel is also pulled from github 01org/edison-linux but from the edison-3.10.17. Nothing going on there, but there is activity in wip-edison-3.19.5.
I'm trying to figure out where development is going, but can't seem to find much else than this. Almost nothing on the mailing list as well. Nevertheless it should be easy enough to modify the script to pull the head of iot-middleware which in turn pulls the latest mraa (0.9 vs 0.7.2 default).
But first we created a layer that patches the kernel with preempt-rt, let's see how that works out first (for now it builds), I don't think 3.19 will be compatible with preempt-rt :-(
I'll take a look at the links that you provided.
As for preempt-rt, I can say that the preempt-rt patch set works fine on 3.10.12 ARM Linux. We also have other folks on my team running 3.19, and we'll be giving 4.1 a whirl shortly. ARM Linux with preempt-rt has actually been very stable for quite some time ... I personally have been using it for well over a year (maybe even 2 years). I cannot comment on x86 stability since I have not professionally dealt much with x86 Linux in quite some time, which is why I bought an Edison.
The biggest problem with preempt-rt that folks run in to is poorly designed drivers (and other proprietary add-ons) that cannot handle normal spinlocks being converted to a mutex. Its always good to enable the kernel debug options when you first dive in to preempt-rt, since it will identify a lot of dumb programmer errors, especially those regarding lock misue and attempting to sleep in atomic context. There are also ISR design changes that need to understood.
That's good info, we are just now getting started with our conversion to preempt-rt on x86, and also just started using Edison as a proof-of-concept platform with hopes that we can leverage our dev efforts by choosing a big name ioT supplier that has a large community supporting it. It would be great to have an official Intel Yocto dev tree in order to be able to pull in fixes as they are made. The official update frequency for Edison on the Intel site seems to be unbearably long looking at the history. As a startup company, this pace impacts our development schedules and product launch.
What ARM platform are you using?
Thanks Tim, from another Tim.
I cannot comment on our platform It is a proprietary board with a 64 bit processor. Don't get me wrong, I think Intel has done a lot of very good work on this, and the documentation has been quite good in most cases.
Its just that the lack of git repository (especially as relates to yocto) seems to be the elephant in the room, at least to me . Maybe I just expect too much. :-)
As the edison kernel is heavily patched, you need a patch preempt-rt, which we got from here: https://translate.google.com/translate?hl=en&sl=ja&tl=en&u=http%3A%2F%2Fqiita.com%2Fyoneken%2Fitems%2F2f6fd50bf9837cf50f…
That's the reason why we are a little uncertain how ell it will work.
This message was posted on behalf of Intel Corporation
Currently, all of Edison source code has been upstreamed, not in yocto git repository, but in Github.
You can find all the files in:
I'd like to add 2 things:
1) The entry point is git.yoctoproject.org/meta-intel-edison, clone this, run the script and will pull all the other repositories. Running the script at a later time download or pull stuff that has been updated.
2) It has been more or less equal to the sources v2,1 from the intel website, however recently it was updated to pull kernel 3.10.98. However,
meta-intel-iot-middleware is checked out at
c6d681475e76107e6c04c5f7a06034dc9e772d1e (from git://git.yoctoproject.org/meta-intel-iot-middleware) which puts upm at 0.3.1 (current 0.6.1) and mraa at 0.7.2 (current 0.10.1).
So it would be good if the latest yocto image v3.0 sources would now be finally released and upstreamed to the yocto git.