linux-edac.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Lorenz <Christian.Lorenz@gromeck.de>
To: "Luck, Tony" <tony.luck@intel.com>, Jason Baron <jbaron@akamai.com>
Cc: "linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>
Subject: Re: EDAC support for 'Rocket Lake'
Date: Mon, 7 Nov 2022 09:20:44 +0100	[thread overview]
Message-ID: <9b38a9cc-74eb-b291-216c-b2c3e2cc34a2@gromeck.de> (raw)
In-Reply-To: <7d76be22-ef32-b7e7-1450-ecd9ec86bdb3@gromeck.de>



Am 21.10.22 um 14:00 schrieb Christian Lorenz:
> 
> Am 06.10.22 um 19:03 schrieb Luck, Tony:
>>> I've really only added hardware I have access to, and we don't have
>>> 'Rocket Lake'. I'm happy to help work on support if you have a datasheet
>>> and can test. It may be as easy as adding some new pci ids for example:
>>
>> Jason,
>>
>> Some web searching hasn't turned up a public data sheet. The EDS volume 2
>> is Intel Doc # 615924. Do you have access through Akamai? If that confirms that
>> you just need to add some new PCI IDs etc. then I can get someone to make
>> it OK to post a patch.
>>
>> Testing is harder. I can probably get access to a rocket lake internally. But
>> I don't think those support ACPI error injection. So would only be able to basic
>> "does the driver load" test. Not "does it report memory errors correctly".
>>
>> -Tony
> 
> Hi,
> 
> I can try to organize a piece of HW.
> Let me know if that would help, and who and where this HW would be needed.
> I will check with our HW vendor and we will see if things can be made possible.
> 
> Christian

Hi,

as I didn't get any response, I would like to ask again.
I understood that adding/fixing the EDAC support for Rocket Lake is lacking
available HW.
Is there any demand from one of you for Rocket Lake HW?
Let me know, so that we can check with our vendor.

Thanks.

Christian

      reply	other threads:[~2022-11-07  8:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05 12:13 EDAC support for 'Rocket Lake' Christian Lorenz
2022-10-05 15:21 ` Tony Luck
2022-10-06 15:29   ` Jason Baron
2022-10-06 17:03     ` Luck, Tony
2022-10-21 12:00       ` Christian Lorenz
2022-11-07  8:20         ` Christian Lorenz [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=9b38a9cc-74eb-b291-216c-b2c3e2cc34a2@gromeck.de \
    --to=christian.lorenz@gromeck.de \
    --cc=jbaron@akamai.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=tony.luck@intel.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).