+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: Linux (https://forum.kodi.tv/forumdisplay.php?fid=52)
+---- Thread: Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server (/showthread.php?tid=231955)
Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - mule1 - 2016-08-31
But if the press releases from today are correct: Kabilake comes without HDMI2.0. So in my opinion not interesting as a future proofed plattform für Kodi. The waiting continues...
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2016-08-31
Even that thingy here: http://www.intel.de/content/www/de/de/nuc/nuc-kit-nuc6i7kyk-features-configurations.html got hdmi 2.0 - can you post your source? According to my sources, they all have hdmi 2.0 http://www.anandtech.com/show/10492/intel-readies-new-nucs-based-on-kaby-lake-and-apollo-lake-socs
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - ezechiel1917 - 2016-08-31
yea it's a shame, kaby lake cpus won't have native hdmi 2.0 output, KL nucs will have probably have it like the SL ones (dp 1.2 path with additional chip on board)
http://www.anandtech.com/show/10610/intel-announces-7th-gen-kaby-lake-14nm-plus-six-notebook-skus-desktop-coming-in-january/3
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - mule1 - 2016-08-31
(2016-08-31, 21:19)fritsch Wrote: Even that thingy here: http://www.intel.de/content/www/de/de/nuc/nuc-kit-nuc6i7kyk-features-configurations.html got hdmi 2.0 - can you post your source? According to my sources, they all have hdmi 2.0 http://www.anandtech.com/show/10492/intel-readies-new-nucs-based-on-kaby-lake-and-apollo-lake-socs
I was astonished too as i read the article on heise news today because i did also read the contrary infos about the upcoming intel nucs before. Either the news are wrong or they plan ti implement some kind of converter into the nucs, but this could mean that HDR isn't possible.
http://www.heise.de/newsticker/meldung/Kaby-Lake-Intel-bringt-siebte-Generation-der-Core-i-Prozessoren-3308002.html
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fab67 - 2016-08-31
according to : http://www.intel.com/content/www/us/en/processors/pentium/pentium-processor.html
The apollo lake will have hd graphics 500 series, isn't it skylake gpu ?
Will apollo lake HW decode HEVC 10bits ?
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - User 182116 - 2016-09-01
I would have thought it pretty pointless to support HDR and REC2020 if you are not going to natively implement HDMI 2.0a,.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2016-09-01
For hdr to happen a loooot needs to be done on sw side. Kernel, DRM, Mesa, ffmpeg and even vaapi driver. From current implementation I see no way to get the p010 surfaces directly. From vaapi driver pov an RGB conversion is currently implemented.
You see: HDR is not the most pressing need currently.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fab67 - 2016-09-01
It's confirmed apollo lake will not have HEVC main10
I will keep my braswell until next generation.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2016-09-01
What? Who confirmed?
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fab67 - 2016-09-01
http://www.anandtech.com/show/10635/intel-quietly-launches-apollo-lake-soc
" However potential HTPC users will want to note that HEVC Main10 support is not included, so Kaby Lake continues to have an edge for newer premium content services."
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2016-09-01
Says the opposite: http://www.anandtech.com/show/10490/more-atom-apollo-lake-on-display
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2016-09-01
Quote:Relative to its direct predecessor, Intel has gifted Apollo Lake with significantly better capabilities than Braswell, including full hardware acceleration for HEVC Main Profile (8-bit) and VP9 video decoding.^^ Braswell has full HEVC 8 bit decoding support, so there is certainly something wrong.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fab67 - 2016-09-01
15 july 2016 ( before official ) vs 1 september ( intel official lauch )
When I saw yesterday that the GPU was based on skylake generation, I have some doubts and now It's confirmed, I hope this isn't correct.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2016-09-01
Braswell is based on Broadwell! But Braswell has the hevc decoder from skylake ... <- so keep calm and wait. I asked my friends at intel to get me another vainfo output.
Quote: Earlier this year Intel partially canceled the Broxton SoC. The de-facto flagship for Atom this generation, Broxton would have gone into modern smartphones and tablets. Instead Broxton was scaled back to just appearing in embedded products such as Joule. Instead, Apollo Lake would be the consumer flag bearer for this generation of Atom.
https://cgit.freedesktop.org/vaapi/intel-driver/tree/src/i965_device_info.c?id=daf8f6c76287452f2bc37af83d9078831ba0a8b0#n543 and https://cgit.freedesktop.org/vaapi/intel-driver/tree/src/i965_device_info.c?id=daf8f6c76287452f2bc37af83d9078831ba0a8b0#n383 which results in: https://cgit.freedesktop.org/vaapi/intel-driver/tree/src/i965_device_info.c?id=daf8f6c76287452f2bc37af83d9078831ba0a8b0#n48
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2016-09-05
And here the BXT output:
Quote:processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 92
model name : 06/5c
stepping : 9
microcode : 0xc
cpu MHz : 800.000
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 21
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 ds_cpl vmx est tm2 ssse3 sdbg cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave rdrand lahf_lm 3dnowprefetch intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust smep erms mpx rdseed smap clflushopt sha_ni xsaveopt xsavec xgetbv1 dtherm ida arat pln pts
bugs :
bogomips : 2185.78
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 92
model name : 06/5c
stepping : 9
microcode : 0xc
cpu MHz : 800.000
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 4
apicid : 2
initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 21
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 ds_cpl vmx est tm2 ssse3 sdbg cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave rdrand lahf_lm 3dnowprefetch intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust smep erms mpx rdseed smap clflushopt sha_ni xsaveopt xsavec xgetbv1 dtherm ida arat pln pts
bugs :
bogomips : 2185.78
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:
processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 92
model name : 06/5c
stepping : 9
microcode : 0xc
cpu MHz : 800.000
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 2
cpu cores : 4
apicid : 4
initial apicid : 4
fpu : yes
fpu_exception : yes
cpuid level : 21
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 ds_cpl vmx est tm2 ssse3 sdbg cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave rdrand lahf_lm 3dnowprefetch intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust smep erms mpx rdseed smap clflushopt sha_ni xsaveopt xsavec xgetbv1 dtherm ida arat pln pts
bugs :
bogomips : 2185.78
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:
processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 92
model name : 06/5c
stepping : 9
microcode : 0xc
cpu MHz : 800.000
cache size : 1024 KB
physical id : 0
siblings : 4
core id : 3
cpu cores : 4
apicid : 6
initial apicid : 6
fpu : yes
fpu_exception : yes
cpuid level : 21
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 ds_cpl vmx est tm2 ssse3 sdbg cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave rdrand lahf_lm 3dnowprefetch intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust smep erms mpx rdseed smap clflushopt sha_ni xsaveopt xsavec xgetbv1 dtherm ida arat pln pts
bugs :
bogomips : 2185.78
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:
with vainfo
Quote:vainfo: VA-API version: 0.39 (libva 1.7.1)
vainfo: Driver version: Intel i965 driver for Intel® Broxton - 1.7.1
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileH264MultiviewHigh : VAEntrypointVLD
VAProfileH264MultiviewHigh : VAEntrypointEncSlice
VAProfileH264StereoHigh : VAEntrypointVLD
VAProfileH264StereoHigh : VAEntrypointEncSlice
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointEncPicture
VAProfileVP8Version0_3 : VAEntrypointVLD
VAProfileVP8Version0_3 : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileVP9Profile0 : VAEntrypointVLD