From mboxrd@z Thu Jan  1 00:00:00 1970
From: Eric Nelson <eric.nelson@boundarydevices.com>
Date: Sat, 03 Mar 2012 08:51:21 -0700
Subject: [U-Boot] [PATCH] i.MX6: mx6qsabrelite: Add keypress support
In-Reply-To: <20120303154851.823CC126F3B0@gemini.denx.de>
References: <1330732824-15345-1-git-send-email-eric.nelson@boundarydevices.com>
	<201203030318.25048.marex@denx.de>
	<4F52390C.4080108@boundarydevices.com>
	<20120303154851.823CC126F3B0@gemini.denx.de>
Message-ID: <4F523DF9.90502@boundarydevices.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 03/03/2012 08:48 AM, Wolfgang Denk wrote:
> Dear Eric Nelson,
>
> In message<4F52390C.4080108@boundarydevices.com>  you wrote:
>>
>>> Why not make it an STDIN device as any other keyboard?
>>>
>> Is there a non-blocking read from stdin available to boot script?
>>
>> How would we represent keys like "Menu", "Home", "Volume up" and "Volume down"?
>>
>> Through ANSI escape sequences?
>
> No.  You don't have to.  Mapping key presses to functions (bind them to
> commands) is a different thing.  Keys could be "1", "2", "3" and "4",
> and could be mapped to "run cmd_1", ... "run cmd_4" respectively.
> Then the user can define what "cmd_1" etc. does.
>

That's perfect. All that's left is the details...

Thanks for your help.