cc'ing Dan Evans so he can keep an eye out for this issue and update the bug if it is a problem or there are changes worth noting.

Dan support is tracking this right? Could you share some metrics if you get a chance? I take it there have been reports on firmware since 59, right?

Counting from Jan 1, 2008 to present, here is what we know:

 * 9 cases specifically coded as Xilinx caused issues
 * 46 cases coded as "distorted audio" or "no audio" (meaning possible Xilinx issues)

Dean wants to talk to Sean about it

Sadly there doesn't seem to be a good way to validate the xilinx image.  Just as easy to reprogram the xilinx every boot.

Dan, how highly should we prioritize this, do you think?

Let's continue to monitor, although changes in Xilinx area are unlikely.

I'm gathering data from our Tier-1 group and will have a report at end of November.  Let's review this bug then.

Ping Dan.  :)

I think this is fading away.  Possibly because SB Classic sales are sun-setting.  I suggest close this and we'll reopen if it becomes urgent.  (closing as wontfix)