From: Jerin Jacob <jerinjacobk@gmail.com>
To: Rakesh Kudurumalla <rkudurumalla@marvell.com>
Cc: Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>, dpdk-dev <dev@dpdk.org>
Subject: Re: [PATCH 1/1] common/cnxk: update partnumber for 103xx
Date: Tue, 30 Aug 2022 10:08:27 +0530 [thread overview]
Message-ID: <CALBAE1NiVHRno7QfXShcmUOYN0ZnpZChnQ4UrUXk37orpg5Qjg@mail.gmail.com> (raw)
In-Reply-To: <20220809133146.713485-1-rkudurumalla@marvell.com>
On Tue, Aug 9, 2022 at 7:02 PM Rakesh Kudurumalla
<rkudurumalla@marvell.com> wrote:
>
> During model population part number is different
> for 103xx and hence dpdk initialization fails.
> This fix resolves the same.
>
> Signed-off-by: Rakesh Kudurumalla <rkudurumalla@marvell.com>
Updated the git commit as follows and applied to
dpdk-next-net-mrvl/for-next-net. Thanks
common/cnxk: fix partnumber for CN103xx
Correct the partnumber value for CN103xx.
Fixes: dd462f68f04a ("common/cnxk: support CN103XX platform")
Cc: stable@dpdk.org
Signed-off-by: Rakesh Kudurumalla <rkudurumalla@marvell.com>
> ---
> drivers/common/cnxk/roc_model.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/common/cnxk/roc_model.c b/drivers/common/cnxk/roc_model.c
> index a68baa65ea..c934a10509 100644
> --- a/drivers/common/cnxk/roc_model.c
> +++ b/drivers/common/cnxk/roc_model.c
> @@ -19,7 +19,7 @@ struct roc_model *roc_model;
> #define PART_106xx 0xB9
> #define PART_105xx 0xBA
> #define PART_105xxN 0xBC
> -#define PART_103xx 0xBE
> +#define PART_103xx 0xBD
> #define PART_98xx 0xB1
> #define PART_96xx 0xB2
> #define PART_95xx 0xB3
> --
> 2.25.1
>
prev parent reply other threads:[~2022-08-30 4:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 13:31 Rakesh Kudurumalla
2022-08-30 4:38 ` Jerin Jacob [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=CALBAE1NiVHRno7QfXShcmUOYN0ZnpZChnQ4UrUXk37orpg5Qjg@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=rkudurumalla@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.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).