[pvrusb2] New driver snapshot: pvrusb2-mci-20060318

Hans Verkuil hverkuil at xs4all.nl
Tue Mar 21 10:27:07 CST 2006


> On Tue, 20 Mar 2007, Wim Bakker wrote:
>
>> On Monday 19 March 2007 22:34, Wim Bakker wrote:
>>> On Sunday 19 March 2006 00:33, Mike Isely wrote:
>>
>>> Mar 19 22:11:31 myhost pvrusb2: size of v4l-cx2341x-enc.fw firmware
>>> must be
>>> a multiple of 8192B
>>
>> I think I copied the HcwFalcn.rom from the cd that belongs
>> to the box. It' s 376836  bytes big and made a symlink
>> to  v4l-cx2341x-enc.fw.
>> I did a split -b 262144 on the rom file and moved the resulting
>> first part to v4l-cx2341x-enc.fw and now it works fine.
>> Didn' t realize that it was that important to the driver, because
>> all the previous snapshots had no real complaints that
>> it was too big to their taste.
>>
>
> The check for a multiple of 8KB is a simple sanity check in the driver; it
> has no meaning beyond the actual check itself.  This was logic that was
> carried over from a time before I started working on the driver.  I
> haven't done anything recently that should have relaxed or constrained
> that any further.  If you tripped on this now, you should have also
> tripped on it before.
>
> Hans points out that there are firmware images floating around that are
> greater than 256KB, though the data beyond 256KB apparently is meaningless
> drivel.  The only effect from this is that now I get to loosen up the
> sanity check.  Hans: Is it at least safe to check that the image size is
> *at least* 256KB?  Personally I don't understand why these firmware images
> with garbage appended aren't just "fixed".

They should be minimal 256 KB. The extra size is *mostly* zeroes, but not
all. I've no idea if Hauppauge is also loading the extra bytes or not (I
should be able to check this). It may be relevant. Who knows?

            Hans



More information about the pvrusb2 mailing list