Mailinglist Archive: opensuse (1196 mails)
| < Previous | Next > |
[opensuse] Re: [opensuse-buildservice] Making kernel modules for specific kernel versions
- From: Roger Oberholtzer <roger@xxxxxx>
- Date: Thu, 07 Jan 2010 11:10:28 +0100
- Message-id: <1262859028.18216.45.camel@xxxxxxxxxxxx>
On Thu, 2010-01-07 at 11:04 +0100, Jan Engelhardt wrote:
I thought the openSUSE kernel was compiled to require precise version
matching when loading modules. Is this not the case?
Sounds too good to be true.
--
Roger Oberholtzer
OPQ Systems / Ramböll RST
Ramböll Sverige AB
Krukmakargatan 21
P.O. Box 17009
SE-104 62 Stockholm, Sweden
Office: Int +46 10-615 60 20
Mobile: Int +46 70-815 1696
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
On Thursday 2010-01-07 11:01, Roger Oberholtzer wrote:
Yes, you just build a KMP...
... KMPs can be used for multiple kernels (the built against one
and laters), if the kabi for those stays stable.
While we do not guarantee that for openSUSE, we try to keep it that way.
A KMP built against the 11.2 GA kernel will for instance still work with
the current update kernel.
If I make a kernel driver package, can I trigger it getting rebuilt
automatically when a kernel update is released? Without me having to
trigger anything by hand?
Often, KMPs still work across a minor kernel update, by means
of the weak-modules mechanism.
I thought the openSUSE kernel was compiled to require precise version
matching when loading modules. Is this not the case?
Section 4.6 in the link I referenced implies that
this is possible. Would it happen automatically if I build against
openSUSE:11.2:Update and a kernel update is released?
It should.
Sounds too good to be true.
--
Roger Oberholtzer
OPQ Systems / Ramböll RST
Ramböll Sverige AB
Krukmakargatan 21
P.O. Box 17009
SE-104 62 Stockholm, Sweden
Office: Int +46 10-615 60 20
Mobile: Int +46 70-815 1696
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
| < Previous | Next > |