On Friday 28 January 2005 04:10, D. Hugh Redelmeier wrote: > I've revised Jose Alberto Reguero's patch for ivtv-0.3.2b. > This is along the lines of my revision to his patch for > ivtv-0.2.0-rc3d. > > I have NOT tested this. > > Remember Axel's post in this thread? > http://sourceforge.net/mailarchive/message.php?msg_id=10630737 > I think that he was refering the the field "jiffies" in struct > api_cmd, not the global variable with the same name. He asked: > The current "u32 then" only interacts with jiffies which already is > (unconditionally) a u64. Is this a 64bits issue at all? > The field jiffies is declared u64. I find that a bit thought > provoking. Perhaps it too should be "unsigned long". On the other > hand, the name "api_cmd" suggests that this representation might be > shared with code outside the driver and therefore that the layout > cannot be unilaterally changed. Does anyone else know? > > How can we get this debugged and adopted? It would be great to > support x86_64.
It would definetely be great to support x86_64. Myself I'm having quite some stability problems with ivtv and/or myth. When you've found/gotten the answers to your questions I wouldn't mind testing any patches. ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ ivtv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
