Re: [EXTERNAL] Re: [RFC PATCH 0/4] DirectX on Linux

2020-06-16 Thread Pavel Machek
Hi! > Thanks for the discussion. I may not be able to immediately answer all of > your questions, but I'll do my best . > Could you do something with your email settings? Because this is not how you should use email on lkml. "[EXTERNAL]" in the subject, top-posting, unwrapped lines... Tha

RE: [EXTERNAL] Re: [RFC PATCH 0/4] DirectX on Linux

2020-05-20 Thread Steve Pronovost
<mailto:alexander.deuc...@amd.com>; KY Srinivasan <mailto:k...@microsoft.com>; Wei Liu <mailto:wei....@kernel.org>; Hawking Zhang <mailto:hawking.zh...@amd.com> Subject: Re: [EXTERNAL] Re: [RFC PATCH 0/4] DirectX on Linux Hi Steve, Sounds all good, some more comme

Re: [EXTERNAL] Re: [RFC PATCH 0/4] DirectX on Linux

2020-05-20 Thread Thomas Zimmermann
Hi Steve, thank you for the fast reply. Am 20.05.20 um 09:42 schrieb Steve Pronovost: >> Echoing what others said, you're not making a DRM driver. The driver should >> live outside of the DRM code. > > Agreed, please see my earlier reply. We'll be moving the driver to > drivers/hyperv node or

RE: [EXTERNAL] Re: [RFC PATCH 0/4] DirectX on Linux

2020-05-20 Thread Steve Pronovost
>Echoing what others said, you're not making a DRM driver. The driver should >live outside of the DRM code. Agreed, please see my earlier reply. We'll be moving the driver to drivers/hyperv node or something similar. Apology for the confusion here. > I have one question about the driver API: on

RE: [EXTERNAL] Re: [RFC PATCH 0/4] DirectX on Linux

2020-05-19 Thread Steve Pronovost
Hey guys, Thanks for the discussion. I may not be able to immediately answer all of your questions, but I'll do my best 😊. drivers/hyperv sounds like it could be a better location. We weren't too sure where to put this, we though /drivers/gpu would be appropriate given this deal with GPUs, but