[openbeos] Re: device driver question
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Sun, 18 May 2003 19:16:52 +0200 CEST
"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 :-)).
Adios...
Axel.
- Follow-Ups:
- [openbeos] Re: device driver question
- From: Bruno van Dooren
- [openbeos] Re: device driver question
- From: François Revol
- References:
- [openbeos] device driver question
- From: Bruno van Dooren
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: Bruno van Dooren
- [openbeos] Re: device driver question
- From: François Revol
- [openbeos] device driver question
- From: Bruno van Dooren