> -----Original Message----- > From: Yi Qingliang [mailto:niqingliang2...@gmail.com] > Sent: Thursday, May 16, 2013 5:46 PM > To: Slater, Joseph > Cc: openembedded-core@lists.openembedded.org oe-core layer > Subject: Re: [OE-core] qt keyboard problem > > On Thursday, May 16, 2013 04:51:04 PM Slater, Joseph wrote: > > > -----Original Message----- > > > From: openembedded-core-boun...@lists.openembedded.org > > > [mailto:openembedded-core- boun...@lists.openembedded.org] On Behalf Of > > > Yi Qingliang > > > Sent: Tuesday, May 14, 2013 11:19 PM > > > To: openembedded-core@lists.openembedded.org oe-core layer > > > Subject: [OE-core] qt keyboard problem > > > > > > Hello, all. > > > > > > I'm running qt application on yocto's qt image. cpu is s3c2442, like > > > mini2440. > > > > > > the problem is: > > > > > > key event issued by pressing gpio-key eat by 'getty' (from busybox), > > > my application can't receive input event, > > > if I remove respawn 'getty' for tty1 in /etc/inittab, everything ok. > > > > This could be the same thing I have seen in a slightly different context. > > If so, you can keep the getty's attached to VT's. Just move the line in > > inittab that starts runlevel 5 to the very end of inittab. As long as the > > getty's start first, you'll be okay. > > you mean: move 'id:5:initdefault:' as the last line of the file, right?
No, the line is "l5:5:wait:/etc/init.d/rc 5". Joe > > > > > > > > # /etc/inittab: init(8) configuration. > # $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $ > > # The default runlevel. > id:5:initdefault: > > # Boot-time system configuration/initialization script. > # This is run first except when booting in emergency (-b) mode. > si::sysinit:/etc/init.d/rcS > > # What to do in single-user mode. > ~~:S:wait:/sbin/sulogin > > # /etc/init.d executes the S and K scripts upon change > # of runlevel. > # > # Runlevel 0 is halt. > # Runlevel 1 is single-user. > # Runlevels 2-5 are multi-user. > # Runlevel 6 is reboot. > > l0:0:wait:/etc/init.d/rc 0 > l1:1:wait:/etc/init.d/rc 1 > l2:2:wait:/etc/init.d/rc 2 > l3:3:wait:/etc/init.d/rc 3 > l4:4:wait:/etc/init.d/rc 4 > l5:5:wait:/etc/init.d/rc 5 > l6:6:wait:/etc/init.d/rc 6 > # Normally not reached, but fallthrough in case of emergency. > z6:6:respawn:/sbin/sulogin > S:2345:respawn:/sbin/getty 115200 ttySAC0 > # /sbin/getty invocations for the runlevels. > # > # The "id" field MUST be the same as the last > # characters of the device (after "tty"). > # > # Format: > # <id>:<runlevels>:<action>:<process> > # > > 1:2345:respawn:/sbin/getty 38400 tty1 > > > > > > > Joe > > > > > any idea? > > > > > > > > > -- > > > Nanjing Jilong > > > Yi Qingliang > > > niqingliang2...@gmail.com > > > > > > _______________________________________________ > > > Openembedded-core mailing list > > > Openembedded-core@lists.openembedded.org > > > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core > -- > Nanjing Jilong > Yi Qingliang > niqingliang2...@gmail.com _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
