APPLIED/cmt: pull request for raspi2 eoan kernel

[Hui Wang]

On 2019/9/26 上午4:21, Seth Forshee wrote:
> On Thu, Sep 19, 2019 at 03:31:38PM +0800, Hui Wang wrote:
>> These are the tests I did during the sprint,
>>
>> arm64 kernel
>>   - boot test on pi3 and pi4: PASSED
>>
>> armhf kernel
>>   - boot test on pi2, pi3 and pi4: PASSED
>>
>>
>> kernel build via ppa: PASSED
>> https://launchpad.net/~hui.wang/+archive/ubuntu/test-raspi
>>
>> And apart from the boot test, I also tested the devices on the pi4 two weeks
>> ago, most of the devices worked well.
>> device verified:
>>    + UART
>>    + USB host x 3.0
>>    + PCIe
>>    + FB over HDMI
>>    + AUDIO over HDMI
>>    + AUDIO over headphone Jack
>>    + I2C
>>    + SPI
>>    + MMC/SDHCI Storage
>>    + SDIO WiFi
>>    + Ethernet
>>    + GPIO
>>
>> device not verified:
>>    x VideoCore GPU
>>    x HW Encoder/Decoder
>>    x Bluetooth
>>    x V4L2 camera
>>
>> feature not supported yet (even not support in the
>> https://github.com/raspberrypi/linux.git):
>>    x cpufreq
>>    x cpuidle
>>    x suspend/resume
>>
>>
>>
>>
>> And the git repository is at,
>> https://github.com/jason77-wang/eoan-rpi-pull/tree/e-raspi2 , from the
>> commit 329843469a92
>>
>>
>> or directly use this one?
>> https://git.launchpad.net/~p-pisati/ubuntu/+source/linux/log/?h=e-raspi2
> Applied to eoan/raspi2. I've also added a few other commits on top and
> uploaded a version to the canonical-kernel-team/bootstrap ppa, along
> with a linux-meta-raspi2 update.
>
> I did see one issue, that the environment you used for doing your
> configs seems to have been incorrect -- the compiler version was older
> than what's in eoan, and some stack protector features were missing. You
> should always use 'cranky updateconfigs' for updating your configs to
> ensure that it's done in a chroot appropriate for the series, with cross
> toolchains to satisfy any feature tests used for setting config options.
OK, got it, thanks.
> Thanks!
> Seth
>