Add-ons driver location

Development
1

I’m trying to investigate the usb_hid driver, so I’ve added some log entries in the code and compiled it.

The original driver is located at “/system/add-ons/kernel/drivers/bin/usb_hid” and if I’ve understood correctly I need to put my new driver in “/system/non-packaged/add-ons/kernel/drivers/bin/usb_hid”

Looking at the logs /system/var/log/syslog, only the existing driver is used and not the new one in the “non-packaged”.

Is this “non-packaged” location wrong for my test ?

2

I think you need to blacklist the original one otherwise Haiku uses the first one it finds.

1 Like
3

Indeed, the usb_hdi addon from haiku package must be blacklisted for such situation.

A quick how to:

2 Likes
4

Ok thanks

I will test the below once I have access to my system:

Package haiku {
BlockedEntries {
add-ons/kernel/drivers/bin/usb_hid
}
}

I’ve a 8bitdo gamepad and I would like to check if the current behavior could be enhanced (listusb is considerating this device as an Xbox 360 controller)

1 Like
5

If the device pretends to be an xbox360 controller, reusing the same product and vendor id, it will be difficult to detect that it is not, in fact, an xbox360 controller.

listusb does not depend on any driver to get that info, it directly communicates with the usb stack.