netdev - Fore 200 firmware

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-next>] [day] [month] [year] [list]

Message-ID: <alpine.SOC.1.00.1005311058180.2805@math.ut.ee>
Date:	Mon, 31 May 2010 11:06:31 +0300 (EEST)
From:	Meelis Roos <mroos@...ux.ee>
To:	Chas Williams <chas@....nrl.navy.mil>
cc:	netdev@...r.kernel.org
Subject: Fore 200 firmware

Hello,

commit 9c54004ea717116a10886e254e26502ffb1136e9 (atm: [fore200e] 
convert to use request_firmware()) made the fore driver user 
request_firmware() but also removed the building of firmware image.

So the current state is that drivers/atm contains the C dump of fore 200 
firmware in drivers/atm/fore200e_pca_fw.c but this firmware is not built 
and not installed by make install. It's also not present in 
linux-firware tree/packages so the fore driver can not load its firmware 
from anywhere. I guess this is not the intended outcome.

Should we move the firmware to linux-firmware repository and remove 
drivers/atm/fore200e_pca_fw.c or should we convert and install the 
firmware in kernel build system?

-- 
Meelis Roos (mroos@...ux.ee)
--
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