[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: adding to nk7110.c
From: |
Pawel Kot |
Subject: |
Re: adding to nk7110.c |
Date: |
Wed, 12 Feb 2003 10:02:38 +0100 |
>>> address@hidden 11 February 2003 18:38:11 >>>
> 1 prototyping the function:
>
> static gn_error NK7110_EnterChar(gn_data *data, struct
gn_statemachine *state);
>
> 2 adding a case statement:
>
> case GN_OP_EnterChar:
> return NK7110_EnterChar(data, state);
>
> 3 adding a function called "EnterChar":
>
> static gn_error EnterChar(gn_data *data, struct gn_statemachine
*state)
> {
> code
> }
Yep, this is correct. Just follow the naming connection.
> I'm going to base that function on a piece of code from nk6110.c, and
> use nk6110.txt and nk7110.txt as a guide for the modification.
Assuming
Very smart.
> I'm not oversimplifying the process grossly (I bet I am!) it seems
that
Not really ;-)
> there are not too many parts of this function which are specific to
the
> 6110, apart from an opening statement:
>
> nk6100_keytable *keytable = DRVINSTANCE(state)->keytable;
> which I must admit I don't wholly understand, and is my first
stumbling
> block. is "nk6100_keytable" included in one of the header files at
the
> opening of the document? Is there an equivalent "nk7100_keytable",
or
> is this where the real work lies, or am I talking nonsense?
See, BuildKeytable() function and the comment inside. nk6100
uses a bit different internal structure then nk7110. It's up to
you how you implement it.
pkot