From: Thomas Kaiser <v4l@kaiser-linux.li>
To: Anders Blomdell <anders.blomdell@control.lth.se>
Cc: Linux Media <linux-media@vger.kernel.org>
Subject: Re: Topro 6800 driver [JPEG decoding solved]
Date: Tue, 17 Mar 2009 21:13:56 +0100 [thread overview]
Message-ID: <49C00484.7060601@kaiser-linux.li> (raw)
In-Reply-To: <49B7D41B.4040801@control.lth.se>
[-- Attachment #1: Type: text/plain, Size: 811 bytes --]
Hello Anders
Good news, I could decode a frame which I extracted from the usbsnoobs I
did :-). See attached picture frame3-03.jpg. It uses the quality 0.
Your black frame you sent me gets now correctly decode, too (frameA-01.jpg)
I found the Huffman table in the Windoz driver file (TP6810.sys) at
offset 0x2a59c. The QTable which I found in a text file on my Windoz box
can be found in this driver file, also.
I attached some binary files which I used to build the 2 attached jpeg.
For example use:
cat FFD8-Q0-320x240.bin huffman1.bin FFDA.bin frame3-3.bin >frame3-03.jpg
to make the picture frame3-03.jpg.
This information should the cam get going in Linux ;-)
Happy Hacking,
Thomas
PS: I sent this to the linux-media mail list, because somebody else is
interested about this information, too.
[-- Attachment #2: frame3-03.jpg --]
[-- Type: image/jpeg, Size: 11452 bytes --]
[-- Attachment #3: frameA-01.jpg --]
[-- Type: image/jpeg, Size: 5952 bytes --]
[-- Attachment #4: FFD8-Q0-320x240.bin --]
[-- Type: application/octet-stream, Size: 160 bytes --]
[-- Attachment #5: FFD8-Q0-640x480.bin --]
[-- Type: application/octet-stream, Size: 160 bytes --]
[-- Attachment #6: FFD8-Q1-320x280.bin --]
[-- Type: application/octet-stream, Size: 160 bytes --]
[-- Attachment #7: FFD8-Q1-640x480.bin --]
[-- Type: application/octet-stream, Size: 160 bytes --]
[-- Attachment #8: FFDA.bin --]
[-- Type: application/octet-stream, Size: 14 bytes --]
[-- Attachment #9: huffman1.bin --]
[-- Type: application/octet-stream, Size: 352 bytes --]
[-- Attachment #10: frame3-3.bin --]
[-- Type: application/octet-stream, Size: 10926 bytes --]
next prev parent reply other threads:[~2009-03-17 20:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 22:15 Topro 6800 driver Anders Blomdell
2009-02-28 10:31 ` Jean-Francois Moine
2009-02-28 15:11 ` Anders Blomdell
2009-02-28 15:54 ` Thomas Kaiser
2009-03-01 7:26 ` Jean-Francois Moine
2009-03-01 16:33 ` Thomas Champagne
2009-03-02 13:20 ` Jean-Francois Moine
2009-03-02 16:58 ` Anders Blomdell
2009-02-28 11:54 ` Thomas Kaiser
[not found] ` <49B194A7.4030808@kaiser-linux.li>
2009-03-09 12:10 ` Anders Blomdell
[not found] ` <49B50E16.8080703@kaiser-linux.li>
2009-03-09 14:06 ` Anders Blomdell
2009-03-09 18:51 ` Anders Blomdell
2009-03-09 20:10 ` Thomas Kaiser
2009-03-09 20:29 ` Anders Blomdell
2009-03-09 20:43 ` Thomas Kaiser
[not found] ` <49B62023.2090206@control.lth.se>
[not found] ` <49B65BA7.6070700@kaiser-linux.li>
[not found] ` <49B68F34.60802@control.lth.se>
[not found] ` <49B6A495.9060204@kaiser-linux.li>
2009-03-11 15:09 ` Anders Blomdell
2009-03-11 19:11 ` Thomas Kaiser
2009-03-17 20:13 ` Thomas Kaiser [this message]
2009-03-18 20:10 ` Topro 6800 driver [JPEG decoding solved] Thomas Kaiser
2009-03-18 21:42 ` Thomas Champagne
2009-03-25 17:10 ` Anders Blomdell
[not found] ` <49B5786D.4060102@kaiser-linux.li>
[not found] ` <49B57CB6.8000402@control.lth.se>
2009-03-09 20:38 ` Mail list, Is WIKI up to date? Thomas Kaiser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49C00484.7060601@kaiser-linux.li \
--to=v4l@kaiser-linux.li \
--cc=anders.blomdell@control.lth.se \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).