| From: David Miller [da...@davemloft.net] | Sent: Thursday, May 21, 2015 12:30 PM | | The prevailing assumption is that it's OK to have configuration | settings that can't be undone. | | And that's bogus from the beginning.
Oh I definitely understand that and agree. Unfortunately I've inherited a driver architecture that makes that ... "difficult" for many operations ... And I have an internal bug filed against me to fix those particular issues. However, that doesn't answer at least one of my questions which was how do I pass information into the driver _before_ it does the device probe? In this case, telling it to _not_ attempt to attached to the chip firmware in order to debug, load firmware, etc.? And, I still need to know what mechanism we need to use to tell the driver to use one kind of transmit functionality or another. [[And in this case, we _can_ switch back and forth at will.]] Casey-- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
