Re: [PATCH v30 0/7] Add MediaTek SoC DRM (vdosys1) support for mt8195

[Chun-Kuang Hu <chunkuang.hu@kernel.org>]

Hi, Angelo:

AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> 於
2023年3月24日 週五 下午4:38寫道：
>
> Il 24/03/23 00:25, Chun-Kuang Hu ha scritto:
> > Hi, Angelo:
> >
> > AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> 於
> > 2023年3月23日 週四 下午4:58寫道：
> >>
> >> Il 21/03/23 13:18, Nancy.Lin ha scritto:
> >>> The hardware path of vdosys1 with DPTx output need to go through by several modules, such as, OVL_ADAPTOR and MERGE.
> >>>
> >>> Add DRM and these modules support by the patches below:
> >>>
> >>
> >> I've tested v30 again on MT8173, MT8192 and MT8195 based Chromebooks.
> >> Green light from me.
> >
> > I'm curious about how you build code and test on Chromebooks. Do you
> > build in cros environment or pure linux
> > (https://archlinuxarm.org/platforms/armv8/mediatek/acer-chromebook-r13).
> > I've a MT8183 based Chromebook (HP 11a) and I've tried to run a
> > upstream kernel on it. cros is too heavy for me and I doubt I could
> > use it. I've tried the pure linux and could boot up with console, but
> > display does not work. If you use the pure linux environment, could
> > you share how it works?
> >
>
> I haven't tested MT8183 (I don't actually have any 8183 machine in my hands)... but
> yes, I can share my test environment.
>
> I have one MicroSD that I use either in the MicroSD slot of the target machine, or
> in a USB reader; this *single* system is what I boot on *all* Chromebooks that I
> have: one kernel, multiple devicetrees, same Debian-based userspace.
>
> What we have to prepare this bootable media can be found at [1], but beware that
> it currently uses an outdated kernel, so, what I have locally is a symlink to my
> kernel tree.
> You can change/add/remove the devicetree blobs that will get added to the image
> by modifying `chromebook-setup.sh`; before tampering with kernel tree symlink,
> please run that script for the first time, as it will download a cross-compiler,
> a kernel tree (that you will replace for sure) and the (very old) Debian rootfs
> that you can update with `apt-get dist-upgrade` after booting the Chromebook.
>
> If you want to check about possible kernel configuration differences, what I use
> is at [2], so that you can compare.

Thanks for the information, I would try to compare the kernel config first.

>
> [1]: https://gitlab.collabora.com/google/chromebooks/-/tree/mtk-av1
> [2]:
> https://gitlab.collabora.com/google/chromeos-kernel/-/blob/mt8195-tracking-master-rolling/arch/arm64/configs/defconfig
>
> Regards,
> Angelo