Much has been made about just how Sirius and XM could share content as a merged company. Some people find obstacles in differing codec, and feel that such sharing is simply not possible. Others see the obstacle and try to identify a solution.

Part of this whole issues centers around the fact that Sirius and XM use differing CODECS to run and operate their respective systems, and the fact that these CODECs are not compatible. Sirius uses PAC and XM uses AAC+. How then can Sirius and XM effectively merge, when their systems have differing foundations?

What if a solution already exists, and what if that solution can be implemented with a firmware update?

A source that we have spoken to on many occasions is pretty adept at digging up information, may have identified plausible solutions in the form of a resume. Additional information that is very interesting (though quite detailed and technical) can be garnered from various patent applications.

THE RESUME - (Excerpts)

The importance here is not the name of the individual, or other personally identifiable information, but rather what this person was doing. I have taken the liberty of editing the resume to show only the work experience section relating to the subject matter at hand. As can clearly be seen, this individual worked on adding AAC+ Codec to the second generation chipset for Sirius receivers. Thus, what many have seen as a potential hurdle in the synergy process may in fact have been addressed back in 2003. It is quite possible that Sirius radios from Generation 2 forward have capabilities to utilize the AAC+ CODEC.

SUMMARY
Experienced firmware engineer with strength on Telecommunication, Digital Signal Processing, Networking, and RT embedded development.

EXPERTISE
• Digital Signal Processing algorithm and software for telecomm systems (5 year solid experience)

• Microprocessor/DSP based embedded RT system design and development (8 year extensive experience)

• Ethernet LAN, TCP/IP based networking and applications (4 year extensive experience)

• C++, C, and assembly programming

MODERATE
• Hardware programming with VHDL and FPGA

• Board level circuit design
EXPERIENCE

Firmware Engineer (03/02 - present)

Worked on wireless communication chipsets and systems development.

• Worked on a video-over-WiFi project. The project is to deliver MPEG2/MPEG4 video over 802.11 WLAN. Did prototyping work on the Altera Excalibur FPGA platform. Software development was based on an ARM922T™ processor integrated in Excalibur.

• As a core member in digital backend firmware development, continued working on a satellite radio project called SDARS. Work focused on the 2nd generation chipset development for Sirius Radio receivers. Responsibilities included:

-Firmware migration onto a new all-in-one baseband chip.

-Adding AAC+ audio codec to the 2nd generation SDARS chipset.

-Working out receiver value-adding features together with customers.

Given the announcement today relating to programming capability, people may want to look at things is a newer light. To be clear, these bits of information do not mean that certain capabilities exist. However, clearly such operations have been thought about for quite some time. In my opinion, Sirius chipset generation 2 and beyond are the “merger friendly” radios.

FROM PATENT APPLICATIONS

[0006] It should be noted that this disclosure is not limited to the efficient download of firmware images alone, but may be applied to any configuration image which is typically stored in non-volatile memory, such as the hardware configuration bit files for a Complex Programmable Logic Device (CPLD) or Field Programmable Gate Array (FPGA). CPLD and FPGA devices utilize a form of non-volatile memory, on or off-chip, to store the hardware configuration data.

This information illustrates capabilities, and how receivers get and handle information.

Position - Long Sirius, Long XM -IMOJB-