[Q1]It seems that GUID information can be set in ROM for the IEEE1394 controller. What purpose do I need to set the GUID information?
[Q2]Do I need special drivers, software, or settings for PC-to-PC communication?(Windows/Linux)
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
[Q1]It seems that GUID information can be set in ROM for the IEEE1394 controller. What purpose do I need to set the GUID information?
[Q2]Do I need special drivers, software, or settings for PC-to-PC communication?(Windows/Linux)
Hi,
The ROM is optional, it provides a hardware mechanism to load the global unique identification (GUID) and miscellaneous implementation specific data to the 1394 host controller.
I believe the Window still provides 1394 Legacy Driver, but you may need additional SW on top of the driver to support PC to PC communication.
Thanks
David
Hi
Are there any functions that cannot be used without setting the GUID in ROM?
In that case, do I need to make any settings on the OS?
What kind of policy is used to set the GUID in IEEE1394? (Example: Port , device unit)
Regards
Hi,
Please see this presentation for information on the GUID in the IEEE 1394, http://www.1394ta.org/developers/seminars/guid.pdf.
You can also refer to both the OHCI controller and 1394 spec.
Thanks
David
Every device on the bus needs a unique GUID.
In practice, the only case where a link-layer controller does not have its own EEPROM is when it is integrated on a motherboard, and the BIOS initializes it with a GUID stored in the main BIOS EEPROM.
There is no standardized way to initialize the GUID from software; neither the Windows nor the Linux drivers do this.