use the correct capitalization for Realtek.

5 files changed, 24 insertions, 24 deletions

diff --git a/sys/dev/ic/re.c b/sys/dev/ic/re.c
index dfa17eea3be..cbd5e898cb4 100644
--- a/sys/dev/ic/re.c
+++ b/sys/dev/ic/re.c
@@ -1,4 +1,4 @@
-/*	$OpenBSD: re.c,v 1.161 2014/11/23 10:03:49 brad Exp $	*/
+/*	$OpenBSD: re.c,v 1.162 2014/11/24 02:03:37 brad Exp $	*/
 /*	$FreeBSD: if_re.c,v 1.31 2004/09/04 07:54:05 ru Exp $	*/
 /*
  * Copyright (c) 1997, 1998-2003
@@ -33,7 +33,7 @@
  */
 
 /*
- * RealTek 8139C+/8169/8169S/8110S PCI NIC driver
+ * Realtek 8139C+/8169/8169S/8110S PCI NIC driver
  *
  * Written by Bill Paul <wpaul@windriver.com>
  * Senior Networking Software Engineer
@@ -41,7 +41,7 @@
  */
 
 /*
- * This driver is designed to support RealTek's next generation of
+ * This driver is designed to support Realtek's next generation of
  * 10/100 and 10/100/1000 PCI ethernet controllers. There are currently
  * seven devices in this family: the RTL8139C+, the RTL8169, the RTL8169S,
  * RTL8110S, the RTL8168, the RTL8111 and the RTL8101E.
@@ -96,7 +96,7 @@
  * (the 'S' stands for 'single-chip'). These devices have the same
  * programming API as the older 8169, but also have some vendor-specific
  * registers for the on-board PHY. The 8110S is a LAN-on-motherboard
- * part designed to be pin-compatible with the RealTek 8100 10/100 chip.
+ * part designed to be pin-compatible with the Realtek 8100 10/100 chip.
  * 
  * This driver takes advantage of the RX and TX checksum offload and
  * VLAN tag insertion/extraction features. It also implements TX
@@ -550,7 +550,7 @@ re_miibus_statchg(struct device *dev)
 	}
 
 	/*
-	 * RealTek controllers do not provide an interface to
+	 * Realtek controllers do not provide an interface to
 	 * Tx/Rx MACs for resolved speed, duplex and flow-control
 	 * parameters.
 	 */
@@ -604,7 +604,7 @@ re_iff(struct rl_softc *sc)
 	}
 
 	/*
-	 * For some unfathomable reason, RealTek decided to reverse
+	 * For some unfathomable reason, Realtek decided to reverse
 	 * the order of the multicast hash registers in the PCI Express
 	 * parts. This means we have to write the hash pattern in reverse
 	 * order for those devices.
@@ -1310,7 +1310,7 @@ re_rxeof(struct rl_softc *sc)
 		 * it is 13 bits (since the max RX frame length is 16K).
 		 * Unfortunately, all 32 bits in the status word
 		 * were already used, so to make room for the extra
-		 * length bit, RealTek took out the 'frame alignment
+		 * length bit, Realtek took out the 'frame alignment
 		 * error' bit and shifted the other status bits
 		 * over one slot. The OWN, EOR, FS and LS bits are
 		 * still in the same places. We have already extracted
diff --git a/sys/dev/ic/rtl80x9reg.h b/sys/dev/ic/rtl80x9reg.h
index 7f302feb588..b5f45afc85b 100644
--- a/sys/dev/ic/rtl80x9reg.h
+++ b/sys/dev/ic/rtl80x9reg.h
@@ -1,4 +1,4 @@
-/*	$OpenBSD: rtl80x9reg.h,v 1.3 2008/06/26 05:42:16 ray Exp $	*/
+/*	$OpenBSD: rtl80x9reg.h,v 1.4 2014/11/24 02:03:37 brad Exp $	*/
 /*	$NetBSD: rtl80x9reg.h,v 1.2 1998/10/31 00:31:43 thorpej Exp $	*/
 
 /*-
@@ -32,7 +32,7 @@
  */
 
 /*
- * Registers on RealTek 8019 and 8029 NE2000-compatible network interfaces.
+ * Registers on Realtek 8019 and 8029 NE2000-compatible network interfaces.
  *
  * Data sheets for these chips can be found at:
  *
diff --git a/sys/dev/ic/rtl80x9var.h b/sys/dev/ic/rtl80x9var.h
index e08efeec0d3..9622865c741 100644
--- a/sys/dev/ic/rtl80x9var.h
+++ b/sys/dev/ic/rtl80x9var.h
@@ -1,4 +1,4 @@
-/*	$OpenBSD: rtl80x9var.h,v 1.5 2008/06/26 05:42:16 ray Exp $	*/
+/*	$OpenBSD: rtl80x9var.h,v 1.6 2014/11/24 02:03:37 brad Exp $	*/
 /*	$NetBSD: rtl80x9var.h,v 1.1 1998/10/31 00:44:33 thorpej Exp $	*/
 
 /*-
@@ -32,7 +32,7 @@
  */
 
 /*
- * Definitions on RealTek 8019 and 8029 NE2000-compatible network interfaces.
+ * Definitions on Realtek 8019 and 8029 NE2000-compatible network interfaces.
  *
  * Data sheets for these chips can be found at:
  *
diff --git a/sys/dev/ic/rtl81x9.c b/sys/dev/ic/rtl81x9.c
index aaf3e799541..fe4e2654c4f 100644
--- a/sys/dev/ic/rtl81x9.c
+++ b/sys/dev/ic/rtl81x9.c
@@ -1,4 +1,4 @@
-/*	$OpenBSD: rtl81x9.c,v 1.83 2014/09/06 05:41:35 jsg Exp $ */
+/*	$OpenBSD: rtl81x9.c,v 1.84 2014/11/24 02:03:37 brad Exp $ */
 
 /*
  * Copyright (c) 1997, 1998
@@ -33,10 +33,10 @@
  */
 
 /*
- * RealTek 8129/8139 PCI NIC driver
+ * Realtek 8129/8139 PCI NIC driver
  *
  * Supports several extremely cheap PCI 10/100 adapters based on
- * the RealTek chipset. Datasheets can be obtained from
+ * the Realtek chipset. Datasheets can be obtained from
  * www.realtek.com.tw.
  *
  * Written by Bill Paul <wpaul@ctr.columbia.edu>
@@ -45,7 +45,7 @@
  */
 
 /*
- * The RealTek 8139 PCI NIC redefines the meaning of 'low end.' This is
+ * The Realtek 8139 PCI NIC redefines the meaning of 'low end.' This is
  * probably the worst PCI ethernet controller ever made, with the possible
  * exception of the FEAST chip made by SMC. The 8139 supports bus-master
  * DMA, but it has a terrible interface that nullifies any performance
@@ -587,11 +587,11 @@ rl_rxeof(struct rl_softc *sc)
 
 		/*
 		 * Here's a totally undocumented fact for you. When the
-		 * RealTek chip is in the process of copying a packet into
+		 * Realtek chip is in the process of copying a packet into
 		 * RAM for you, the length will be 0xfff0. If you spot a
 		 * packet header with this value, you need to stop. The
 		 * datasheet makes absolutely no mention of this and
-		 * RealTek should be shot for this.
+		 * Realtek should be shot for this.
 		 */
 		rxstat = htole32(rxstat);
 		total_len = rxstat >> 16;
@@ -617,7 +617,7 @@ rl_rxeof(struct rl_softc *sc)
 		rx_bytes += total_len + 4;
 
 		/*
-		 * XXX The RealTek chip includes the CRC with every
+		 * XXX The Realtek chip includes the CRC with every
 		 * received frame, and there's no way to turn this
 		 * behavior off (at least, I can't find anything in
 		 * the manual that explains how to do it) so we have
@@ -805,7 +805,7 @@ rl_encap(struct rl_softc *sc, struct mbuf *m_head)
 	struct mbuf	*m_new;
 
 	/*
-	 * The RealTek is brain damaged and wants longword-aligned
+	 * The Realtek is brain damaged and wants longword-aligned
 	 * TX buffers, plus we can only have one fragment buffer
 	 * per packet. We have to copy pretty much all the time.
 	 */
diff --git a/sys/dev/ic/rtl81x9reg.h b/sys/dev/ic/rtl81x9reg.h
index 3357553c517..0be8c6194a0 100644
--- a/sys/dev/ic/rtl81x9reg.h
+++ b/sys/dev/ic/rtl81x9reg.h
@@ -1,4 +1,4 @@
-/*	$OpenBSD: rtl81x9reg.h,v 1.87 2014/11/19 02:37:41 brad Exp $	*/
+/*	$OpenBSD: rtl81x9reg.h,v 1.88 2014/11/24 02:03:37 brad Exp $	*/
 
 /*
  * Copyright (c) 1997, 1998
@@ -35,7 +35,7 @@
  */
 
 /*
- * RealTek 8129/8139 register offsets
+ * Realtek 8129/8139 register offsets
  */
 #define	RL_IDR0		0x0000		/* ID register 0 (station addr) */
 #define RL_IDR1		0x0001		/* Must use 32-bit accesses (?) */
@@ -522,7 +522,7 @@
 #define RL_GMEDIASTAT_TBI	0x80	/* TBI enabled */
 
 /*
- * The RealTek doesn't use a fragment-based descriptor mechanism.
+ * The Realtek doesn't use a fragment-based descriptor mechanism.
  * Instead, there are only four register sets, each of which represents
  * one 'descriptor.' Basically, each TX descriptor is just a contiguous
  * packet buffer (32-bit aligned!) and we place the buffer addresses in
@@ -945,12 +945,12 @@ struct rl_softc {
 /*
  * General constants that are fun to know.
  *
- * RealTek PCI vendor ID
+ * Realtek PCI vendor ID
  */
 #define	RT_VENDORID				0x10EC
 
 /*
- * RealTek chip device IDs.
+ * Realtek chip device IDs.
  */
 #define RT_DEVICEID_8129			0x8129
 #define RT_DEVICEID_8101E			0x8136