Thanks to the sloooooow compile and package generation I have myself only tested so far:
udelay(2000) - works
udelay(50) - breaks
Currently compiling with 250, as Catcrash suggested that 100 breaks.
Ideally we should have two independent confirmations for each number and find the point where it changes from works -> breaks
What do we have so far:
udelay(2000) - works (> 2 people)
udelay(1000) - works (knuutsen, catcrash)
udelay(250) - compiling (stephan d.)
udelay(100) - breaks (catcrash)
udelay(50) - breaks (stephan d.)
Thanks to the sloooooow compile and package generation I have myself only tested so far:
udelay(2000) - works
udelay(50) - breaks
Currently compiling with 250, as Catcrash suggested that 100 breaks.
Ideally we should have two independent confirmations for each number and find the point where it changes from works -> breaks
What do we have so far:
udelay(2000) - works (> 2 people)
udelay(1000) - works (knuutsen, catcrash)
udelay(250) - compiling (stephan d.)
udelay(100) - breaks (catcrash)
udelay(50) - breaks (stephan d.)