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: <alpine.SOC.1.00.1006011747570.22519@math.ut.ee>
Date:	Tue, 1 Jun 2010 17:52:23 +0300 (EEST)
From:	Meelis Roos <mroos@...ux.ee>
To:	chas3@...rs.sourceforge.net
cc:	netdev@...r.kernel.org
Subject: Re: Fore 200 firmware

> >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.
> 
> this firmware is in the linux-atm source tree now.  the 2.5.1 release
> should have the firmware.

2.5.1 does not seem to contain the firmware.

Even if it will be there in the next release, we should still do 
something to distribute it to the user so that any modern distro has the 
firmware available (in linux-firmware or via similar means) so the user 
does not have to redo the detective work I am doing. Packaging it along 
with linux-atm packages (atm-tools in Debian) does not seem correct, so 
do we need to make a special firmware package out of it or just add to 
some other firmware repo that is packaged already?

What's the licence of the firmware anyway - unknown likely?

And we can probably remove drivers/atm/fore200e_pca_fw.c if we 
distribute the firmware out of kernel tree.

-- 
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ