From: Michael Tremer <michael.tremer@ipfire.org>
To: sig-arm@lists.ipfire.org
Subject: Re: Rockchip RK3188 Radxa Rock
Date: Sun, 05 Oct 2014 20:14:26 +0200 [thread overview]
Message-ID: <1412532866.2037.189.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <CAF+_YkpGPUAWpUWsWzw+p8QgK-FZq20UsoGvUvboS+6962kmaQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4507 bytes --]
Hey,
looking forward to hearing from you when this is finished.
Just wanted to remind you to keep your replies on list if a discussion
started there...
-Michael
On Sun, 2014-10-05 at 01:01 +0200, Jochen Kauz wrote:
> Hi Michael,
> 1. as I written in another post, sharing is caring.. we have the
> kernel sources and we build them from sources that we publish at our
> github repo or our own gitlab, and we respect in every way the GPL and
> the idea of FLOSS.
> 2. I have looked at your kernel sources, and it is not a good idea to
> have them merged, cause Rockchip is much too different in the specific
> kernel sources we have. We have dtb at 3.10.37, but the source is far
> away from your specific multiarch of IMX.
> 3. thanks for the first hints to build it, but I think more of a fork
> to implement the Rockchip kernel into IPFire at this point. So we
> could have our own uboot and kernel, that's much easier in first step.
> 4. another possibility.... what about mainline kernel? Could you merge
> into mainline?
> 5. Only as an information.. I have put my Crewmember Astralix into CC
> cause we both are working on this item together.
>
>
> Cheers
> JochenKauz
>
> 2014-10-04 12:15 GMT+02:00 Michael Tremer <michael.tremer(a)ipfire.org>:
> Hi Mario,
>
> On Thu, 2014-10-02 at 00:35 +0200, Jochen Kauz wrote:
> > Hi list,
> > I'm a member of CrewRKTablets and we make development of
> custom
> > kernels and roms for rockchip based devices, mostly tablets.
> > But we have one toy that we find interesting to try a port
> to, the
> > Radxa Rock of Tom Cubie, a rk3188 based development board.
> > It has a quadcore Cortex-A9 1.6GHz, 1-2GB RAM, WLAN,
> ethernet, 2 Host
> > USB 2.0, 1 USB OTG, serial and much more.
> > We are running at this point Ubuntu 14.04 with 3.0.36 kernel
> on it.
> >
> >
> > Now Astralix and me want to get IPFire on it running.
> > We have kernel sources for 3.0.36, 3.10.37 and uboot.
>
> It is always very much trouble to support new ARM SBCs. Best
> of luck
> with that!
>
> We require to build our kernels from source. Primarily because
> this is
> an Open Source project and secondly because we modify the
> kernel a lot
> with patches that harden it or add some features.
>
> > I have read a little bit in the history of this list.. and I
> know we
> > need grsecurity.. okay found patch sets for 3.0 and 3.10.
> But I think
> > there are more things, could you please give me some more
> information
> > what additional should be added to the kernel?
>
> As there is not much support from Rockchip in the kernel, I
> assume that
> your patchset will be quite huge. Hopefully it supports the
> multiplatform approach and brings DTB files, etc. If so, you
> can add
> your patches to the kernel build instructions:
>
> http://cgit.ipfire.org/ipfire-2.x.git/tree/lfs/linux
>
> Update the configuration:
>
> http://cgit.ipfire.org/ipfire-2.x.git/tree/config/kernel/kernel.config.armv5tel-ipfire-multi
>
> And you are ready to go.
>
> The same rules as above apply for u-boot as well. You will
> find that in
> lfs/u-boot
>
> http://cgit.ipfire.org/ipfire-2.x.git/tree/lfs/u-boot
>
> If the patches are clean and do not break support for any of
> the other
> platforms, we will merge that and of course we will assist you
> here if
> you need us to. But I won't make any promises up front that we
> can add
> support for that hardware, because there are always many
> things that
> cause us trouble and requires a lot of work to maintain
> support for that
> hardware.
>
> Best,
> -Michael
>
> > Best regards
> > JochenKauz
> > _______________________________________________
> > SIG-ARM mailing list
> > SIG-ARM(a)lists.ipfire.org
> > http://lists.ipfire.org/mailman/listinfo/sig-arm
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next parent reply other threads:[~2014-10-05 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAF+_YkpGPUAWpUWsWzw+p8QgK-FZq20UsoGvUvboS+6962kmaQ@mail.gmail.com>
2014-10-05 18:14 ` Michael Tremer [this message]
[not found] <CAF+_Ykr-Sgh5686wPW0UnyRt+YkxqpbF+PbRMD9AQgifATzNgg@mail.gmail.com>
2014-10-22 20:36 ` Michael Tremer
[not found] <CAF+_YkrdKQAvKTumRmd+CRn7eVdk9hJPDfnHCrQXQh=AakWjnw@mail.gmail.com>
2014-10-05 20:41 ` Michael Tremer
[not found] <CAF+_YkrP7vKax=hNepvYRgJszuzN2DVo5RS5SHGERcTow8hAoQ@mail.gmail.com>
2014-10-04 10:15 ` Michael Tremer
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=1412532866.2037.189.camel@rice-oxley.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=sig-arm@lists.ipfire.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