Proper way to release binary driver?

"Eric W. Biederman" wrote: > If what you are after is a way to release a driver that is not a > hassle to add to an already working system, you will find a more > receptive ear. I have heard some talk, that it would be a good idea > to figure out how to standardize how to compile a kernel driver

Re: Proper way to release binary driver?

Hi, I'd take a look at how nvidia delivers the module for their video cards... http://www.nvidia.com/Products/Drivers.nsf/Linux.html you build the module with your current kernel or download the one for your distribution (limited number) 4-front tenchnologies has also done a long-term good job

Re: Proper way to release binary driver?

On 04.06 Christopher Turcksin wrote: > > In practice, that doesn't work. A driver compiled with 2.2.16 doesn't > load with 2.2.16-5.0 (from RedHat 6.2) (just an example). > Thats is probably because RH 2.2.16-5.0 is not 2.2.16, but 2.2.17-pre-something. Due to the bad idea of distros to name

Re: Proper way to release binary driver?

> We had hoped that MODVERSIONS would allow us to provide a single (or at > most a few) binary driver. Kernels with even minor version numbers are > supposed to be stable (even if they are buggy) ie. not have wildly > changing kernel interfaces. They have a stable API. THe ABI thing is an irrelev

Re: Proper way to release binary driver?

Hello, I would like to thank everybody who replied to my question yesterday. There were a lot of good suggestions and examples for me to go and look at. The conclusion we had come to between ourselves here was already very similar to most things suggested, but we were running into some smaller

How to build modules outside the kernel tree? [Was: Proper way to release binary driver?]

Christopher Turcksin <[EMAIL PROTECTED]> writes: > "Eric W. Biederman" wrote: > > > If what you are after is a way to release a driver that is not a > > hassle to add to an already working system, you will find a more > > receptive ear. I have heard some talk, that it would be a good idea > > t

Re: How to build modules outside the kernel tree? [Was: Proper way to release binary driver?]

Eric W. Biederman wrote: > So for solutions (That I know of): > > With recent kernels with modules_install a: > /lib/modules/`uname -r`/build > directory is created, that effectively points to the kernel source > tree the modules were built with. With the 2.4.x currently this is a > symlink so