From: Andrey Utkin <andrey_utkin@fastmail.com>
To: Marty Plummer <netz.kernel@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: TW2866 i2c driver and solo6x10
Date: Wed, 3 Aug 2016 22:28:19 +0300 [thread overview]
Message-ID: <20160803192819.GB24606@zver> (raw)
In-Reply-To: <d5269058-c953-5b3e-7b19-0b4c6474714c@gmail.com>
On Wed, Jul 27, 2016 at 11:51:22PM -0500, Marty Plummer wrote:
> I have one of those rebranded chinese security dvrs, the ones with all the gaping
> security holes. I'd like to fix that up and setup a good rtsp server on it, but
> first comes low-level stuff, drivers and such. I've been squinting at the pcb and
> ID'ing chips for a bit now, and I've figured most of them out. Looks like the actual
> video processing is done on 4 tw2866 chips, though the kernel module has symbols
> referring to tw2865. I've seen another driver in the kernel tree, the bluecherry
> solo6x10, but that's on the pci bus. as far as I can figure, the dvr uses i2c for
> them. So, what I'm wondering is would it be feasible to factor out some of the solo
> functionality into a generic tw2865 driver and be able to pull from that for an i2c
> kernel module? I'd really hate to have to rewrite the whole thing, duplicated code
> and overworking are generally a bad idea, even if I do have a datasheet for the chip
> in question
Hi Matt,
Bluecherry LLC software developer here (barely knowing about tw28xx stuff).
If I was you, I'd restrain from such project unless I had a bulk of such
hardware, not just single unit. This is because things are hard to get
right without tinkering step by step. Also somebody would still need to
do fair amount of coding. And unless you are already qualified to do it
alone, you'd need many cycles of asking questions and providing lots of
details of your actual system. If you are interested in merging your
results upstream, then there's even more efforts to put.
As a developer affiliated with Bluecherry LLC, I will do my best to help
you, but I am mere mortal with all sorts of constraints - knowledge,
time, etc. But I or Bluecherry won't just make everything for you, even
if you send us a sample of hardware (which would be a good start for a
volunteer willing to take that challenge).
So feel free to post here your specific questions if you go for it.
next prev parent reply other threads:[~2016-08-03 19:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 4:51 TW2866 i2c driver and solo6x10 Marty Plummer
2016-08-03 19:28 ` Andrey Utkin [this message]
2016-08-03 20:26 ` Marty Plummer
2016-08-03 21:01 ` Andrey Utkin
[not found] <25e70ffb-147a-33f4-76cf-3435ab555520@gmail.com>
2016-08-03 21:35 ` Marty Plummer
2016-08-03 22:05 ` Marty Plummer
2016-09-19 18:20 ` Andrey Utkin
2016-09-22 22:06 ` Marty Plummer
2016-09-22 22:17 ` Andrey Utkin
2016-09-22 22:30 ` Marty Plummer
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=20160803192819.GB24606@zver \
--to=andrey_utkin@fastmail.com \
--cc=linux-media@vger.kernel.org \
--cc=netz.kernel@gmail.com \
/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