Add note about hal calloutHEADmaster

1 files changed, 11 insertions, 0 deletions

diff --git a/README.SysInfo b/README.SysInfo
index 1a598e5..5c6efa8 100644
--- a/README.SysInfo
+++ b/README.SysInfo
@@ -17,6 +17,17 @@ file from the iPod and write it as
 http://ipodlinux.org/Device_Information for more details about the method used.
 Having that file is enough for libgpod to figure out the iPod firewire id.
 
+If you have hal available at build time, a hal callout and .fdi file will be
+built and installed.  This will query an iPod when it is plugged in and save the
+SysInfoExtended file in the proper place.  This is all automatic.  For it to
+work, the callout must be installed in a path that hal reads.  The most portable
+location is $(hallibdir)/hal/scripts, where $hallibdir can be found using
+pkg-config.  If you are building libgpod from source with the default $prefix
+(/usr/local), you should explicitly pass configure the --with-hal-callouts-dir
+option.  For example:
+
+./configure --with-hal-callouts-dir=`pkg-config --variable libdir hal`/hal/scripts
+
 The 2nd method requires more manual intervention. First, you need to get your
 firewire id manually. To do that, run "sudo lsusb -v | grep -i Serial" (without
 the "") with your iPod plugged in, this should print a 16 character long string