From: Joe Perches <joe@perches.com>
To: gerg@snapgear.com
Cc: netdev@vger.kernel.org, linux-m68k@vger.kernel.org,
Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH 2/2] net: add support for NS8390 based eth controllers on some ColdFire CPU boards
Date: Tue, 03 Jul 2012 22:18:11 -0700 [thread overview]
Message-ID: <1341379091.3627.15.camel@joe2Laptop> (raw)
In-Reply-To: <1341377789-12970-3-git-send-email-gerg@snapgear.com>
On Wed, 2012-07-04 at 14:56 +1000, gerg@snapgear.com wrote:
> From: Greg Ungerer <gerg@uclinux.org>
>
> A number of older ColdFire CPU 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.
Hi Greg, just some trivia:
[]
> diff --git a/drivers/net/ethernet/8390/mcf8390.c b/drivers/net/ethernet/8390/mcf8390.c
[]
> +#ifdef NE2000_ODDOFFSET
> +/*
> + * A lot of the ColdFire boards use a separate address region for odd offset
> + * register addresses. The following macros and functions convert and map
> + * as required. Note that the data port accesses are treated a little
> + * differently, and always accessed via the insX/outsX functions.
> + */
> +#define NE_PTR(a) (((a) & 0x1) ? (NE2000_ODDOFFSET + (a) - 1) : (a))
Maybe use static inlines instead of macros?
static inline void *NE_PTR(void *ptr)
{
if ((unsigned long)ptr & 1)
return ptr - 1 + NE2000_ODDOFFSET;
return ptr;
}
[]
> +static void mcf8390_get_8390_hdr(struct net_device *dev,
> + struct e8390_pkt_hdr *hdr, int ring_page)
> +{
[]
> + /*
> + * This *shouldn't* happen.
> + * If it does, it's the last thing you'll see
> + */
> + if (ei_status.dmaing) {
> + netdev_err(dev,
> + "%s: DMAing conflict [DMAstat:%d][irqlock:%d]\n",
> + __func__, ei_local->dmaing, ei_local->irqlock);
This message seems to get repeated a few times.
Maybe another function/macro or maybe a BUG?
some_dma_err(dev, __func__, ei_local);
> +static void mcf8390_block_input(struct net_device *dev, int count,
> + struct sk_buff *skb, int ring_offset)
> +{
[]
> + /*
> + * This *shouldn't* happen.
> + * If it does, it's the last thing you'll see
> + */
> + if (ei_local->dmaing) {
> + netdev_err(dev,
> + "%s: DMAing conflict [DMAstat:%d][irqlock:%d]\n",
> + __func__, ei_local->dmaing, ei_local->irqlock);
> + return;
> + }
> +static void mcf8390_block_output(struct net_device *dev, int count,
> + const unsigned char *buf,
> + const int start_page)
> +{
[]
> + /*
> + *This *shouldn't* happen.
> + * If it does, it's the last thing you'll see
> + */
> + if (ei_local->dmaing) {
> + netdev_err(dev,
> + "%s: DMAing conflict [DMAstat:%d][irqlock:%d]\n",
> + __func__, ei_local->dmaing, ei_local->irqlock);
> + return;
> + }
> +static int mcf8390_init(struct net_device *dev)
> +{
> + static u32 offsets[] = {
> + 0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07,
> + 0x08, 0x09, 0x0a, 0x0b, 0x0c, 0x0d, 0x0e, 0x0f,
> + };
const? u8?
> + pr_debug("Found ethernet address: %pM\n", dev->dev_addr);
netdev_dbg ?
next prev parent reply other threads:[~2012-07-04 5:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 4:56 [PATCH 0/2] net: support for NS8390 based ethernet on ColdFire CPU boards gerg
2012-07-04 4:56 ` [PATCH 1/2] m68knommu: move the badly named mcfne.h to a better mcf8390.h gerg
2012-07-04 4:56 ` [PATCH 2/2] net: add support for NS8390 based eth controllers on some ColdFire CPU boards gerg
2012-07-04 5:18 ` Joe Perches [this message]
2012-07-04 6:18 ` Greg Ungerer
2012-07-04 6:39 ` Joe Perches
2012-07-04 7:52 ` Geert Uytterhoeven
2012-07-04 8:06 ` Greg Ungerer
2012-07-04 14:52 ` Joe Perches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1341379091.3627.15.camel@joe2Laptop \
--to=joe@perches.com \
--cc=gerg@snapgear.com \
--cc=gerg@uclinux.org \
--cc=linux-m68k@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox