> We really need this in 2.6.20 I think. Why is this urgent? This is just a workaround for one target's buggy firmware, right? And I would hope there is firmware available that fixes this without any workaruonds on the other side ... or is that not the case? - R.