lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 11 Jan 2009 12:24:58 +0000 From: David Woodhouse <dwmw2@...radead.org> To: David Miller <davem@...emloft.net> Cc: Valdis.Kletnieks@...edu, alessandro.suardi@...il.com, jaswinderlinux@...il.com, linux-kernel@...r.kernel.org, netdev@...r.kernel.org Subject: Re: 2.6.28-git8: tg3 doesn't work due to firmware not loading (-git7 is ok) On Sun, 2009-01-11 at 04:08 -0800, David Miller wrote: > From: Valdis.Kletnieks@...edu > Date: Sun, 11 Jan 2009 06:10:58 -0500 > > > On Fri, 09 Jan 2009 14:04:22 PST, David Miller said: > > > From: "Alessandro Suardi" <alessandro.suardi@...il.com> > > > Date: Fri, 9 Jan 2009 18:30:40 +0100 > > > > > > > Clearly the requirement changed in -git8, AFAICS. > > > > > > Because -git8 is where the firmware requirement got added. > > > > > > If you build the TG3 driver statically into your kernel, > > > the only way to get the firmware properly loaded is to > > > enable that CONFIG_FIRMWARE_IN_KERNEL option. > > > > Maybe this is one of those cases where we actually do want a SELECT? > > > > select FIRMWARE_IN_KERNEL if TIGON3=y > > > > or similar? > > I have no idea how this is intended to work, David will know. Actually, I think the real issue here might be that the tg3 driver is now behaving _differently_ to how other modern drivers work. It tries to obtain the firmware once at initialisation time and if that fails it doesn't register the device. Other drivers will load the firmware later, at the time the device is brought up. This means that even if you build the driver into the kernel without its firmware, it can still request the firmware later, when you try to start _using_ it. And when the file system is available. I'll take a look and see if I can remedy that. Then we wouldn't _need_ the FIRMWARE_IN_KERNEL option. -- David Woodhouse Open Source Technology Centre David.Woodhouse@...el.com Intel Corporation -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists