old pitch

[b]Problem: Only One Device Name Supported[/b] (prior to Frodo)
Xbmc only detects xbox 360 controllers if they are a wireless 360 controller of one device name variety.  Across platforms, revisions, wired/wireless, and drivers, it is known by other names, meaning non-obvious controller support is only available to those who update the supplied xml file with their device name manually.

[b]Problem: Invalid Keymapping[/b] (prior to Frodo)
Xbmc's default xml file for the 360 controller uses the xbox1 buttons and axes.  Xbox 360 controllers only go up to button 10 (in some cases it uses up to button 15, and now the keymap supports both cases), while the default keymap.xml for it goes up to 17, resulting in missing functionality.  No way to zoom or scroll, no playlist access, and d-pad is mostly useless.  Furthermore, xbox 360 triggers are on 1 axis, not 2 like xbox1 controllers, breaking everything to do with the triggers

[b]Solution[/b]
XBMC's keymap for Xbox 360 controllers should include an alt name for every device name that xbox 360 controllers have across OSes and revisions, so it works automatically out of the box.  Unfortunately, Windows drivers handle 360 controllers differently than Linux drivers, so a second keymap will be required.  People with xbox 360 controllers should reply with their OS, driver and the device name for their xbox 360 controller as reported in xbmc.log using the instructions below if the keymap on pastebin doesn't work automatically.  The included version of the keymap xml file fixes all the mappings and is optimized.  It includes every device name known so far as altnames.  The devs updated the official xml file with v1.95 in Frodo beta 2.