From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Marc Zyngier <maz@wild-wind.fr.eu.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] eisa.ids: Add Network Peripherals FDDI boards
Date: Sun, 31 May 2009 00:54:26 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.1.10.0905310041200.15490@ftp.linux-mips.org> (raw)
Add EISA IDs for Network Peripherals FDDI boards. Descriptions taken
from the respective EISA configuration files.
Signed-off-by: Maciej W. Rozycki <macro@linux-mips.org>
---
It's unlikely we'll ever support these cards, the problem being the lack
of documentation. Assuming the policy for the EISA ID database is the
same as for PCI I'm sending these entries for the sake of completeness.
Please apply.
Maciej
patch-mips-2.6.27-rc8-20081004-npi-eisa-0
Index: linux-mips-2.6.27-rc8-20081004-dolch/drivers/eisa/eisa.ids
===================================================================
--- linux-mips-2.6.27-rc8-20081004-dolch.orig/drivers/eisa/eisa.ids
+++ linux-mips-2.6.27-rc8-20081004-dolch/drivers/eisa/eisa.ids
@@ -1140,6 +1140,11 @@ NON0301 "c't Universale Graphic Adapter"
NON0401 "c't Universal Ethernet Adapter"
NON0501 "c't Universal 16-Bit Sound Adapter"
NON0601 "c't Universal 8-Bit Adapter"
+NPI0120 "Network Peripherals NP-EISA-1 FDDI Interface"
+NPI0221 "Network Peripherals NP-EISA-2 FDDI Interface"
+NPI0223 "Network Peripherals NP-EISA-2E Enhanced FDDI Interface"
+NPI0301 "Network Peripherals NP-EISA-3 FDDI Interface"
+NPI0303 "Network Peripherals NP-EISA-3E Enhanced FDDI Interface"
NSS0011 "Newport Systems Solutions WNIC Adapter"
NVL0701 "Novell NE3200 Bus Master Ethernet"
NVL0702 "Novell NE3200T Bus Master Ethernet"
next reply other threads:[~2009-05-30 23:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-30 23:54 Maciej W. Rozycki [this message]
2009-06-02 2:28 ` Andrew Morton
2009-06-02 8:09 ` Marc Zyngier
2009-06-02 19:07 ` Maciej W. Rozycki
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=alpine.LFD.1.10.0905310041200.15490@ftp.linux-mips.org \
--to=macro@linux-mips.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@wild-wind.fr.eu.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
Powered by JetHome