public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Bonilla Beeche <abonilla@linuxwireless.org>
To: ipw2200-devel@lists.sourceforge.net, netdev@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Cc: jketreno@linux.intel.com, Linus Torvalds <torvalds@osdl.org>
Subject: [PATCH Linus Git] README.ipw2200 does not contain firmware information.
Date: Tue, 06 Sep 2005 19:48:37 -0600	[thread overview]
Message-ID: <1126057717.5165.9.camel@localhost.localdomain> (raw)

[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]

Hi,

	The kconfig from net/wireless says to look at the README.ipw2200 for
further installation of the firmware file. We have that information unde
INSTALL not under README.ipw2200, still I just added a part that talks
about installing the firmware file. This because README.ipw2200 is
already in the Documentation/networking/.

I'm still spamming everyone cause I have not been told where to send
this directly. :-)

Signed-off-by: Alejandro Bonilla <abonilla@linuxwireless.org>

Pasted and attached.

debian:~/linux-2.6# diff -usr Documentation/networking/README.ipw2200~
Documentation/networking/README.ipw2200

--- Documentation/networking/README.ipw2200~    2005-09-06
19:33:24.000000000 -0600
+++ Documentation/networking/README.ipw2200     2005-09-06
19:33:24.000000000 -0600
@@ -27,7 +27,8 @@
 1.4. Sysfs Helper Files
 2.   About the Version Numbers
 3.   Support
-4.   License
+4.   Firmware installation
+5.   License
 
 
 1.   Introduction
@@ -272,7 +273,18 @@
     http://ipw2200.sf.net/
 
 
-4.  License
+4.  Firmware installation
+----------------------------------------------
+
+The driver requires a firmware image, download it and extract the files
+under /lib/firmware
+
+The firmware can be downloaded from the following URL:
+
+    http://ipw2200.sf.net/
+
+
+5.  License
 -----------------------------------------------
 
   Copyright(c) 2003 - 2005 Intel Corporation. All rights reserved.


[-- Attachment #2: IPW2200-README-git.patch --]
[-- Type: text/x-patch, Size: 790 bytes --]

--- Documentation/networking/README.ipw2200~	2005-09-06 19:33:24.000000000 -0600
+++ Documentation/networking/README.ipw2200	2005-09-06 19:33:24.000000000 -0600
@@ -27,7 +27,8 @@
 1.4. Sysfs Helper Files
 2.   About the Version Numbers
 3.   Support
-4.   License
+4.   Firmware installation
+5.   License
 
 
 1.   Introduction
@@ -272,7 +273,18 @@
     http://ipw2200.sf.net/
 
 
-4.  License
+4.  Firmware installation
+----------------------------------------------
+
+The driver requires a firmware image, download it and extract the files
+under /lib/firmware
+
+The firmware can be downloaded from the following URL:
+
+    http://ipw2200.sf.net/
+
+
+5.  License
 -----------------------------------------------
 
   Copyright(c) 2003 - 2005 Intel Corporation. All rights reserved.

             reply	other threads:[~2005-09-07  1:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-07  1:48 Alejandro Bonilla Beeche [this message]
2005-09-10  8:35 ` 2nd Try - [PATCH Linus Git] README.ipw2200 does not contain firmware information Alejandro Bonilla Beeche

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=1126057717.5165.9.camel@localhost.localdomain \
    --to=abonilla@linuxwireless.org \
    --cc=ipw2200-devel@lists.sourceforge.net \
    --cc=jketreno@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=torvalds@osdl.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