> -Original Message-
> From: Auld, Matthew
> Sent: Thursday, July 28, 2022 1:38 PM
> To: C, Ramalingam ; intel-...@lists.freedesktop.org
> Cc: dri-devel@lists.freedesktop.org; Thomas Hellström
>
> Subject: Re: [PATCH] drm/i915/ttm: don't leak the ccs state
>
> -Original Message-
> From: Auld, Matthew
> Sent: Wednesday, July 27, 2022 10:14 PM
> To: intel-...@lists.freedesktop.org
> Cc: dri-devel@lists.freedesktop.org; Thomas Hellström
> ; C,
> Ramalingam
> Subject: [PATCH] drm/i915/ttm: don't leak the ccs state
>
On 2022-02-07 at 15:37:09 +0100, Christian König wrote:
> Am 07.02.22 um 14:53 schrieb Ramalingam C:
> > On 2022-02-07 at 12:41:59 +0100, Christian König wrote:
> > > Am 07.02.22 um 10:37 schrieb Ramalingam C:
> > > > On flat-ccs capable platform we need to evict and resore the ccs data
> > > >
On 2022-01-20 at 16:09:01 +, Robert Beckett wrote:
>
>
> On 20/01/2022 15:58, Matthew Auld wrote:
> > On 20/01/2022 15:44, Robert Beckett wrote:
> > >
> > >
> > > On 20/01/2022 14:59, Matthew Auld wrote:
> > > > On 20/01/2022 13:15, Robert Beckett wrote:
> > > > >
> > > > >
> > > > > On
> -Original Message-
> From: Sean Paul
> Sent: Tuesday, June 23, 2020 9:29 PM
> To: dri-devel@lists.freedesktop.org; intel-...@lists.freedesktop.org
> Cc: Li, Juston ; C, Ramalingam
> ; ville.syrj...@linux.intel.com;
> jani.nik...@linux.intel.com; joonas.lahti...@
> -Original Message-
> From: Sean Paul
> Sent: Tuesday, June 23, 2020 9:29 PM
> To: dri-devel@lists.freedesktop.org; intel-...@lists.freedesktop.org
> Cc: Li, Juston ; C, Ramalingam
> ; ville.syrj...@linux.intel.com;
> jani.nik...@linux.intel.com; joonas.lahti...@
> -Original Message-
> From: Sean Paul
> Sent: Tuesday, June 23, 2020 9:29 PM
> To: dri-devel@lists.freedesktop.org; intel-...@lists.freedesktop.org
> Cc: Li, Juston ; C, Ramalingam
> ; ville.syrj...@linux.intel.com;
> jani.nik...@linux.intel.com; joonas.lahti...@
> -Original Message-
> From: Maarten Lankhorst [mailto:maarten.lankho...@linux.intel.com]
> Sent: Tuesday, March 5, 2019 8:09 PM
> To: C, Ramalingam ; intel-...@lists.freedesktop.org;
> dri-devel@lists.freedesktop.org; daniel.vet...@ffwll.ch; Shankar, Uma
>
> Su
1626eab70ebc61d015e69a4bc3479d9228539343
Author: Ramalingam C
Date: Fri Feb 15 14:04:58 2019 +0530
drm/i915: header for i915 - MEI_HDCP interface
v15 is now part of github.
Best Regards,
Ramalingam C
> -Original Message-
> From: Winkler, Tomas
> Sent: Monday, February 25, 2019 1:45 AM
> To: C
Tomas,
Could you please help to review and give final "Go" for the series?
Thanks
--Ram.
On 2/21/2019 11:41 PM, Ramalingam C wrote:
This series enables the HDCP2.2 Type 0 for I915. The sequence for
HDCP2.2 authentication and encryption is implemented as a generic flow
between HDMI and DP.
> -Original Message-
> From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel Vetter
> Sent: Thursday, February 21, 2019 1:10 AM
> To: C, Ramalingam
> Cc: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
> daniel.vet...@ffwll.ch; Winkle
On 2/10/2019 1:55 PM, Winkler, Tomas wrote:
On 2/9/2019 9:39 PM, Winkler, Tomas wrote:
Request ME FW to start the HDCP2.2 session for an intel port.
Prepares payloads for command WIRED_INITIATE_HDCP2_SESSION and
sends
to ME FW.
On Success, ME FW will start a HDCP2.2 session for the port
On 2/9/2019 9:39 PM, Winkler, Tomas wrote:
Request ME FW to start the HDCP2.2 session for an intel port.
Prepares payloads for command WIRED_INITIATE_HDCP2_SESSION and sends
to ME FW.
On Success, ME FW will start a HDCP2.2 session for the port and provides the
content for HDCP2.2 AKE_Init
On 2/8/2019 1:18 AM, Daniel Vetter wrote:
On Thu, Feb 07, 2019 at 08:40:08PM +0100, Daniel Vetter wrote:
On Thu, Feb 07, 2019 at 02:33:57AM +0530, Ramalingam C wrote:
Defining the mei-i915 interface functions and initialization of
the interface.
v2:
Adjust to the new interface changes.
> -Original Message-
> From: Winkler, Tomas
> Sent: Friday, February 8, 2019 3:42 AM
> To: C, Ramalingam ; intel-...@lists.freedesktop.org;
> dri-devel@lists.freedesktop.org; daniel.vet...@ffwll.ch; Shankar, Uma
>
> Subject: RE: [PATCH v11 39/42] misc/mei/hdcp
> -Original Message-
> From: Winkler, Tomas
> Sent: Friday, February 8, 2019 3:05 AM
> To: C, Ramalingam ; intel-...@lists.freedesktop.org;
> dri-devel@lists.freedesktop.org; daniel.vet...@ffwll.ch; Shankar, Uma
>
> Subject: RE: [PATCH v11 28/42] misc/mei/hdcp: Init
On 2/7/2019 8:43 PM, Winkler, Tomas wrote:
v2:
mei interface handle is protected with mutex. [Chris Wilson]
v3:
Notifiers are used for the mei interface state.
v4:
Poll for mei client device state
Error msg for out of mem [Uma]
Inline req for init function removed [Uma]
v5:
Sure. Intention was enabling the HDCP2.2 testing on CI for ICL. I will drop
this patch, instead I will cherry-pick the one you have published for other
branch.
Best Regards,
Ramalingam C
> -Original Message-
> From: Winkler, Tomas
> Sent: Thursday, February 7, 2019 12:47 P
Daniel,
Due to significant changes @unbind and cleanup, i have dropped your r-b.
Please review it again.
--Ram
On 2/7/2019 2:33 AM, Ramalingam C wrote:
Defining the mei-i915 interface functions and initialization of
the interface.
v2:
Adjust to the new interface changes. [Tomas]
On 2/6/2019 3:57 PM, Winkler, Tomas wrote:
Request ME FW to start the HDCP2.2 session for an intel port.
Prepares payloads for command WIRED_INITIATE_HDCP2_SESSION and
sends
to
ME FW.
On Success, ME FW will start a HDCP2.2 session for the port and
provides the content for HDCP2.2 AKE_Init
Thanks Tomas.
On 2/5/2019 6:39 PM, Winkler, Tomas wrote:
Request ME FW to start the HDCP2.2 session for an intel port.
Prepares payloads for command WIRED_INITIATE_HDCP2_SESSION and sends
to
ME FW.
On Success, ME FW will start a HDCP2.2 session for the port and
provides the content for
On 2/4/2019 9:34 PM, Winkler, Tomas wrote:
On HDMI connector init, intel_hdcp_init is passed with a flag for hdcp2.2
support based on the platform capability.
v2:
Rebased.
v3:
Collected the reviewed-by received.
Signed-off-by: Ramalingam C
Reviewed-by: Uma Shankar
---
daniel,
Could you please review this patch too.? Already Updated this as per
your previous review comment.
--Ram
On 1/31/2019 12:29 PM, Ramalingam C wrote:
Implement the required WA sequence for KBL to fix the
incorrect positioning of the window of oppurtunity and enc_en
signalling.
v2:
On 2/4/2019 7:54 PM, Shankar, Uma wrote:
-Original Message-
From: C, Ramalingam
Sent: Thursday, January 31, 2019 12:29 PM
To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
Uma
Cc: C, Ramalingam
Subject: [PATCH
On 2/4/2019 7:39 PM, Shankar, Uma wrote:
-Original Message-
From: C, Ramalingam
Sent: Thursday, January 31, 2019 12:29 PM
To: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
daniel.vet...@ffwll.ch; Winkler, Tomas ; Shankar,
Uma
Cc: C, Ramalingam
Subject: [PATCH
Tomas,
On 1/31/2019 2:02 PM, Daniel Vetter wrote:
Also we need CI results without this patch so I can start merging. Rough
merge plan:
- needs ack to merge component.c through drm-intel
- merge all the i915 patches
- topic branch for mei, shared with mei subsystem
Is this convenient to you? Or
On 1/31/2019 1:26 PM, Daniel Vetter wrote:
On Thu, Jan 31, 2019 at 12:29:23PM +0530, Ramalingam C wrote:
"hdcp_encrypted" flag is defined to denote the HDCP1.4 encryption status.
This SW tracking is used to determine the need for real hdcp1.4 disable
and hdcp_check_link upon CP_IRQ.
On
On 1/31/2019 1:47 PM, Daniel Vetter wrote:
On Thu, Jan 31, 2019 at 12:29:22PM +0530, Ramalingam C wrote:
Defining the mei-i915 interface functions and initialization of
the interface.
v2:
Adjust to the new interface changes. [Tomas]
Added further debug logs for the failures at MEI i/f.
On 12/20/2018 9:36 PM, Winkler, Tomas wrote:
+static void __exit mei_hdcp_exit(void)
+{
+ mei_hdcp_component_cleanup(>dev);
Don’t think you can do that, no guarantees this will be valid pointer
As we discussed offline, we have the below line at cleanup.
So valid pointer is made sure. I
On 12/19/2018 12:15 PM, C, Ramalingam wrote:
Tomas and Daniel,
From the discussion on this thread, I infer following understanding:
* At present(v9) I915 wants to be hard binded to mei_hdcp
device-driver binding status through components
o This means I915 driver load will get
On 12/19/2018 8:51 PM, Daniel Vetter wrote:
Indeed, I overlooked that. Maybe highlight it a bit more with a separate
if (!CONFIG_ENABLED(MEI_HDCP))
return false;
so it stick out more in the previous patch. Currently it's a bit burried.
With that + the init ordering
On 12/19/2018 9:18 PM, Daniel Vetter wrote:
On Thu, Dec 13, 2018 at 09:31:10AM +0530, Ramalingam C wrote:
"hdcp_encrypted" flag is defined to denote the HDCP1.4 encryption status.
This SW tracking is used to determine the need for real hdcp1.4 disable
and hdcp_check_link upon CP_IRQ.
On
On 12/19/2018 10:05 PM, Daniel Vetter wrote:
On Wed, Dec 19, 2018 at 5:22 PM C, Ramalingam wrote:
On 12/19/2018 9:28 PM, Daniel Vetter wrote:
On Wed, Dec 19, 2018 at 09:09:00PM +0530, C, Ramalingam wrote:
On 12/19/2018 8:46 PM, Daniel Vetter wrote:
On Thu, Dec 13, 2018 at 09:31:15AM +0530
On 12/19/2018 9:28 PM, Daniel Vetter wrote:
On Wed, Dec 19, 2018 at 09:09:00PM +0530, C, Ramalingam wrote:
On 12/19/2018 8:46 PM, Daniel Vetter wrote:
On Thu, Dec 13, 2018 at 09:31:15AM +0530, Ramalingam C wrote:
Enums and macros are defined for HDCP2.2 link check.
Signed-off-by: Ramalingam
On 12/19/2018 9:10 PM, Daniel Vetter wrote:
On Thu, Dec 13, 2018 at 09:31:39AM +0530, Ramalingam C wrote:
Implement the required WA sequence for KBL to fix the
incorrect positioning of the window of oppurtunity and enc_en
signalling.
Signed-off-by: Ramalingam C
---
On 12/19/2018 9:05 PM, Daniel Vetter wrote:
On Wed, Dec 19, 2018 at 08:35:48PM +0530, C, Ramalingam wrote:
On 12/19/2018 8:05 PM, Daniel Vetter wrote:
On Thu, Dec 13, 2018 at 09:31:12AM +0530, Ramalingam C wrote:
+ if (!hdcp->is_repeater && shim->conf
On 12/19/2018 8:46 PM, Daniel Vetter wrote:
On Thu, Dec 13, 2018 at 09:31:15AM +0530, Ramalingam C wrote:
Enums and macros are defined for HDCP2.2 link check.
Signed-off-by: Ramalingam C
---
include/drm/drm_hdcp.h | 8
1 file changed, 8 insertions(+)
diff --git
On 12/19/2018 8:18 PM, Daniel Vetter wrote:
On Thu, Dec 13, 2018 at 09:31:14AM +0530, Ramalingam C wrote:
Implements the HDCP2.2 repeaters authentication steps such as verifying
the downstream topology and sending stream management information.
v2: Rebased.
v3:
-EINVAL is returned for
On 12/19/2018 7:30 PM, Daniel Vetter wrote:
On Thu, Dec 13, 2018 at 09:31:09AM +0530, Ramalingam C wrote:
Defining the mei-i915 interface functions and initialization of
the interface.
v2:
Adjust to the new interface changes. [Tomas]
Added further debug logs for the failures at MEI i/f.
On 12/19/2018 8:05 PM, Daniel Vetter wrote:
On Thu, Dec 13, 2018 at 09:31:12AM +0530, Ramalingam C wrote:
Implements HDCP2.2 authentication for hdcp2.2 receivers, with
following steps:
Authentication and Key exchange (AKE).
Locality Check (LC).
Session Key
Winkler, Tomas wrote:
On Sat, Dec 15, 2018 at 09:20:38PM +, Winkler, Tomas wrote:
On Thu, Dec 13, 2018 at 5:27 PM Winkler, Tomas
wrote:
On Thu, Dec 13, 2018 at 1:36 PM C, Ramalingam
wrote:
Tomas and Daniel,
We got an issue here.
The relationship that we try to build between I915
Tomas and Daniel,
We got an issue here.
The relationship that we try to build between I915 and mei_hdcp is as follows:
* We are using the components to establish the relationship.
* I915 is component master where as mei_hdcp is component.
* I915 adds the component master during the module
On 12/13/2018 1:47 PM, Winkler, Tomas wrote:
All HDCP1.4 routines are gathered together, followed by the generic functions
those can be extended for HDCP2.2 too.
Signed-off-by: Ramalingam C
---
drivers/gpu/drm/i915/intel_hdcp.c | 118 +++--
-
1 file
On 12/13/2018 1:52 PM, Winkler, Tomas wrote:
Implements the HDCP2.2 repeaters authentication steps such as verifying the
downstream topology and sending stream management information.
v2: Rebased.
v3:
-EINVAL is returned for topology error and rollover scenario.
Endianness conversion
On 12/12/2018 4:34 PM, C, Ramalingam wrote:
On 12/12/2018 4:08 PM, Daniel Vetter wrote:
On Wed, Dec 12, 2018 at 02:28:29PM +0530, C, Ramalingam wrote:
On 12/7/2018 7:59 PM, Daniel Vetter wrote:
On Fri, Dec 07, 2018 at 11:22:44AM +0530, C, Ramalingam wrote:
On 12/6/2018 3:53 PM, Daniel
On 12/12/2018 4:08 PM, Daniel Vetter wrote:
On Wed, Dec 12, 2018 at 02:28:29PM +0530, C, Ramalingam wrote:
On 12/7/2018 7:59 PM, Daniel Vetter wrote:
On Fri, Dec 07, 2018 at 11:22:44AM +0530, C, Ramalingam wrote:
On 12/6/2018 3:53 PM, Daniel Vetter wrote:
On Tue, Nov 27, 2018 at 04:13:03PM
On 12/6/2018 4:15 PM, Daniel Vetter wrote:
On Tue, Nov 27, 2018 at 04:13:06PM +0530, Ramalingam C wrote:
Implements the HDCP2.2 repeaters authentication steps such as verifying
the downstream topology and sending stream management information.
v2:
Rebased.
v3:
No Changes.
v4:
-EINVAL
On 12/7/2018 7:59 PM, Daniel Vetter wrote:
On Fri, Dec 07, 2018 at 11:22:44AM +0530, C, Ramalingam wrote:
On 12/6/2018 3:53 PM, Daniel Vetter wrote:
On Tue, Nov 27, 2018 at 04:13:03PM +0530, Ramalingam C wrote:
Defining the mei-i915 interface functions and initialization of
the interface
Hi,
In one of the offline discussion Tomas has shared his review comments on v8.
So I am sharing the abstract of his suggestions here for the discussion and for
the agreement of interface in the community.
Tomas please correct/add if I am missing any points.
1. Remove the
On 12/7/2018 11:22 AM, C, Ramalingam wrote:
On 12/6/2018 3:53 PM, Daniel Vetter wrote:
On Tue, Nov 27, 2018 at 04:13:03PM +0530, Ramalingam C wrote:
Defining the mei-i915 interface functions and initialization of
the interface.
Signed-off-by: Ramalingam C
Signed-off-by: Tomas Winkler
On 12/7/2018 11:22 AM, C, Ramalingam wrote:
On 12/6/2018 3:53 PM, Daniel Vetter wrote:
On Tue, Nov 27, 2018 at 04:13:03PM +0530, Ramalingam C wrote:
Defining the mei-i915 interface functions and initialization of
the interface.
Signed-off-by: Ramalingam C
Signed-off-by: Tomas Winkler
On 12/6/2018 7:50 PM, Daniel Vetter wrote:
On Tue, Nov 27, 2018 at 04:13:31PM +0530, Ramalingam C wrote:
Implement the required WA sequence for KBL to fix the
incorrect positioning of the window of oppurtunity and enc_en
signalling.
Signed-off-by: Ramalingam C
---
On 12/6/2018 6:57 PM, Daniel Vetter wrote:
On Tue, Nov 27, 2018 at 04:13:07PM +0530, Ramalingam C wrote:
Implements the link integrity check once in 500mSec.
Once encryption is enabled, an ongoing Link Integrity Check is
performed by the HDCP Receiver to check that cipher synchronization
is
On 12/6/2018 4:00 PM, Daniel Vetter wrote:
On Tue, Nov 27, 2018 at 04:13:04PM +0530, Ramalingam C wrote:
Considering that HDCP2.2 is more secure than HDCP1.4, When a setup
supports HDCP2.2 and HDCP1.4, HDCP2.2 will be enabled.
When HDCP2.2 enabling fails and HDCP1.4 is supported, HDCP1.4 is
On 12/6/2018 3:53 PM, Daniel Vetter wrote:
On Tue, Nov 27, 2018 at 04:13:03PM +0530, Ramalingam C wrote:
Defining the mei-i915 interface functions and initialization of
the interface.
Signed-off-by: Ramalingam C
Signed-off-by: Tomas Winkler
---
drivers/gpu/drm/i915/i915_drv.h | 2 +
On 12/6/2018 3:33 PM, Daniel Vetter wrote:
On Tue, Nov 27, 2018 at 04:13:02PM +0530, Ramalingam C wrote:
Add the HDCP2.2 initialization to the existing HDCP1.4 stack.
With the comments below addressed the commit message is a bit untrue,
since this just wires up a basic hdcp2_supported flag in
On 12/5/2018 12:45 AM, Ville Syrjälä wrote:
On Tue, Dec 04, 2018 at 11:37:05PM +0530, Ramalingam C wrote:
HDCP1.4 is enabled and validated only on GEN9+ platforms.
Signed-off-by: Ramalingam C
Reviewed-by: Sean Paul
---
drivers/gpu/drm/i915/intel_hdcp.c | 3 +--
1 file changed, 1
Sean and Daniel,
Could you please help me with the review these changes?
--Ram
On 11/27/2018 7:32 PM, Ramalingam C wrote:
Couple of more HDCP1.4 fixes on
- Key load process for CFL
- Encryption status change time
- debug log addition
- active platform coverage
Ramalingam C (4):
On 11/28/2018 10:56 AM, Stéphane Marchesin wrote:
Hi,
Just a drive-by comment, but did you check that this fails gracefully
on platforms which don't enable the ME? For example Chrome OS :)
That is taken care :) HDCP2.2 is attempted only if platform enables the
ME and its required kernel
On 11/27/2018 11:07 PM, Daniel Vetter wrote:
On Tue, Nov 27, 2018 at 04:54:15PM +, Bloomfield, Jon wrote:
I'm not formally reviewing this series, but while glancing at it, I noticed
-Original Message-
From: Intel-gfx On Behalf Of
Ramalingam C
Sent: Tuesday, November 27, 2018
On 11/27/2018 8:45 PM, Ville Syrjälä wrote:
On Tue, Nov 27, 2018 at 07:32:56PM +0530, Ramalingam C wrote:
HDCP1.4 key load process varies between Intel platform to platform.
For Gen9 platforms except BXT and GLK, HDCP1.4 key is loaded using
the GT Driver Mailbox interface. Instead of listing
> -Original Message-
> From: Sean Paul [mailto:seanp...@chromium.org]
> Sent: Tuesday, July 10, 2018 2:21 AM
> To: C, Ramalingam
> Cc: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
> dan...@ffwll.ch; Winkler, Tomas ; Usyskin,
> Alexander ; Shankar
> -Original Message-
> From: Sean Paul [mailto:seanp...@chromium.org]
> Sent: Thursday, July 12, 2018 12:38 AM
> To: C, Ramalingam
> Cc: Sean Paul ; intel-...@lists.freedesktop.org; dri-
> de...@lists.freedesktop.org; dan...@ffwll.ch; Winkler, Tomas
> ; Usyskin, Alexa
> -Original Message-
> From: Sean Paul [mailto:seanp...@chromium.org]
> Sent: Thursday, July 12, 2018 2:36 AM
> To: C, Ramalingam
> Cc: Sean Paul ; intel-...@lists.freedesktop.org; dri-
> de...@lists.freedesktop.org; dan...@ffwll.ch; Winkler, Tomas
> ; Usyskin, Alexa
> -Original Message-
> From: Sean Paul [mailto:seanp...@chromium.org]
> Sent: Tuesday, July 10, 2018 2:04 AM
> To: C, Ramalingam
> Cc: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
> dan...@ffwll.ch; Winkler, Tomas ; Usyskin,
> Alexander ; Shan
> -Original Message-
> From: Sean Paul [mailto:seanp...@chromium.org]
> Sent: Tuesday, July 10, 2018 2:00 AM
> To: C, Ramalingam
> Cc: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
> dan...@ffwll.ch; Winkler, Tomas ; Usyskin,
> Alexander ; Shan
> -Original Message-
> From: Sean Paul [mailto:seanp...@chromium.org]
> Sent: Tuesday, July 10, 2018 1:53 AM
> To: C, Ramalingam
> Cc: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
> dan...@ffwll.ch; Winkler, Tomas ; Usyskin,
> Alexander ; Shan
Thanks seanpaul for the reviews.
> -Original Message-
> From: Sean Paul [mailto:seanp...@chromium.org]
> Sent: Tuesday, July 10, 2018 1:51 AM
> To: C, Ramalingam
> Cc: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
> dan...@ffwll.ch; Winkle
Best Regards,
Ramalingam C
> -Original Message-
> From: daniel.vet...@ffwll.ch [mailto:daniel.vet...@ffwll.ch] On Behalf Of
> Daniel Vetter
> Sent: Wednesday, June 20, 2018 5:14 PM
> To: C, Ramalingam
> Cc: intel-gfx ; dri-devel de...@lists.freedesktop.org&g
> -Original Message-
> From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel Vetter
> Sent: Tuesday, May 29, 2018 2:01 PM
> To: C, Ramalingam
> Cc: Daniel Vetter ; intel-...@lists.freedesktop.org; dri-
> de...@lists.freedesktop.org; seanp...@chromiu
> -Original Message-
> From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel Vetter
> Sent: Tuesday, May 29, 2018 12:27 PM
> To: C, Ramalingam
> Cc: intel-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
> seanp...@chromium.org; dan...@ffw
> -Original Message-
> From: Usyskin, Alexander
> Sent: Thursday, May 17, 2018 11:29 AM
> To: C, Ramalingam <ramalinga...@intel.com>; Shankar, Uma
> <uma.shan...@intel.com>; intel-...@lists.freedesktop.org; dri-
> de...@lists.freedesktop.org; seanp...@chrom
Best Regards,
Ramalingam C
> -Original Message-
> From: Sean Paul [mailto:seanp...@chromium.org]
> Sent: Tuesday, December 5, 2017 8:07 PM
> To: C, Ramalingam <ramalinga...@intel.com>
> Cc: dri-devel <dri-devel@lists.freedesktop.org>; Hans Verkuil
> <
> -Original Message-
> From: Sean Paul [mailto:seanp...@chromium.org]
> Sent: Wednesday, July 26, 2017 8:23 PM
> To: C, Ramalingam <ramalinga...@intel.com>
> Cc: Sean Paul <seanp...@chromium.org>; Vetter, Daniel
> <daniel.vet...@intel.co
74 matches
Mail list logo
