[OpenWrt-Devel] brcm2708: add kernel 4.14 support

Stijn Tintel stijn at linux-ipv6.be
Mon Nov 12 18:11:54 EST 2018

On 12/11/18 19:00, Christian Lamparter wrote:
> (Did some EMails get mangled?:
> "openwrt-devel at lists.openwrt.org jogo at openwrt.org" <hauke at hauke-m.de>")
> On Monday, November 12, 2018 4:55:12 PM CET Stijn Tintel wrote:
>> On 12/11/18 15:26, Alexandru Ardelean wrote:
>>> [Related to RPi] The RPi kernel seems a bit hard to maintain in the
>>> OpenWrt tree, because if you pull patches from the RPi github tree
>>> (branch rpi-4.14.y) you need to periodically check & update them.
>>> I tried to keep a 4.14 of OpenWrt in my own tree, and it's a pain to
>>> maintain [just for my personal need].
>>> Every couple of 4.14.xxx bumps, some of the patches don't apply
>>> anymore, because some of them are too big [thrown in], and conflict
>>> with upstream stuff.
>>> So, if going forward with OpenWrt + RPi [which I would love to see],
>>> this will be a somewhat hefty work-load.
>> The problem of patches no longer applying happens with other platforms
>> as well sometimes. Once we have kernel 4.19 support and 19.01 has been
>> branched, I would like to introduce a new target bcm283x and phase out
>> brcm2708. The idea is to use a vanilla kernel with as little patches as
>> possible,  and boot with vanilla u-boot. But to support the target at
>> all in 19.01, which will use kernel 4.14, I would like to push this to
>> master, and preferably sooner rather than later.
> There's atleast one easy-to-overlook issue/conflict with the rpi-4.14.y
> trees and what's upstream in vanilla-4.14 (and for 4.19 in the future):
> missing or conflicting dt machine compatibles.
> And they are important because the brcm2708 target was switched to
> Mathias' "generic dt" method 
> (see commit 6f041288927b6b7 "brcm2708: convert to dt-based board-detection")
> Back then, I added the upstream compatibles in the 
> "brcm2708: add compatible strings" with the caveat that the 
> ComputeModules are still WIP. (see patch/commit message:
> <https://lists.openwrt.org/pipermail/openwrt-devel/2017-December/010359.html>)
> But it doesn't look like that patch "960-add-rasbperrypi-compatible.patch"
> made it into your repo. So I wonder if sysupgrade is working at all?

This is partially handled by the following patches now:


I'll adapt your patch for the ones that are still missing, and use
upstream names for compute modules.


openwrt-devel mailing list
openwrt-devel at lists.openwrt.org

More information about the openwrt-devel mailing list