This will move configuration of which external should be used when
programming a mote to the mote specific UDEV scripts so the MCH can pick
this information up via the device hierarchy. Depending on whether the path
will be given via a symlink or the content of a file it can be placed in
either:
/dev/remote/MOTEMAC/bin/moteprogrammer
or
/dev/remote/MOTEMAC/moteprogrammer
Since other external programs might be optionally needed (see issue 6) the
former option might be cleaner.
Original issue reported on code.google.com by jonas.fonseca on 14 Nov 2007 at 2:10
Original issue reported on code.google.com by
jonas.fonseca
on 14 Nov 2007 at 2:10