From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Xose Vazquez Perez <xose.vazquez@gmail.com>,
Daniel Drake <dsd@laptop.org>,
Ulrich Kunitz <kune@deine-taler.de>,
David Woodhouse <dwmw2@infradead.org>,
Ben Hutchings <ben@decadent.org.uk>,
<linux-wireless@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH] linux-firmware: add MISSING file
Date: Sat, 12 Jan 2013 23:39:43 +0100 [thread overview]
Message-ID: <1358030383-15609-1-git-send-email-xose.vazquez@gmail.com> (raw)
to document the reason why a firmware is not present
Cc: Daniel Drake <dsd@laptop.org>
Cc: Ulrich Kunitz <kune@deine-taler.de>
Cc: David Woodhouse <dwmw2@infradead.org>
Cc: Ben Hutchings <ben@decadent.org.uk>
Cc: <linux-wireless@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>
Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
---
MISSING | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
create mode 100644 MISSING
diff --git a/MISSING b/MISSING
new file mode 100644
index 0000000..f228099
--- /dev/null
+++ b/MISSING
@@ -0,0 +1,20 @@
+ ***********
+ * MISSING *
+ ***********
+
+This file attempts to document the reason why a firmware is not present
+in this bundle.
+
+--------------------------------------------------------------------------
+
+Driver: zd1211rw -- ZyDAS/Atheros ZD1211/ZD1211B/AR5007UG wireless driver
+
+Trouble: Allegedly GPLv2, but no source visible. Found in hex form in the
+ vendor driver.
+
+URL: http://sf.net/projects/zd1211/files/
+
+Implication: CRITICAL, hardware undetected.
+
+--------------------------------------------------------------------------
+
--
1.7.11.7
next reply other threads:[~2013-01-12 22:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 22:39 Xose Vazquez Perez [this message]
2013-01-12 23:09 ` richard -rw- weinberger
2013-01-14 22:55 ` Pavel Roskin
2013-01-21 1:31 ` Ben Hutchings
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1358030383-15609-1-git-send-email-xose.vazquez@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=ben@decadent.org.uk \
--cc=dsd@laptop.org \
--cc=dwmw2@infradead.org \
--cc=kune@deine-taler.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®