I mentioned in my last message a couple of things to try in order to make
further progress. One of those was
2. Take some of the snoop log output and convert it by hand to a binary
file, so that it can actually be looked at with hexdump to see if similar
clues are present. I have a few tools that, while not making this
automatic, do make the job not too too unpleasant.
So, I have implemented this one. That is, I have removed everything other
than frame data from your log file, and from mine. After that, I have
converted said frame data to binary, using a program called "hex2bin"
that I found several years ago (see footnote).
After that, I have done hexdump -C to the result in order to see if any
interesting text becomes visible.
What I have to report is:
No detectable text patterns, neither in the raw data output from your
camera, nor from mine. It appears to me that we have nothing there but raw
data and the camera-specific frame headers which we have already figured
out are there.
(footnote)
The program was in source form, and carries the following notice
/*
hex2bin.c reverse hexdump
Copyright (c) 1996 by Andreas Leitgeb (AvL) <avl@xxxxxxxxxxxxxxxxxx>
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose and without fee is hereby granted,
provided that the above copyright notice appear in all copies and that
both that copyright notice and this permission notice appear in
supporting documentation.
*/
Probably nobody on a list like this one needs a thing like this, but just
in case that anyone does, I just checked with Google for hex2bin.c and
this one comes up as the second hit. I have used it on previous occasions,
and it seems to work nicely.
(end footnote)
Theodore Kilgore
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
