From: netz.kernel@gmail.com (Marty Plummer)
To: linux-arm-kernel@lists.infradead.org
Subject: Older hisilicon chipsets
Date: Fri, 26 Aug 2016 19:48:06 -0500 [thread overview]
Message-ID: <7773f0e5-d045-1e93-529b-74a601467ed1@gmail.com> (raw)
Greetings.
It has recently come to my mind to begin working on an updated firmware
for my employer's CCTV/DVR boxes, which are based around the Hi3520 line
of arm SoC.
In the process of learning which files I need to edit in order to
integrate my changes into the linux build system, I've come to find that
arch/arm/mach-hisi/{Kconfig,Makefile} covers no less than four different
chips from Hisilicon, and that seems to make it a bit awkward to insert
a whole new arch/arm/mach- directory for one single SoC and create
duplicate menuitems for Hisilicon.
So, I'm wondering whereabouts I should place the data for the chips that
I am working on, for the sake of organization and whatnot.
Also, I've been having difficulty getting a response from Hisilicon
regarding my request for source code for this and a few other of their
chips running in our other, newer DVRs, even though a cursory
examination after accessing the devices via telnet shows they do in fact
run a busybox/linux/uClibc based system, with a number of GPL licensed
libraries and kernel modules.
Regards,
Marty
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160826/222521ef/attachment.sig>
next reply other threads:[~2016-08-27 0:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-27 0:48 Marty Plummer [this message]
2016-08-27 15:04 ` Older hisilicon chipsets Jason Cooper
2016-08-27 18:53 ` Marty Plummer
2016-08-29 10:54 ` Arnd Bergmann
2016-08-29 15:46 ` Jason Cooper
2016-08-30 8:55 ` Wei Xu
2016-08-30 14:43 ` Marty Plummer
2016-08-30 14:58 ` Jason Cooper
2016-08-30 15:36 ` Arnd Bergmann
2016-08-30 15:34 ` Wei Xu
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=7773f0e5-d045-1e93-529b-74a601467ed1@gmail.com \
--to=netz.kernel@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).