On Mon, Sep 29, 2014 at 05:46:38PM -0500, Felipe Balbi wrote: > Hi, > > On Mon, Sep 29, 2014 at 05:38:33PM -0500, Michael Welling wrote: > > > > > Alright, this is already ridiculous. Andrew, if I resend the patch can > > > > > you apply it since maintainer has been ignoring this thread anyway ? > > > > > > > > > > > > > Do you reall think this is the best way to approach this? > > > > > > when maintainer doesn't respond for weeks, yeah! Sure it is. > > > > > > > Perhaps it would be better to explain what each field of the > > > > configuration register does and then we can move on. > > > > > > perhaps Jonathan could tell me exactly what he wants because I can't > > > handle back-and-forth anymore. Specially when he complains about stuff > > > he asked me to modify himself. > > > > > > > In particular the OPT3001_CONFIGURATION_L field needs to be explained > > > > such that the ABI can be properly applied. > > > > > > > > Looking at the docs for the Windows demo program the field is associated > > > > with a latch configuration. What does this bit field actually do? > > > > Still no technical information. Without all the facts how can you expect > > him to tell you what he wants? > > yeah, because clearly he doesn't know himself, right ? Could you explain how it works to me then? > > > > > Either have TI release the documentation or add comments to each of the > > > > fields of each of the registers such that we can understand what exactly > > > > they are doing. > > > > > > TI will release the documentation when that's all cleared up with Legal. > > > You can't expect it to be any earlier than that. > > > > I am a little fuzzy on how the source code can be released when an NDA > > is required to access the datasheet. > > > > Isn't the source code going to be breaking the NDA by releasing information > > that is in the datasheet? > > that's really not my role inside TI, though. I have no degree by any law > school from any country. When I get asked to write a driver, all I do is > request permission to release it, if that says "okay, release it", I > don't go after the Lawyer who decided it was okay to release the driver. > > On top of that, what does that has anything to do with anything ? I'm > pretty sure many have released code based off of either simulation or > pre-release HW. Lack of public documentation does not prevent source > code from being released at all. > > Try to get documentation for most of SoCs supported under the ARM tree > and you'll see at least 80% of them will require NDA and/or a big > purchase order of many SoCs before you can get documentation. > I don't know I am just trying to the more facts so my mailbox will stop pinging. :) > -- > balbi -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
