Re: RTEMS SMP Status Report v3

[Chris Johns]

On 24/12/16 7:56 am, Gedare Bloom wrote:
> On Fri, Dec 23, 2016 at 4:45 AM, Sebastian Huber
>  wrote:
>> On 23/12/16 02:01, Chris Johns wrote:
>>>
>>> I like the idea of ELF notes being used to tag every API function in RTEMS
>>> with the standard and API they come from. We can then have a tool to audit
>>> the executable. There was a post recently from Nick Clifton on binutils
>>> about annotating ELF binaries this way. Linux also has code to add notes to
>>> ELF files.
>>>
> Is this described somewhere as an open project? What is the scope of it?
> 

https://fedoraproject.org/wiki/Toolchain/Watermark#Markup_for_ELF_objects

Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH source-builder] Add distro aliases for Gentoo hosts

[Ralf Ramsauer]

Gentoo stores most of the basic stuff in /bin and not /usr/bin. Default
values do not work for Gentoo. Add 'gentoo' as a new variation.

Signed-off-by: Ralf Ramsauer 
---
 source-builder/sb/linux.py | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/source-builder/sb/linux.py b/source-builder/sb/linux.py
index 9d90288..f270121 100644
--- a/source-builder/sb/linux.py
+++ b/source-builder/sb/linux.py
@@ -119,6 +119,12 @@ def load():
  '__chown':('exe', 'required', 
'/usr/bin/chown') },
 'suse'   : { '__chgrp':('exe', 'required', 
'/usr/bin/chgrp'),
  '__chown':('exe', 'required', 
'/usr/sbin/chown') },
+'gentoo' : { '__bzip2':('exe', 'required', '/bin/bzip2'),
+ '__chgrp':('exe', 'required', '/bin/chgrp'),
+ '__chown':('exe', 'required', '/bin/chown'),
+ '__gzip': ('exe', 'required', '/bin/gzip'),
+ '__grep': ('exe', 'required', '/bin/grep'),
+ '__sed':  ('exe', 'required', '/bin/sed') },
 }
 
 if distro in variations:
-- 
2.11.0

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH source-builder] Add distro aliases for Gentoo hosts

[Chris Johns]

On 10/01/2017 05:43, Ralf Ramsauer wrote:

Gentoo stores most of the basic stuff in /bin and not /usr/bin. Default
values do not work for Gentoo. Add 'gentoo' as a new variation.

Signed-off-by: Ralf Ramsauer 


Pushed. Thank you.

Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: Desirable Application Stacks (Add-On Library Collections)

[Joel Sherrill]

On Sun, Jan 8, 2017 at 7:52 PM, Chris Johns  wrote:

> On 09/01/2017 11:02, gro...@chichak.ca wrote:
>
>>
>> I ended up writing my own web page server. It sucks, I wish there was a
>> better way, and I’m certain that it’s going to bite me really soon now.
>>
>>
> The mhttpd server in the legacy and libbsd stack allows for hooks to get
> at data. I have a client with a product that has uploading and downloading,
> web sockets and JSON exported data with JS code to handle the interface.
> The interface is nice to use.
>
>
mhttpd is Mongoose. Mongoose moved to GPL with a dual license for
commercial use.

As Christian mentioned, we should move to civitweb which took the last
non-GPL
version of Mongoose and forked.

https://github.com/civetweb/civetweb

I agree that it would be nice if this were an RSB package.

Chris and I saw a presentation on XMPP and IoT. Apparently, xmpp.org has
some standard protocols
defined related to IoT which seem to have some standardization. I don't
know enough to know if
the device side is worth hosting on RTEMS, but it seems promising.

I have also been curious if there is a Linux or Arduino i2c device library
which should be ported to
RTEMS. We have the Linux compatible API so that is an option. I assume that
the Arduino has
a bottom adapter layer we could provide and get their i2c device library to
work.

--joel


> Chris
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: Desirable Application Stacks (Add-On Library Collections)

[Chris Johns]

On 10/01/2017 09:42, Joel Sherrill wrote:



On Sun, Jan 8, 2017 at 7:52 PM, Chris Johns mailto:chr...@rtems.org>> wrote:

On 09/01/2017 11:02, gro...@chichak.ca  wrote:


I ended up writing my own web page server. It sucks, I wish
there was a better way, and I’m certain that it’s going to bite
me really soon now.


The mhttpd server in the legacy and libbsd stack allows for hooks to
get at data. I have a client with a product that has uploading and
downloading, web sockets and JSON exported data with JS code to
handle the interface. The interface is nice to use.


mhttpd is Mongoose. Mongoose moved to GPL with a dual license for
commercial use.


Yes. I used the version we have which is before the license change. I 
just wanted to say the mhttp code we have can do this.



As Christian mentioned, we should move to civitweb which took the last
non-GPL version of Mongoose and forked.


As Christian points out tests are not supported and an important issue. 
Until we have a suitable solution it makes it difficult to know if the 
library we build it ok.


Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: Desirable Application Stacks (Add-On Library Collections)

[Joel Sherrill]

On Mon, Jan 9, 2017 at 5:15 PM, Chris Johns  wrote:

> On 10/01/2017 09:42, Joel Sherrill wrote:
>
>>
>>
>> On Sun, Jan 8, 2017 at 7:52 PM, Chris Johns > > wrote:
>>
>> On 09/01/2017 11:02, gro...@chichak.ca 
>> wrote:
>>
>>
>> I ended up writing my own web page server. It sucks, I wish
>> there was a better way, and I’m certain that it’s going to bite
>> me really soon now.
>>
>>
>> The mhttpd server in the legacy and libbsd stack allows for hooks to
>> get at data. I have a client with a product that has uploading and
>> downloading, web sockets and JSON exported data with JS code to
>> handle the interface. The interface is nice to use.
>>
>>
>> mhttpd is Mongoose. Mongoose moved to GPL with a dual license for
>> commercial use.
>>
>
> Yes. I used the version we have which is before the license change. I just
> wanted to say the mhttp code we have can do this.
>
> As Christian mentioned, we should move to civitweb which took the last
>> non-GPL version of Mongoose and forked.
>>
>
> As Christian points out tests are not supported and an important issue.
> Until we have a suitable solution it makes it difficult to know if the
> library we build it ok.
>
>
This is a general problem it would be nice to have a solution to. We could
have
RTEMS specific examples, tests, and instructions for any third party package
built by the RSB.

I'm not picking with this thread. I was hoping to pick up enough ideas where
a nice GSoC project would be fleshing this side of the RSB out.


> Chris
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: Desirable Application Stacks (Add-On Library Collections)

[Chris Johns]

On 10/01/2017 10:25, Joel Sherrill wrote:

I'm not picking with this thread.


Sure.


I was hoping to pick up enough ideas where
a nice GSoC project would be fleshing this side of the RSB out.


I have no idea how to approach this problem and I am assuming we want to 
use the tests in a package.


Building a package to create a library is just the C compiler and build 
flags. Creating an executable is a more complex step requiring more 
parts of the system to be working, ie rtems_waf.git tweaks. Each package 
has its own way of building tests so I am not sure if the solution is in 
the RSB, RTEMS, RTEMS BSPs, the packages themselves or all of these.


If this was a GSoC project and it includes tests it would be in the 
difficult category because the student would need experience in tools, 
build systems and RTEMS. A keen student would need to be showing a real 
interest in this area now.


Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: Desirable Application Stacks (Add-On Library Collections)

[Joel Sherrill]

On Mon, Jan 9, 2017 at 5:42 PM, Chris Johns  wrote:

> On 10/01/2017 10:25, Joel Sherrill wrote:
>
>> I'm not picking with this thread.
>>
>
> Sure.
>
> I was hoping to pick up enough ideas where
>> a nice GSoC project would be fleshing this side of the RSB out.
>>
>
> I have no idea how to approach this problem and I am assuming we want to
> use the tests in a package.
>
> I would assume that is an option as is having external tests ourselves
that show how to use it with RTEMS.


> Building a package to create a library is just the C compiler and build
> flags. Creating an executable is a more complex step requiring more parts
> of the system to be working, ie rtems_waf.git tweaks. Each package has its
> own way of building tests so I am not sure if the solution is in the RSB,
> RTEMS, RTEMS BSPs, the packages themselves or all of these.
>
>
I would be willing to consider this lower priority since it is a one
package at a time problem.

I was really more concerned with examples that show how to use something
after it is installed. Say for a matrix math library, we have a simple test
that uses one or two operations. Just enough to get a user started and
sanity check a package is installed.


> If this was a GSoC project and it includes tests it would be in the
> difficult category because the student would need experience in tools,
> build systems and RTEMS. A keen student would need to be showing a real
> interest in this area now.
>
>
Agreed. Especially since we don't have the problem scoped or good solutions
for all the issues ourselves.


> Chris
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel