FOSDEM 2014 Embedded dev room CFP

FOSDEM 2014 Embedded dev room CFP

[Paul Eggleton]

Hi all,

I didn't notice if it was already announced here, but the CFP for the FOSDEM 
Embedded dev room in 2014 is open:

https://lists.fosdem.org/pipermail/fosdem/2013-October/001870.html

It would be great to have some folks give OpenEmbedded/Yocto Project-related 
presentation(s) this year - we usually manage at least one for FOSDEM. It 
could be about a new feature you've worked on, a success story, a proposal for 
a new direction, a related project etc.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: FOSDEM 2014 Embedded dev room CFP

[Alex J Lennon]

[-- Attachment #1: Type: text/plain, Size: 3281 bytes --]


On 07/11/2013 10:11, Paul Eggleton wrote:
> Hi all,
>
> I didn't notice if it was already announced here, but the CFP for the FOSDEM
> Embedded dev room in 2014 is open:
>
> https://lists.fosdem.org/pipermail/fosdem/2013-October/001870.html
>
> It would be great to have some folks give OpenEmbedded/Yocto Project-related
> presentation(s) this year - we usually manage at least one for FOSDEM. It
> could be about a new feature you've worked on, a success story, a proposal for
> a new direction, a related project etc.

Hi Paul,

I'll be attending FOSDEM this year and could bring some kit along for a 
demo if there's interest,
and table space available.

I doubt I'll have time to prepare a presentation but would be happy to 
make some time for a
discussion if anybody has questions on the development process we went 
through at DD.

The project I think would be most relevant here is a wireless sensor 
mesh network that
we've been working on for some time.

This comprises a number of low cost sensor 802.15.4 radio nodes running 
a proprietary mesh
stack. These are then deployed around a building, forming their own mesh 
for comms, and providing
sensor information back into the enterprise.

We are planning to use Yocto on an OEM i.MX6-based headless gateway we 
have under development
to provide the interface between the mesh and the Internet for sense 
data, and also for installation /
network monitoring purposes.

As Yocto is so flexible in terms of platform targetting, whilst our 
i.MX6 hardware is in development
I have been building for both both Freescale's i.MX6 EVK and also the 
Raspberry Pi for test engineers
to do initial evaluation.

So there's an Internet of Things aspect, 802.15.4 mesh networking, a 
couple of different hardware
platforms running essentially the same code-base to accelerate 
development, and as the gateway
application is .NET based running on Linux/Mono, it shows that companies 
with existing .NET
code-bases and Windows development teams can leverage Yocto+Mono to 
target their embedded
apps. at Linux platforms.

Is that something that would be of interest?

Regards, Alex


Cheers, Paul

-- 

Dynamic Devices Ltd <http://www.dynamicdevices.co.uk/>

Alex J Lennon / Director
1 Queensway, Liverpool L22 4RA

mobile: +44 (0)7956 668178

Linkedin <http://www.linkedin.com/in/alexjlennon> Skype 
<skype:alexjlennon?add>

This e-mail message may contain confidential or legally privileged 
information and is intended only for the use of the intended 
recipient(s). Any unauthorized disclosure, dissemination, distribution, 
copying or the taking of any action in reliance on the information 
herein is prohibited. E-mails are not secure and cannot be guaranteed to 
be error free as they can be intercepted, amended, or contain viruses. 
Anyone who communicates with us by e-mail is deemed to have accepted 
these risks. Company Name is not responsible for errors or omissions in 
this message and denies any responsibility for any damage arising from 
the use of e-mail. Any opinion and other statement contained in this 
message and any attachment are solely those of the author and do not 
necessarily represent those of the company.


[-- Attachment #2.1: Type: text/html, Size: 5922 bytes --]

[-- Attachment #2.2: ddlogo-4.png --]
[-- Type: image/png, Size: 3997 bytes --]

[-- Attachment #2.3: linkedin.png --]
[-- Type: image/png, Size: 631 bytes --]

[-- Attachment #2.4: skype.png --]
[-- Type: image/png, Size: 800 bytes --]

Re: [yocto] FOSDEM 2014 Embedded dev room CFP

[Paul Barker]

On 7 November 2013 10:11, Paul Eggleton <paul.eggleton@linux.intel.com> wrote:
> Hi all,
>
> I didn't notice if it was already announced here, but the CFP for the FOSDEM
> Embedded dev room in 2014 is open:
>
> https://lists.fosdem.org/pipermail/fosdem/2013-October/001870.html
>
> It would be great to have some folks give OpenEmbedded/Yocto Project-related
> presentation(s) this year - we usually manage at least one for FOSDEM. It
> could be about a new feature you've worked on, a success story, a proposal for
> a new direction, a related project etc.
>

I'm planning to attend FOSDEM 2014 and could look at giving a talk on
how I've used OpenEmbedded in developing an underwater noise
monitoring platform and how I've gone from there to contributing to OE
and maintaining opkg. I'll throw together an abstract and see if it
gets accepted.

It should be good to meet a couple of other OpenEmbedded developers as well!

Thanks,

-- 
Paul Barker

Email: paul@paulbarker.me.uk
http://www.paulbarker.me.uk

Re: FOSDEM 2014 Embedded dev room CFP

[Paul Barker]

On 7 November 2013 10:11, Paul Eggleton <paul.eggleton@linux.intel.com> wrote:
> Hi all,
>
> I didn't notice if it was already announced here, but the CFP for the FOSDEM
> Embedded dev room in 2014 is open:
>
> https://lists.fosdem.org/pipermail/fosdem/2013-October/001870.html
>
> It would be great to have some folks give OpenEmbedded/Yocto Project-related
> presentation(s) this year - we usually manage at least one for FOSDEM. It
> could be about a new feature you've worked on, a success story, a proposal for
> a new direction, a related project etc.
>

I'm planning to attend FOSDEM 2014 and could look at giving a talk on
how I've used OpenEmbedded in developing an underwater noise
monitoring platform and how I've gone from there to contributing to OE
and maintaining opkg. I'll throw together an abstract and see if it
gets accepted.

It should be good to meet a couple of other OpenEmbedded developers as well!

Thanks,

-- 
Paul Barker

Email: paul@paulbarker.me.uk
http://www.paulbarker.me.uk

Re: [yocto] FOSDEM 2014 Embedded dev room CFP

[Philip Balister]

On 11/20/2013 06:49 AM, Paul Barker wrote:
> On 7 November 2013 10:11, Paul Eggleton <paul.eggleton@linux.intel.com> wrote:
>> Hi all,
>>
>> I didn't notice if it was already announced here, but the CFP for the FOSDEM
>> Embedded dev room in 2014 is open:
>>
>> https://lists.fosdem.org/pipermail/fosdem/2013-October/001870.html
>>
>> It would be great to have some folks give OpenEmbedded/Yocto Project-related
>> presentation(s) this year - we usually manage at least one for FOSDEM. It
>> could be about a new feature you've worked on, a success story, a proposal for
>> a new direction, a related project etc.
>>
> 
> I'm planning to attend FOSDEM 2014 and could look at giving a talk on
> how I've used OpenEmbedded in developing an underwater noise
> monitoring platform and how I've gone from there to contributing to OE
> and maintaining opkg. I'll throw together an abstract and see if it
> gets accepted.
> 
> It should be good to meet a couple of other OpenEmbedded developers as well!

This is an excellent abstract. Build system talks tend to be pretty
dull, and only interesting to other build system people :) Talks about
cool things a build system lets you do are way more interesting.

Please submit an abstract.

Philip

> 
> Thanks,
> 

Re: FOSDEM 2014 Embedded dev room CFP

[Philip Balister]

On 11/20/2013 06:49 AM, Paul Barker wrote:
> On 7 November 2013 10:11, Paul Eggleton <paul.eggleton@linux.intel.com> wrote:
>> Hi all,
>>
>> I didn't notice if it was already announced here, but the CFP for the FOSDEM
>> Embedded dev room in 2014 is open:
>>
>> https://lists.fosdem.org/pipermail/fosdem/2013-October/001870.html
>>
>> It would be great to have some folks give OpenEmbedded/Yocto Project-related
>> presentation(s) this year - we usually manage at least one for FOSDEM. It
>> could be about a new feature you've worked on, a success story, a proposal for
>> a new direction, a related project etc.
>>
> 
> I'm planning to attend FOSDEM 2014 and could look at giving a talk on
> how I've used OpenEmbedded in developing an underwater noise
> monitoring platform and how I've gone from there to contributing to OE
> and maintaining opkg. I'll throw together an abstract and see if it
> gets accepted.
> 
> It should be good to meet a couple of other OpenEmbedded developers as well!

This is an excellent abstract. Build system talks tend to be pretty
dull, and only interesting to other build system people :) Talks about
cool things a build system lets you do are way more interesting.

Please submit an abstract.

Philip

> 
> Thanks,
> 

Re: FOSDEM 2014 Embedded dev room CFP

[Ulf Samuelsson]

2013-11-07 11:11, Paul Eggleton skrev:
> Hi all,
>
> I didn't notice if it was already announced here, but the CFP for the FOSDEM
> Embedded dev room in 2014 is open:
>
> https://lists.fosdem.org/pipermail/fosdem/2013-October/001870.html
>
> It would be great to have some folks give OpenEmbedded/Yocto Project-related
> presentation(s) this year - we usually manage at least one for FOSDEM. It
> could be about a new feature you've worked on, a success story, a proposal for
> a new direction, a related project etc.
>
> Cheers,
> Paul
>

Working on this cool "Internet of Things" for a customer based on 
BeagleBone/Angstrom

The BeagleBone USB host is connected to a USB/ISM band Radio.
This allows wireless communications with a number of sensors.
Some fixed, some handheld. If you have a handheld sensor,
you approach the server, and "log in".
You can then wander around outside the RF range and do measurements
and then return to hand over the measured data to the server.

The server is also connected to "the cloud" over Ethernet/Wi-Fi.

The server gets its configuration (list of sensors) from the cloud, and
when the sensors report in, the sensor data is uploaded to the cloud.

Runs as a systemd service.

A user can then look at the sensor data through a browser,
or through an app on a phone or on a tablet.

The device can be monitored remotedly, since it logs stuff over UDP.
Have created a small UDP application which receives data
and prints it out. The native application sends escape sequences
allowing color coding of log data.

The UDP logging window is running natively on the Beaglebone screen
so you can see the sensors sending data, and you can see when
the server communicates with the cloud.

One minute later, the temperature data is visible on my iPad.
- Got my Galaxy Tab stolen last year at FOSDEM :-(

The only issue, is that the application, written in C++,  is proprietary.
It was originally written in C# for XP Embedded.

A number of C++ classes has been developed for the application,
and I asked and got approval to release any C++ class which
can be considered to be generic as open-source,
maybe with the boost license or the MIT license.
Then they can be used by other projects without license issues.

Thinking of a title:

Proprietary application, still benefiting open source.

What do you guys think?

Would it be appropriate to show it in the OE stand?

-- 
Best Regards
Ulf Samuelsson
eMagii