Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Oct 2006 13:35:42 +0000 (UTC)
From:      Ruslan Ermilov <ru@FreeBSD.org>
To:        src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   cvs commit: src/sys/dev/atkbdc atkbd.c
Message-ID:  <200610251335.k9PDZgFd089461@repoman.freebsd.org>

next in thread | raw e-mail | index | archive | help
ru          2006-10-25 13:35:42 UTC

  FreeBSD src repository

  Modified files:
    sys/dev/atkbdc       atkbd.c 
  Log:
  Fix LEDs not working when atkbd is an active keyboard and the physical
  keyboard is attached only after the system has already booted.
  
  If USB keyboard is also present, and there's no kbdmux(4), the problem
  has been hiding itself because as soon as we get to multi-user, the
  USB keyboard becomes an active keyboard (see devd.conf), thus marking
  atkbd inactive and letting the old code initialize the keyboard.
  
  With kbdmux(4), or if there's no USB keyboard, the atkbd keyboard is
  always active, whether it's physically attached or not, thus it never
  initialized itself properly on a physical attach.
  
  To fix this, move block that initialized the keyboard on attach upper
  so it doesn't depend on the (KBD_IS_ACTIVE(kbd) && KBD_IS_BUSY(kbd))
  condition.  Also move KBD_FOUND_DEVICE() a few lines upper so that
  KDSETLED and KDSETREPEAT that follow it propagate to the controller.
  
  MFC after:      3 days
  
  Revision  Changes    Path
  1.52      +16 -16    src/sys/dev/atkbdc/atkbd.c



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200610251335.k9PDZgFd089461>