DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Helin" <helin.zhang@intel.com>
To: "xuelin.shi@freescale.com" <xuelin.shi@freescale.com>,
	"thomas.monjalon@6wind.com" <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] e1000: fix e1000 PCI access endian issue.
Date: Wed, 25 Mar 2015 06:34:31 +0000	[thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A830B72@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1423704412-29143-1-git-send-email-xuelin.shi@freescale.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of
> xuelin.shi@freescale.com
> Sent: Thursday, February 12, 2015 9:27 AM
> To: thomas.monjalon@6wind.com
> Cc: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] e1000: fix e1000 PCI access endian issue.
> 
> From: Xuelin Shi <xuelin.shi@freescale.com>
> 
> e1000 is little endian, but cpu maybe not.
> add necessary conversions.
> 
> rte_cpu_to_le_32(...) for PCI write
> rte_le_to_cpu_32(...) for PCI read.
> 
> Signed-off-by: Xuelin Shi <xuelin.shi@freescale.com>
Acked-by: Helin Zhang <helin.zhang@intel.com>

> ---
>  lib/librte_pmd_e1000/e1000/e1000_osdep.h | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/lib/librte_pmd_e1000/e1000/e1000_osdep.h
> b/lib/librte_pmd_e1000/e1000/e1000_osdep.h
> index 438641e..d04ec73 100644
> --- a/lib/librte_pmd_e1000/e1000/e1000_osdep.h
> +++ b/lib/librte_pmd_e1000/e1000/e1000_osdep.h
> @@ -43,6 +43,7 @@
>  #include <rte_cycles.h>
>  #include <rte_log.h>
>  #include <rte_debug.h>
> +#include <rte_byteorder.h>
> 
>  #include "../e1000_logs.h"
> 
> @@ -96,7 +97,7 @@ typedef int		bool;
>  #define E1000_PCI_REG(reg) (*((volatile uint32_t *)(reg)))
> 
>  #define E1000_PCI_REG_WRITE(reg, value) do { \
> -	E1000_PCI_REG((reg)) = (value); \
> +	E1000_PCI_REG((reg)) = (rte_cpu_to_le_32(value)); \
>  } while (0)
> 
>  #define E1000_PCI_REG_ADDR(hw, reg) \
> @@ -107,7 +108,7 @@ typedef int		bool;
> 
>  static inline uint32_t e1000_read_addr(volatile void* addr)  {
> -	return E1000_PCI_REG(addr);
> +	return rte_le_to_cpu_32(E1000_PCI_REG(addr));
>  }
> 
>  /* Necessary defines */
> --
> 1.9.1

      parent reply	other threads:[~2015-03-25  6:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-12  1:26 xuelin.shi
2015-02-20 10:46 ` Thomas Monjalon
2015-03-25  6:34 ` Zhang, Helin [this message]

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=F35DEAC7BCE34641BA9FAC6BCA4A12E70A830B72@SHSMSX104.ccr.corp.intel.com \
    --to=helin.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.com \
    --cc=xuelin.shi@freescale.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).