@@ -811,7 +811,6 @@ static int atkbd_probe(struct atkbd *atkbd)
811
811
{
812
812
struct ps2dev * ps2dev = & atkbd -> ps2dev ;
813
813
unsigned char param [2 ];
814
- bool skip_getid ;
815
814
816
815
/*
817
816
* Some systems, where the bit-twiddling when testing the io-lines of the
@@ -825,6 +824,11 @@ static int atkbd_probe(struct atkbd *atkbd)
825
824
"keyboard reset failed on %s\n" ,
826
825
ps2dev -> serio -> phys );
827
826
827
+ if (atkbd_skip_getid (atkbd )) {
828
+ atkbd -> id = 0xab83 ;
829
+ return 0 ;
830
+ }
831
+
828
832
/*
829
833
* Then we check the keyboard ID. We should get 0xab83 under normal conditions.
830
834
* Some keyboards report different values, but the first byte is always 0xab or
@@ -833,18 +837,17 @@ static int atkbd_probe(struct atkbd *atkbd)
833
837
*/
834
838
835
839
param [0 ] = param [1 ] = 0xa5 ; /* initialize with invalid values */
836
- skip_getid = atkbd_skip_getid (atkbd );
837
- if (skip_getid || ps2_command (ps2dev , param , ATKBD_CMD_GETID )) {
840
+ if (ps2_command (ps2dev , param , ATKBD_CMD_GETID )) {
838
841
839
842
/*
840
- * If the get ID command was skipped or failed, we check if we can at least set
843
+ * If the get ID command failed, we check if we can at least set
841
844
* the LEDs on the keyboard. This should work on every keyboard out there.
842
845
* It also turns the LEDs off, which we want anyway.
843
846
*/
844
847
param [0 ] = 0 ;
845
848
if (ps2_command (ps2dev , param , ATKBD_CMD_SETLEDS ))
846
849
return -1 ;
847
- atkbd -> id = skip_getid ? 0xab83 : 0xabba ;
850
+ atkbd -> id = 0xabba ;
848
851
return 0 ;
849
852
}
850
853
0 commit comments