Re: [DEVEL] Enable support for Renesas platform
Some pointers to the actual process I use:
1. boot debian stable with kernel deb from sid
2. install reportbug utility
3. analyse the kernel .config (/boot/config-*), figure out what's missing
4. use reportbug utility to file a bug for "linux" package, asking to
enable kernel configs
5. review flash-kernel package database (this one is responsible for
copying dtb to /boot, and generating a boot.scr)
6. file bug against flash-kernel package to add device
Examples:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839595
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876774
Sometimes I also encounter dead ends:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906268
Am Sa., 19. Nov. 2022 um 09:06 Uhr schrieb Josua Mayer
<josua.mayer97@gmail.com>:
>
> Hi everybody!
>
> Firstly seeing an SoC vendor reach out directly about enabling their HW in Debian seems great to me!
>
> I have been doing a little bit of this work in the past, asking the Debian developers to add support for certain devices I had been working with. It was a very slow process, often years between me establishing contact and an actual release supporting a device.
> It turned out that I didn't always have the time to follow through, and also sometimes encountered bugs specific to the more obscure components like debian-installer.
>
> I'd like to make progress with this approach again, eventually. Especially with SoC vendors supporting upstream Linux well, such as NXP (which I work with a lot) - but also Renesas (my colleague tells me), support is quite possible.
> So @Huynh, I'd be happy to assist / answer some questions.
>
> However note I am not part of the Debian project.
> I don't know if joining makes sense, I don't know if the Debian project would like to incorporate some developers who specifically would collaborate to support certain vendors in Debian.....
> Just - there are things outsiders cannot do - like maintaining a "Blend" e.g.
>
> Sincerely
> Josua Mayer
>
> Fabio Fantoni <fantonifabio@tiscali.it> schrieb am Fr., 18. Nov. 2022, 12:50:
>>
>> Il 18/11/2022 09:20, Huỳnh Thành Hưng ha scritto:
>> > Dear Debian-developer,
>> >
>> > I’m from Renesas Electronics Corporation,
>> >
>> > My group is developing to support running Debian OS on our devices,
>> > also for getting ARM System Ready IR certificate.
>> >
>> > I recognize that the latest Debian 11 (Bullseye) has the kernel which
>> > do not enable support for Renesas platform.
>> >
>> > * *linux-image-5.10.0-18-arm64_5.10.140-1_arm64.deb*
>> >
>> > Can you help me to enable those configs, also support the official
>> > release version of Debian Live Installer ISO which support Renesas
>> > platform?
>> >
>> Hi, thanks for your work, having "out of the box" support on other ARM
>> devices I think would be a great thing.
>> I unfortunately saw years ago when I tried several ARM devices for work,
>> before choosing what to use for thin clients that the support was
>> lacking and it took me a long time to prepare a system to use
>> In recent years I've seen more interest in integrating upstream (mainly
>> the kernel) and having more support in distributions to make it easier
>> and faster for users to use them
>>
>> A first step is enable it in the kernel as you saw, add in stable
>> version is not possible FWIK but should be added in unstable before
>> (later, once added and migrated to testing, it will instead be possible
>> to have it in the backports), if it will be added before the approaching
>> freeze there is a chance it will be added in debian 12
>>
>> looking at latest version of kernel packaging for experimental in arm64
>> config about renesas boards seems not present and I don't see an MR for
>> add it: https://salsa.debian.org/kernel-team/linux
>>
>> probably can be useful see other contacts related to ARM port (mailing
>> list, irc, debian developers working on arm on debian) here:
>> https://www.debian.org/ports/arm/
>>
>> I'm not a maintainer of the ARM part, kernel, bootloader and installer
>> but I hope you will be able to find someone who can help you and that we
>> can have a further improvement in the ARM devices support
>>
>> > I classify the defconfig, also classify the new kernel module to
>> > support our devices.
>> >
>> > * For new kernel defconfig:
>> >
>> > CONFIG_ARCH_RENESAS=y
>> >
>> > CONFIG_SOC_RENESAS=y
>> >
>> > CONFIG_ARCH_RCAR_GEN3=y
>> >
>> > CONFIG_ARCH_R8A774A1=y
>> >
>> > CONFIG_RST_RCAR=y
>> >
>> > CONFIG_SYSC_RCAR=y
>> >
>> > CONFIG_SYSC_R8A774A1=y
>> >
>> > CONFIG_RENESAS_IRQC=y
>> >
>> > CONFIG_RAVB=y
>> >
>> > CONFIG_SERIAL_SH_SCI=y
>> >
>> > CONFIG_CLK_RCAR_GEN3_CPG=y
>> >
>> > CONFIG_CLK_RENESAS_CPG_MSSR=y
>> >
>> > CONFIG_CLK_RENESAS_DIV6=y
>> >
>> > CONFIG_CLK_RCAR_USB2_CLOCK_SEL=y
>> >
>> > CONFIG_PINCTRL_RENESAS=y
>> >
>> > CONFIG_PINCTRL_SH_PFC=y
>> >
>> > CONFIG_PINCTRL_PFC_R8A774A1=y
>> >
>> > CONFIG_RCAR_THERMAL=y
>> >
>> > CONFIG_RCAR_GEN3_THERMAL=y
>> >
>> > CONFIG_RENESAS_DMA=y
>> >
>> > CONFIG_RCAR_DMAC=y
>> >
>> > CONFIG_PCIE_RCAR=y
>> >
>> > CONFIG_PCIE_RCAR_HOST=y
>> >
>> > CONFIG_SYS_SUPPORTS_SH_CMT=y
>> >
>> > CONFIG_SYS_SUPPORTS_SH_TMU=y
>> >
>> > CONFIG_SH_TIMER_CMT=y
>> >
>> > CONFIG_SH_TIMER_TMU=y
>> >
>> > CONFIG_RENESAS_OSTM=y
>> >
>> > CONFIG_IPMMU_VMSA=y
>> >
>> > CONFIG_COMMON_CLK_VC5=y
>> >
>> > CONFIG_MMC_TMIO_CORE=m
>> >
>> > CONFIG_MMC_SDHI=m
>> >
>> > CONFIG_MMC_SDHI_INTERNAL_DMAC=m
>> >
>> > CONFIG_MMC_SDHI_SYS_DMAC=m
>> >
>> > CONFIG_RENESAS_USB_DMAC=m
>> >
>> > CONFIG_I2C_RCAR=m
>> >
>> > CONFIG_GPIO_RCAR=m
>> >
>> > CONFIG_VIDEO_RENESAS_FCP=m
>> >
>> > CONFIG_VIDEO_RENESAS_VSP1=m
>> >
>> > CONFIG_VIDEO_RCAR_CSI2=m
>> >
>> > CONFIG_VIDEO_RCAR_VIN=m
>> >
>> > CONFIG_DRM_RCAR_DU=m
>> >
>> > CONFIG_DRM_RCAR_CMM=m
>> >
>> > CONFIG_DRM_RCAR_DW_HDMI=m
>> >
>> > CONFIG_DRM_RCAR_LVDS=m
>> >
>> > CONFIG_PHY_RCAR_GEN3_USB2=m
>> >
>> > CONFIG_PHY_RCAR_GEN3_USB3=m
>> >
>> > CONFIG_USB_XHCI_RCAR=m
>> >
>> > CONFIG_USB_RENESAS_USBHS=m
>> >
>> > CONFIG_USB_RENESAS_USBHS_HCD=m
>> >
>> > CONFIG_USB_RENESAS_USBHS_UDC=m
>> >
>> > CONFIG_USB_RENESAS_USB3=m
>> >
>> > CONFIG_PWM_RCAR=m
>> >
>> > CONFIG_SPI_SH_MSIOF=m
>> >
>> > CONFIG_SND_SOC_RCAR=m
>> >
>> > CONFIG_CAN_RCAR=m
>> >
>> > CONFIG_CAN_RCAR_CANFD=m
>> >
>> > CONFIG_RENESAS_WDT=y
>> >
>> > * For new kernel modules to be installed in
>> > *linux-image-5.10.0-18-arm64_5.10.140-1_arm64.deb*
>> > o *I2C Common:*
>> > + drivers/i2c/*.ko
>> > o *Renesas I2C: depend on I2C Common*
>> > + drivers/i2c/busses/i2c-rcar.ko
>> > o *Renesas GPIO:*
>> > + drivers/gpio/gpio-rcar.ko
>> > o *Renesas SDHI:*
>> > + drivers/mmc/host/tmio_mmc_core.ko
>> > + drivers/mmc/host/renesas_sdhi_core.ko
>> > + drivers/mmc/host/renesas_sdhi_internal_dmac.ko
>> > + drivers/mmc/host/renesas_sdhi_sys_dmac.ko
>> > o *V4L2 Common driver:*
>> > + drivers/media/common/videobuf2/*.ko
>> > + drivers/media/v4l2-core/*.ko
>> > + drivers/media/mc/mc.ko
>> > o *Renesas video device: depend on "V4L2 Common driver"*
>> > + drivers/media/platform/rcar-fcp.ko
>> > + drivers/media/platform/vsp1/vsp1.ko
>> > o *Renesas display: depend on "Renesas video device"*
>> > + drivers/gpu/drm/rcar-du/*.ko
>> > o *Renesas USB:*
>> > + drivers/phy/renesas/phy-rcar-gen3-usb2.ko
>> > + drivers/phy/renesas/phy-rcar-gen3-usb3.ko
>> > + drivers/usb/renesas_usbhs/renesas_usbhs.ko
>> > + drivers/usb/gadget/udc/renesas_usb3.ko
>> > o *Realtek driver:*
>> > + drivers/net/phy/realtek.ko
>> > + drivers/net/mdio/mdio-mux.ko
>> > o *Renesas CAN/CANFD*
>> > + drviers/net/can/rcar/rcar_can.ko
>> > + drviers/net/can/rcar/rcar_canfd.ko
>> > o *Renesas SPI/MSIOF*
>> > + drivers/spi/spi-sh-msiof.ko
>> > o *Renesas Sound*
>> > + sound/soc/sh/rcar/snd-soc-rcar.ko
>> > o *Renesas PWM driver*
>> > + drivers/pwm/pwm-rcar.ko
>> >
>> > Thank you so much.
>> >
>> > Best Regards,
>> >
>> > *Huynh Thanh Hung*
>> >
>> > -----------------------------------------------
>> >
>> > *SS4 – RZS2 Group.***
>> >
>> > *Renesas Design Vietnam Co., Ltd.*
>> >
>> > -----------------------------------------------
>> >
>> >
>>
Reply to: