-
```
h and v blank should be computed automatically.
```
Original issue reported on code.google.com by `moritzka...@gmail.com` on 14 Jun 2012 at 10:20
-
```
investigate if the grab and xmos grab fns could be threads instead of separate
processes.
```
Original issue reported on code.google.com by `moritzka...@gmail.com` on 14 Jun 2012 at 10:25
-
```
investigate if the grab and xmos grab fns could be threads instead of separate
processes.
```
Original issue reported on code.google.com by `moritzka...@gmail.com` on 14 Jun 2012 at 10:25
-
```
h and v blank should be computed automatically.
```
Original issue reported on code.google.com by `moritzka...@gmail.com` on 14 Jun 2012 at 10:20
-
app_design is failing:
http://swdb.xmos.local:8000/products/testinstance/206465/
Because bug was fixed in https://github.com/xmos/lib_dsp/pull/28
but design_test.expect was't updated.
-
means i cant use vulkan?
-
```
investigate if the grab and xmos grab fns could be threads instead of separate
processes.
```
Original issue reported on code.google.com by `moritzka...@gmail.com` on 14 Jun 2012 at 10:25
-
Here is a suggested API for fft work:
```
typedef struct {
int32_t re;
int32_t im;
} lib_dsp_fft_complex_t;
typedef struct {
int16_t re;
int16_t im;
} lib_dsp_fft_complex_short_t;
v…
-
```
investigate if the grab and xmos grab fns could be threads instead of separate
processes.
```
Original issue reported on code.google.com by `moritzka...@gmail.com` on 14 Jun 2012 at 10:25
-
```
investigate if the grab and xmos grab fns could be threads instead of separate
processes.
```
Original issue reported on code.google.com by `moritzka...@gmail.com` on 14 Jun 2012 at 10:25