From: Marty Plummer <netz.kernel@gmail.com>
To: linux-media <linux-media@vger.kernel.org>
Subject: Re: TW2866 i2c driver and solo6x10
Date: Wed, 3 Aug 2016 17:05:01 -0500 [thread overview]
Message-ID: <59f51702-cbc6-deda-c64e-56938b4c33e6@gmail.com> (raw)
In-Reply-To: <75985f71-e1d6-cf22-91c0-6429955156e6@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2948 bytes --]
On 08/03/2016 04:35 PM, Marty Plummer wrote:
> On 08/03/2016 04:01 PM, Andrey Utkin wrote:
>> On Wed, Aug 03, 2016 at 03:26:39PM -0500, Marty Plummer wrote:
>>> An understanable sentement, but its not just about me (though I actually own two
>>> of the same dvr's). There is a large number, if reports are to be believed, of
>>> more or less identical dvr systems with the same security holes and hard-coded
>>> credentials, with no vendor firmware updates. In addition, I am also in possesion
>>> of the chip vendor sdk with full source code for the kernel and modules and a
>>> host of pertenant datasheets. My end goal is something along the line of openwrt
>>> or lede for these systems in the interest of the community at large.
>>>
>>> I'm not averse to the concept of hard work, and while I'm very experienced when
>>> it comes to kernel hacking I think I can manage well enough with relevant source
>>> and examples, of which there is a large amount.
>>>
>>> One concern I have is dealing with devicetree, but I think I can manage.
>>>
>>
>> That's intriguing. I'm interested to know what this model is and where
>> it can be bought, and also to see all the sdk. BTW have you got sdk from
>> manufacturer after asking for it, or otherwise? Are manufacturers keen
>> to answer technical questions?
>>
> The particular device in question was sold by an american company called
> Night Owl (nightowlsp.com) and is the zeus-dvr5/10 (otherwise identical
> except for the installed hdd size). The main board bears the markings
> "rs-dm-77a" and the main webserver type binary is called 'raysharp_dvr',
> and only operates in IE using activex and reduced security settings.
>
> I'm not certain if you can outright buy it new anymore, as it is very
> old and out of warranty, but a million new clones pop up each day, all
> based on the same hi35xx chipset (mine is hi3520 in particular).
>
> I've uploaded most of the source files to https://github.com/Hi-Spy/hi3520
> with exception to the PDFs and binary blobs. The sdk is based around
> kernel version 2.6.24, so it's quite old, but only has around 10k lines
> of diff files between it and stock.
>
> No, I was in communication with a few people with @hisilicon.com emails
> that I managed to find on the kernel mailing list (see arch/arm/mach-hisi)
> who eventually pointed me at mobile@huawei.com, but I've yet to recieve
> a response. In the meanwhile I was trawling the chinese internet for
> data, and managed to come across someone selling it for 5yuan, which is
> too cheap to pass up. I don't know how cooperative they are going to be,
> considering they've been using linux, u-boot, and a host of other GPL'd
> software without mention or license for at least 5 years, the release
> date of my particular SoC.
>
>
>
Ah crap. I meant to include a 'not' or 'in' in the "While I'm very experienced"
sentence. Brain not working.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-08-03 22:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <25e70ffb-147a-33f4-76cf-3435ab555520@gmail.com>
2016-08-03 21:35 ` TW2866 i2c driver and solo6x10 Marty Plummer
2016-08-03 22:05 ` Marty Plummer [this message]
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
2016-07-28 4:51 Marty Plummer
2016-08-03 19:28 ` Andrey Utkin
2016-08-03 20:26 ` Marty Plummer
2016-08-03 21:01 ` Andrey Utkin
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=59f51702-cbc6-deda-c64e-56938b4c33e6@gmail.com \
--to=netz.kernel@gmail.com \
--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