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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <89515e61-6aeb-4063-bc47-52a9ea982a26@lunn.ch>
Date: Tue, 4 Mar 2025 17:21:20 +0100
From: Andrew Lunn <andrew@...n.ch>
To: FUJITA Tomonori <fujita.tomonori@...il.com>
Cc: max.schulze@...ine.de, hfdevel@....net, netdev@...r.kernel.org
Subject: Re: tn40xx / qt2025: cannot load firmware, error -2

> You hit the error during boot? In that case, the firmware file might
> not be included in the initramfs.

With a C driver, you would add a MODULE_FIRMWARE() macro indicating
the firmware filename. The tools building the initramfs should then be
able to pull the firmware in. I see you have:

kernel::module_phy_driver! {
    drivers: [PhyQT2025],
    ...
    firmware: ["qt2025-2.0.3.3.fw"],
}

Does this last line do the equivalent of MODULE_FIRMWARE()?

	Andrew

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ