Re: [RFC v1] Data port coherency control for UMDs.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



We don’t have any timeline for this at the moment. 
NEO driver is quite fresh in open source and adoption will be handled in near future.

Can we move on with review process and handle adoption in separate thread?

Thanks,
Bartosz

-----Original Message-----
From: Joonas Lahtinen [mailto:joonas.lahtinen@xxxxxxxxxxxxxxx] 
Sent: Wednesday, April 4, 2018 11:19 AM
To: Dunajski, Bartosz <bartosz.dunajski@xxxxxxxxx>; Ewins, Jon <jon.ewins@xxxxxxxxx>; Lis, Tomasz <tomasz.lis@xxxxxxxxx>; intel-gfx@xxxxxxxxxxxxxxxxxxxxx; Dave Airlie <airlied@xxxxxxxxxx>
Cc: chris@xxxxxxxxxxxxxxxxxx; Winiarski, Michal <michal.winiarski@xxxxxxxxx>
Subject: RE: [RFC v1] Data port coherency control for UMDs.

Quoting Dunajski, Bartosz (2018-03-30 12:00:51)
> I think the adoption is not a problem here.

Adoption is important for fulfilling the DRM subsystem requirements for merging new kernel uAPI that I referred to previously.

So do we have some timeline for any distro picking up the new driver?

Regards, Joonas

_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx




[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux