0

I am compiling an embedded Linux kernel driver for hardware h264 encoder . When modprobing, the module_init(sunxi_cedar_init); function gets called. But driver's probe callback is never called:

[ 196.516138] cedar_ve: loading out-of-tree module taints kernel. [ 196.517019] cedar_ve: module verification failed: signature and/or required key missing - tainting kernel [ 196.518369] sunxi cedar version 0.1

Two question:

  1. What are the prerequisites for probe callback to be called? This is not duplicate of when Linux calls PCI driver's probe function? because I am not using a PCI device.

  2. Can failed module verification prevent probe callback?

jpou
  • 1,935
  • 2
  • 21
  • 30
  • As you could guess, the function `platform_driver_register` registers a driver for **platform** devices. So you can use that word in your search request. See e,g, [that question](https://stackoverflow.com/questions/9168885/when-does-the-probe-function-for-a-linux-kernel-driver-gets-called). (As you could find, that question doesn't contain the **code** and refers to now-dead link. Lucky its self-answer has a "platform" word, otherwise one could only guess which kind of driver it asks about.) "Can failed module verification prevent `probe` callback?" - No, failed verification is not a reason. – Tsyvarev Feb 20 '23 at 16:25

0 Answers0