Open GoogleCodeExporter opened 9 years ago
Original comment by jonas.fonseca
on 12 Nov 2007 at 10:41
The simplest and most powerful way to fix this is to make it possible for UDEV
scripts to define attributes via the device hierarchy by placing them in a named
directory such as:
/dev/remote/MOTEMAC/attr/
and make the MCH unconditionally send all such attributes to the MCS. The other
way
the simplest solution is to make mote attributes available to mote programming
scripts via environment variables by allowing the MCS to define key=value pairs
that
will be passed to exeve() when programming.
Original comment by jonas.fonseca
on 19 Nov 2007 at 10:44
Here is a patch that shows how the mote programming will become more generic,
remains
is to make the mote programmer path configurable via UDEV (issue 21), protocol
changes to send the mote attribute environment variables, and finally the
sending of
MCH attributes.
Original comment by jonas.fonseca
on 19 Nov 2007 at 1:15
Attachments:
Retargeting this to next release since it needs more thought. For the upcoming
release we can just add the necessary changes to the MCH-MCS protocol by adding
the
platform attribute to MsgMoteConnectionInfo, etc.
The above patch + related cleanups has been merged, however, as a preparation
and
nice cleanup.
Original comment by jonas.fonseca
on 22 Nov 2007 at 12:19
Original issue reported on code.google.com by
jonas.fonseca
on 6 Nov 2007 at 3:29