[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [dsdp-tm-dev] initial discovery service
|
Hi Javier,
Service Discovery (or "autodetect") is certainly of
interest for us at Wind River, too.
As you might remember from the Toronto meeting, there is a
Technology Sub-Group
for Autodetect, but no lead has been assigned yet -- would
you want to lead this
I think for the actual autodetect, there are a few
flavors:
* Autodetect during system definition (in the wizard),
assuming that detected services remain the same over time
* Autodetect on each connect, allowing to disable services
as needed
The actual detection of services could go
* via network (ECF provides some discovery services through
Zeroconf),
* it could be through vendor-specific agents running on the
remote system,
* or it could be even without asking the live target, e.g.
by looking at a local ELF image of the kernel on the target or investigating
SPIRIT files.
In any case, it looks like the autodetect would basically
create a filter that limits a list of
possible subsystems for a given system connection to the
list of those that are actually
available; and, for those subsystems that have been found
available, perhaps automatically
set some properties.
I was not sure how autodetect would relate to a view for
hardware actions like restart or reflash?
Cheers,
Martin
--
Martin Oberhuber - WindRiver,
Austria
+43(662)457915-85
Hi All,
Symbian couldn't attend the phone meeting yesterday,
but we would like to raise a question about the initial discovery of remote
embedded systems and how to manage them.
We think it would be interesting having a remote system discovery
facility, allowing to retrieve information through a standard protocol such as
the description of the system and the list of available services.
Also executing basic hardware services
on the remote systems (mainly restart and reflash) could be
interesting.
The discovery
facility could consist on:
* A
contribution to the RSE "New Connection" wizard, at the same position where RSE allows checking
if the provided IP exists
* A standard
TCP/IP based protocol (to be investigated) to report the available services on
the embedded system and start them as requested by the user. At this stage
possibly the SPIRIT information could also be retrieved.
* A view to manage registered embedded systems and
perform basic hardware actions as restart or reflash.
As in
the current release only the IP address is checked, possibly an early
handshake with the embedded system could be useful.
Is anybody else interested in this feature ?
Javier Montalvo
OrĂºs
Engineering Tools
Symbian
Software Limited.
Tel: +44 (0)207 154 1091
*******************************************************************
***
Symbian Software Ltd is a company registered in England and
Wales with
registered number 4190020 and registered office at 2-6
Boundary Row,
Southwark, London, SE1 8HP, UK. This message is
intended only for use by
the named addressee and may contain
privileged and/or confidential
information. If you are not the
named addressee you should not disseminate,
copy or take any action
in reliance on it. If you have received this
message in error
please notify postmaster@xxxxxxxxxxx and delete the
message and any
attachments accompanying it immediately. Neither Symbian
nor any of
its Affiliates accepts liability for any corruption,
interception,
amendment, tampering or viruses occurring to this message
in
transit or for any message sent by its employees which is not
in
compliance with Symbian corporate policy.
*************************
*********************************************