Manu Abraham wrote: > Initially we thought it would be best to do it in userspace, but the > addition of ioctls to the API, made that thought a bit diminished .. > This is applicable for most of the frontends though .. Hm, let's ask the other way around: What is the advantage of doing this in kernelspace? Can we: - guarantee that all frontends behave the same, so we had a real, device independent, API? - define an API which covers all possibilities (input ranges, ...), so we don't need additional, private IOCTLs? - pass results in a good way to the userspace? For example, a blocking read of a "frontend parameter" structure which returns new found transponders? Is this flexible enough? Felix
