Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
/*
|
2012-01-27 21:36:01 +08:00
|
|
|
* drivers/net/ethernet/ibm/emac/core.h
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
*
|
|
|
|
* Driver for PowerPC 4xx on-chip ethernet controller.
|
|
|
|
*
|
2007-12-05 08:14:33 +08:00
|
|
|
* Copyright 2007 Benjamin Herrenschmidt, IBM Corp.
|
|
|
|
* <benh@kernel.crashing.org>
|
|
|
|
*
|
|
|
|
* Based on the arch/ppc version of the driver:
|
|
|
|
*
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
* Copyright (c) 2004, 2005 Zultys Technologies.
|
|
|
|
* Eugene Surovegin <eugene.surovegin@zultys.com> or <ebs@ebshome.net>
|
|
|
|
*
|
|
|
|
* Based on original work by
|
|
|
|
* Armin Kuster <akuster@mvista.com>
|
|
|
|
* Johnnie Peters <jpeters@mvista.com>
|
|
|
|
* Copyright 2000, 2001 MontaVista Softare Inc.
|
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or modify it
|
|
|
|
* under the terms of the GNU General Public License as published by the
|
|
|
|
* Free Software Foundation; either version 2 of the License, or (at your
|
|
|
|
* option) any later version.
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
#ifndef __IBM_NEWEMAC_CORE_H
|
|
|
|
#define __IBM_NEWEMAC_CORE_H
|
|
|
|
|
|
|
|
#include <linux/module.h>
|
|
|
|
#include <linux/list.h>
|
|
|
|
#include <linux/kernel.h>
|
|
|
|
#include <linux/interrupt.h>
|
|
|
|
#include <linux/netdevice.h>
|
|
|
|
#include <linux/dma-mapping.h>
|
|
|
|
#include <linux/spinlock.h>
|
2008-05-23 14:28:54 +08:00
|
|
|
#include <linux/of_platform.h>
|
include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
percpu.h is included by sched.h and module.h and thus ends up being
included when building most .c files. percpu.h includes slab.h which
in turn includes gfp.h making everything defined by the two files
universally available and complicating inclusion dependencies.
percpu.h -> slab.h dependency is about to be removed. Prepare for
this change by updating users of gfp and slab facilities include those
headers directly instead of assuming availability. As this conversion
needs to touch large number of source files, the following script is
used as the basis of conversion.
http://userweb.kernel.org/~tj/misc/slabh-sweep.py
The script does the followings.
* Scan files for gfp and slab usages and update includes such that
only the necessary includes are there. ie. if only gfp is used,
gfp.h, if slab is used, slab.h.
* When the script inserts a new include, it looks at the include
blocks and try to put the new include such that its order conforms
to its surrounding. It's put in the include block which contains
core kernel includes, in the same order that the rest are ordered -
alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
doesn't seem to be any matching order.
* If the script can't find a place to put a new include (mostly
because the file doesn't have fitting include block), it prints out
an error message indicating which .h file needs to be added to the
file.
The conversion was done in the following steps.
1. The initial automatic conversion of all .c files updated slightly
over 4000 files, deleting around 700 includes and adding ~480 gfp.h
and ~3000 slab.h inclusions. The script emitted errors for ~400
files.
2. Each error was manually checked. Some didn't need the inclusion,
some needed manual addition while adding it to implementation .h or
embedding .c file was more appropriate for others. This step added
inclusions to around 150 files.
3. The script was run again and the output was compared to the edits
from #2 to make sure no file was left behind.
4. Several build tests were done and a couple of problems were fixed.
e.g. lib/decompress_*.c used malloc/free() wrappers around slab
APIs requiring slab.h to be added manually.
5. The script was run on all .h files but without automatically
editing them as sprinkling gfp.h and slab.h inclusions around .h
files could easily lead to inclusion dependency hell. Most gfp.h
inclusion directives were ignored as stuff from gfp.h was usually
wildly available and often used in preprocessor macros. Each
slab.h inclusion directive was examined and added manually as
necessary.
6. percpu.h was updated not to include slab.h.
7. Build test were done on the following configurations and failures
were fixed. CONFIG_GCOV_KERNEL was turned off for all tests (as my
distributed build env didn't work with gcov compiles) and a few
more options had to be turned off depending on archs to make things
build (like ipr on powerpc/64 which failed due to missing writeq).
* x86 and x86_64 UP and SMP allmodconfig and a custom test config.
* powerpc and powerpc64 SMP allmodconfig
* sparc and sparc64 SMP allmodconfig
* ia64 SMP allmodconfig
* s390 SMP allmodconfig
* alpha SMP allmodconfig
* um on x86_64 SMP allmodconfig
8. percpu.h modifications were reverted so that it could be applied as
a separate patch and serve as bisection point.
Given the fact that I had only a couple of failures from tests on step
6, I'm fairly confident about the coverage of this conversion patch.
If there is a breakage, it's likely to be something in one of the arch
headers which should be easily discoverable easily on most builds of
the specific arch.
Signed-off-by: Tejun Heo <tj@kernel.org>
Guess-its-ok-by: Christoph Lameter <cl@linux-foundation.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
2010-03-24 16:04:11 +08:00
|
|
|
#include <linux/slab.h>
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
|
|
|
|
#include <asm/io.h>
|
|
|
|
#include <asm/dcr.h>
|
|
|
|
|
|
|
|
#include "emac.h"
|
|
|
|
#include "phy.h"
|
|
|
|
#include "zmii.h"
|
|
|
|
#include "rgmii.h"
|
|
|
|
#include "mal.h"
|
|
|
|
#include "tah.h"
|
|
|
|
#include "debug.h"
|
|
|
|
|
2011-08-19 12:33:49 +08:00
|
|
|
#define NUM_TX_BUFF CONFIG_IBM_EMAC_TXB
|
|
|
|
#define NUM_RX_BUFF CONFIG_IBM_EMAC_RXB
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
|
|
|
|
/* Simple sanity check */
|
|
|
|
#if NUM_TX_BUFF > 256 || NUM_RX_BUFF > 256
|
|
|
|
#error Invalid number of buffer descriptors (greater than 256)
|
|
|
|
#endif
|
|
|
|
|
|
|
|
#define EMAC_MIN_MTU 46
|
|
|
|
|
|
|
|
/* Maximum L2 header length (VLAN tagged, no FCS) */
|
|
|
|
#define EMAC_MTU_OVERHEAD (6 * 2 + 2 + 4)
|
|
|
|
|
|
|
|
/* RX BD size for the given MTU */
|
|
|
|
static inline int emac_rx_size(int mtu)
|
|
|
|
{
|
|
|
|
if (mtu > ETH_DATA_LEN)
|
|
|
|
return MAL_MAX_RX_SIZE;
|
|
|
|
else
|
|
|
|
return mal_rx_size(ETH_DATA_LEN + EMAC_MTU_OVERHEAD);
|
|
|
|
}
|
|
|
|
|
|
|
|
#define EMAC_DMA_ALIGN(x) ALIGN((x), dma_get_cache_alignment())
|
|
|
|
|
|
|
|
#define EMAC_RX_SKB_HEADROOM \
|
2011-08-19 12:33:49 +08:00
|
|
|
EMAC_DMA_ALIGN(CONFIG_IBM_EMAC_RX_SKB_HEADROOM)
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
|
|
|
|
/* Size of RX skb for the given MTU */
|
|
|
|
static inline int emac_rx_skb_size(int mtu)
|
|
|
|
{
|
|
|
|
int size = max(mtu + EMAC_MTU_OVERHEAD, emac_rx_size(mtu));
|
|
|
|
return EMAC_DMA_ALIGN(size + 2) + EMAC_RX_SKB_HEADROOM;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* RX DMA sync size */
|
|
|
|
static inline int emac_rx_sync_size(int mtu)
|
|
|
|
{
|
|
|
|
return EMAC_DMA_ALIGN(emac_rx_size(mtu) + 2);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Driver statistcs is split into two parts to make it more cache friendly:
|
|
|
|
* - normal statistics (packet count, etc)
|
|
|
|
* - error statistics
|
|
|
|
*
|
|
|
|
* When statistics is requested by ethtool, these parts are concatenated,
|
|
|
|
* normal one goes first.
|
|
|
|
*
|
|
|
|
* Please, keep these structures in sync with emac_stats_keys.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/* Normal TX/RX Statistics */
|
|
|
|
struct emac_stats {
|
|
|
|
u64 rx_packets;
|
|
|
|
u64 rx_bytes;
|
|
|
|
u64 tx_packets;
|
|
|
|
u64 tx_bytes;
|
|
|
|
u64 rx_packets_csum;
|
|
|
|
u64 tx_packets_csum;
|
|
|
|
};
|
|
|
|
|
|
|
|
/* Error statistics */
|
|
|
|
struct emac_error_stats {
|
|
|
|
u64 tx_undo;
|
|
|
|
|
|
|
|
/* Software RX Errors */
|
|
|
|
u64 rx_dropped_stack;
|
|
|
|
u64 rx_dropped_oom;
|
|
|
|
u64 rx_dropped_error;
|
|
|
|
u64 rx_dropped_resize;
|
|
|
|
u64 rx_dropped_mtu;
|
|
|
|
u64 rx_stopped;
|
|
|
|
/* BD reported RX errors */
|
|
|
|
u64 rx_bd_errors;
|
|
|
|
u64 rx_bd_overrun;
|
|
|
|
u64 rx_bd_bad_packet;
|
|
|
|
u64 rx_bd_runt_packet;
|
|
|
|
u64 rx_bd_short_event;
|
|
|
|
u64 rx_bd_alignment_error;
|
|
|
|
u64 rx_bd_bad_fcs;
|
|
|
|
u64 rx_bd_packet_too_long;
|
|
|
|
u64 rx_bd_out_of_range;
|
|
|
|
u64 rx_bd_in_range;
|
|
|
|
/* EMAC IRQ reported RX errors */
|
|
|
|
u64 rx_parity;
|
|
|
|
u64 rx_fifo_overrun;
|
|
|
|
u64 rx_overrun;
|
|
|
|
u64 rx_bad_packet;
|
|
|
|
u64 rx_runt_packet;
|
|
|
|
u64 rx_short_event;
|
|
|
|
u64 rx_alignment_error;
|
|
|
|
u64 rx_bad_fcs;
|
|
|
|
u64 rx_packet_too_long;
|
|
|
|
u64 rx_out_of_range;
|
|
|
|
u64 rx_in_range;
|
|
|
|
|
|
|
|
/* Software TX Errors */
|
|
|
|
u64 tx_dropped;
|
|
|
|
/* BD reported TX errors */
|
|
|
|
u64 tx_bd_errors;
|
|
|
|
u64 tx_bd_bad_fcs;
|
|
|
|
u64 tx_bd_carrier_loss;
|
|
|
|
u64 tx_bd_excessive_deferral;
|
|
|
|
u64 tx_bd_excessive_collisions;
|
|
|
|
u64 tx_bd_late_collision;
|
|
|
|
u64 tx_bd_multple_collisions;
|
|
|
|
u64 tx_bd_single_collision;
|
|
|
|
u64 tx_bd_underrun;
|
|
|
|
u64 tx_bd_sqe;
|
|
|
|
/* EMAC IRQ reported TX errors */
|
|
|
|
u64 tx_parity;
|
|
|
|
u64 tx_underrun;
|
|
|
|
u64 tx_sqe;
|
|
|
|
u64 tx_errors;
|
|
|
|
};
|
|
|
|
|
|
|
|
#define EMAC_ETHTOOL_STATS_COUNT ((sizeof(struct emac_stats) + \
|
|
|
|
sizeof(struct emac_error_stats)) \
|
|
|
|
/ sizeof(u64))
|
|
|
|
|
|
|
|
struct emac_instance {
|
|
|
|
struct net_device *ndev;
|
|
|
|
struct resource rsrc_regs;
|
|
|
|
struct emac_regs __iomem *emacp;
|
2010-08-06 23:25:50 +08:00
|
|
|
struct platform_device *ofdev;
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
struct device_node **blist; /* bootlist entry */
|
|
|
|
|
|
|
|
/* MAL linkage */
|
|
|
|
u32 mal_ph;
|
2010-08-06 23:25:50 +08:00
|
|
|
struct platform_device *mal_dev;
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
u32 mal_rx_chan;
|
|
|
|
u32 mal_tx_chan;
|
|
|
|
struct mal_instance *mal;
|
|
|
|
struct mal_commac commac;
|
|
|
|
|
|
|
|
/* PHY infos */
|
|
|
|
u32 phy_mode;
|
|
|
|
u32 phy_map;
|
|
|
|
u32 phy_address;
|
|
|
|
u32 phy_feat_exc;
|
|
|
|
struct mii_phy phy;
|
|
|
|
struct mutex link_lock;
|
|
|
|
struct delayed_work link_work;
|
|
|
|
int link_polling;
|
|
|
|
|
2008-10-02 14:37:57 +08:00
|
|
|
/* GPCS PHY infos */
|
|
|
|
u32 gpcs_address;
|
|
|
|
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
/* Shared MDIO if any */
|
|
|
|
u32 mdio_ph;
|
2010-08-06 23:25:50 +08:00
|
|
|
struct platform_device *mdio_dev;
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
struct emac_instance *mdio_instance;
|
|
|
|
struct mutex mdio_lock;
|
|
|
|
|
|
|
|
/* ZMII infos if any */
|
|
|
|
u32 zmii_ph;
|
|
|
|
u32 zmii_port;
|
2010-08-06 23:25:50 +08:00
|
|
|
struct platform_device *zmii_dev;
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
|
|
|
|
/* RGMII infos if any */
|
|
|
|
u32 rgmii_ph;
|
|
|
|
u32 rgmii_port;
|
2010-08-06 23:25:50 +08:00
|
|
|
struct platform_device *rgmii_dev;
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
|
|
|
|
/* TAH infos if any */
|
|
|
|
u32 tah_ph;
|
|
|
|
u32 tah_port;
|
2010-08-06 23:25:50 +08:00
|
|
|
struct platform_device *tah_dev;
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
|
|
|
|
/* IRQs */
|
|
|
|
int wol_irq;
|
|
|
|
int emac_irq;
|
|
|
|
|
|
|
|
/* OPB bus frequency in Mhz */
|
|
|
|
u32 opb_bus_freq;
|
|
|
|
|
|
|
|
/* Cell index within an ASIC (for clk mgmnt) */
|
|
|
|
u32 cell_index;
|
|
|
|
|
|
|
|
/* Max supported MTU */
|
|
|
|
u32 max_mtu;
|
|
|
|
|
|
|
|
/* Feature bits (from probe table) */
|
|
|
|
unsigned int features;
|
|
|
|
|
|
|
|
/* Tx and Rx fifo sizes & other infos in bytes */
|
|
|
|
u32 tx_fifo_size;
|
|
|
|
u32 tx_fifo_size_gige;
|
|
|
|
u32 rx_fifo_size;
|
|
|
|
u32 rx_fifo_size_gige;
|
|
|
|
u32 fifo_entry_size;
|
|
|
|
u32 mal_burst_size; /* move to MAL ? */
|
|
|
|
|
ibm_newemac: Parameterize EMAC Multicast Match Handling
Various instances of the EMAC core have varying: 1) number of address
match slots, 2) width of the registers for handling address match slots,
3) number of registers for handling address match slots and 4) base
offset for those registers.
As the driver stands today, it assumes that all EMACs have 4 IAHT and
GAHT 32-bit registers, starting at offset 0x30 from the register base,
with only 16-bits of each used for a total of 64 match slots.
The 405EX(r) and 460EX now use the EMAC4SYNC core rather than the EMAC4
core. This core has 8 IAHT and GAHT registers, starting at offset 0x80
from the register base, with ALL 32-bits of each used for a total of
256 match slots.
This adds a new compatible device tree entry "emac4sync" and a new,
related feature flag "EMAC_FTR_EMAC4SYNC" along with a series of macros
and inlines which supply the appropriate parameterized value based on
the presence or absence of the EMAC4SYNC feature.
The code has further been reworked where appropriate to use those macros
and inlines.
In addition, the register size passed to ioremap is now taken from the
device tree:
c4 for EMAC4SYNC cores
74 for EMAC4 cores
70 for EMAC cores
rather than sizeof (emac_regs).
Finally, the device trees have been updated with the appropriate compatible
entries and resource sizes.
This has been tested on an AMCC Haleakala board such that: 1) inbound
ICMP requests to 'haleakala.local' via MDNS from both Mac OS X 10.4.11
and Ubuntu 8.04 systems as well as 2) outbound ICMP requests from
'haleakala.local' to those same systems in the '.local' domain via MDNS
now work.
Signed-off-by: Grant Erickson <gerickson@nuovations.com>
Acked-by: Jeff Garzik <jgarzik@pobox.com>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
2008-07-08 06:03:11 +08:00
|
|
|
/* IAHT and GAHT filter parameterization */
|
|
|
|
u32 xaht_slots_shift;
|
|
|
|
u32 xaht_width_shift;
|
|
|
|
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
/* Descriptor management
|
|
|
|
*/
|
|
|
|
struct mal_descriptor *tx_desc;
|
|
|
|
int tx_cnt;
|
|
|
|
int tx_slot;
|
|
|
|
int ack_slot;
|
|
|
|
|
|
|
|
struct mal_descriptor *rx_desc;
|
|
|
|
int rx_slot;
|
|
|
|
struct sk_buff *rx_sg_skb; /* 1 */
|
|
|
|
int rx_skb_size;
|
|
|
|
int rx_sync_size;
|
|
|
|
|
|
|
|
struct sk_buff *tx_skb[NUM_TX_BUFF];
|
|
|
|
struct sk_buff *rx_skb[NUM_RX_BUFF];
|
|
|
|
|
|
|
|
/* Stats
|
|
|
|
*/
|
|
|
|
struct emac_error_stats estats;
|
|
|
|
struct net_device_stats nstats;
|
|
|
|
struct emac_stats stats;
|
|
|
|
|
|
|
|
/* Misc
|
|
|
|
*/
|
|
|
|
int reset_failed;
|
|
|
|
int stop_timeout; /* in us */
|
|
|
|
int no_mcast;
|
|
|
|
int mcast_pending;
|
2007-11-20 11:50:46 +08:00
|
|
|
int opened;
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
struct work_struct reset_work;
|
|
|
|
spinlock_t lock;
|
|
|
|
};
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Features of various EMAC implementations
|
|
|
|
*/
|
|
|
|
|
|
|
|
/*
|
|
|
|
* No flow control on 40x according to the original driver
|
|
|
|
*/
|
|
|
|
#define EMAC_FTR_NO_FLOW_CONTROL_40x 0x00000001
|
|
|
|
/*
|
|
|
|
* Cell is an EMAC4
|
|
|
|
*/
|
|
|
|
#define EMAC_FTR_EMAC4 0x00000002
|
|
|
|
/*
|
|
|
|
* For the 440SPe, AMCC inexplicably changed the polarity of
|
|
|
|
* the "operation complete" bit in the MII control register.
|
|
|
|
*/
|
|
|
|
#define EMAC_FTR_STACR_OC_INVERT 0x00000004
|
|
|
|
/*
|
|
|
|
* Set if we have a TAH.
|
|
|
|
*/
|
|
|
|
#define EMAC_FTR_HAS_TAH 0x00000008
|
|
|
|
/*
|
|
|
|
* Set if we have a ZMII.
|
|
|
|
*/
|
|
|
|
#define EMAC_FTR_HAS_ZMII 0x00000010
|
|
|
|
/*
|
|
|
|
* Set if we have a RGMII.
|
|
|
|
*/
|
|
|
|
#define EMAC_FTR_HAS_RGMII 0x00000020
|
|
|
|
/*
|
2007-12-05 08:14:29 +08:00
|
|
|
* Set if we have new type STACR with STAOPC
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
*/
|
2007-12-05 08:14:29 +08:00
|
|
|
#define EMAC_FTR_HAS_NEW_STACR 0x00000040
|
2008-04-22 08:46:46 +08:00
|
|
|
/*
|
|
|
|
* Set if we need phy clock workaround for 440gx
|
|
|
|
*/
|
|
|
|
#define EMAC_FTR_440GX_PHY_CLK_FIX 0x00000080
|
2008-04-22 08:46:48 +08:00
|
|
|
/*
|
|
|
|
* Set if we need phy clock workaround for 440ep or 440gr
|
|
|
|
*/
|
|
|
|
#define EMAC_FTR_440EP_PHY_CLK_FIX 0x00000100
|
ibm_newemac: Parameterize EMAC Multicast Match Handling
Various instances of the EMAC core have varying: 1) number of address
match slots, 2) width of the registers for handling address match slots,
3) number of registers for handling address match slots and 4) base
offset for those registers.
As the driver stands today, it assumes that all EMACs have 4 IAHT and
GAHT 32-bit registers, starting at offset 0x30 from the register base,
with only 16-bits of each used for a total of 64 match slots.
The 405EX(r) and 460EX now use the EMAC4SYNC core rather than the EMAC4
core. This core has 8 IAHT and GAHT registers, starting at offset 0x80
from the register base, with ALL 32-bits of each used for a total of
256 match slots.
This adds a new compatible device tree entry "emac4sync" and a new,
related feature flag "EMAC_FTR_EMAC4SYNC" along with a series of macros
and inlines which supply the appropriate parameterized value based on
the presence or absence of the EMAC4SYNC feature.
The code has further been reworked where appropriate to use those macros
and inlines.
In addition, the register size passed to ioremap is now taken from the
device tree:
c4 for EMAC4SYNC cores
74 for EMAC4 cores
70 for EMAC cores
rather than sizeof (emac_regs).
Finally, the device trees have been updated with the appropriate compatible
entries and resource sizes.
This has been tested on an AMCC Haleakala board such that: 1) inbound
ICMP requests to 'haleakala.local' via MDNS from both Mac OS X 10.4.11
and Ubuntu 8.04 systems as well as 2) outbound ICMP requests from
'haleakala.local' to those same systems in the '.local' domain via MDNS
now work.
Signed-off-by: Grant Erickson <gerickson@nuovations.com>
Acked-by: Jeff Garzik <jgarzik@pobox.com>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
2008-07-08 06:03:11 +08:00
|
|
|
/*
|
|
|
|
* The 405EX and 460EX contain the EMAC4SYNC core
|
|
|
|
*/
|
|
|
|
#define EMAC_FTR_EMAC4SYNC 0x00000200
|
2008-10-02 14:37:57 +08:00
|
|
|
/*
|
|
|
|
* Set if we need phy clock workaround for 460ex or 460gt
|
|
|
|
*/
|
|
|
|
#define EMAC_FTR_460EX_PHY_CLK_FIX 0x00000400
|
2012-03-05 08:58:22 +08:00
|
|
|
/*
|
|
|
|
* APM821xx requires Jumbo frame size set explicitly
|
|
|
|
*/
|
|
|
|
#define EMAC_APM821XX_REQ_JUMBO_FRAME_SIZE 0x00000800
|
|
|
|
/*
|
|
|
|
* APM821xx does not support Half Duplex mode
|
|
|
|
*/
|
|
|
|
#define EMAC_FTR_APM821XX_NO_HALF_DUPLEX 0x00001000
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
|
|
|
|
/* Right now, we don't quite handle the always/possible masks on the
|
|
|
|
* most optimal way as we don't have a way to say something like
|
|
|
|
* always EMAC4. Patches welcome.
|
|
|
|
*/
|
|
|
|
enum {
|
|
|
|
EMAC_FTRS_ALWAYS = 0,
|
|
|
|
|
|
|
|
EMAC_FTRS_POSSIBLE =
|
2011-08-19 12:33:49 +08:00
|
|
|
#ifdef CONFIG_IBM_EMAC_EMAC4
|
ibm_newemac: Parameterize EMAC Multicast Match Handling
Various instances of the EMAC core have varying: 1) number of address
match slots, 2) width of the registers for handling address match slots,
3) number of registers for handling address match slots and 4) base
offset for those registers.
As the driver stands today, it assumes that all EMACs have 4 IAHT and
GAHT 32-bit registers, starting at offset 0x30 from the register base,
with only 16-bits of each used for a total of 64 match slots.
The 405EX(r) and 460EX now use the EMAC4SYNC core rather than the EMAC4
core. This core has 8 IAHT and GAHT registers, starting at offset 0x80
from the register base, with ALL 32-bits of each used for a total of
256 match slots.
This adds a new compatible device tree entry "emac4sync" and a new,
related feature flag "EMAC_FTR_EMAC4SYNC" along with a series of macros
and inlines which supply the appropriate parameterized value based on
the presence or absence of the EMAC4SYNC feature.
The code has further been reworked where appropriate to use those macros
and inlines.
In addition, the register size passed to ioremap is now taken from the
device tree:
c4 for EMAC4SYNC cores
74 for EMAC4 cores
70 for EMAC cores
rather than sizeof (emac_regs).
Finally, the device trees have been updated with the appropriate compatible
entries and resource sizes.
This has been tested on an AMCC Haleakala board such that: 1) inbound
ICMP requests to 'haleakala.local' via MDNS from both Mac OS X 10.4.11
and Ubuntu 8.04 systems as well as 2) outbound ICMP requests from
'haleakala.local' to those same systems in the '.local' domain via MDNS
now work.
Signed-off-by: Grant Erickson <gerickson@nuovations.com>
Acked-by: Jeff Garzik <jgarzik@pobox.com>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
2008-07-08 06:03:11 +08:00
|
|
|
EMAC_FTR_EMAC4 | EMAC_FTR_EMAC4SYNC |
|
|
|
|
EMAC_FTR_HAS_NEW_STACR |
|
2008-04-22 08:46:46 +08:00
|
|
|
EMAC_FTR_STACR_OC_INVERT | EMAC_FTR_440GX_PHY_CLK_FIX |
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
#endif
|
2011-08-19 12:33:49 +08:00
|
|
|
#ifdef CONFIG_IBM_EMAC_TAH
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
EMAC_FTR_HAS_TAH |
|
|
|
|
#endif
|
2011-08-19 12:33:49 +08:00
|
|
|
#ifdef CONFIG_IBM_EMAC_ZMII
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
EMAC_FTR_HAS_ZMII |
|
|
|
|
#endif
|
2011-08-19 12:33:49 +08:00
|
|
|
#ifdef CONFIG_IBM_EMAC_RGMII
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
EMAC_FTR_HAS_RGMII |
|
2008-09-04 10:57:57 +08:00
|
|
|
#endif
|
2011-08-19 12:33:49 +08:00
|
|
|
#ifdef CONFIG_IBM_EMAC_NO_FLOW_CTRL
|
2008-09-04 10:57:57 +08:00
|
|
|
EMAC_FTR_NO_FLOW_CONTROL_40x |
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
#endif
|
2008-10-02 14:37:57 +08:00
|
|
|
EMAC_FTR_460EX_PHY_CLK_FIX |
|
2012-03-05 08:58:22 +08:00
|
|
|
EMAC_FTR_440EP_PHY_CLK_FIX |
|
|
|
|
EMAC_APM821XX_REQ_JUMBO_FRAME_SIZE |
|
|
|
|
EMAC_FTR_APM821XX_NO_HALF_DUPLEX,
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
};
|
|
|
|
|
|
|
|
static inline int emac_has_feature(struct emac_instance *dev,
|
|
|
|
unsigned long feature)
|
|
|
|
{
|
|
|
|
return (EMAC_FTRS_ALWAYS & feature) ||
|
|
|
|
(EMAC_FTRS_POSSIBLE & dev->features & feature);
|
|
|
|
}
|
|
|
|
|
ibm_newemac: Parameterize EMAC Multicast Match Handling
Various instances of the EMAC core have varying: 1) number of address
match slots, 2) width of the registers for handling address match slots,
3) number of registers for handling address match slots and 4) base
offset for those registers.
As the driver stands today, it assumes that all EMACs have 4 IAHT and
GAHT 32-bit registers, starting at offset 0x30 from the register base,
with only 16-bits of each used for a total of 64 match slots.
The 405EX(r) and 460EX now use the EMAC4SYNC core rather than the EMAC4
core. This core has 8 IAHT and GAHT registers, starting at offset 0x80
from the register base, with ALL 32-bits of each used for a total of
256 match slots.
This adds a new compatible device tree entry "emac4sync" and a new,
related feature flag "EMAC_FTR_EMAC4SYNC" along with a series of macros
and inlines which supply the appropriate parameterized value based on
the presence or absence of the EMAC4SYNC feature.
The code has further been reworked where appropriate to use those macros
and inlines.
In addition, the register size passed to ioremap is now taken from the
device tree:
c4 for EMAC4SYNC cores
74 for EMAC4 cores
70 for EMAC cores
rather than sizeof (emac_regs).
Finally, the device trees have been updated with the appropriate compatible
entries and resource sizes.
This has been tested on an AMCC Haleakala board such that: 1) inbound
ICMP requests to 'haleakala.local' via MDNS from both Mac OS X 10.4.11
and Ubuntu 8.04 systems as well as 2) outbound ICMP requests from
'haleakala.local' to those same systems in the '.local' domain via MDNS
now work.
Signed-off-by: Grant Erickson <gerickson@nuovations.com>
Acked-by: Jeff Garzik <jgarzik@pobox.com>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
2008-07-08 06:03:11 +08:00
|
|
|
/*
|
|
|
|
* Various instances of the EMAC core have varying 1) number of
|
|
|
|
* address match slots, 2) width of the registers for handling address
|
|
|
|
* match slots, 3) number of registers for handling address match
|
|
|
|
* slots and 4) base offset for those registers.
|
|
|
|
*
|
|
|
|
* These macros and inlines handle these differences based on
|
|
|
|
* parameters supplied by the device structure which are, in turn,
|
|
|
|
* initialized based on the "compatible" entry in the device tree.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#define EMAC4_XAHT_SLOTS_SHIFT 6
|
|
|
|
#define EMAC4_XAHT_WIDTH_SHIFT 4
|
|
|
|
|
|
|
|
#define EMAC4SYNC_XAHT_SLOTS_SHIFT 8
|
|
|
|
#define EMAC4SYNC_XAHT_WIDTH_SHIFT 5
|
|
|
|
|
|
|
|
#define EMAC_XAHT_SLOTS(dev) (1 << (dev)->xaht_slots_shift)
|
|
|
|
#define EMAC_XAHT_WIDTH(dev) (1 << (dev)->xaht_width_shift)
|
|
|
|
#define EMAC_XAHT_REGS(dev) (1 << ((dev)->xaht_slots_shift - \
|
|
|
|
(dev)->xaht_width_shift))
|
|
|
|
|
|
|
|
#define EMAC_XAHT_CRC_TO_SLOT(dev, crc) \
|
|
|
|
((EMAC_XAHT_SLOTS(dev) - 1) - \
|
|
|
|
((crc) >> ((sizeof (u32) * BITS_PER_BYTE) - \
|
|
|
|
(dev)->xaht_slots_shift)))
|
|
|
|
|
|
|
|
#define EMAC_XAHT_SLOT_TO_REG(dev, slot) \
|
|
|
|
((slot) >> (dev)->xaht_width_shift)
|
|
|
|
|
|
|
|
#define EMAC_XAHT_SLOT_TO_MASK(dev, slot) \
|
|
|
|
((u32)(1 << (EMAC_XAHT_WIDTH(dev) - 1)) >> \
|
|
|
|
((slot) & (u32)(EMAC_XAHT_WIDTH(dev) - 1)))
|
|
|
|
|
|
|
|
static inline u32 *emac_xaht_base(struct emac_instance *dev)
|
|
|
|
{
|
|
|
|
struct emac_regs __iomem *p = dev->emacp;
|
|
|
|
int offset;
|
|
|
|
|
|
|
|
/* The first IAHT entry always is the base of the block of
|
|
|
|
* IAHT and GAHT registers.
|
|
|
|
*/
|
|
|
|
if (emac_has_feature(dev, EMAC_FTR_EMAC4SYNC))
|
|
|
|
offset = offsetof(struct emac_regs, u1.emac4sync.iaht1);
|
|
|
|
else
|
|
|
|
offset = offsetof(struct emac_regs, u0.emac4.iaht1);
|
|
|
|
|
2010-09-23 13:40:09 +08:00
|
|
|
return (u32 *)((ptrdiff_t)p + offset);
|
ibm_newemac: Parameterize EMAC Multicast Match Handling
Various instances of the EMAC core have varying: 1) number of address
match slots, 2) width of the registers for handling address match slots,
3) number of registers for handling address match slots and 4) base
offset for those registers.
As the driver stands today, it assumes that all EMACs have 4 IAHT and
GAHT 32-bit registers, starting at offset 0x30 from the register base,
with only 16-bits of each used for a total of 64 match slots.
The 405EX(r) and 460EX now use the EMAC4SYNC core rather than the EMAC4
core. This core has 8 IAHT and GAHT registers, starting at offset 0x80
from the register base, with ALL 32-bits of each used for a total of
256 match slots.
This adds a new compatible device tree entry "emac4sync" and a new,
related feature flag "EMAC_FTR_EMAC4SYNC" along with a series of macros
and inlines which supply the appropriate parameterized value based on
the presence or absence of the EMAC4SYNC feature.
The code has further been reworked where appropriate to use those macros
and inlines.
In addition, the register size passed to ioremap is now taken from the
device tree:
c4 for EMAC4SYNC cores
74 for EMAC4 cores
70 for EMAC cores
rather than sizeof (emac_regs).
Finally, the device trees have been updated with the appropriate compatible
entries and resource sizes.
This has been tested on an AMCC Haleakala board such that: 1) inbound
ICMP requests to 'haleakala.local' via MDNS from both Mac OS X 10.4.11
and Ubuntu 8.04 systems as well as 2) outbound ICMP requests from
'haleakala.local' to those same systems in the '.local' domain via MDNS
now work.
Signed-off-by: Grant Erickson <gerickson@nuovations.com>
Acked-by: Jeff Garzik <jgarzik@pobox.com>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
2008-07-08 06:03:11 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
static inline u32 *emac_gaht_base(struct emac_instance *dev)
|
|
|
|
{
|
|
|
|
/* GAHT registers always come after an identical number of
|
|
|
|
* IAHT registers.
|
|
|
|
*/
|
2010-09-23 13:40:09 +08:00
|
|
|
return emac_xaht_base(dev) + EMAC_XAHT_REGS(dev);
|
ibm_newemac: Parameterize EMAC Multicast Match Handling
Various instances of the EMAC core have varying: 1) number of address
match slots, 2) width of the registers for handling address match slots,
3) number of registers for handling address match slots and 4) base
offset for those registers.
As the driver stands today, it assumes that all EMACs have 4 IAHT and
GAHT 32-bit registers, starting at offset 0x30 from the register base,
with only 16-bits of each used for a total of 64 match slots.
The 405EX(r) and 460EX now use the EMAC4SYNC core rather than the EMAC4
core. This core has 8 IAHT and GAHT registers, starting at offset 0x80
from the register base, with ALL 32-bits of each used for a total of
256 match slots.
This adds a new compatible device tree entry "emac4sync" and a new,
related feature flag "EMAC_FTR_EMAC4SYNC" along with a series of macros
and inlines which supply the appropriate parameterized value based on
the presence or absence of the EMAC4SYNC feature.
The code has further been reworked where appropriate to use those macros
and inlines.
In addition, the register size passed to ioremap is now taken from the
device tree:
c4 for EMAC4SYNC cores
74 for EMAC4 cores
70 for EMAC cores
rather than sizeof (emac_regs).
Finally, the device trees have been updated with the appropriate compatible
entries and resource sizes.
This has been tested on an AMCC Haleakala board such that: 1) inbound
ICMP requests to 'haleakala.local' via MDNS from both Mac OS X 10.4.11
and Ubuntu 8.04 systems as well as 2) outbound ICMP requests from
'haleakala.local' to those same systems in the '.local' domain via MDNS
now work.
Signed-off-by: Grant Erickson <gerickson@nuovations.com>
Acked-by: Jeff Garzik <jgarzik@pobox.com>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
2008-07-08 06:03:11 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
static inline u32 *emac_iaht_base(struct emac_instance *dev)
|
|
|
|
{
|
|
|
|
/* IAHT registers always come before an identical number of
|
|
|
|
* GAHT registers.
|
|
|
|
*/
|
2010-09-23 13:40:09 +08:00
|
|
|
return emac_xaht_base(dev);
|
ibm_newemac: Parameterize EMAC Multicast Match Handling
Various instances of the EMAC core have varying: 1) number of address
match slots, 2) width of the registers for handling address match slots,
3) number of registers for handling address match slots and 4) base
offset for those registers.
As the driver stands today, it assumes that all EMACs have 4 IAHT and
GAHT 32-bit registers, starting at offset 0x30 from the register base,
with only 16-bits of each used for a total of 64 match slots.
The 405EX(r) and 460EX now use the EMAC4SYNC core rather than the EMAC4
core. This core has 8 IAHT and GAHT registers, starting at offset 0x80
from the register base, with ALL 32-bits of each used for a total of
256 match slots.
This adds a new compatible device tree entry "emac4sync" and a new,
related feature flag "EMAC_FTR_EMAC4SYNC" along with a series of macros
and inlines which supply the appropriate parameterized value based on
the presence or absence of the EMAC4SYNC feature.
The code has further been reworked where appropriate to use those macros
and inlines.
In addition, the register size passed to ioremap is now taken from the
device tree:
c4 for EMAC4SYNC cores
74 for EMAC4 cores
70 for EMAC cores
rather than sizeof (emac_regs).
Finally, the device trees have been updated with the appropriate compatible
entries and resource sizes.
This has been tested on an AMCC Haleakala board such that: 1) inbound
ICMP requests to 'haleakala.local' via MDNS from both Mac OS X 10.4.11
and Ubuntu 8.04 systems as well as 2) outbound ICMP requests from
'haleakala.local' to those same systems in the '.local' domain via MDNS
now work.
Signed-off-by: Grant Erickson <gerickson@nuovations.com>
Acked-by: Jeff Garzik <jgarzik@pobox.com>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
2008-07-08 06:03:11 +08:00
|
|
|
}
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
|
|
|
|
/* Ethtool get_regs complex data.
|
|
|
|
* We want to get not just EMAC registers, but also MAL, ZMII, RGMII, TAH
|
|
|
|
* when available.
|
|
|
|
*
|
|
|
|
* Returned BLOB consists of the ibm_emac_ethtool_regs_hdr,
|
|
|
|
* MAL registers, EMAC registers and optional ZMII, RGMII, TAH registers.
|
|
|
|
* Each register component is preceded with emac_ethtool_regs_subhdr.
|
|
|
|
* Order of the optional headers follows their relative bit posititions
|
|
|
|
* in emac_ethtool_regs_hdr.components
|
|
|
|
*/
|
|
|
|
#define EMAC_ETHTOOL_REGS_ZMII 0x00000001
|
|
|
|
#define EMAC_ETHTOOL_REGS_RGMII 0x00000002
|
|
|
|
#define EMAC_ETHTOOL_REGS_TAH 0x00000004
|
|
|
|
|
|
|
|
struct emac_ethtool_regs_hdr {
|
|
|
|
u32 components;
|
|
|
|
};
|
|
|
|
|
|
|
|
struct emac_ethtool_regs_subhdr {
|
|
|
|
u32 version;
|
|
|
|
u32 index;
|
|
|
|
};
|
|
|
|
|
ibm_newemac: Parameterize EMAC Multicast Match Handling
Various instances of the EMAC core have varying: 1) number of address
match slots, 2) width of the registers for handling address match slots,
3) number of registers for handling address match slots and 4) base
offset for those registers.
As the driver stands today, it assumes that all EMACs have 4 IAHT and
GAHT 32-bit registers, starting at offset 0x30 from the register base,
with only 16-bits of each used for a total of 64 match slots.
The 405EX(r) and 460EX now use the EMAC4SYNC core rather than the EMAC4
core. This core has 8 IAHT and GAHT registers, starting at offset 0x80
from the register base, with ALL 32-bits of each used for a total of
256 match slots.
This adds a new compatible device tree entry "emac4sync" and a new,
related feature flag "EMAC_FTR_EMAC4SYNC" along with a series of macros
and inlines which supply the appropriate parameterized value based on
the presence or absence of the EMAC4SYNC feature.
The code has further been reworked where appropriate to use those macros
and inlines.
In addition, the register size passed to ioremap is now taken from the
device tree:
c4 for EMAC4SYNC cores
74 for EMAC4 cores
70 for EMAC cores
rather than sizeof (emac_regs).
Finally, the device trees have been updated with the appropriate compatible
entries and resource sizes.
This has been tested on an AMCC Haleakala board such that: 1) inbound
ICMP requests to 'haleakala.local' via MDNS from both Mac OS X 10.4.11
and Ubuntu 8.04 systems as well as 2) outbound ICMP requests from
'haleakala.local' to those same systems in the '.local' domain via MDNS
now work.
Signed-off-by: Grant Erickson <gerickson@nuovations.com>
Acked-by: Jeff Garzik <jgarzik@pobox.com>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
2008-07-08 06:03:11 +08:00
|
|
|
#define EMAC_ETHTOOL_REGS_VER 0
|
|
|
|
#define EMAC_ETHTOOL_REGS_SIZE(dev) ((dev)->rsrc_regs.end - \
|
|
|
|
(dev)->rsrc_regs.start + 1)
|
|
|
|
#define EMAC4_ETHTOOL_REGS_VER 1
|
|
|
|
#define EMAC4_ETHTOOL_REGS_SIZE(dev) ((dev)->rsrc_regs.end - \
|
|
|
|
(dev)->rsrc_regs.start + 1)
|
|
|
|
|
Device tree aware EMAC driver
Based on BenH's earlier work, this is a new version of the EMAC driver
for the built-in ethernet found on PowerPC 4xx embedded CPUs. The
same ASIC is also found in the Axon bridge chip. This new version is
designed to work in the arch/powerpc tree, using the device tree to
probe the device, rather than the old and ugly arch/ppc OCP layer.
This driver is designed to sit alongside the old driver (that lies in
drivers/net/ibm_emac and this one in drivers/net/ibm_newemac). The
old driver is left in place to support arch/ppc until arch/ppc itself
reaches its final demise (not too long now, with luck).
This driver still has a number of things that could do with cleaning
up, but I think they can be fixed up after merging. Specifically:
- Should be adjusted to properly use the dma mapping API.
Axon needs this.
- Probe logic needs reworking, in conjuction with the general
probing code for of_platform devices. The dependencies here between
EMAC, MAL, ZMII etc. make this complicated. At present, it usually
works, because we initialize and register the sub-drivers before the
EMAC driver itself, and (being in driver code) runs after the devices
themselves have been instantiated from the device tree.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2007-08-23 11:56:01 +08:00
|
|
|
#endif /* __IBM_NEWEMAC_CORE_H */
|