2016-05-12 17:28 GMT+02:00 Nicolas Chauvet <kwizart@xxxxxxxxx>:
> This is needed when serial drivers are compiled as module on arm
> Current candidates are 8250_omap or msn_serial
>
> Signed-off-by: Nicolas Chauvet <kwizart@xxxxxxxxx>
> ---
> modules.d/90kernel-modules/module-setup.sh | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/modules.d/90kernel-modules/module-setup.sh b/modules.d/90kernel-modules/module-setup.sh
> index 7904c02..215f468 100755
> --- a/modules.d/90kernel-modules/module-setup.sh
> +++ b/modules.d/90kernel-modules/module-setup.sh
> @@ -30,6 +30,7 @@ installkernel() {
> "=drivers/i2c/busses" \
> "=drivers/regulator" \
> "=drivers/rtc" \
> + "=drivers/tty/serial" \
> "=drivers/usb/host" \
> "=drivers/usb/phy" \
> ${NULL}
> --
@peter, thx for review, and sorry for the late answear.
I've got the following confirmation by the upstream msn_serial maintainer:
<sboyd> nchauvet: if the tty driver is built as a module the console
part can't be used
<sboyd> you can run a getty though
<sboyd> I've done that to test the module loading of that driver and
it works fine
It means that bundling the tty_serial as a module into the initramfs
would requires to have a getty.
Given that there is currently no need to have a getty into the
initrafms I expect this can wait for the rootfs to be available.
So I discard this patch.
FYI the reason why I've started to experiment building the msm_serial
as a module is because there is a a spurious message related to msm
init() even on unrelated hardware (so before probe())
[ 3.135866] msm_serial: driver initialized
Is there any issue with the other patch ? (it's unrelated to this one).
--
-
Nicolas (kwizart)
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
