Hi,
We develop kernel module for the interface for our scientific devices. We have to provide headers of the module, because they provide ioctl's for user-space software. Unfortunately I didn't find any information about how to do it correctly. The first way is to put headers into /usr/include/linux tree. The second way is to put all of the sources into /usr/src/kernel- modules tree. Which way is the correct for 3th-party module? What name is correct for the '-devel' rpm package of kmp?
Matwey V. Kornilov napsal(a):
We develop kernel module for the interface for our scientific devices. We have to provide headers of the module, because they provide ioctl's for user-space software. Unfortunately I didn't find any information about how to do it correctly. The first way is to put headers into /usr/include/linux tree. The second way is to put all of the sources into /usr/src/kernel- modules tree. Which way is the correct for 3th-party module?
If this is the userspace interface, then /usr/include/linux seems like the right place, so that you can just say #include <linux/myioctl.h> in your application.
What name is correct for the '-devel' rpm package of kmp?
<main package>-devel I'd say.
Michal
Michal Marek wrote:
Matwey V. Kornilov napsal(a):
What name is correct for the '-devel' rpm package of kmp?
<main package>-devel I'd say.
The package that consists of /usr/include/linux/*.h is named linux-kernel- headers. <main package>-headers is alternative name this way. I am little confused.
The second possible problem is to build devel package separately. The driver API never changes and this way we should avoid rebuilding of userspace software when new version of the driver package appears.
buildservice@lists.opensuse.org
-
Matwey V. Kornilov -
Michal Marek