Date: Wed, 20 Sep 2006 14:23:11 +0200 From: Marius Strobl <marius@alchemy.franken.de> To: Ruslan Ermilov <ru@freebsd.org> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org, Maksim Yevmenkin <maksim.yevmenkin@gmail.com> Subject: Re: cvs commit: src/sys/dev/kbdmux kbdmux.c Message-ID: <20060920122311.GA81536@alchemy.franken.de> In-Reply-To: <20060920121017.GU94944@alchemy.franken.de> References: <20060919190645.GA23068@rambler-co.ru> <bb4a86c70609191236j13fe1563w123cb046261ee129@mail.gmail.com> <20060919194819.GA23360@rambler-co.ru> <bb4a86c70609191300t3bea8380qa1898d1a89b6fc27@mail.gmail.com> <20060919203608.GE23360@rambler-co.ru> <bb4a86c70609191415m59a9ef89x91f25e6912339390@mail.gmail.com> <20060919215605.GB44298@rambler-co.ru> <20060919221404.GT94944@alchemy.franken.de> <20060920055715.GA81843@rambler-co.ru> <20060920121017.GU94944@alchemy.franken.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 20, 2006 at 02:10:17PM +0200, Marius Strobl wrote: > On Wed, Sep 20, 2006 at 09:57:15AM +0400, Ruslan Ermilov wrote: > > On Wed, Sep 20, 2006 at 12:14:04AM +0200, Marius Strobl wrote: > > > On Wed, Sep 20, 2006 at 01:56:05AM +0400, Ruslan Ermilov wrote: > > > > > > > > The proper fix would be to fix the kernel to pass an argument by > > > > value, like the userland does. But from the practical point of > > > > view, it may make sense to change the API and say that these > > > > IOCTLs now take a pointer type argument. I'm not sure. If you > > > > know of any applications (mine test util not counting :-) that > > > > use KDSKBMODE/KDSETLED/KDSKBSTATE, then we should probably fix > > > > the kernel callers. > > > > > > XFree86/Xorg use KDSKBMODE and KDSETLED, see f.e. the Xorg > > > "kbd" driver: > > > http://webcvs.freedesktop.org/xorg/xserver/xorg/hw/xfree86/os-support/bsd/bsd_kbd.c?revision=1.8&view=markup > > > > > Hmm, but they don't work on sparc64. How X.Org ever works then? > > I remember installing it on my sparc64 laptop... > > KDSETLED just never worked on sparc64 so far (from userland...), > keyboard LEDs just don't get lit when in X. As for KDSKBMODE > K_RAW is defined as 0 so X happens to put the keyboard into > raw mode as expected and syscons(4) makes sure that the > keyboard is in translate mode in sccngetch(). So apart from > the keyboard LEDs keyboards just happen to work in X and > when back on the console on sparc64. ...at least if one doesn't use custom keycodes in X Marius
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060920122311.GA81536>