From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stefan Pietzonke <jay-t@gmx.net>
Subject: fix for keyboard driver config
Date: Mon, 02 Nov 2015 20:59:24 +0100
Message-ID: <5637C09C.8050001@gmx.net>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <linux-8086-owner@vger.kernel.org>
Sender: linux-8086-owner@vger.kernel.org
List-ID: <linux-8086.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
To: linux-8086@vger.kernel.org

Hello,
while trying to make an ELKS build with the GitHub ELKS sources I found 
a bug in the key maps configuration file:

elks/elks/arch/i86/drivers/char/KeyMaps/mkcfg

The grep command to extract the key map names from the code headers was 
missing the -a option. Some of the text files got recognized as "binary 
files". And the menuconfig showed just garbage to choose from.

If I build a comb360 image with the German keyboard driver then a simple 
"ls" command at / shows no files and hangs forever... I don't know if it 
has something to do with the keyboard driver.

cheers

Stefan Pietzonke


Here is a fix code snippet: (mkcfg) for the missing "-a" on grep: (mkcfg)

#!/bin/bash

# This is a script to create the correct choice command to select from
# the currently available keyboard code sets when configuring ELKS.

function codes() {
     grep '^/\* Keymap:' keys-*.h -a | cut -d : -f 1,3,4 | tr : ' '
}