In other words, a developer that would work with it would need to reserve a considerable amount of time in order for it to lose weight and be able to be merged upstream outside staging. The same code is copied over and over on several parts
Depending on the version of atomisp, one has to change the source code to enable the right support It doesn't properly use the V4L2 framework The sensor drivers don't use the v4l-subdev kernel API lots of layers internally abstracting stuff The main problem is that the atomisp driver has too many troubles: > The main problem is to extract exact version of firmware and C code for
> hardware? I could help with that by providing hardware for development. > Was there anyone who wanted to work on this but could not due to lack of > no developer had time to work with (and/or hardware availability) > (In reply to RussianNeuroMancer from comment #14) (In reply to Andy Shevchenko from comment #15)
