linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Martyn Welch <martyn.welch@ge.com>
To: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
	davem@davemloft.net,
	Sandeep Gopalpet <Sandeep.Kumar@freescale.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Gianfar driver failing on MPC8641D based board
Date: Mon, 01 Mar 2010 13:07:32 +0000	[thread overview]
Message-ID: <4B8BBC14.9010705@ge.com> (raw)
In-Reply-To: <20100226213825.GA32363@oksana.dev.rtsoft.ru>

Anton Vorontsov wrote:
> diff --git a/drivers/net/gianfar.c b/drivers/net/gianfar.c
> index 8bd3c9f..cccb409 100644
> --- a/drivers/net/gianfar.c
> +++ b/drivers/net/gianfar.c
> @@ -2021,7 +2021,6 @@ static int gfar_start_xmit(struct sk_buff *skb, struct net_device *dev)
>  	}
>  
>  	/* setup the TxBD length and buffer pointer for the first BD */
> -	tx_queue->tx_skbuff[tx_queue->skb_curtx] = skb;
>  	txbdp_start->bufPtr = dma_map_single(&priv->ofdev->dev, skb->data,
>  			skb_headlen(skb), DMA_TO_DEVICE);
>  
> @@ -2053,6 +2052,10 @@ static int gfar_start_xmit(struct sk_buff *skb, struct net_device *dev)
>  
>  	txbdp_start->lstatus = lstatus;
>  
> +	eieio(); /* force lstatus write before tx_skbuff */
> +
> +	tx_queue->tx_skbuff[tx_queue->skb_curtx] = skb;
> +
>  	/* Update the current skb pointer to the next entry we will use
>  	 * (wrapping if necessary) */
>  	tx_queue->skb_curtx = (tx_queue->skb_curtx + 1) &
>   
I can confirm 10/10 successful boots on p2020ds and mpc8641_hpcn.

Martyn


-- 
Martyn Welch (Principal Software Engineer)   |   Registered in England and
GE Intelligent Platforms                     |   Wales (3828642) at 100
T +44(0)127322748                            |   Barbirolli Square, Manchester,
E martyn.welch@ge.com                        |   M2 3AB  VAT:GB 927559189

  parent reply	other threads:[~2010-03-01 13:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05 14:00 Gianfar driver failing on MPC8641D based board Martyn Welch
2010-02-25 10:31 ` Martyn Welch
2010-02-25 16:46   ` Martyn Welch
2010-02-25 16:51     ` Anton Vorontsov
2010-02-25 17:49       ` Anton Vorontsov
2010-02-26  0:53         ` Paul Gortmaker
2010-02-26  3:14           ` Anton Vorontsov
2010-02-26  4:58             ` Kumar Gopalpet-B05799
2010-02-26 12:06             ` Martyn Welch
2010-02-26 14:35               ` Anton Vorontsov
2010-02-26 14:52                 ` Paul Gortmaker
2010-02-26 15:18                   ` Martyn Welch
2010-02-26 15:34                     ` Martyn Welch
2010-02-26 16:10                       ` Anton Vorontsov
2010-02-26 16:27                         ` Paul Gortmaker
2010-02-26 21:38                           ` Anton Vorontsov
2010-02-26 22:12                             ` Paul Gortmaker
2010-02-27  5:35                             ` Kumar Gopalpet-B05799
2010-03-02 14:02                               ` Anton Vorontsov
2010-03-01 13:07                             ` Martyn Welch [this message]
2010-02-26 11:51       ` Martyn Welch
2010-02-25 18:27     ` Kumar Gala

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=4B8BBC14.9010705@ge.com \
    --to=martyn.welch@ge.com \
    --cc=Sandeep.Kumar@freescale.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=netdev@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    /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;
as well as URLs for NNTP newsgroup(s).