Thread: lock transaction - bug and fix
Brought to you by:
aeb,
bencollins
From: Manfred W. <e95...@st...> - 2000-04-26 21:27:22
|
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 |
From: Andreas B. <and...@mu...> - 2000-04-27 01:18:55
|
On Wed, Apr 26, 2000 at 10:25:47PM +0200, Manfred Weihs wrote: > 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. Oh, thanks. Good that it works now :-) -- Andreas E. Bombe <and...@mu...> DSA key 0x04880A44 http://home.pages.de/~andreas.bombe/ http://linux1394.sourceforge.net/ |