On 2016-04-13 14:24, Maxin B. John wrote:
Hi,
On Wed, Apr 13, 2016 at 02:13:43PM +0200, Gary Thomas wrote:
On 2016-04-13 14:08, Jussi Kukkonen wrote:
On 13 April 2016 at 14:35, Gary Thomas <[email protected]
<mailto:[email protected]>> wrote:
<snip>
Have you checked that your /etc/formfactor/machconfig contains
"HAVE_KEYBOARD=0"? This value is used by
/etc/matchbox/session to decide whether to load the keyboard panel or not, and
by .the Xsession script to decide whether
to start the daemonized keyboard or not.
Has this or any of the files it depends on (/etc/formfactor/*) changed recently?
As I said, as recently as mid February everything worked as expected, no longer.
If something changed that I need to track, I'm happy to adapt.
Yes, there was a change in Keyboard related logic in formfactor with this
recent commit:
commit 463fd5ee26c5037b0f4ecfe4bc6ed48945b3b07e
Author: Ross Burton <[email protected]>
Date: Thu Mar 3 16:56:43 2016 +0000
formfactor: assume a keyboard is plugged in
A sensible assumption is that BSPs have a USB keyboard and mouse connected
unless told otherwise, so flip the logic in the formfactor config script that
previously assumed that a keyboard was not connected by default.
[ YOCTO #9174 ]
(From OE-Core rev: a82ce3e477a475dccea3837eabacd9e93b873ee6)
Wow, what an assumption! Anyway, adding the correct machconfig for
my target fixes the problem.
Thanks for the pointer
Signed-off-by: Ross Burton <[email protected]>
Signed-off-by: Richard Purdie <[email protected]>
<snip>
if [ -z "$HAVE_KEYBOARD" ]; then
- HAVE_KEYBOARD=0
+ HAVE_KEYBOARD=1
Best Regards,
Maxin
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
