There are three reasons which cause repetition:
- While we fetch and parse the config ROM, another bus resets happens.
We then need to start over reading the config ROM. This kind of
repetition cannot easily be prevented, but hopefully happens less
often.
- A variation of the theme: Device plugged out, plugged in again.
Causes the config ROM to be at least partially fetched and parsed
again.
- If the firmware author did the CRC algorithm wrong, he got it wrong
for the bus information block, the root directory, and each
subdirectory or leaf (unit directories, instance directories,
textual descriptor leaves, icon descriptors...). Giving a log
notice about each of these CRCs is surely redundant.
When I added the log notice, I didn't try to suppress at least the
latter kind of repetition because I figured that this kind of mistake is
rare nowadays. (If I'm not mistaken, there have for example been
clarifications in IEEE 1212-2001.) Of course it isn't rare to those
people who happen to work with affected devices all the time. So I will
try to reduce the log spam.
BTW, "fix my IEEE 1394 ROM CRC" can sometimes be done by firmware update.
--
Stefan Richter
-=====-==--- -=-= ----=
http://arcgraph.de/sr/
--
