<html>
<head>
</head>
<body text="#000000" bgcolor="#FFFFFF">
+1 <br>
<br>
Having a focused SIG would promote better attention to
details/issues in the ARM community than being 'embedded' within a
larger, more diffuse group.<br>
<br>
While ARM platforms are often associated with embedded systems,
that's not always the case. For instance I wouldn't classify
NVidia's CARMA board as 'embedded' (
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<a href="http://www.nvidia.com/object/carma-devkit.html">http://www.nvidia.com/object/carma-devkit.html</a>).
Damn thing has more horsepower than my desktop. <br>
<br>
I don't what this to digress into a 'definition of embedded' thread.
But as suggested, keeping ARM separate is no different than other
operating system specific SIGs.<br>
<br>
<br>
<div class="moz-cite-prefix">On 01/24/2013 06:01 AM, Kevin Walchko
wrote:<br>
</div>
<blockquote
cite="mid:122FF92A-3DFC-4554-9209-8C51134381B3@gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="MS Exchange Server version
08.03.0279.000">
<title>Re: [ros-users] Use cases for ROS on ARM based computers</title>
<!-- Converted from text/plain format -->
<p><font size="2">I think embedded is potentially too broad, and
looking at the mail group quickly there appears to be a lot of
different topics discussed (bandwidth, C++ vs C, RTOS for ROS,
etc).<br>
<br>
There seems to be a lot of interest in specifically ARM and
supporting ROS specifically on ARM. I think if a SIG is going
to produce something, it helps to be focused. There appears to
be a lot of work to just setup the infrastructure, test, and
distribute ROS packages for ARM. In order to achieve this, I
think it should be its own SIG. I see no difference between
this and the OSX SIG I support … which is a lot of work.<br>
<br>
<br>
<br>
On Jan 23, 2013, at 11:50 PM, Brian Gerkey
<a class="moz-txt-link-rfc2396E" href="mailto:gerkey@osrfoundation.org"><gerkey@osrfoundation.org></a> wrote:<br>
<br>
> On Wed, Jan 23, 2013 at 3:59 PM, Marcus Liebhardt<br>
> <a class="moz-txt-link-rfc2396E" href="mailto:marcus.liebhardt@rnd.yujinrobot.com"><marcus.liebhardt@rnd.yujinrobot.com></a> wrote:<br>
>> On Thu, Jan 24, 2013 at 3:14 AM, Tully Foote
<a class="moz-txt-link-rfc2396E" href="mailto:tfoote@willowgarage.com"><tfoote@willowgarage.com></a><br>
>> wrote:<br>
>>><br>
>>> Hi Everyone,<br>
>>><br>
>>> Thanks for the interest. Based on the interest
we have setup a SIG for<br>
>>> this. I encourage you to join if you have time
to participate.<br>
>><br>
>><br>
>> I wonder, if it is necessary to create an extra SIG
for this. Although the<br>
>> group of people interested in ROS on ARM has grown to
a significant size,<br>
>> there are still not so many people out there.<br>
>> In order to avoid people getting scattered all over
the place (and might<br>
>> even lost), I suggest we use the existing Embedded
SIG<br>
>> (<a moz-do-not-send="true"
href="http://www.ros.org/wiki/sig/Embedded">http://www.ros.org/wiki/sig/Embedded</a>)
for this.<br>
>> It gathers people interesting in and working on
different embedded levels,<br>
>> such as ROS on ARMs running Linux distributions and
ROS on/with "bare-metal"<br>
>> embedded boards.<br>
>> If this list/group gets to busy in the future, we
still could split it up in<br>
>> different groups later.<br>
><br>
> As a lurker on the ros-sig-embedded list, I agree with
Markus. Unless<br>
> we really have two distinct communities, "embedded" and
"arm," it<br>
> would seem that one group is enough.<br>
><br>
> brian.<br>
> _______________________________________________<br>
> ros-users mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:ros-users@code.ros.org">ros-users@code.ros.org</a><br>
> <a moz-do-not-send="true"
href="https://code.ros.org/mailman/listinfo/ros-users">https://code.ros.org/mailman/listinfo/ros-users</a><br>
<br>
_______________________________________________<br>
ros-users mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:ros-users@code.ros.org">ros-users@code.ros.org</a><br>
<a moz-do-not-send="true"
href="https://code.ros.org/mailman/listinfo/ros-users">https://code.ros.org/mailman/listinfo/ros-users</a><br>
</font>
</p>
</blockquote>
<br>
</body>
</html>