lock transaction - bug and fix

[Manfred W. <e95...@st...>]

Since the lock-compare_swap transaction obviously did not work, I used a
packet analyzer today to have a lock at the lock packets and found out,
that the extended tcode was not filled out correctly (it contained 0
whereas it should contain 2 [which I used as the extcode argument of
raw1394lock])

My fix was to add the following line to the function raw1394_start_lock
(I added it as line 82 in the file readwrite.c of libraw1394):

        req->misc=extcode;

Now it works. I suggest to add this to cvs, too.

Manfred Weihs