On Wed, Oct 22, 2008 at 12:13 AM, Marcel Holtmann <holtmann@xxxxxxxxxxxxxxx> wrote: > Hi Tomas, > >> >> > > On Tue, 2008-10-21 at 11:27 -0700, reinette chatre wrote: >> >> > >> Two new versions of 3945 uCode is now available for download from >> >> > >> http://intellinuxwireless.org/?n=Downloads. Two versions are available >> >> > >> as we have updated the API version of the uCode and included pending >> >> > >> fixes in both API versions. >> >> > >> >> >> > >> Version 15.28.1.8 supports API v1 and can be used with most current 3945 >> >> > >> drivers. Version 15.28.2.8 (API v2) is required when you start using the >> >> > >> latest 3945 driver from wireless-testing at the time it includes the >> >> > >> patch "iwl3945 : Fix a-band association for passive channels". >> >> > > >> >> > > Can you make the driver work with the old ucode? We even do that for >> >> > > drivers where we don't control the ucode like b43... >> >> > >> >> > What for? >> >> >> >> Well, so that installing a new kernel doesn't suddenly break your >> >> network connection and ability to download the firmware, for instance. >> >> If you want more arguments you can go read all the "b43 sucks" threads >> >> about it. >> > >> > Johnannes has a point, that is a lot nicer to users... >> >> Maybe, but it will complicate the code beyond good taste to just >> satisfy the single moment when kernel is upgraded. I don't mean in >> general I mean in this particular case when API changes. >> Anyhow a good distro shell deal with this in packaging dependencies >> and normal person will keep old kernel around when compiling new one. >> Both ucodes can be present on the file system at the same time so I >> hope the risk is low. > > it is the same argument as for everything else. We should be able to run > a new kernel with old userspace. Yet this is not user space, if there won't be a little :) license issue this will integral part of the driver. Tomas -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
