On Fri, 20 Nov 2009 15:27:16 +0800
"Min, Hongbo" <[email protected]> wrote:
> The purpose is to identify the Moblin device that is connected to a PC host.
> If the Moblin-based MID is connected to a desktop PC via USB cable, like the
> current popular solution in Android and WindowMobile, the PC should have
> ability to identify such a Moblin device by a unique ID and then communicate
> it.
>
> Take Linux as PC host for example, the Moblin device connected to it will be
> visible through a DBUS interface with 'GetDevice(unique ID)' returning it.
>
> It may be a property that will be customized by OEM on Moblin-based MID.
There are a few possible sources of usually unique identifiers
- Hard disk serial number
- MAC address of network device
- BIOS UUID
The BIOS UUID is probably the most useful but depends upon the
manufacturer supporting and/or setting it.
If you run dmidecode on a system you'll see under the system information
section something like:
Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: System manufacturer
Product Name: System Name
Version: System Version
Serial Number: System Serial Number
UUID: 00000000-0000-0000-0000-000000000000
Wake-up Type: Power Switch
SKU Number: To Be Filled By O.E.M.
Family: To Be Filled By O.E.M.
Where the UID is hopefully not all zeroes and the other fields are filled
in. Some vendors fill the lot in properly, some ship machines that
actually report like the above ! I've not been through the netbooks to
see if the BIOS vendors are putting in proper UUID values.
Alan
_______________________________________________
Moblin dev Mailing List
[email protected]
To manage or unsubscribe from this mailing list visit:
http://lists.moblin.org/listinfo/dev or your user account on http://moblin.org
once logged in.
For more information on the Moblin Developer Mailing lists visit:
http://moblin.org/community/mailing-lists
