How to get notified of a USB plugin and manually specify the driver to use
I am trying to get at the bottom of how to intercept when a USB is plugged in, so that you can completely customize the experience of plugging it in and using it. Without anything else happening. That is, without the USB device invoking some functionality of some driver or anything like that. I would like to invoke this process manually, and prevent it otherwise.
I read this which was very helpful:
http://matthias.vallentin.net/blog/2007/04/writing-a-linux-kernel-driver-for-an-unknown-usb-device/#the-device-driver
In it it says:
The USB driver is represented by a struct
usb_drivercontaining some function callbacks and variables identifying the USB driver. When the module is loaded via theinsmodprogram, the__init usb_ml_init(void)function is executed which registers the driver with the USB subsystem. When the module is unloaded,__exit usb_ml_exit(void)is called which deregisters the driver from the USB subsystem. The__initand__exittokens indicate that these functions are only called at initialization and exit time. Having loaded the module, the probe and disconnect function callbacks are set up. In the probe function callback, which is called when the device is being plugged in, the driver initializes any local data structures used to manage the USB device. For example, it allocates memory for the struct usb_ml which contains run-time status information about the connected device.
So what it sounds like is the Linux Kernel automatically calls probe for all connected usb devices. I would like to basically know how to prevent all other potential drivers' probe function from being called so that the only one that is called is my driver. Then from there my driver can manually select one of the other drivers, and install it and everything.
Please advise on where to look in the linux source code on how to handle this problem of preventing the probe from being called on all except my own driver, or how otherwise to accomplish this.
kernel users
asked 4 mins ago
user10869858user10869858
1
New contributor
user10869858 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I am trying to get at the bottom of how to intercept when a USB is plugged in, so that you can completely customize the experience of plugging it in and using it. Without anything else happening. That is, without the USB device invoking some functionality of some driver or anything like that. I would like to invoke this process manually, and prevent it otherwise.
I read this which was very helpful:
http://matthias.vallentin.net/blog/2007/04/writing-a-linux-kernel-driver-for-an-unknown-usb-device/#the-device-driver
In it it says:
The USB driver is represented by a struct
usb_drivercontaining some function callbacks and variables identifying the USB driver. When the module is loaded via theinsmodprogram, the__init usb_ml_init(void)function is executed which registers the driver with the USB subsystem. When the module is unloaded,__exit usb_ml_exit(void)is called which deregisters the driver from the USB subsystem. The__initand__exittokens indicate that these functions are only called at initialization and exit time. Having loaded the module, the probe and disconnect function callbacks are set up. In the probe function callback, which is called when the device is being plugged in, the driver initializes any local data structures used to manage the USB device. For example, it allocates memory for the struct usb_ml which contains run-time status information about the connected device.
So what it sounds like is the Linux Kernel automatically calls probe for all connected usb devices. I would like to basically know how to prevent all other potential drivers' probe function from being called so that the only one that is called is my driver. Then from there my driver can manually select one of the other drivers, and install it and everything.
Please advise on where to look in the linux source code on how to handle this problem of preventing the probe from being called on all except my own driver, or how otherwise to accomplish this.
kernel users
asked 4 mins ago
user10869858user10869858
1
New contributor
user10869858 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I am trying to get at the bottom of how to intercept when a USB is plugged in, so that you can completely customize the experience of plugging it in and using it. Without anything else happening. That is, without the USB device invoking some functionality of some driver or anything like that. I would like to invoke this process manually, and prevent it otherwise.
I read this which was very helpful:
http://matthias.vallentin.net/blog/2007/04/writing-a-linux-kernel-driver-for-an-unknown-usb-device/#the-device-driver
In it it says:
The USB driver is represented by a struct
usb_drivercontaining some function callbacks and variables identifying the USB driver. When the module is loaded via theinsmodprogram, the__init usb_ml_init(void)function is executed which registers the driver with the USB subsystem. When the module is unloaded,__exit usb_ml_exit(void)is called which deregisters the driver from the USB subsystem. The__initand__exittokens indicate that these functions are only called at initialization and exit time. Having loaded the module, the probe and disconnect function callbacks are set up. In the probe function callback, which is called when the device is being plugged in, the driver initializes any local data structures used to manage the USB device. For example, it allocates memory for the struct usb_ml which contains run-time status information about the connected device.
So what it sounds like is the Linux Kernel automatically calls probe for all connected usb devices. I would like to basically know how to prevent all other potential drivers' probe function from being called so that the only one that is called is my driver. Then from there my driver can manually select one of the other drivers, and install it and everything.
Please advise on where to look in the linux source code on how to handle this problem of preventing the probe from being called on all except my own driver, or how otherwise to accomplish this.
kernel users
asked 4 mins ago
user10869858user10869858
1
New contributor
user10869858 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I am trying to get at the bottom of how to intercept when a USB is plugged in, so that you can completely customize the experience of plugging it in and using it. Without anything else happening. That is, without the USB device invoking some functionality of some driver or anything like that. I would like to invoke this process manually, and prevent it otherwise.
I read this which was very helpful:
http://matthias.vallentin.net/blog/2007/04/writing-a-linux-kernel-driver-for-an-unknown-usb-device/#the-device-driver
In it it says:
The USB driver is represented by a struct
usb_drivercontaining some function callbacks and variables identifying the USB driver. When the module is loaded via theinsmodprogram, the__init usb_ml_init(void)function is executed which registers the driver with the USB subsystem. When the module is unloaded,__exit usb_ml_exit(void)is called which deregisters the driver from the USB subsystem. The__initand__exittokens indicate that these functions are only called at initialization and exit time. Having loaded the module, the probe and disconnect function callbacks are set up. In the probe function callback, which is called when the device is being plugged in, the driver initializes any local data structures used to manage the USB device. For example, it allocates memory for the struct usb_ml which contains run-time status information about the connected device.
So what it sounds like is the Linux Kernel automatically calls probe for all connected usb devices. I would like to basically know how to prevent all other potential drivers' probe function from being called so that the only one that is called is my driver. Then from there my driver can manually select one of the other drivers, and install it and everything.
Please advise on where to look in the linux source code on how to handle this problem of preventing the probe from being called on all except my own driver, or how otherwise to accomplish this.
kernel users
kernel users
asked 4 mins ago
user10869858user10869858
1
New contributor
user10869858 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 4 mins ago
user10869858user10869858
1
New contributor
user10869858 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 4 mins ago
user10869858user10869858
1
New contributor
user10869858 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 4 mins ago
user10869858user10869858
1
asked 4 mins ago
user10869858user10869858
1
1
New contributor
user10869858 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
user10869858 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
user10869858 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
user10869858 is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493593%2fhow-to-get-notified-of-a-usb-plugin-and-manually-specify-the-driver-to-use%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
user10869858 is a new contributor. Be nice, and check out our Code of Conduct.
user10869858 is a new contributor. Be nice, and check out our Code of Conduct.
user10869858 is a new contributor. Be nice, and check out our Code of Conduct.
user10869858 is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493593%2fhow-to-get-notified-of-a-usb-plugin-and-manually-specify-the-driver-to-use%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
