On Fri, Feb 9, 2018 at 1:52 PM, Hauke Mehrtens <ha...@hauke-m.de> wrote:
> On 01/21/2018 06:53 PM, Hauke Mehrtens wrote:
>> This add support for kernel 4.14 to the mvebu target. My main reason to
>> add kernel 4.14 support is to make it easier to also add support for the
>> Marvell Armada 3700LP ARM64 SoCs especially the ESPRESSObin board.
>> I do not have any of the currently supported boards so I can not runtime
>> test this myself, Lucian Cristian already tested an older version of
>> these patches on one of his boards.
>> My current working tree for this target can be found here:
>> This tree also contains the code needed for the ESPRESSObin, but we
>> still have some problems with the image creation, the bootloader boots
>> by default the kernel + dtb from a ext4 file system on a SD card and
>> also uses this partition as root file system.
>> Tomasz Maciej Nowak is working on the image generation for the
>> ESPRESSObin board.
>> I am waiting for positive and negative feedback on these patches, if you
>> run into a problem which you do not have with kernel 4.9 please report
>> changes in:
>> * refresh on current generic kernel 4.14 integration
>> * create ubifs fs format version 4 also with kernel 4.14, this should
>> fix sysupgrade (downgrade) from kernel 4.14 to 4.9
>> * rename the wireless driver path when upgrading
>> Hauke Mehrtens (5):
>> kernel: ubifs: create use file system format 4 by default
>> mvebu: move files to files-4.9 and files-4.4 folder
>> mvebu: copy config and patches from 4.9 to 4.14
>> mvebu: Make kernel 4.14 patches apply
>> mvebu: migrate uci config to new PCIe path
> I haven't heard of any problems, expected that one patch does not apply
> any more with kernel 4.14.18, which is fixed now.
> I will merge this on Sunday if I do not get any negative feedback.
> You can find my tree here:
i just pulled your staging tree and decided to compile firmware for my
CONFIG_TRACE_EVAL_MAP_FILE makes the kernel fail. It needs to be
> Lede-dev mailing list
Lede-dev mailing list