On Mon, Aug 18, 2014 at 8:59 AM, Agron Selimaj <as9902613@xxxxxxxxx> wrote: > Hello, > > I am making a GPIO driver for a custom x86_64 motherboard. > > It came with a windows driver which is fairly simple but before > reading or witting to a certain GPIO pin I have to keep reading an > other ioport with inb() until GPIO data is ready. > > However, I need to make sure this is the right motherboard so I am > reading a 10 byte string where the model information is located, but > just before I read the last byte the kernel is killing my kernel > module and marking it as tainted. Why would this happen? Backtrace, module source code? > I also noticed that detection and probing is now done using platform > drivers on ARM platform. I would like to follow the same on x86_64 but > I don't find any documentation/examples to help me. Documentation/driver-model/platform.txt should be a good start. -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html