Re: [MiNT] update:WRITE_BOOT,ALLOW_TRP_CHG

[Paul Wratt <paul.wratt@gmail.com>]

On Sat, Oct 6, 2012 at 12:46 AM, Peter Persson <pep.fishmoose@gmail.com> wrote:
> 2012/10/4 Helmut Karlowski <helmut.karlowski@ish.de>:
>
>>> I think there are, or used to be, some dead/commented-out code for
>>> this. At least I've seen some document in the CVS which describes
>>> parts of a possible implementation, don't know if it's in source or
>>> txt form though. Maybe it has been removed.
>>
>> Never seen something like that.
>
> I can't seem to find it now either, but I'm sure there were notes
> about it either in the code or in a text file in the repo. Doesn't
> really matter. I think Ozk decided to wait with the implementation
> because of lack of documentation for the Milan keyboard interface
> (that's hearsay on my behalf however).
>
that should still be available in either 1.16.3, 1.17.0 and/or Ozk
branches (his old stuff added last year)

>> Once the kernel has such an interface (Xbconin ;-)), I guess using it in the
>> AES is no big deal.
>
> Sounds very good, it would be very very useful imo.
>
/dev/xkbd would then be useful without an AES too - that makes it a
genuine "future proof" feature

FYI, especially for those considering add that dev to kernel, most
(99%) PC keyboards are "cheap" where multi-key-press is concerned, 3
is max. only high quality keyboard can register more (read: gaming
keyboards) - this then has affect on FireBee, CT6x, and anything else
that uses PS/2 keyboards..

But if kernel presents info, programmer not need to worry about it
(mostly) - as long as NOTE is posted in some text somewhere, so they
know why it not work as expected with their/users keyboard (ie 4+
keys, etc)

So next question (after answer Jo's one):
Who feels like starting /dev/xkbd development

Also any JoyStick API is useful ATM (cos there is not one). If that
static v1 was added, it might inspire someone to and event driven v2
type (which also has potential for other devices too)

Paul