[PATCH] sealevel 8 port RS-232/RS-422/RS-485 board

[DHollenbeck]

Vendor Sealevel suggested these changes for its new board.  Tried them, 
they work with the card.  Please apply the patch below, which was made 
from 2.6.10 but can be applied to 2.6.11.2 without errors.

Dick
--- linux/drivers/serial/8250_pci.orig  2005-03-10 13:09:39.0 -0600
+++ linux/drivers/serial/8250_pci.c 2005-03-10 15:03:39.0 -0600
@@ -1867,6 +1867,9 @@
   {   PCI_VENDOR_ID_SEALEVEL, PCI_DEVICE_ID_SEALEVEL_COMM8,
   PCI_ANY_ID, PCI_ANY_ID, 0, 0,
   pbn_b2_8_115200 },
+   {   PCI_VENDOR_ID_SEALEVEL, PCI_DEVICE_ID_SEALEVEL_UCOMM8,
+   PCI_ANY_ID, PCI_ANY_ID, 0, 0,
+   pbn_b2_8_115200 },
   {   PCI_VENDOR_ID_PLX, PCI_DEVICE_ID_PLX_GTEK_SERIAL2,
   PCI_ANY_ID, PCI_ANY_ID, 0, 0,
--- linux/drivers/pci/pci.ids.orig  2005-03-10 13:10:10.0 -0600
+++ linux/drivers/pci/pci.ids   2005-03-10 15:21:43.0 -0600
@@ -5714,6 +5714,7 @@
   7401  Four Port RS-232 Interface
   7402  Four Port RS-422/485 Interface
   7801  Eight Port RS-232 Interface
+   7804  Eight Port RS-232/422/485 Interface
   8001  8001 Digital I/O Adapter
135f  I-Data International A-S
1360  Meinberg Funkuhren
--- linux/include/linux/pci_ids.h.orig  2005-03-10 13:11:25.0 -0600
+++ linux/include/linux/pci_ids.h   2005-03-10 15:06:07.0 -0600
@@ -1780,6 +1780,7 @@
#define PCI_DEVICE_ID_SEALEVEL_UCOMM2320x7202
#define PCI_DEVICE_ID_SEALEVEL_COMM4   0x7401
#define PCI_DEVICE_ID_SEALEVEL_COMM8   0x7801
+#define PCI_DEVICE_ID_SEALEVEL_UCOMM8  0x7804
#define PCI_VENDOR_ID_HYPERCOPE0x1365
#define PCI_DEVICE_ID_HYPERCOPE_PLX0x9050

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.6.x.y gatekeeper discipline

[DHollenbeck]

Where do you see that patch as being applied in the new .y stable series?
Chris
I got that patch description from here:
When you go to http://kernel.org, and click on the stand alone " C " to 
the right of 2.6.11.2

It is a hyperlink to:
http://kernel.org/pub/linux/kernel/v2.6/testing/cset/
Have I mis-understood something, or is the website misleading?  Or both :)
Dick
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2.6.x.y gatekeeper discipline

[DHollenbeck]

I had hoped that the proper discipline in rejecting non-critical patches 
would have pertained.  I remain unconvinced that the .y releases are 
anything but noise that should have been kept elsewhere.  After reading 
through a patch summary, I see this as typical:

--
 ChangeSet 2005/02/22 20:56:28-05:00, bunk @ stusta.de
 
 [diffview]
 

[PATCH] drivers/net/via-rhine.c: make a variable static const
This patch makes a needlessly global variable static const.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
Signed-off-by: Jeff Garzik <[EMAIL PROTECTED]>
--
It's possible I simply don't get it, but the above description of a 
patch hardly seems like it would qualify for the intentions of the 
2.6.x.y series.

Is this typical, and is this in line with the intent of the x.y series?
If this is going to achieve the objective, the gatekeeper has to be a 
real stubborn, unpopular horse's ass it seems, with a sign on his 
forehead that reads:  GO AWAY AND COME ANOTHER DAY!

Somewhat disappointedly,
Dick
--
Please help fix the U.S. software industry before it is too late.
Contact your U.S. representatives with this information:
http://lpf.ai.mit.edu/Patents/industry-at-risk.html
http://www.groklaw.net/article.php?story=20041003041632172
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/