Revision: 2212
http://gtkpod.svn.sourceforge.net/gtkpod/?rev=2212&view=rev
Author: tmzullinger
Date: 2009-01-13 18:23:44 +0000 (Tue, 13 Jan 2009)
Log Message:
-----------
Add some notes on the hal callout
Modified Paths:
--------------
libgpod/trunk/ChangeLog
libgpod/trunk/README.SysInfo
libgpod/trunk/TROUBLESHOOTING
Modified: libgpod/trunk/ChangeLog
===================================================================
--- libgpod/trunk/ChangeLog 2009-01-13 18:23:28 UTC (rev 2211)
+++ libgpod/trunk/ChangeLog 2009-01-13 18:23:44 UTC (rev 2212)
@@ -1,5 +1,8 @@
2009-01-13 Todd Zullinger <tmzullinger at users.sourceforge.net>
+ * README.SysInfo, TROUBLESHOOTING: Add some notes on the hal
+ callout
+
* TROUBLESHOOTING: Minor grammatical fixes
2009-01-13 Christophe Fergeau <teuf at gnome.org>
Modified: libgpod/trunk/README.SysInfo
===================================================================
--- libgpod/trunk/README.SysInfo 2009-01-13 18:23:28 UTC (rev 2211)
+++ libgpod/trunk/README.SysInfo 2009-01-13 18:23:44 UTC (rev 2212)
@@ -3,21 +3,32 @@
needs to know the so-called iPod "firewire id", otherwise the iPod won't
recognize what libgpod wrote to it and will behave as if it's empty.
-There are two ways to set up the iPod to make libgpod able to find its firewire
-id.
+There are several ways to set up an iPod so libgpod can find its firewire id.
-The 1st one is mostly automated. First, make sure you have libsgutils installed
-before running configure/autogen.sh. If you built libgpod without it, install
-it and run configure/make/make install. You should now have an
-ipod-read-sysinfo-extended tool available. Run it with the iPod device path
-(eg /dev/sda) and the iPod mount point (eg /mnt/ipod) as arguments. This may
-require root privileges. ipod-read-sysinfo-extended will read an XML
-file from the iPod and write it as
-/mnt/ipod/iPod_Control/Device/SysInfoExtended. See
-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.
+The preferred method is automatic. Make sure you have hal and libsgutils
+installed before running configure/autogen.sh. If you built libgpod without
+them, run configure/make/make install after you install them.
-The 2nd method requires more manual intervention. First, you need to get your
+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 should be entirely automatic. If you have trouble with this, see the
+TROUBLESHOOTING file for some hints.
+
+If you build with libsgutils but without hal, the next best method is mostly
+automatic. You should have an ipod-read-sysinfo-extended tool available. Run it
+with the iPod device path and the iPod mount point /mnt/ipod) as arguments. For
+example:
+
+ $ ipod-read-sysinfo-extended /dev/sda /mnt/ipod
+
+This may require root privileges. It reads an XML file from the iPod and writes
+it as /mnt/ipod/iPod_Control/Device/SysInfoExtended. More details on this
method
+can be found at http://ipodlinux.org/Device_Information.
+
+Having the SysInfoExtended file created by ipod-read-sysinfo-extended or the
hal
+callout is enough for libgpod to figure out the iPod firewire id.
+
+The last 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
like 00A1234567891231. For an iPod Touch, this number will be much longer than
Modified: libgpod/trunk/TROUBLESHOOTING
===================================================================
--- libgpod/trunk/TROUBLESHOOTING 2009-01-13 18:23:28 UTC (rev 2211)
+++ libgpod/trunk/TROUBLESHOOTING 2009-01-13 18:23:44 UTC (rev 2212)
@@ -95,3 +95,21 @@
------------------------------------------------------------
+* The hal callout doesn't run automatically to setup SysInfoExtended
+
+If you have hal and libsgutils installed before running autogen.sh or
configure,
+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 should be completely automatic. However, for this to work, the callout
must
+be installed in hal's callout path. $libdir/hal/scripts is the most portable
+location (hal's $libdir can be found using pkg-config). If you are building
+libgpod from source with the default $prefix (/usr/local), you need to take
care
+to install the callout and .fdi file in the proper locations. The easiest way
to
+do this at the moment is by passing the locations to the make command. For
+example:
+
+ $ ./configure && make
+ ...
+ $ make haldir="$(pkg-config --variable libdir hal)/hal/scripts" \
+ fdidir="$(pkg-config --variable prefix hal)/share/hal/fdi" \
+ install
This was sent by the SourceForge.net collaborative development platform, the
world's largest Open Source development site.
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
gtkpod-cvs2 mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gtkpod-cvs2
