Hello, Greg Ungerer wrote:
I would be surprised if this was a general problem given how much this driver is used. So I would be more inclined to say it is specific to the NXP processor you are using.
I think I had a similar problem with NXP's SC16IS752. (But I can't test the patch right now because I don't have the hardware here.)
I would be more willing to integrate a fix that was specific to the processor that is causing you the problem.
I understand your reservations about applying the patch generally. But if you go for the #ifdef'd version, use a label that identifies the problem instead a label that identifies the CPU. Detlef _______________________________________________ uClinux-dev mailing list [email protected] http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by [email protected] To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
