On Jan 25, 8:27 pm, "jon.schell" <jon.sch...@kyocera.com> wrote:
> That is the whole of the problem. Then as background, I said that I > already know how to copy a device driver, as I used an LED driver as a > template and used that to interface with the app, but that it's > limited to one byte with no context. I could make that system work if > I really had to, but there has to be a correct way to do it, and I > don't have an example of what I expect it to be, which is either using > an ioctl somehow to pass the whole set of data at once, or having the > driver have multiple attributes so that I can write the data to it in > context. ioctl will certainly work, and fairly easily, but adding new ioctl's to the kernel is now discouraged, which may be a problem if you ever want your driver incorporated upstream but shoving multi-line formatted data through the sysfs interface is also discouraged - essentially you are supposed to make a different 'file' for each property an idea that might be worth considering would be to implement a virtual uart that would allow your application to have a conversation with whatever is running on the modem processor -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
