Hi Julian, Thanks for looking at the patch.
On Sun, Apr 17, 2016 at 5:07 PM, Julian Calaby <[email protected]> wrote: > Hi Steve, > > This looks like it's using standard serial rates. Does it accept > non-standard rates? If not, should this be checked before being passed > to the hardware? > It should use standard serial rates, and obviously I defaulted it to a sensible one. However, there's nothing that prevents you from using odd and arbitrary rates in the firmware and it should just suck it in and use it. In other words, the firmware will happily try to set 9507 baud if you tell it to. This is specifically for debugging and working with the firmware and IMHO, if you are using this feature and feel a need to set it to something weird, I think the user should be allowed to. If you know enough to be able to shoot yourself in the foot with this, then you should know enough of what you should or shouldn't do and should be allowed to. It's a debugging tool only and I don't see any reason to waste lines in the driver to validate this input. That's my perspective on the issue, but I recognize other opinions may differ. Or you may know of a specific chip where it does matter (the 6003s and 6004s I'm using don't seem to care). If you or Kalle insist on it, I'll be happy to add in some value checking for this parameter. It just doesn't seem worth-while to me. - Steve -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
