Hi! Thanks for the information! 

After I use follow your method, I find out that the key_sym and key_cap field of F17 is correct now, which is 0xF0CE.

However, the scan code field is still 0, while F13 is 0x59, F14 is 0x5E, F15 is 0x5D and F16 is 0x5F. Those definitions 
are a little different from those defined in the Microsoft document. So I am wondering that if they can be redefined to 
match the document, and also add supports for F17 in the future ? :)

Best Regards,
John

> Likely not as I don't have a keyboard here that has keys upto F17 on it :)
> 
> Is the scancode a valid code?
> 
> http://download.microsoft.com/download/1/6/1/161ba512-40e2-4cc9-843a-
> 923143f3456c/translate.pdf
> 
> Put the input driver into a high level of verbosity (devi-hid -vvvvvvvv kbd) 
> and you should see what the driver is picking up.  If the scan codes are valid
>  (which I expect that they should be) then its just a matter of updating your 
> keyboard map with something that recognizes those scan codes.  The keyboard 
> map files are located in /usr/photon/keyboard
>  
> The .kdef file is the compilable definition file that you would have to make 
> your changes in.
> 
> Best regards,
> 
> Erick
> 
> 
> > Is there a chance that devi-hid will support F17 and other USB Keyboard 
> usages
> >  in 6.4.2 ?
> > 
> > > > I have searched all over the project codes and cannot find the source 
> code
> >  
> > > for
> > > >  devi-hid, can anyone kindly tell me where it is located ?
> > > > Thanks
> > > 
> > > Hi,
> > > 
> > > Its not currently published, is there something in particular that you are
>  
> > > having troubles with?
> > > 
> > > Best regards,
> > > 
> > > Erick
> > 
> > 
> 
>