2 ms·
It's allegedly from a Freescale clock driver (see the comments at the top). I'm trying to find the original on Freescale's site, unsuccessfully thus far. If it
by tlrobinson 18y ago
It's allegedly from a Freescale clock driver (see the comments at the top). I'm trying to find the original on Freescale's site, unsuccessfully thus far.
If it is indeed a Freescale-supplied driver issue, it makes me wonder how many other devices failed yesterday...