Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 20 Feb 2004 19:19:42 +0100
From:      Melvyn Sopacua <freebsd-current@webteckies.org>
To:        "M. Warner Losh" <imp@bsdimp.com>
Cc:        current@FreeBSD.org
Subject:   Re: Review/Test: Pseudo-device unit number management patch
Message-ID:  <200402201919.42458.freebsd-current@webteckies.org>
In-Reply-To: <20040218.063204.74403147.imp@bsdimp.com>
References:  <200402170846.17399.freebsd-current@webteckies.org> <39796.1077013415@critter.freebsd.dk> <20040218.063204.74403147.imp@bsdimp.com>

next in thread | previous in thread | raw e-mail | index | archive | help

[-- Attachment #1 --]
On Wednesday 18 February 2004 14:32, M. Warner Losh wrote:
> In message: <39796.1077013415@critter.freebsd.dk>
>
>             "Poul-Henning Kamp" <phk@phk.freebsd.dk> writes:
> : Current our handing is that if it disappears, it's gone, if it comes
> : back it's probably a new one anyway.
>
> Yes.  If the hardware goes away and comes back, it can be very
> difficult to know if you have the same hardware or different
> hardware. 

For something as critical as a keyboard, would it be possible:
- to keep the current layer in tact, but fool the layer that the device is 
always there?
- store the last used keyboard somewhere and if no keyboard is found on boot, 
assume the last one used and start emulating it's existence

All this of course, controllable by a kernel / bootloader / sysctl option, so 
that environments where keyboard switching is normal do not suffer.

-- 
Melvyn

=======================================================
FreeBSD sarevok.idg.nl 5.2-CURRENT FreeBSD 5.2-CURRENT #2: Mon Feb 16 19:59:52 
CET 2004     
root@sarevok.webteckies.org:/usr/obj/usr/src/sys/SAREVOK_NOAPM_NODEBUG  i386
=======================================================

[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQBANk++Ov9JNmfFN5URAkuuAJ9n7cnnvON6JytaP61Bx6lYwbFDmwCgsHEk
jJjCXjNLoBP5MQcG13KcBAc=
=T8be
-----END PGP SIGNATURE-----

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