Since it is a new driver, shall I follow the "Submitting Drivers for the
Linux Kernel" Doc? The driver is ready and passed all our QA cycles. I
have three source base, one is for 2.6.16 and 2.6.18 (for RHL 5.X and
SLES 10 SP3) , one is for 2.6.32 (For RHL 6.X, SLES11SP1), one for
2.6.27 (For SLES11). Can it be integrated to the 2.6.18 and 2.6.32 tree?
or it has to be in the latest 2.6.39 or later?
Thanks,
Joyce
On Tue, 2011-06-21 at 16:53 -0700, Joyce Yu - System Software wrote:
Since it is a new driver, shall I follow the "Submitting Drivers for the
Linux Kernel" Doc? The driver is ready and passed all our QA cycles. I
have three source base, one is for 2.6.16 and 2.6.18 (for RHL 5.X and
SLES 10 SP3) , one is for 2.6.32 (For RHL 6.X, SLES11SP1), one for
2.6.27 (For SLES11). Can it be integrated to the 2.6.18 and 2.6.32 tree?
or it has to be in the latest 2.6.39 or later?
There are 'longterm' branches for Linux 2.6.27 and 2.6.32, but they
don't include new drivers. If you want your driver to go into existing
distributions then you have to talk to the distributors. They will
generally tell you that your driver should be accepted in mainline Linux
first. So you should first submit a driver based on David Miller's
net-2.6 tree (targetting 3.0) or net-next-2.6 (targetting 3.1).
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.