[openbeos] Re: device driver question
- From: François Revol <revol@xxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Sun, 18 May 2003 21:20:51 +0200 (CEST)
En réponse à Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>:
> "Bruno van Dooren" <bruno_van_dooren@xxxxxxxxxxx> wrote:
> > now assume that the mouse was not plugged in at boot time (no
> > devices. init_hardware fails),
> > i see this and i plug it in after boot time.
> > how can i let the system know that it should try to init_hardware and
>
> > load the driver?
> >
> > i could manually remove the driver and drop it again in the /bin
> > folder, but that is soooo ugly.
> > there has to be some way to do this right?
>
> Yes and no - there is the "rescan" command (shell) which triggers a
> reloading of your driver, i.e.:
> $ rescan kb_mouse
>
> Since both, the keyboard and the mouse, are connected via PS/2, and are
> therefore using the PS/2 protocol, BeOS has one driver to rule them
> all. I don't know if you plan to duplicate this, though, it wouldn't be
> needed for compatibility (and if you did, a name like "keyboard_mouse"
> would be preferable :-)).
>
What could "kb" mean besides kick-ban ? :))
Or maybe ps2_kbmouse, or ps2_keyb_mouse ?
François.
--
"One driver to rule them all."
Axel Dörfler.
- References:
- [openbeos] Re: device driver question
- From: Axel Dörfler
Other related posts:
- » [openbeos] device driver question
- » [openbeos] Re: device driver question
- » [openbeos] Re: device driver question
- » [openbeos] Re: device driver question
- » [openbeos] Re: device driver question
- » [openbeos] Re: device driver question
- » [openbeos] Re: device driver question
- » [openbeos] Re: device driver question
- [openbeos] Re: device driver question
- From: Axel Dörfler