Bug#242866: marked as done (drivers containing firmware blobs)
Your message dated Wed, 25 Mar 2009 12:41:28 +0100
with message-id <20090325114128.GA5182@stro.at>
and subject line drivers containing firmware blobs
has caused the Debian Bug report #242866,
regarding drivers containing firmware blobs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
242866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=242866
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: drivers containing firmware blobs
- From: Marco d'Itri <md@Linux.IT>
- Date: Fri, 9 Apr 2004 12:40:59 +0200
- Message-id: <20040409104059.GA4933@wonderland.linux.it>
Package: kernel
Severity: serious
Tags: sarge, sid
The following files contain binary firmwares, and distributing them
appears to be a DFSG violation. (See #239952)
drivers/net/appletalk/cops_ffdrv.h
drivers/net/acenic_firmware.h
drivers/net/tokenring/3c359_microcode.h
drivers/net/pcmcia/ositech.h
drivers/char/drm/mga_ucode.h
drivers/char/drm/r128_cce.c
drivers/char/drm/radeon_cp.c
--
ciao, |
Marco | [5631 stO4f5PcqYDgg]
--- End Message ---
--- Begin Message ---
- To: 242866-done@bugs.debian.org
- Subject: drivers containing firmware blobs
- From: maximilian attems <max@stro.at>
- Date: Wed, 25 Mar 2009 12:41:28 +0100
- Message-id: <20090325114128.GA5182@stro.at>
Version: 2.6.29-1
allmost all drivers are now using request_firmware(),
just one or two that aren't, but are to be switched
are still disabled.
woow closing this, let's be happy we wont have a new
firmware dance on squeeze release.
--
maks
--- End Message ---
Reply to: