All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
To: Trigger Huang <trigger.huang@gmail.com>, dri-devel@lists.freedesktop.org
Cc: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
Subject: Re: [accel/ivpu] Help -- Which Intel CPU processor can be used for iVPU driver?
Date: Thu, 2 Nov 2023 10:24:24 +0100	[thread overview]
Message-ID: <ccf8e1ae-efa5-4d09-bc43-4ed18536c910@linux.intel.com> (raw)
In-Reply-To: <CANH0Q9mzBVr7KTJQmvLsqndpTZ8JU0rDfDQhu10kFsRgfybA4A@mail.gmail.com>

Hi,

You need a Meteor Lake based platform.
Intel 14th gen desktop CPUs were supposed to be Meteor Lake but they ended up as Raptor Lake.
NPU (formerly known as VPU) will be available in 14th gen mobile chips.
I will update the Kconfig description.

Regards,
Jacek

On 02.11.2023 07:59, Trigger Huang wrote:
> Hello,
> 
> I want to have a try for the iVPU driver but don't know which CPU platform
> is suitable. Would you help?
> 
> According to the description in linux/drivers/accel/ivpu/Kconfig, it says
> that Choose this option if you have a system that has an *14*th generation
> Intel CPU
> But according to the Intel  I7 *14*700k spec (
> https://www.intel.com/content/www/us/en/products/sku/236783/intel-core-i7-processor-14700k-33m-cache-up-to-5-60-ghz/specifications.html),
> there is
> no description about Versatile Processing Unit.
> 
> So which CPU should I choose?
> 
> Thanks,
> Trigger
> 

  reply	other threads:[~2023-11-02  9:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02  6:59 [accel/ivpu] Help -- Which Intel CPU processor can be used for iVPU driver? Trigger Huang
2023-11-02  9:24 ` Jacek Lawrynowicz [this message]
2023-11-02 11:09   ` Trigger Huang
2023-11-03  8:37     ` Jacek Lawrynowicz

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=ccf8e1ae-efa5-4d09-bc43-4ed18536c910@linux.intel.com \
    --to=jacek.lawrynowicz@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=stanislaw.gruszka@linux.intel.com \
    --cc=trigger.huang@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.