<Joerg-Neo900>
re stresstest etc: we won't do much stress testing, we just write little bash jobs that test the functionality of the new sensors and actors (mostly LEDs)
<Joerg-Neo900>
and yes, any help with that is highly appreciated
<Joerg-Neo900>
get the datasheets of something you're interested in, find out about existing drivers in upstream linux for it (or simply talk to it via I2C, pretty much everything is I2C in Neo900), then consider and write fancy little testing scripts or even apps using that sensor or actor
<Joerg-Neo900>
we won't need that on Neo900 anymore, since we got autonomous charging. Though you still _can_ do similar stuff if you want to, it's just not _needed_ anymore
<Joerg-Neo900>
this and similar stuff is exactly what we need proto_v2 for to test all subsystems
<Joerg-Neo900>
OS devels however may already want to start integrating that stuff into the OS, using proto_v2 as development&testing platform
louisdk has joined #neo900
<Joerg-Neo900>
the one thing we will test more thoroughly (sort of "strsstest") is our modem sandboxing and monitoring solution, we will run some software against the complete hardware sensors and actors involved there, to demonstrate how it works
<Joerg-Neo900>
I'm unclear how accurate and useful the magnetic compass will be, since we have steel components from N900 that were not designed to minimize interference with magnetic fields. Though many other devices seem to also have steel parts and a magnetic compas and I think usually you can calibrate out eny adverse effects, we will have to check that and there's no guarantee we can achieve good results
<Joerg-Neo900>
likelihood of total failure of compass is low anyway
<Joerg-Neo900>
sw devels might need to take into account with calibration: *) state of kbd slide open/closed (moving magnet in display), *) state of kickstand in/out (steel 'cover' in kickstand moving relative to the magnet in battery lid)
<Joerg-Neo900>
com/p/neo900/doc/create/ and create the page for /Lights-Backlight/. Then search upstream linux for any drivers you can find for that chip, and add name and URLs/links to the wikipage