netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: John Linn <john.linn@xilinx.com>
Cc: Michal Simek <monstr@monstr.eu>,
	sadanand.mutyala@xilinx.com, netdev@vger.kernel.org,
	linuxppc-dev@ozlabs.org, davem@davemloft.net
Subject: Re: [PATCH] net: xilinx_emaclite: Fix problem with first incoming packet
Date: Tue, 22 Sep 2009 09:53:43 -0700	[thread overview]
Message-ID: <fa686aa40909220953g708445d9s9c25bd839cc2dd2e@mail.gmail.com> (raw)
In-Reply-To: <fac40d47-5b19-4225-9fee-f7a058851fc0@SG2EHSMHS017.ehs.local>

On Tue, Sep 22, 2009 at 8:24 AM, John Linn <john.linn@xilinx.com> wrote:
> From: Michal Simek <monstr@monstr.eu>
>
> You can't ping the board or connect to it unless you send
> any packet out from board.
>
> Tested-by: John Williams <john.williams@petalogix.com>
> Signed-off-by: Michal Simek <monstr@monstr.eu>
> Acked-by: John Linn <john.linn@xilinx.com>

John, Since this patch is being *sent* by you, then you should use a
"signed-off-by" tag instead because it actually passed through your
hands.

Oh, and:
Acked-by: Grant Likely <grant.likely@secretlab.ca>

> ---
>  drivers/net/xilinx_emaclite.c |    7 ++-----
>  1 files changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/net/xilinx_emaclite.c b/drivers/net/xilinx_emaclite.c
> index dc22782..83a044d 100644
> --- a/drivers/net/xilinx_emaclite.c
> +++ b/drivers/net/xilinx_emaclite.c
> @@ -134,18 +134,15 @@ static void xemaclite_enable_interrupts(struct net_local *drvdata)
>        }
>
>        /* Enable the Rx interrupts for the first buffer */
> -       reg_data = in_be32(drvdata->base_addr + XEL_RSR_OFFSET);
>        out_be32(drvdata->base_addr + XEL_RSR_OFFSET,
> -                reg_data | XEL_RSR_RECV_IE_MASK);
> +                XEL_RSR_RECV_IE_MASK);
>
>        /* Enable the Rx interrupts for the second Buffer if
>         * configured in HW */
>        if (drvdata->rx_ping_pong != 0) {
> -               reg_data = in_be32(drvdata->base_addr + XEL_BUFFER_OFFSET +
> -                                  XEL_RSR_OFFSET);
>                out_be32(drvdata->base_addr + XEL_BUFFER_OFFSET +
>                         XEL_RSR_OFFSET,
> -                        reg_data | XEL_RSR_RECV_IE_MASK);
> +                        XEL_RSR_RECV_IE_MASK);
>        }
>
>        /* Enable the Global Interrupt Enable */
> --
> 1.6.2.1
>
>
>
> This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
>
>
>



-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2009-09-22 16:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-22 15:24 [PATCH] net: xilinx_emaclite: Fix problem with first incoming packet John Linn
2009-09-22 16:53 ` Grant Likely [this message]
2009-09-22 16:56   ` John Linn
2009-09-22 21:17     ` David Miller

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=fa686aa40909220953g708445d9s9c25bd839cc2dd2e@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=davem@davemloft.net \
    --cc=john.linn@xilinx.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=monstr@monstr.eu \
    --cc=netdev@vger.kernel.org \
    --cc=sadanand.mutyala@xilinx.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).