AH! There we go. Just as you said.

pi@retropie ~ $ sudo lsusb -v

Bus 001 Device 005: ID 0583:2060 Padix Co., Ltd (Rockfire)
......
  iManufacturer           0
  iProduct                2 USB,2-axis 8-button gamepad
  iSerial                 0
  bNumConfigurations      1

That’s my SNES controller. It happens to match up with…

pi@retropie /opt/retropie/emulators/retroarch/configs $ vim USB_2-axis_8-button_gamepad.cfg
input_device = "USB,2-axis 8-button gamepad  "
input_driver = "udev"
input_b_btn = "1"

And for the PS3 Controller, which is a Bluetooth device, I ran

pi@retropie ~ $ hcitool con
Connections:
        > ACL 00:1E:3D:DF:C9:73 handle 11 state 1 lm MASTER

This give me the MAC address of the controller, so then I investigate the name

pi@retropie ~ $ hcitool name 00:1E:3D:DF:C9:73
PLAYSTATION(R)3 Controller

And that happens to match up to the device name in..

pi@retropie ~ $ cat /opt/retropie/emulators/retroarch/configs/PS3Controller.cfg
input_device = "PLAYSTATION(R)3 Controller"
input_driver = "udev"
input_b_btn = "14"
input_y_btn = "15"
input_select_btn = "0"

That answers my question. I totally didn’t think the Buffalo controller would get reported with such a name, so I never drew that connection. Now to get the PS3 controller to work for my PSX games…

(I’m home now, so I can physically play with stuff)

Floob, in your video I watched earlier today, you mentioned that it may not make a difference if you change the file name of the controller cfg file (USB_2-axis_8-button_gamepad.cfg). It seems, if the only connection between the controller and a profile is the iProduct name, wouldn’t that break the connection?

Also, I’m sorry for missing this bit from the first response:

Retroarch creates a configuration file based off of the lsusb identification.

You did actually answer me with that.

EDIT: I threw a summary into the top so future forum browsers can see it easier.