Re: Palm Life Drive and Evolution Pilot

[Andrew Greig <algreig bigpond net au>]

On Thu, 2008-06-12 at 11:46 +0200, Frederic Crozat wrote:

> >        
> 
> Well, if Andrew is using gnome-pilot package from Mandriva 2008.1, the
> patch is already there.. 
> 
> But maybe, some bits are still missing for Palm Drive in hal-info.
> 
> Please, attach output of lshal when PalmDrive is connected before and
> after hotsync is started (since I remember it changes the way it is
> advertised over usb but I'm not 100% sure).
> 

Hi Frederic,

I have created 3 text files haloutput_early.txt haloutput_hotsync.txt
and  haloutput_later.txt  (after it timed out).  Each of these files is
126.8Kb in size.  Would you prefer that I cut the three sections which
relate to the visor, and pda and pda and send only those for each state?

Or should I send the first file with all the output from hal, and then
the sections related to the visor and pda for the next two states?
Probably be around 140Kb that way.

I found nothing in /etc/hal but I did
in /usr/share/hal/fdi/information/10freedesktop/10-usb-pda.fdi

LifeDrive does not get a mention in the section related to the visor
module, but it does in the section related to libusb.

I could not get the LifeDrive to sync under libusb on anything, but
since I fell back to the visor module I can get pilot-xfer and J-Pilot
to sync.

Here is the extract of 10-usb-pda.fdi of which I speak:

  <!-- PalmOS PDAs via Linux 'visor' kernel driver -->
      <match key="@serial.originating_device:info.linux.driver"
string="visor">

	<!--
	    on Sony Clie 3.5 devices we need to mark port 0 instead of port 1.
For
	    this reason, we mark the usb interface with port number to use
(FIXME: is
	    there a better solution?). However, we should also do this for
clies that
	    have been upgraded to a later version of OS, but I'm not sure if
those have
	    the same product id - in that case this would not work for them.
The driver
	    doumentation however advertises that the information about what
port should
	    be used is written to syslog, perhaps we can somehow get that
information
	    from the driver directly?)
	-->
	<match key="@serial.originating_device:usb.vendor_id" int="0x054c">
  	  <!-- Sony Clie: 3.5, SJ-22 -->
          <match key="@serial.originating_device:usb.product_id"
int_outof="0x0038;0x0066">
            <match key="serial.port" int="0">
              <append key="info.capabilities"
type="strlist">pda</append>
              <merge key="pda.platform" type="string">palm</merge>
              <merge key="pda.palm.hotsync_interface"
type="copy_property">serial.device</merge>
            </match>
          </match>
	</match>

        <!-- Handspring -->
	<match key="@serial.originating_device:usb.vendor_id" int="0x082d">
  	  <!-- Visor -->
          <match key="@serial.originating_device:usb.product_id"
int="0x0100">
            <match key="serial.port" int="1">
              <append key="info.capabilities"
type="strlist">pda</append>
              <merge key="pda.platform" type="string">palm</merge>
              <merge key="pda.palm.hotsync_interface"
type="copy_property">serial.device</merge>
            </match>
          </match>
	</match>

	<!-- Known Palm PDAs from Palm, Inc. -->
	<match key="@serial.originating_device:usb.vendor_id" int="0x0830">
  	  <!-- Palm m130 -->
          <match key="@serial.originating_device:usb.product_id"
int="0x0050">
            <match key="serial.port" int="0">
              <append key="info.capabilities"
type="strlist">pda</append>
              <merge key="pda.platform" type="string">palm</merge>
              <merge key="pda.palm.hotsync_interface"
type="copy_property">serial.device</merge>
            </match>
          </match>
  	  <!-- Tungsten T5 -->
          <match key="@serial.originating_device:usb.product_id"
int="0x0061">
            <match key="serial.port" int="1">
              <append key="info.capabilities"
type="strlist">pda</append>
              <merge key="pda.platform" type="string">palm</merge>
              <merge key="pda.palm.hotsync_interface"
type="copy_property">serial.device</merge>
            </match>
          </match>
	</match>

  	<!-- All the other PalmOS PDAs as fallback -->
	<match key="pda.platform" exists="false">
          <match key="serial.port" int="0">
            <append key="info.capabilities" type="strlist">pda</append>
            <merge key="pda.platform" type="string">palm</merge>
            <merge key="pda.palm.hotsync_interface"
type="copy_property">serial.device</merge>
          </match>
          <match key="serial.port" int="1">
            <append key="info.capabilities" type="strlist">pda</append>
            <merge key="pda.platform" type="string">palm</merge>
            <merge key="pda.palm.hotsync_interface"
type="copy_property">serial.device</merge>
          </match>
	</match>

      </match>
    </match>

    <!-- PalmOS PDAs via libusb -->
    <match key="info.subsystem" string="usb_device">

      <!-- Sony -->
      <match key="usb_device.vendor_id" int="0x054c">
        <!-- Sony NR and other Palm OS 4.1, Sony S S320 and other Palm
OS 3.5, Sony T, SJ series, and other Palm OS 4.0,
	     Sony S360, Sony NR70V/U, Sony NX, Sony NZ, Sony UX, Sony TJ
	  -->
        <match key="usb_device.product_id"
int_outof="0x000a;0x0038;0x0066;0x0095;0x009a;0x00da;0x00e9;0x0144;0x0169">
          <append key="info.capabilities" type="strlist">pda</append>
          <merge key="pda.platform" type="string">palm</merge>
          <merge key="pda.palm.hotsync_interface"
type="copy_property">linux.device_file</merge>
        </match>
      </match>

      <!-- Handspring -->
      <match key="usb_device.vendor_id" int="0x082d">
        <!-- Visor/Treo 300, Treo, Treo 600  -->
        <match key="usb_device.product_id"
int_outof="0x0100;0x0200;0x0300">
          <append key="info.capabilities" type="strlist">pda</append>
          <merge key="pda.platform" type="string">palm</merge>
          <merge key="pda.palm.hotsync_interface"
type="copy_property">linux.device_file</merge>
        </match>
      </match>

      <!-- Palm, Inc. and palmOne -->
      <match key="usb_device.vendor_id" int="0x0830">
        <!-- m500,m505,m515,2xunknown,i705,Tungsten Z,Tungsten
W,m125,m130,3x unknown,
	     (Tungsten series, Zire 71), 3x(Zire 21, 31, 72, Z22, Tungsten E2,
T3, TX, Treo 650, 680, LifeDrive),
	     2x Zire, m100, 2y unknown -->
        <match key="usb_device.product_id"
int_outof="0x0001;0x0002;0x0003;0x0010;0x0011;0x0020;0x0030;0x0031;0x0040;0x0050;0x0051;0x0052;0x0053;0x0060;0x0061;0x0062;0x0063;0x0070;0x0071;0x0080;0x0099;0x0100">
          <append key="info.capabilities" type="strlist">pda</append>
          <merge key="pda.platform" type="string">palm</merge>
          <merge key="pda.palm.hotsync_interface"
type="copy_property">linux.device_file</merge>
        </match>
      </match>


So in this last stanza, the Life Drive is mentioned by name and by
number, 0830-0061, so why was libusb such a strain?

If I were to copy the stanza for the Tungsten T5 and change the model
number and string to suit the LifeDrive, would that allow hotsync to
work under the visor module, again?

In the old days my Palm iii just worked under serial port, and my
Tungsten W and later the LifeDrive always worked under visor. I would
like to get it working under libusb, but I just need it to work.

Thanks for your patience with me.

Andrew Greig