11-07-2016, 12:23 AM
(11-06-2016, 06:35 AM)MarkHaysHarris777 Wrote:it occurs to me that using a program call to set a hardware register is a software solution. that , to me, is one of the basic reasons/purposes of software, the manipulation of the present hardware to achieve a goal. can you explain to me why it is not? thanks.(11-03-2016, 10:43 AM)waldo Wrote: What is the difference between the HW method and the SW patch ?
What we are trying to do is to enable only the Tx-delay and to disable ONLY the Rx-delay. Both approaches are a hardware solution ; one sets the GMAC register with a program call ( this uses the longsleep kernel patch to achieve the hardware result ) , and the other uses a physical resistor on the board to 'pull-down' the line to ground which will also afffect the same hardward change -- namely , the Rx-delay will be disabled and only the Tx-delay will be enabled.
This either works or it doesn't. It is sad to hear that register setting is not working for people; I am preparing to implement the resistor fix on my ubuntu board ( my non working board ); I'll be reporting back here with the results soon. In the mean time it would be interesting to note which ones ( if any ) the register setting to disable the Rx-delay is actually working in the field.
Twleve out of twelve boards were 'fixed' in the lab by setting the register; so something is 'off' in the field. Just a note, setting Rx-delay = 0 does not work since that setting still results in a 2ns delay regardless; the Rx-delay actually has to be disabled.