-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Why is iwlwifi still at version 1.2.23?
Is there some problem with it?
- --
Antonio Quartulli,
Student of Computer Science at University of Pisa
Web: http://www.quartulli.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQEVAwUBR7YxvpUBe9lBofULAQKazggAmHSKYtXEs9eCLfiCVpwY+En0jNpghP2r
xN/JJibRq4qbHtMKC521PeLZ6RP2901TnL5p8htpRlC0A02b19UU+7V7ivSuHOip
LRgOP6Q3LUYaXTcG/GCULmTCdeGCI20ENrfbwuo1twODPX21XXUUgzq3ckHRjqLs
opxGgC9sQ8KamUHqs9Sf78mRV+SHEN19jf7aOT5uPQZQBTA6LWYlOiAxhauNpzCJ
7Lr5wExAA0hA4rVrxNXI5bcaCXofEB2x+NrpPkNMYD8tvR9nB0olERcPHDNboaBx
e0M4t7khI/GT5S52Py6BO83+jwDLUD4/7WuLGyWbErKZF5t99B2WTw==
=omxU
-----END PGP SIGNATURE-----
On , Antonio Quartulli wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Why is iwlwifi still at version 1.2.23?
> Is there some problem with it?
I assume you are referring to the out of tree driver available from
intellinuxwireless.org.
iwlwifi has been included in the kernel since 2.6.24, for this reason
development has shifted to focus on upstream. The repository at
intellinuxwireless.org has not been receiving changes since release of
1.2.23 - all changes go directly upstream. You can use the latest
upstream driver by utilizing the compat-wireless project
(http://linuxwireless.org/en/users/Download). Currently the upstream
driver also has version number 1.2.23 - even tough it received
significant changes since the out of tree release of 1.2.23. To reduce
this confusion we did send a version update to the development tree
(making the in kernel iwlwifi be version 1.2.26), this change is still
to be applied.
Version numbering does make less sense now that we are in the kernel ...
please be assured that you are using the latest driver when you are
using the compat-wireless project.
Reinette
On Thu, 2009-12-24 at 13:08 +0800, David Miller wrote:
>
> Someone please expediently fix whatever it is that makes the iwlwifi
> drivers rebuild every single time I type make.
>
> It's a real intense pain when I have an 'allmodconfig' tree for build
> validations, I pull some unrelated changed into the tree, and I see
> iwlwifi rebuild no matter what.
>
> This is not sane behavior.
I'm trying allmodconfig on wireless-testing now. It takes some time to
finish make. But a simple running "make M=drivers/net/wireless/" twice
doesn't show this issue.
Thanks,
-yi
On Thu, 2009-12-24 at 13:52 +0800, David Miller wrote:
> From: Zhu Yi <[email protected]>
> Date: Thu, 24 Dec 2009 13:46:07 +0800
>
> > I'm trying allmodconfig on wireless-testing now. It takes some time to
> > finish make. But a simple running "make M=drivers/net/wireless/" twice
> > doesn't show this issue.
> >
>
> It's the include of generated/utsrelease.h by iwl-core.h that causes
> the rebuild.
Thanks. It was first introduced by below commit. And was later changed
to use generated/utsrelease.h. I'm wondering if we should really use
linux/utsrelease.h (or linux/version.h) or remove the kernel version
totally from the driver version (driver compile tag can be remained).
Any suggestions?
Thanks,
-yi
commit 900bb717424e5df12b1ef7ebb017be2a8915b806
Author: Reinette Chatre <[email protected]>
Date: Wed Dec 2 12:53:01 2009 -0800
iwlwifi: driver version track kernel version
The driver version number is a remnant from when there was an out-of-tree
iwlwifi driver. Now that the driver forms part of kernel source we do not
need a separate driver version. Instead, we now use the kernel version as
driver version. We maintain the previous tags used to indicate which
components the driver has been compiled with.
From: Zhu Yi <[email protected]>
Date: Thu, 24 Dec 2009 13:46:07 +0800
> I'm trying allmodconfig on wireless-testing now. It takes some time to
> finish make. But a simple running "make M=drivers/net/wireless/" twice
> doesn't show this issue.
>
It's the include of generated/utsrelease.h by iwl-core.h that causes
the rebuild.
From: Zhu Yi <[email protected]>
Date: Thu, 24 Dec 2009 14:24:56 +0800
> Thanks. It was first introduced by below commit. And was later changed
> to use generated/utsrelease.h. I'm wondering if we should really use
> linux/utsrelease.h (or linux/version.h) or remove the kernel version
> totally from the driver version (driver compile tag can be remained).
> Any suggestions?
Remove the dependency, every time you type make the build number
increases and this will force your driver to rebuild.