| Message ID | CABMQnV+st1kHUJwtpmr-H5PQv=ka1iGmcRudn48-dNfzuvxKmA@mail.gmail.com (mailing list archive) |
|---|---|
| State | Not Applicable |
| Headers | show |
Hi Nobuhiro-san On 2015?03?10? 17:05, Nobuhiro Iwamatsu wrote: > Hi, all. > > This is user land issue. > Hiep, if you have not changed ttySCX in inittab, you will need to change. > Could you check your inittab? > > --- a/inittab 2015-03-10 15:01:58.986609389 +0900 > +++ b/inittab 2015-03-10 15:00:32.132094877 +0900 > @@ -28,7 +28,7 @@ > l6:6:wait:/etc/init.d/rc 6 > # Normally not reached, but fallthrough in case of emergency. > z6:6:respawn:/sbin/sulogin > -SC6:12345:respawn:/sbin/getty -L 38400 ttySC6 > +SC0:12345:respawn:/sbin/getty -L 38400 ttySC0 > # /sbin/getty invocations for the runlevels. > # > # The "id" field MUST be the same as the last There is no inittab file in Linaro userland that I am using. But I tried to change it in Yocto. Then I can boot my boards well. Best Regards, Hiep. > Best regards, > Nobuhiro > > 2015-03-10 8:49 GMT+09:00 Laurent Pinchart <laurent.pinchart@ideasonboard.com>: >> Hello Hiep-san, >> >> (CC'ing Geert) >> >> On Monday 09 March 2015 18:43:54 Cao Minh Hiep wrote: >>> On 2015?03?09? 16:06, Laurent Pinchart wrote: >>>> On Monday 09 March 2015 10:07:04 Cao Minh Hiep wrote: >>>>> Hi Laurent-san >>>>> >>>>> I am Hiep from Jinzai Solution. >>>>> I'm sorry to bother you again! >>>> No worries. >>>> >>>>> We are testing the linux ver v4.0-rc2 on Koelsch, We can not boot the >>>>> kernel v4.0-rc2 on Koelsch, >>>>> Then we found a patch has changed as below: >>>>> "1f75cda ARM: shmobile: koelsch: Rename SCIF[01] serial ports to >>>>> ttySC[01]" >>>>> >>>>> Please see it when you have time! >>>> Could you please detail your boot failure ? You might need to change your >>>> /etc/inittab to adjust to the serial port new name, but apart from that >>>> there shouldn't be any issue. I can boot my Koelsch board on 4.0-v2. >>> Sure, I use the rootfs of Linaro-nano 2014.09 to test v4.0-rc2. >>> When booting kernel with default config, bootlogs showed until these >>> messages appearing. >>> "init: auto-serial-console main process ended, respawning >>> init: auto-serial-console main process ended, respawning >>> init: auto-serial-console main process ended, respawning >>> init: tty1 main process (1449) killed by TERM signal >>> init: auto-serial-console respawning too fast, stopped" >>> >>> Then, my Koelsch board stoped here.(my Lager board is the same) >>> (I attached the bootlogs_file) >>> >>> So, When I tried to add "console=ttySC0," into bootargs (at .dts file), >>> i can boot my Koelsch board without any problems. >>> And these are the same on Lager board. >> Thank you for the information. >> >> Geert, it looks like the console= kernel command line argument is used by >> userspace to figure out the console device on which to spawn a terminal. What >> would you think about adding it back ? >> >>> Thank you! >>> Jinso/Hiep >>> ========= >>> information: >>> Actually, on v4.0-rc2, we have two patches related each other as below: >>> 79e69d1 ARM: shmobile: koelsch dts:Drop console= bootargs parameter BAD. >>> 1f75cda ARM: shmobile: koelsch: Rename SCIF01 serial ports to ttySC01 >>> >>> And for Lager: >>> 569dd56 ARM: shmobile: lager dts: Drop console= bootargs parameter >>> 78c11ec ARM: shmobile: lager: Rename SCIFA[01] serial ports to ttySC[01] >>> >>> There is only 79e69d1 patch on v3.19-rcX, I also had a problem with >>> bootting Koelsch on v3.19-rcX >>> (using linaro-nano 2014.09). But it was good on Yocto and >>> linaro-nano-2013.02 >> -- >> Regards, >> >> Laurent Pinchart >> >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-sh" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- To unsubscribe from this list: send the line "unsubscribe linux-sh" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Hiep-san, On Tue, Mar 10, 2015 at 10:03 AM, Cao Minh Hiep <cm-hiep@jinso.co.jp> wrote: > On 2015?03?10? 17:05, Nobuhiro Iwamatsu wrote: >> This is user land issue. >> Hiep, if you have not changed ttySCX in inittab, you will need to change. >> Could you check your inittab? >> >> --- a/inittab 2015-03-10 15:01:58.986609389 +0900 >> +++ b/inittab 2015-03-10 15:00:32.132094877 +0900 >> @@ -28,7 +28,7 @@ >> l6:6:wait:/etc/init.d/rc 6 >> # Normally not reached, but fallthrough in case of emergency. >> z6:6:respawn:/sbin/sulogin >> -SC6:12345:respawn:/sbin/getty -L 38400 ttySC6 >> +SC0:12345:respawn:/sbin/getty -L 38400 ttySC0 >> # /sbin/getty invocations for the runlevels. >> # >> # The "id" field MUST be the same as the last > > There is no inittab file in Linaro userland that I am using. I'm not familiar with the Linaro userland. Is there any other configuration file that contains the string "ttySC6"? Or does the Linaro userland derive it from the kernel command line? If yes, perhaps there's a newer version that does look at stdout-path instead? The goal of the stdout-path support was to have a better description in DT and automate things. So I don't think reverting the change is the proper way forward. If you can't get it to work, I think we should bring it up with the DT people first, some of which work for Linaro. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds -- To unsubscribe from this list: send the line "unsubscribe linux-sh" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, Mar 10, 2015 at 12:32:59PM +0100, Geert Uytterhoeven wrote: > Hi Hiep-san, > > On Tue, Mar 10, 2015 at 10:03 AM, Cao Minh Hiep <cm-hiep@jinso.co.jp> wrote: > > On 2015?03?10? 17:05, Nobuhiro Iwamatsu wrote: > >> This is user land issue. > >> Hiep, if you have not changed ttySCX in inittab, you will need to change. > >> Could you check your inittab? > >> > >> --- a/inittab 2015-03-10 15:01:58.986609389 +0900 > >> +++ b/inittab 2015-03-10 15:00:32.132094877 +0900 > >> @@ -28,7 +28,7 @@ > >> l6:6:wait:/etc/init.d/rc 6 > >> # Normally not reached, but fallthrough in case of emergency. > >> z6:6:respawn:/sbin/sulogin > >> -SC6:12345:respawn:/sbin/getty -L 38400 ttySC6 > >> +SC0:12345:respawn:/sbin/getty -L 38400 ttySC0 > >> # /sbin/getty invocations for the runlevels. > >> # > >> # The "id" field MUST be the same as the last > > > > There is no inittab file in Linaro userland that I am using. > > I'm not familiar with the Linaro userland. > > Is there any other configuration file that contains the string "ttySC6"? > Or does the Linaro userland derive it from the kernel command line? > If yes, perhaps there's a newer version that does look at stdout-path instead? > > The goal of the stdout-path support was to have a better description in DT > and automate things. So I don't think reverting the change is the proper way > forward. > > If you can't get it to work, I think we should bring it up with the DT people > first, some of which work for Linaro. I am inclined to agree with with Geert on this issue. -- To unsubscribe from this list: send the line "unsubscribe linux-sh" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Geert-san Thanks for you comments, On 2015?03?10? 20:32, Geert Uytterhoeven wrote: > Hi Hiep-san, > > On Tue, Mar 10, 2015 at 10:03 AM, Cao Minh Hiep <cm-hiep@jinso.co.jp> wrote: >> On 2015?03?10? 17:05, Nobuhiro Iwamatsu wrote: >>> This is user land issue. >>> Hiep, if you have not changed ttySCX in inittab, you will need to change. >>> Could you check your inittab? >>> >>> --- a/inittab 2015-03-10 15:01:58.986609389 +0900 >>> +++ b/inittab 2015-03-10 15:00:32.132094877 +0900 >>> @@ -28,7 +28,7 @@ >>> l6:6:wait:/etc/init.d/rc 6 >>> # Normally not reached, but fallthrough in case of emergency. >>> z6:6:respawn:/sbin/sulogin >>> -SC6:12345:respawn:/sbin/getty -L 38400 ttySC6 >>> +SC0:12345:respawn:/sbin/getty -L 38400 ttySC0 >>> # /sbin/getty invocations for the runlevels. >>> # >>> # The "id" field MUST be the same as the last >> There is no inittab file in Linaro userland that I am using. > I'm not familiar with the Linaro userland. > > Is there any other configuration file that contains the string "ttySC6"? > Or does the Linaro userland derive it from the kernel command line? > If yes, perhaps there's a newer version that does look at stdout-path instead? There is not any configuration file that contains ttySC6's string, I think the Linaro userland drive it from the kernel command line. > The goal of the stdout-path support was to have a better description in DT > and automate things. So I don't think reverting the change is the proper way > forward. Thanks for your explanation > If you can't get it to work, I think we should bring it up with the DT people > first, some of which work for Linaro. Now, I am trying to boot with other version of Linaro Userland. Next, I am going to find other setting of userland or uboot in order to boot with current kernel version. if impossible,firstly I am also thinking of changing other Userland (Yocto or Debian). Best Regards, Hiep. -- To unsubscribe from this list: send the line "unsubscribe linux-sh" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Geert, On Tuesday 10 March 2015 12:32:59 Geert Uytterhoeven wrote: > On Tue, Mar 10, 2015 at 10:03 AM, Cao Minh Hiep <cm-hiep@jinso.co.jp> wrote: > > On 2015?03?10? 17:05, Nobuhiro Iwamatsu wrote: > >> This is user land issue. > >> Hiep, if you have not changed ttySCX in inittab, you will need to change. > >> Could you check your inittab? > >> > >> --- a/inittab 2015-03-10 15:01:58.986609389 +0900 > >> +++ b/inittab 2015-03-10 15:00:32.132094877 +0900 > >> @@ -28,7 +28,7 @@ > >> > >> l6:6:wait:/etc/init.d/rc 6 > >> # Normally not reached, but fallthrough in case of emergency. > >> z6:6:respawn:/sbin/sulogin > >> > >> -SC6:12345:respawn:/sbin/getty -L 38400 ttySC6 > >> +SC0:12345:respawn:/sbin/getty -L 38400 ttySC0 > >> > >> # /sbin/getty invocations for the runlevels. > >> # > >> # The "id" field MUST be the same as the last > > > > There is no inittab file in Linaro userland that I am using. > > I'm not familiar with the Linaro userland. > > Is there any other configuration file that contains the string "ttySC6"? > Or does the Linaro userland derive it from the kernel command line? > If yes, perhaps there's a newer version that does look at stdout-path > instead? > > The goal of the stdout-path support was to have a better description in DT > and automate things. So I don't think reverting the change is the proper way > forward. > > If you can't get it to work, I think we should bring it up with the DT > people first, some of which work for Linaro. I quite agree with that, but how should userspace know which device node in /dev corresponds to the console specified in stdout-path ?
On Wed, 2015-03-11 at 08:45 +0200, Laurent Pinchart wrote: > Hi Geert, > > On Tuesday 10 March 2015 12:32:59 Geert Uytterhoeven wrote: > > On Tue, Mar 10, 2015 at 10:03 AM, Cao Minh Hiep <cm-hiep@jinso.co.jp> wrote: > > > On 2015?03?10? 17:05, Nobuhiro Iwamatsu wrote: > > >> This is user land issue. > > >> Hiep, if you have not changed ttySCX in inittab, you will need to change. > > >> Could you check your inittab? > > >> > > >> --- a/inittab 2015-03-10 15:01:58.986609389 +0900 > > >> +++ b/inittab 2015-03-10 15:00:32.132094877 +0900 > > >> @@ -28,7 +28,7 @@ > > >> > > >> l6:6:wait:/etc/init.d/rc 6 > > >> # Normally not reached, but fallthrough in case of emergency. > > >> z6:6:respawn:/sbin/sulogin > > >> > > >> -SC6:12345:respawn:/sbin/getty -L 38400 ttySC6 > > >> +SC0:12345:respawn:/sbin/getty -L 38400 ttySC0 > > >> > > >> # /sbin/getty invocations for the runlevels. > > >> # > > >> # The "id" field MUST be the same as the last > > > > > > There is no inittab file in Linaro userland that I am using. > > > > I'm not familiar with the Linaro userland. > > > > Is there any other configuration file that contains the string "ttySC6"? > > Or does the Linaro userland derive it from the kernel command line? > > If yes, perhaps there's a newer version that does look at stdout-path > > instead? > > > > The goal of the stdout-path support was to have a better description in DT > > and automate things. So I don't think reverting the change is the proper way > > forward. > > > > If you can't get it to work, I think we should bring it up with the DT > > people first, some of which work for Linaro. > > I quite agree with that, but how should userspace know which device node in > /dev corresponds to the console specified in stdout-path ? By reading the /proc/consoles file. Ben. -- To unsubscribe from this list: send the line "unsubscribe linux-sh" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
--- a/inittab 2015-03-10 15:01:58.986609389 +0900 +++ b/inittab 2015-03-10 15:00:32.132094877 +0900 @@ -28,7 +28,7 @@ l6:6:wait:/etc/init.d/rc 6 # Normally not reached, but fallthrough in case of emergency. z6:6:respawn:/sbin/sulogin -SC6:12345:respawn:/sbin/getty -L 38400 ttySC6 +SC0:12345:respawn:/sbin/getty -L 38400 ttySC0 # /sbin/getty invocations for the runlevels. # # The "id" field MUST be the same as the last