Revision tags: release/6.2.0_cvs, release/6.2.0 |
|
#
ac3912b0 |
| 25-Oct-2006 |
Ruslan Ermilov <ru@FreeBSD.org> |
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 p
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
show more ...
|
#
9fddcc66 |
| 27-Sep-2006 |
Ruslan Ermilov <ru@FreeBSD.org> |
Fix our ioctl(2) implementation when the argument is "int". New ioctls passing integer arguments should use the _IOWINT() macro. This fixes a lot of ioctl's not working on sparc64, most notable bein
Fix our ioctl(2) implementation when the argument is "int". New ioctls passing integer arguments should use the _IOWINT() macro. This fixes a lot of ioctl's not working on sparc64, most notable being keyboard/syscons ioctls.
Full ABI compatibility is provided, with the bonus of fixing the handling of old ioctls on sparc64.
Reviewed by: bde (with contributions) Tested by: emax, marius MFC after: 1 week
show more ...
|
Revision tags: release/5.5.0_cvs, release/5.5.0 |
|
#
f6ce2a64 |
| 17-May-2006 |
Poul-Henning Kamp <phk@FreeBSD.org> |
Send the pcvt(4) driver off to retirement.
|
#
73dbd3da |
| 12-May-2006 |
John Baldwin <jhb@FreeBSD.org> |
Remove various bits of conditional Alpha code and fixup a few comments.
|
Revision tags: release/6.1.0_cvs, release/6.1.0 |
|
#
6621aa5c |
| 26-Apr-2006 |
Maxim Sobolev <sobomax@FreeBSD.org> |
Use the same method for detecting actual presence of AT-style keyboard controller as we use in boot blocks (querying status register until bit 1 goes off). If that doesn't happed during reasonable pe
Use the same method for detecting actual presence of AT-style keyboard controller as we use in boot blocks (querying status register until bit 1 goes off). If that doesn't happed during reasonable period assume that the hardware doesn't have AT-style keyboard controller. This makes FreeBSD working almost OOB on MacBook Pro (still there are issues with putting second CPU core on-line, but since installation CD comes with UP kernel with this change one should be able to install FreeBSD without playing tricks with hints). Other legacy-free hardware (e.g. IBM NetVista S40) should benefit from this as well, but since I don't have any I can't verify.
It should make no difference on the ordinary i386 hardware (since in that case that hardware already would be having an issues with A20 routines in boot blocks). I don't know much about AT-style keyboard controller on other platforms (and don't have dedicated access to one), therefore, the code is restricted to i386 for now. I suspect that amd64 may need this as well, but I would rather leave this decision to someone who knows better about the platform(s) in question.
I have tested this change on as many "ordinary i386 boxes" as I can get my hands on, and it doesn't create any false negatives on hardware with AT-style keyboard present.
MFC after: 1 month
show more ...
|
Revision tags: release/6.0.0_cvs, release/6.0.0 |
|
#
520b6353 |
| 10-Jun-2005 |
Marius Strobl <marius@FreeBSD.org> |
- Hook up the new locations of the atkbdc(4), atkbd(4) and psm(4) source files after they were repo-copied to sys/dev/atkbdc. The sources of atkbdc(4) and its children were moved to the new locat
- Hook up the new locations of the atkbdc(4), atkbd(4) and psm(4) source files after they were repo-copied to sys/dev/atkbdc. The sources of atkbdc(4) and its children were moved to the new location in preparation for adding an EBus front-end to atkbdc(4) for use on sparc64; i.e. in order to not further scatter them over the whole tree which would have been the result of adding atkbdc_ebus.c in e.g. sys/sparc64/ebus. Another reason for the repo-copies was that some of the sources were misfiled, e.g. sys/isa/atkbd_isa.c wasn't ISA-specific at all but for hanging atkbd(4) off of atkbdc(4) and was renamed to atkbd_atkbdc.c accordingly. Most of sys/isa/psm.c, i.e. expect for its PSMC PNP part, also isn't ISA-specific. - Separate the parts of atkbdc_isa.c which aren't actually ISA-specific but are shareable between different atkbdc(4) bus front-ends into atkbdc_subr.c (repo-copied from atkbdc_isa.c). While here use bus_generic_rl_alloc_resource() and bus_generic_rl_release_resource() respectively in atkbdc_isa.c instead of rolling own versions. - Add sparc64 MD bits to atkbdc(4) and atkbd(4) and an EBus front-end for atkbdc(4). PS/2 controllers and input devices are used on a couple of Sun OEM boards and occur on either the EBus or the ISA bus. Depending on the board it's either the only on-board mean to connect a keyboard and mouse or an alternative to either RS232 or USB devices. - Wrap the PSMC PNP part of psm.c in #ifdef DEV_ISA so it can be compiled without isa(4) (e.g. for EBus-only machines). This ISA-specific part isn't separated into its own source file, yet, as it requires more work than was feasible for 6.0 in order to do it in a clean way. Actually philip@ is working on a rewrite of psm(4) so a more comprehensive clean-up and separation of hardware dependent and independent parts is expected to happen after 6.0.
Tested on: i386, sparc64 (AX1105, AXe and AXi boards) Reviewed by: philip
show more ...
|
Revision tags: release/5.4.0_cvs, release/5.4.0 |
|
#
ff690962 |
| 26-Feb-2005 |
Sam Leffler <sam@FreeBSD.org> |
plug memory leak
Noticed by: Coverity Prevent analysis tool
|
Revision tags: release/4.11.0_cvs, release/4.11.0 |
|
#
f5517dc8 |
| 16-Dec-2004 |
John Baldwin <jhb@FreeBSD.org> |
Add a new flag to the atkbd(4) driver to disable testing the keyboard port during the device probe as this can cause hangs on some machines, specifically Compaq R3000Z series amd64 laptops. The flag
Add a new flag to the atkbd(4) driver to disable testing the keyboard port during the device probe as this can cause hangs on some machines, specifically Compaq R3000Z series amd64 laptops. The flag is bit 3, or 0x8.
PR: amd64/67745 Reported by: Neil Winterbauer newntrbr at ucla dot edu, many others Tested by: ade, astrodog at gmail dot com, many others MFC after: 1 week
show more ...
|
Revision tags: release/5.3.0_cvs, release/5.3.0 |
|
#
092a5c45 |
| 10-Jun-2004 |
John Baldwin <jhb@FreeBSD.org> |
Remove atdevbase and replace it's remaining uses with direct references to KERNBASE instead.
|
Revision tags: release/4.10.0_cvs, release/4.10.0, release/5.2.1_cvs, release/5.2.1, release/5.2.0_cvs, release/5.2.0, release/4.9.0_cvs, release/4.9.0 |
|
#
7ea199a7 |
| 07-Oct-2003 |
Max Khon <fjoe@FreeBSD.org> |
Assign keycodes for Power, Sleep and Wake keys.
Submitted by: Eugene Grosbein <eugen@grosbein.pp.ru>
|
#
aad970f1 |
| 24-Aug-2003 |
David E. O'Brien <obrien@FreeBSD.org> |
Use __FBSDID(). Also some minor style cleanups.
|
#
8ce4e518 |
| 13-Jul-2003 |
Hidetoshi Shimokawa <simokawa@FreeBSD.org> |
Fix for FAIL_IF_NO_KBD case as expected.
Even if we have no AT keyboard, an AT keyboard is registered because it's probed with KB_CONF_PROBE_ONLY flag set during console initialization. Unregister t
Fix for FAIL_IF_NO_KBD case as expected.
Even if we have no AT keyboard, an AT keyboard is registered because it's probed with KB_CONF_PROBE_ONLY flag set during console initialization. Unregister the keyboard if it doesn't present while second probe.
This should fix USB keyboard only case without 'kbdcontrol -k /dev/kbd1'.
show more ...
|
#
8a9bc9c0 |
| 02-Jul-2003 |
John Baldwin <jhb@FreeBSD.org> |
- Use the new resource_disabled() helper function to see if devices are disabled. - Change the apm driver to match the acpi driver's behavior by checking to see if the device is disabled in the i
- Use the new resource_disabled() helper function to see if devices are disabled. - Change the apm driver to match the acpi driver's behavior by checking to see if the device is disabled in the identify routine instead of in the probe routine. This way if the device is disabled it is never created.
Note that a few places (ips(4), Alpha SMP) used "disable" instead of "disabled" for their hint names, and these hints must be changed to "disabled". If this is a big problem, resource_disabled() can always be changed to honor both names.
show more ...
|
Revision tags: release/5.1.0_cvs, release/5.1.0 |
|
#
51da11a2 |
| 30-Apr-2003 |
Mark Murray <markm@FreeBSD.org> |
Fix some easy, global, lint warnings. In most cases, this means making some local variables static. In a couple of cases, this means removing an unused variable.
|
#
104a9b7e |
| 29-Apr-2003 |
Alexander Kabaev <kan@FreeBSD.org> |
Deprecate machine/limits.h in favor of new sys/limits.h. Change all in-tree consumers to include <sys/limits.h>
Discussed on: standards@ Partially submitted by: Craig Rodrigues <rodrigc@attbi.com>
|
Revision tags: release/4.8.0_cvs, release/4.8.0 |
|
#
c0f44a59 |
| 05-Feb-2003 |
Philippe Charnier <charnier@FreeBSD.org> |
Spelling.
|
Revision tags: release/5.0.0_cvs, release/5.0.0, release/4.7.0_cvs |
|
#
93b0017f |
| 25-Aug-2002 |
Philippe Charnier <charnier@FreeBSD.org> |
Replace various spelling with FALLTHROUGH which is lint()able
|
Revision tags: release/4.6.2_cvs, release/4.6.2, release/4.6.1, release/4.6.0_cvs |
|
#
2ce7d7a0 |
| 09-Apr-2002 |
Poul-Henning Kamp <phk@FreeBSD.org> |
GC various bits and pieces of USERCONFIG from all over the place.
|
#
2bb113d0 |
| 08-Apr-2002 |
Jeroen Ruigrok van der Werven <asmodai@FreeBSD.org> |
Fix typo: conole -> console
PR: 33965 Submitted by: Nicola Vitale <nivit@libero.it>
|
Revision tags: release/4.5.0_cvs, release/4.4.0_cvs |
|
#
76495257 |
| 20-Jul-2001 |
Kazutaka YOKOTA <yokota@FreeBSD.org> |
Return consistent key action codes at key press and release events. Otherwise you would see unexpected results if shift or locking keys are defined to give different actions depending on other shift/
Return consistent key action codes at key press and release events. Otherwise you would see unexpected results if shift or locking keys are defined to give different actions depending on other shift/locking keys' state.
Please keep the ukbd module and the kernel in sync, otherwise the USB keyboard won't work after this change. MFC after: 10 days
show more ...
|
Revision tags: release/4.3.0_cvs, release/4.3.0 |
|
#
d2db0502 |
| 22-Jan-2001 |
David Malone <dwmalone@FreeBSD.org> |
Free the kbd pointer when it isn't NULL, as opposed to when it is. This was a typo in the M_ZERO patches.
Submitted by: Mike Silbersack <silby@silby.com>
|
#
7cc0979f |
| 08-Dec-2000 |
David Malone <dwmalone@FreeBSD.org> |
Convert more malloc+bzero to malloc+M_ZERO.
Submitted by: josh@zipperup.org Submitted by: Robert Drehmel <robd@gmx.net>
|
Revision tags: release/4.2.0 |
|
#
db7e3af1 |
| 15-Oct-2000 |
Poul-Henning Kamp <phk@FreeBSD.org> |
Remove unneeded #include <machine/clock.h>
|
#
00d25f51 |
| 08-Oct-2000 |
Poul-Henning Kamp <phk@FreeBSD.org> |
Initiate deorbit burn sequence for <machine/console.h>.
Replace all in-tree uses with necessary subset of <sys/{fb,kb,cons}io.h>. This is also the appropriate fix for exo-tree sources.
Put warnings
Initiate deorbit burn sequence for <machine/console.h>.
Replace all in-tree uses with necessary subset of <sys/{fb,kb,cons}io.h>. This is also the appropriate fix for exo-tree sources.
Put warnings in <machine/console.h> to discourage use. November 15th 2000 the warnings will be converted to errors. January 15th 2001 the <machine/console.h> files will be removed.
show more ...
|
Revision tags: release/4.1.1_cvs, release/4.1.0, release/3.5.0_cvs |
|
#
2073104f |
| 28-May-2000 |
Andrey A. Chernov <ache@FreeBSD.org> |
Manipulate with AltGR Led (really CapsLock Led) only in K_XLATE mode, because all other modes not set ALKED flag and it means that CapsLock always turned off for them. Real bug example is X11 which n
Manipulate with AltGR Led (really CapsLock Led) only in K_XLATE mode, because all other modes not set ALKED flag and it means that CapsLock always turned off for them. Real bug example is X11 which never turn on CapsLock with Russian keyboard.
PR: 18651 Submitted by: "Mike E. Matsnev" <mike@po.cs.msu.su>
show more ...
|