On 7/31/2016 10:12 PM, John Kasunich wrote: > > What is the bug? "claimed" fields retaining their value > over an unloadrt/loadrt cycle? Since they are arrays and > are initialized as part of the declaration, I don't see how > it can be a bug in the driver code.
IMHO, if you get different behavior between loading a driver the first time vs unloading/reloading it, that's a bug (or at the very least curious behavior that needs to be documented). > What about the 0x803 as a control_offset value instead of > a multiple of 4? That sounds like a typo to me, I've never > seen a chip that had such a break in the pattern of I/O > addresses. Looks like that's supposed to be 0x80C, assuming you're referring to this line: https://github.com/machinekit/machinekit/blob/master/src/hal/drivers/beaglebone_gpio.h#L80 ...probably hasn't shown up until now because most folks don't disable the on-board eMMC, so wouldn't be using that pin. -- Charles Steinkuehler [email protected] -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
