[pvrusb2] pvrusb2 Digest, Vol 51, Issue 14

[Joel Mayer]

2. Updating Isely Drivers and Firmware-

Two or three times a week I go to a terminal as root
in my SuSE Linux 11.1 distro and type  in "zypper up".
(omit the quotes). Often as not, zypper rewards me
with a big bunch of much appreciated updates to my
base collection of software.

Time after time I see messages saying: mythtv component
this or that is about to be updated. But I have yet to
detect a reference to Mike Isely's software. Why is
that? Have I configured my repository searches
incorrectly? Is there no communication between the
Isely web pages and the people at zypper?

I read someplace zypper is so smart, it resolves
dependencies so well. That there is a measurable
improvement in processor speed on zypper installed
software compared to software installed by Yast.

That being the case, what do I have to do to get
Isely enterprises hooked up with zypper?

Joel Mayer 
  ----- Original Message ----- 
  From: pvrusb2-request at isely.net<mailto:pvrusb2-request at isely.net> 
  To: pvrusb2 at isely.net<mailto:pvrusb2 at isely.net> 
  Sent: Monday, November 23, 2009 1:00 PM
  Subject: pvrusb2 Digest, Vol 51, Issue 14


  Send pvrusb2 mailing list submissions to
  pvrusb2 at isely.net<mailto:pvrusb2 at isely.net>

  To subscribe or unsubscribe via the World Wide Web, visit
  http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2<http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2>
  or, via email, send a message with subject or body 'help' to
  pvrusb2-request at isely.net<mailto:pvrusb2-request at isely.net>

  You can reach the person managing the list at
  pvrusb2-owner at isely.net<mailto:pvrusb2-owner at isely.net>

  When replying, please edit your Subject line so it is more specific
  than "Re: Contents of pvrusb2 digest..."


  Today's Topics:

     1. Re: HVR-1900 needs driver change to support 16K fx2 firmware.
        (Mike Isely)


  ----------------------------------------------------------------------

  Message: 1
  Date: Sun, 22 Nov 2009 18:51:51 -0600 (CST)
  From: Mike Isely <isely at isely.net<mailto:isely at isely.net>>
  Subject: Re: [pvrusb2] HVR-1900 needs driver change to support 16K fx2
  firmware.
  To: Communications nexus for pvrusb2 driver <pvrusb2 at isely.net<mailto:pvrusb2 at isely.net>>
  Message-ID: <alpine.DEB.1.10.0911221845350.5588 at ivanova.isely.net<mailto:alpine.DEB.1.10.0911221845350.5588 at ivanova.isely.net>>
  Content-Type: text/plain; charset=us-ascii


  Gary:

  The driver has already been updated (and since the HVR-1950 has BOTH 
  16KB and 8KB firmware floating around the actual fix is slightly more 
  complex than simply checking for 16KB in place of 8KB).

  However there is a lag before the in-kernel version is going to pick up 
  the changes.  In the mean time you can grab the latest standalone driver 
  which includes the needed changes.  See here: 

  http://www.isely.net/pvrusb2/download.html<http://www.isely.net/pvrusb2/download.html>

  The documentation is also already updated to describe this situation.  
  See here:

  http://www.isely.net/pvrusb2/setup.html#Firmware<http://www.isely.net/pvrusb2/setup.html#Firmware>

    -Mike


  On Sun, 22 Nov 2009, Gary Francis wrote:

  > Hi Mike,
  >    Firstly, thanks for all the effort in maintaining drivers for the pvrusb2.
  >    I recently acquired an HVR-1900 and now have it working with both Ubuntu
  > 9.04 and Slackware64 13.0, except for the IR Blaster. Using the extract script
  > from the 20091031 snapshot I was able to extract the required firmware, but
  > had a couple of problems in using the latest FX2 firmware.
  > 
  > The firmware for the HVR-1900 (From 1.2a driver CD) is now 16k in size. To use
  > this required two changes to the driver source.
  > 1. The addition of the 16k flag for the HVR-1900 in pvrusb2-devattr.c.
  > *** 393,398 ****
  > --- 393,399 ----
  >                .flag_has_analogtuner = !0,
  >                .flag_has_composite = !0,
  >                .flag_has_svideo = !0,
  > +               .flag_fx2_16kb = !0,
  >                .signal_routing_scheme = PVR2_ROUTING_SCHEME_HAUPPAUGE,
  >                .digital_control_scheme = PVR2_DIGITAL_SCHEME_HAUPPAUGE,
  >                .led_scheme = PVR2_LED_SCHEME_HAUPPAUGE,
  > 
  > 2. The firmware uploader pvr2_upload_firmware1 in pvrusb2-hdw.c checks is
  > hardcoded to check for an 8192 byte upload, causing a 16k upload to fail. I
  > changed this to use the actual size of firmware expected.
  > *** 1890,1897 ****
  > 
  >        trace_firmware("Upload done (%d bytes sent)",ret);
  > 
  > !       /* We should have written 8192 bytes */
  > !       if (ret == 8192) {
  >                hdw->fw1_state = FW1_STATE_RELOAD;
  >                return 0;
  >        }
  > --- 1890,1897 ----
  > 
  >        trace_firmware("Upload done (%d bytes sent)",ret);
  > 
  > !       /* We should have written fwsize bytes */
  > !       if (ret == fwsize) {
  >                hdw->fw1_state = FW1_STATE_RELOAD;
  >                return 0;
  >        }
  > 
  > Keep up the good work
  > 
  > Gary
  > 
  > 

  -- 

  Mike Isely
  isely @ isely (dot) net
  PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8


  ------------------------------

  _______________________________________________
  pvrusb2 mailing list
  pvrusb2 at isely.net<mailto:pvrusb2 at isely.net>
  http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2<http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2>


  End of pvrusb2 Digest, Vol 51, Issue 14
  ***************************************