Skip to contentSkip to conversation

m68k/net: add support for NS8390 based eth controllers on some ColdFire boards

PATCH In review [email protected] 2 participants 13 messages Jun 25, 2012 – Jun 27, 2012

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

cover m68k/net: add support for NS8390 based eth controllers on some ColdFire boards

I have broken up the NS8390 support for ColdFire boards into 2 patches. The first is the net support side of it, and the other is the ColdFire platform support.

If no-one has any comments then I'll send the first patch onto the net list for review. I'll add the second platform patch to the m68knommu git tree for-next branch.

#1 lore raw

PATCH 1/2 net: add support for NS8390 based eth controllers on some ColdFire boards

From: Greg Ungerer <[email protected]>

A number of older ColdFire based boards use NS8390 based network controllers. Most use the Davicom 9008F or the UMC 9008F. This driver provides the support code to get these devices working on these platforms.

The way these devices are wired up to the ColdFire bus is similar but not completely identical on the various boards. Most use a special region to access odd register addresses, and still provide for both 8bit and 16bit accesses. But a couple do have a more advanced hardware decode and use direct mapping of all registers. It is easy enough to handle all the access variations in one driver though.

---
 arch/m68k/include/asm/mcfne.h       |  129 +---------
 drivers/net/ethernet/8390/Kconfig   |   14 +
 drivers/net/ethernet/8390/Makefile  |    1 +
 drivers/net/ethernet/8390/mcf8390.c |  477 +++++++++++++++++++++++++++++++++++
 4 files changed, 501 insertions(+), 120 deletions(-)
 create mode 100644 drivers/net/ethernet/8390/mcf8390.c
arch/m68k/include/asm/mcfne.h +9 -120
index bf638be..f5760b1 100644
@@ -37,6 +37,7 @@
 #if defined(CONFIG_ARN5206)
 #define NE2000_ADDR		0x40000300
 #define NE2000_ODDOFFSET	0x00010000
+#define NE2000_ADDRSIZE		0x00020000
 #define	NE2000_IRQ_VECTOR	0xf0
 #define	NE2000_IRQ_PRIORITY	2
 #define	NE2000_IRQ_LEVEL	4
@@ -46,6 +47,7 @@
 #if defined(CONFIG_M5206eC3)
 #define	NE2000_ADDR		0x40000300
 #define	NE2000_ODDOFFSET	0x00010000
+#define	NE2000_ADDRSIZE		0x00020000
 #define	NE2000_IRQ_VECTOR	0x1c
 #define	NE2000_IRQ_PRIORITY	2
 #define	NE2000_IRQ_LEVEL	4
@@ -54,6 +56,7 @@
 
 #if defined(CONFIG_M5206e) && defined(CONFIG_NETtel)
 #define NE2000_ADDR		0x30000300
+#define NE2000_ADDRSIZE		0x00001000
 #define NE2000_IRQ_VECTOR	25
 #define NE2000_IRQ_PRIORITY	1
 #define NE2000_IRQ_LEVEL	3
@@ -63,6 +66,7 @@
 #if defined(CONFIG_M5307C3)
 #define NE2000_ADDR		0x40000300
 #define NE2000_ODDOFFSET	0x00010000
+#define NE2000_ADDRSIZE		0x00020000
 #define NE2000_IRQ_VECTOR	0x1b
 #define	NE2000_BYTE		volatile unsigned short
 #endif
@@ -70,6 +74,7 @@
 #if defined(CONFIG_M5272) && defined(CONFIG_NETtel)
 #define NE2000_ADDR		0x30600300
 #define NE2000_ODDOFFSET	0x00008000
+#define NE2000_ADDRSIZE		0x00010000
 #define NE2000_IRQ_VECTOR	67
 #undef	BSWAP
 #define	BSWAP(w)		(w)
@@ -82,6 +87,7 @@
 #define NE2000_ADDR0		0x30600300
 #define NE2000_ADDR1		0x30800300
 #define NE2000_ODDOFFSET	0x00008000
+#define NE2000_ADDRSIZE		0x00010000
 #define NE2000_IRQ_VECTOR0	27
 #define NE2000_IRQ_VECTOR1	29
 #undef	BSWAP
@@ -94,6 +100,7 @@
 #if defined(CONFIG_M5307) && defined(CONFIG_SECUREEDGEMP3)
 #define NE2000_ADDR		0x30600300
 #define NE2000_ODDOFFSET	0x00008000
+#define NE2000_ADDRSIZE		0x00010000
 #define NE2000_IRQ_VECTOR	27
 #undef	BSWAP
 #define	BSWAP(w)		(w)
@@ -105,6 +112,7 @@
 #if defined(CONFIG_ARN5307)
 #define NE2000_ADDR		0xfe600300
 #define NE2000_ODDOFFSET	0x00010000
+#define NE2000_ADDRSIZE		0x00020000
 #define NE2000_IRQ_VECTOR	0x1b
 #define NE2000_IRQ_PRIORITY	2
 #define NE2000_IRQ_LEVEL	3
@@ -114,129 +122,10 @@
 #if defined(CONFIG_M5407C3)
 #define NE2000_ADDR		0x40000300
 #define NE2000_ODDOFFSET	0x00010000
+#define NE2000_ADDRSIZE		0x00020000
 #define NE2000_IRQ_VECTOR	0x1b
 #define	NE2000_BYTE		volatile unsigned short
 #endif
 
 /****************************************************************************/
-
-/*
- *	Side-band address space for odd address requires re-mapping
- *	many of the standard ISA access functions.
- */
-#ifdef NE2000_ODDOFFSET
-
-#undef outb
-#undef outb_p
-#undef inb
-#undef inb_p
-#undef outsb
-#undef outsw
-#undef insb
-#undef insw
-
-#define	outb	ne2000_outb
-#define	inb	ne2000_inb
-#define	outb_p	ne2000_outb
-#define	inb_p	ne2000_inb
-#define	outsb	ne2000_outsb
-#define	outsw	ne2000_outsw
-#define	insb	ne2000_insb
-#define	insw	ne2000_insw
-
-
-#ifndef COLDFIRE_NE2000_FUNCS
-
-void ne2000_outb(unsigned int val, unsigned int addr);
-int  ne2000_inb(unsigned int addr);
-void ne2000_insb(unsigned int addr, void *vbuf, int unsigned long len);
-void ne2000_insw(unsigned int addr, void *vbuf, unsigned long len);
-void ne2000_outsb(unsigned int addr, void *vbuf, unsigned long len);
-void ne2000_outsw(unsigned int addr, void *vbuf, unsigned long len);
-
-#else
-
-/*
- *	This macro converts a conventional register address into the
- *	real memory pointer of the mapped NE2000 device.
- *	On most NE2000 implementations on ColdFire boards the chip is
- *	mapped in kinda funny, due to its ISA heritage.
- */
-#define	NE2000_PTR(addr)	((addr&0x1)?(NE2000_ODDOFFSET+addr-1):(addr))
-#define	NE2000_DATA_PTR(addr)	(addr)
-
-
-void ne2000_outb(unsigned int val, unsigned int addr)
-{
-	NE2000_BYTE	*rp;
-
-	rp = (NE2000_BYTE *) NE2000_PTR(addr);
-	*rp = RSWAP(val);
-}
-
-int ne2000_inb(unsigned int addr)
-{
-	NE2000_BYTE	*rp, val;
-
-	rp = (NE2000_BYTE *) NE2000_PTR(addr);
-	val = *rp;
-	return((int) ((NE2000_BYTE) RSWAP(val)));
-}
-
-void ne2000_insb(unsigned int addr, void *vbuf, int unsigned long len)
-{
-	NE2000_BYTE	*rp, val;
-	unsigned char	*buf;
-
-	buf = (unsigned char *) vbuf;
-	rp = (NE2000_BYTE *) NE2000_DATA_PTR(addr);
-	for (; (len > 0); len--) {
-		val = *rp;
-		*buf++ = RSWAP(val);
-	}
-}
-
-void ne2000_insw(unsigned int addr, void *vbuf, unsigned long len)
-{
-	volatile unsigned short	*rp;
-	unsigned short		w, *buf;
-
-	buf = (unsigned short *) vbuf;
-	rp = (volatile unsigned short *) NE2000_DATA_PTR(addr);
-	for (; (len > 0); len--) {
-		w = *rp;
-		*buf++ = BSWAP(w);
-	}
-}
-
-void ne2000_outsb(unsigned int addr, const void *vbuf, unsigned long len)
-{
-	NE2000_BYTE	*rp, val;
-	unsigned char	*buf;
-
-	buf = (unsigned char *) vbuf;
-	rp = (NE2000_BYTE *) NE2000_DATA_PTR(addr);
-	for (; (len > 0); len--) {
-		val = *buf++;
-		*rp = RSWAP(val);
-	}
-}
-
-void ne2000_outsw(unsigned int addr, const void *vbuf, unsigned long len)
-{
-	volatile unsigned short	*rp;
-	unsigned short		w, *buf;
-
-	buf = (unsigned short *) vbuf;
-	rp = (volatile unsigned short *) NE2000_DATA_PTR(addr);
-	for (; (len > 0); len--) {
-		w = *buf++;
-		*rp = BSWAP(w);
-	}
-}
-
-#endif /* COLDFIRE_NE2000_FUNCS */
-#endif /* NE2000_OFFOFFSET */
-
-/****************************************************************************/
 #endif	/* mcfne_h */
drivers/net/ethernet/8390/Kconfig +14 -0
index 2e53867..e1219e0 100644
@@ -162,6 +162,20 @@ config MAC8390
 	  and read the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 
+config MCF8390
+	tristate "ColdFire NS8390 based Ethernet support"
+	depends on COLDFIRE
+	select CRC32
+	---help---
+	  This driver is for Ethernet devices using an NS8390-compatible
+	  chipset on many common ColdFire CPU based boards. Many of the older
+	  Freescale dev boards use this, and some other common boards like
+	  some SnapGear routers do as well.
+
+	  If you have one of these boards and want to use the network interface
+	  on them then choose Y. To compile this driver as a module, choose M
+	  here, the module will be called mcf8390.
+
 config NE2000
 	tristate "NE2000/NE1000 support"
 	depends on (ISA || (Q40 && m) || M32R || MACH_TX49XX)
drivers/net/ethernet/8390/Makefile +1 -0
index d13790b..f43038b 100644
@@ -14,6 +14,7 @@ obj-$(CONFIG_HPLAN_PLUS) += hp-plus.o 8390p.o
 obj-$(CONFIG_HPLAN) += hp.o 8390p.o
 obj-$(CONFIG_HYDRA) += hydra.o 8390.o
 obj-$(CONFIG_LNE390) += lne390.o 8390.o
+obj-$(CONFIG_MCF8390) += mcf8390.o 8390.o
 obj-$(CONFIG_NE2000) += ne.o 8390p.o
 obj-$(CONFIG_NE2_MCA) += ne2.o 8390p.o
 obj-$(CONFIG_NE2K_PCI) += ne2k-pci.o 8390.o
drivers/net/ethernet/8390/mcf8390.c new file +477 -0

477 lines not on this page · raw message

Signature · 1 line
1.7.0.4
#2 lore raw

Re: [PATCH 1/2] net: add support for NS8390 based eth controllers on some ColdFire boards

Quoted 1 line · On Mon, Jun 25, 2012 at 3:29 AM, <[email protected]> wrote:

 arch/m68k/include/asm/mcfne.h       |  129 +---------

mcf8390.h?
mcfne.h is queued for removal.

Quoted 3 lines

 drivers/net/ethernet/8390/Kconfig   |   14 + drivers/net/ethernet/8390/Makefile  |    1 + drivers/net/ethernet/8390/mcf8390.c |  477 +++++++++++++++++++++++++++++++++++

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds

#3 lore raw

Re: [PATCH 1/2] net: add support for NS8390 based eth controllers on some ColdFire boards

Hi Geert,

Quoted 5 lines · Geert Uytterhoeven
Quoted 1 line · On Mon, Jun 25, 2012 at 3:29 AM,<[email protected]> wrote:
  arch/m68k/include/asm/mcfne.h       |  129 +---------

mcf8390.h?
mcfne.h is queued for removal.

I was trying to save it :-)
Do you think I should just silently move the modified mcfne.h to a mcf8390.h?

Regards
Greg

Quoted 6 lines
Quoted 3 lines
  drivers/net/ethernet/8390/Kconfig   |   14 +
  drivers/net/ethernet/8390/Makefile  |    1 +
  drivers/net/ethernet/8390/mcf8390.c |  477 +++++++++++++++++++++++++++++++++++

Gr{oetje,eeting}s,

Quoted 8 lines

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds

------------------------------------------------------------------------

Greg Ungerer  --  Principal Engineer        EMAIL:     [email protected]
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
8 Gardner Close,                            FAX:         +61 7 3891 3630
Milton, QLD, 4064, Australia                WEB: http://www.SnapGear.com
#4 lore raw

Re: [PATCH 1/2] net: add support for NS8390 based eth controllers on some ColdFire boards

Quoted 11 lines · Greg Ungerer
Quoted 6 lines · Geert Uytterhoeven
Quoted 2 lines · On Mon, Jun 25, 2012 at 3:29 AM,<[email protected]>  wrote:

 arch/m68k/include/asm/mcfne.h       |  129 +---------

mcf8390.h?
mcfne.h is queued for removal.

I was trying to save it :-)
Do you think I should just silently move the modified mcfne.h to a mcf8390.h?

Sure. Why not?

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds

#5 lore raw

Re: [PATCH 1/2] net: add support for NS8390 based eth controllers on some ColdFire boards

Quoted 6 lines · Geert Uytterhoeven
Quoted 5 lines · Greg Ungerer
Quoted 4 lines · Geert Uytterhoeven
Quoted 2 lines · On Mon, Jun 25, 2012 at 3:29 AM,<[email protected]> wrote:
  arch/m68k/include/asm/mcfne.h       |  129 +---------
Quoted 8 lines
Quoted 6 lines
Quoted 2 lines

mcf8390.h?
mcfne.h is queued for removal.

I was trying to save it :-)
Do you think I should just silently move the modified mcfne.h to a mcf8390.h?

Sure. Why not?

We lose any git history linking the original and new file.

Regards
Greg

------------------------------------------------------------------------

Greg Ungerer  --  Principal Engineer        EMAIL:     [email protected]
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
8 Gardner Close,                            FAX:         +61 7 3891 3630
Milton, QLD, 4064, Australia                WEB: http://www.SnapGear.com
#6 lore raw

Re: [PATCH 1/2] net: add support for NS8390 based eth controllers on some ColdFire boards

Quoted 10 lines · Greg Ungerer
Quoted 9 lines · Geert Uytterhoeven
Quoted 8 lines · Greg Ungerer
Quoted 6 lines · Geert Uytterhoeven
Quoted 2 lines · On Mon, Jun 25, 2012 at 3:29 AM,<[email protected]>    wrote:

 arch/m68k/include/asm/mcfne.h       |  129 +---------

mcf8390.h?
mcfne.h is queued for removal.

Quoted 7 lines
Quoted 5 lines
Quoted 3 lines

I was trying to save it :-)
Do you think I should just silently move the modified mcfne.h to a mcf8390.h?

Sure. Why not?

We lose any git history linking the original and new file.

Your commit renaming-and-modifying it will provide the link?

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds

#7 lore raw

Re: [PATCH 1/2] net: add support for NS8390 based eth controllers on some ColdFire boards

Quoted 15 lines · Geert Uytterhoeven
Quoted 14 lines · Greg Ungerer
Quoted 13 lines · Geert Uytterhoeven
Quoted 11 lines · Greg Ungerer
Quoted 6 lines · Geert Uytterhoeven
Quoted 2 lines · On Mon, Jun 25, 2012 at 3:29 AM,<[email protected]> wrote:
  arch/m68k/include/asm/mcfne.h       |  129 +---------

mcf8390.h?
mcfne.h is queued for removal.

I was trying to save it :-)
Do you think I should just silently move the modified mcfne.h to a mcf8390.h?

Quoted 5 lines
Quoted 3 lines
Quoted 1 line

Sure. Why not?

We lose any git history linking the original and new file.

Your commit renaming-and-modifying it will provide the link?

I would normally do that with a "git mv". But isn't that going to clash with your "git rm"? Or am I mis-understanding what you mean?

Regards
Greg

Signature · 5 lines
------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     [email protected]
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
8 Gardner Close,                            FAX:         +61 7 3891 3630
Milton, QLD, 4064, Australia                WEB: http://www.SnapGear.com
#8 lore raw

Re: [PATCH 1/2] net: add support for NS8390 based eth controllers on some ColdFire boards

Hi Greg,

Quoted 16 lines · Greg Ungerer
Quoted 15 lines · Geert Uytterhoeven
Quoted 14 lines · Greg Ungerer
Quoted 13 lines · Geert Uytterhoeven
Quoted 10 lines · Greg Ungerer
Quoted 5 lines · Geert Uytterhoeven
Quoted 1 line · On Mon, Jun 25, 2012 at 3:29 AM,<[email protected]>      wrote:

 arch/m68k/include/asm/mcfne.h       |  129 +---------

mcf8390.h?
mcfne.h is queued for removal.

I was trying to save it :-)
Do you think I should just silently move the modified mcfne.h to a mcf8390.h?

Quoted 8 lines
Quoted 5 lines
Quoted 3 lines
Quoted 1 line

Sure. Why not?

We lose any git history linking the original and new file.

Your commit renaming-and-modifying it will provide the link?

I would normally do that with a "git mv". But isn't that going to clash with your "git rm"?  Or am I mis-understanding what you mean?

It may indeed give a merge conflict.

If the conflict is too complicated (we'll see in -next), I can remove its scheduled deletion.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds

#9 lore raw

Re: [PATCH 1/2] net: add support for NS8390 based eth controllers on some ColdFire boards

Hi Geert,

Quoted 23 lines · Geert Uytterhoeven
Quoted 22 lines · Greg Ungerer
Quoted 20 lines · Geert Uytterhoeven
Quoted 10 lines · Greg Ungerer
Quoted 9 lines · Geert Uytterhoeven
Quoted 7 lines · Greg Ungerer
Quoted 5 lines · Geert Uytterhoeven
Quoted 1 line · On Mon, Jun 25, 2012 at 3:29 AM,<[email protected]> wrote:

arch/m68k/include/asm/mcfne.h 129 +---------

mcf8390.h?
mcfne.h is queued for removal.

Quoted 7 lines
Quoted 5 lines
Quoted 3 lines

I was trying to save it :-)
Do you think I should just silently move the modified mcfne.h to a mcf8390.h?

Sure. Why not?

We lose any git history linking the original and new file.

Your commit renaming-and-modifying it will provide the link?

Quoted 7 lines
Quoted 2 lines

I would normally do that with a "git mv". But isn't that going to clash with your "git rm"? Or am I mis-understanding what you mean?

It may indeed give a merge conflict.

If the conflict is too complicated (we'll see in -next), I can remove its scheduled deletion.

My concern here is that I expect that patch will go through DaveM's netdev tree. And he may get a little annoyed when a merge conflict arises in Linux next. Given that at this point we have the chance to resolve it.

I will just create a new mcf8390.h if you want to keep the removal that is already staged. Keep everyone happy :-)

Regards
Greg

------------------------------------------------------------------------

Greg Ungerer  --  Principal Engineer        EMAIL:     [email protected]
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
8 Gardner Close,                            FAX:         +61 7 3891 3630
Milton, QLD, 4064, Australia                WEB: http://www.SnapGear.com
#10 lore raw

Re: [PATCH 1/2] net: add support for NS8390 based eth controllers on some ColdFire boards

Hi Greg,

Quoted 17 lines · Greg Ungerer
Quoted 16 lines · Geert Uytterhoeven
Quoted 14 lines · Greg Ungerer
Quoted 10 lines · Geert Uytterhoeven
Quoted 7 lines · Greg Ungerer
Quoted 4 lines · Geert Uytterhoeven
Quoted 2 lines

Do you think I should just silently move the modified mcfne.h to a mcf8390.h?

Sure. Why not?

We lose any git history linking the original and new file.

Your commit renaming-and-modifying it will provide the link?

I would normally do that with a "git mv". But isn't that going to clash with your "git rm"? Or am I mis-understanding what you mean?

Quoted 7 lines
Quoted 4 lines

It may indeed give a merge conflict.

If the conflict is too complicated (we'll see in -next), I can remove its scheduled deletion.

My concern here is that I expect that patch will go through DaveM's netdev tree. And he may get a little annoyed when a merge conflict

Point taken.

Quoted 2 lines

arises in Linux next. Given that at this point we have the chance to resolve it.

Removed from scheduled removal.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds

#11 lore raw

Re: [PATCH 1/2] net: add support for NS8390 based eth controllers on some ColdFire boards

Hi Geert,

Quoted 26 lines · Geert Uytterhoeven
Quoted 17 lines · Greg Ungerer
Quoted 16 lines · Geert Uytterhoeven
Quoted 14 lines · Greg Ungerer
Quoted 10 lines · Geert Uytterhoeven
Quoted 7 lines · Greg Ungerer
Quoted 4 lines · Geert Uytterhoeven
Quoted 2 lines

Do you think I should just silently move the modified mcfne.h to a mcf8390.h?

Sure. Why not?

We lose any git history linking the original and new file.

Your commit renaming-and-modifying it will provide the link?

I would normally do that with a "git mv". But isn't that going to clash with your "git rm"? Or am I mis-understanding what you mean?

Quoted 7 lines
Quoted 4 lines

It may indeed give a merge conflict.

If the conflict is too complicated (we'll see in -next), I can remove its scheduled deletion.

My concern here is that I expect that patch will go through DaveM's netdev tree. And he may get a little annoyed when a merge conflict

Quoted 6 lines

Point taken.

Quoted 2 lines

arises in Linux next. Given that at this point we have the chance to resolve it.

Removed from scheduled removal.

Fantastic, thanks. I will re-roll the patch moving the mcfne.h to mcf8390.h, and resend here before I forward on.

Regards
Greg

------------------------------------------------------------------------

Greg Ungerer  --  Principal Engineer        EMAIL:     [email protected]
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
8 Gardner Close,                            FAX:         +61 7 3891 3630
Milton, QLD, 4064, Australia                WEB: http://www.SnapGear.com
#12 lore raw

PATCH 2/2 m68knommu: platform support for 8390 based ethernet used on some boards

In reply to [email protected]

From: Greg Ungerer <[email protected]>

Quite a few of Freescale's older ColdFire development boards used an NS8390 based ethernet interface. Add a platform definition for the resources used by these devices so we can use it on these older boards.

---
 arch/m68k/platform/coldfire/Makefile  |    1 +
 arch/m68k/platform/coldfire/mcf8390.c |   38 +++++++++++++++++++++++++++++++++
 2 files changed, 39 insertions(+), 0 deletions(-)
 create mode 100644 arch/m68k/platform/coldfire/mcf8390.c
arch/m68k/platform/coldfire/Makefile +1 -0
index 76d389d..e62de37 100644
@@ -31,6 +31,7 @@ obj-$(CONFIG_M54xx)	+= m54xx.o sltimers.o intc-2.o
 obj-$(CONFIG_NETtel)	+= nettel.o
 obj-$(CONFIG_CLEOPATRA)	+= nettel.o
 obj-$(CONFIG_FIREBEE)	+= firebee.o
+obj-$(CONFIG_MCF8390)	+= mcf8390.o
 
 obj-y			+= pinmux.o gpio.o
 extra-y := head.o
arch/m68k/platform/coldfire/mcf8390.c new file +38 -0
new file mode 100644
index 0000000..6db9213
@@ -0,0 +1,38 @@
+/*
+ * mcf8390.c  -- platform support for 8390 ethernet on many boards
+ *
+ * (C) Copyright 2012, Greg Ungerer <[email protected]>
+ *
+ * This file is subject to the terms and conditions of the GNU General Public
+ * License.  See the file COPYING in the main directory of this archive
+ * for more details.
+ */
+
+#include <linux/kernel.h>
+#include <linux/module.h>
+#include <linux/init.h>
+#include <linux/resource.h>
+#include <linux/platform_device.h>
+#include <asm/mcfne.h>
+
+static struct resource mcf8390_resources[] = {
+	{
+		.start	= NE2000_ADDR,
+		.end	= NE2000_ADDR + NE2000_ADDRSIZE - 1,
+		.flags	= IORESOURCE_MEM,
+	},
+	{
+		.start	= NE2000_IRQ_VECTOR,
+		.end	= NE2000_IRQ_VECTOR,
+		.flags	= IORESOURCE_IRQ,
+	},
+};
+
+static int __init mcf8390_platform_init(void)
+{
+	platform_device_register_simple("mcf8390", -1, mcf8390_resources,
+		ARRAY_SIZE(mcf8390_resources));
+	return 0;
+}
+
+arch_initcall(mcf8390_platform_init);
Signature · 1 line
1.7.0.4