From: John Harrison <john.c.harrison@intel.com>
To: Timo Aaltonen <tjaalton@ubuntu.com>, <Intel-GFX@Lists.FreeDesktop.Org>
Cc: DRI-Devel@Lists.FreeDesktop.Org
Subject: Re: [Intel-gfx] [PATCH 0/2] Initial GuC firmware release for DG2
Date: Wed, 27 Apr 2022 15:14:16 -0700 [thread overview]
Message-ID: <727fbd97-bf4e-1802-6e30-8b943ca523f6@intel.com> (raw)
In-Reply-To: <6410f76c-af4c-2c75-1ba7-aee3480a6539@ubuntu.com>
On 4/27/2022 11:24, Timo Aaltonen wrote:
> John.C.Harrison@Intel.com kirjoitti 27.4.2022 klo 19.55:
>> From: John Harrison <John.C.Harrison@Intel.com>
>>
>> Add GuC firmware for DG2.
>>
>> Note that an older version of this patch exists in the CI topic
>> branch. Hence this set includes a revert of that patch before applying
>> the new version. When merging, the revert would simply be dropped and
>> the corresponding patch in the topic branch would also be dropped.
>>
>> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
>>
>>
>> John Harrison (2):
>> Revert "drm/i915/dg2: Define GuC firmware version for DG2"
>> drm/i915/dg2: Define GuC firmware version for DG2
>>
>> drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>
> The firmware is not public yet, though? Shouldn't it have been sent
> upstream already? Same complaint applies to DMC.
>
>
Not sure about the DMC team, but for i915 we upload the firmware to an
FDO repo so that the CI system can find it and run the pre-merge testing
with it. However, we don't send the final pull request for the real
linux firmware repo until we have merged the i915 patch to
drm-gt-intel-next and it is definitely going upstream. Otherwise, we
might end up pushing firmwares to the linux repo that never get used.
John.
next prev parent reply other threads:[~2022-04-27 22:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 16:55 [Intel-gfx] [PATCH 0/2] Initial GuC firmware release for DG2 John.C.Harrison
2022-04-27 16:55 ` [Intel-gfx] [PATCH 1/2] Revert "drm/i915/dg2: Define GuC firmware version for DG2" John.C.Harrison
2022-04-27 16:55 ` [Intel-gfx] [PATCH 2/2] drm/i915/dg2: Define GuC firmware version for DG2 John.C.Harrison
2022-04-28 0:24 ` Ceraolo Spurio, Daniele
2022-04-27 17:37 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Initial GuC firmware release " Patchwork
2022-04-27 18:24 ` [Intel-gfx] [PATCH 0/2] " Timo Aaltonen
2022-04-27 22:14 ` John Harrison [this message]
2022-04-28 5:52 ` Lucas De Marchi
2022-04-27 18:59 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " Patchwork
2022-04-28 0:01 ` John Harrison
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=727fbd97-bf4e-1802-6e30-8b943ca523f6@intel.com \
--to=john.c.harrison@intel.com \
--cc=DRI-Devel@Lists.FreeDesktop.Org \
--cc=Intel-GFX@Lists.FreeDesktop.Org \
--cc=tjaalton@ubuntu.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