如何配置raw_gadget模拟Realtek RTL8192 USB无线网卡以触发Linux内核r8192u_usb.ko驱动的rtl8192_usb_probe()函数（无真实硬件测试）

Let's break down exactly what you need to do to get the r8192u_usb_probe() function triggered when emulating the Realtek RTL8192 USB adapter with raw_gadget. The core issue here is that raw_gadget needs to mimic the exact USB identity and interface characteristics that the driver expects—here's the step-by-step breakdown:

The r8192u_usb driver uses a USB device ID table to match hardware. You need to mimic the exact idVendor and idProduct that the driver recognizes, plus any required interface/class attributes.

• Check the driver's supported device list directly from the source code:

  grep -A15 "static const struct usb_device_id r8192u_usb_id_table" drivers/staging/rtl8192u/r8192u_usb.c
  

  Common values for Realtek RTL8192CU adapters are idVendor=0x0bda and idProduct=0x8172, but double-check to match your driver's exact entries.
• You can also use modinfo r8192u_usb if the driver is already built as a module to see the supported alias entries.

First, ensure your kernel has raw_gadget enabled (CONFIG_USB_RAW_GADGET=y or =m). Then follow these steps to set up the emulated device:

1. Load the raw_gadget module (if built as a module):

   modprobe raw_gadget
   

2. Navigate to the USB gadget config filesystem:

   cd /sys/kernel/config/usb_gadget/
   

3. Create a new gadget instance and set its identity:

   mkdir my_rtl8192 && cd my_rtl8192
   # Replace with your driver's actual vendor/product IDs
   echo 0x0bda > idVendor
   echo 0x8172 > idProduct
   

4. Add human-readable strings (match the real device's values if possible):

   mkdir -p strings/0x409
   echo "Realtek Semiconductor Corp." > strings/0x409/manufacturer
   echo "RTL8192CU Wireless LAN Adapter" > strings/0x409/product
   echo "123456" > strings/0x409/serialnumber
   

5. Create a configuration and set power limits:

   mkdir -p configs/c.1/strings/0x409
   echo 250 > configs/c.1/MaxPower
   echo "Default Configuration" > configs/c.1/strings/0x409/configuration
   

6. Critical: Emulate the correct USB interface and endpoints
   The r8192u_usb driver expects specific interface class/subclass/protocol values and endpoint types. Use the usb_raw function in raw_gadget to define a custom interface that matches what the driver looks for:

   mkdir functions/usb_raw.0
   

   Now you need to write the interface and endpoint descriptors to the desc file. These must match the descriptors the driver checks in r8192u_usb_probe(). For RTL8192U, this typically includes a vendor-specific interface with bulk and interrupt endpoints. Example descriptor bytes (adjust if your driver expects different values):

   # Interface descriptor (bLength=9, bDescriptorType=4, vendor-specific class)
   echo -n -e '\x09\x04\x00\x00\x03\xff\x00\x00\x00' > functions/usb_raw.0/desc
   # Bulk OUT endpoint (address 0x01)
   echo -n -e '\x07\x05\x01\x02\x40\x00\x00' >> functions/usb_raw.0/desc
   # Bulk IN endpoint (address 0x82)
   echo -n -e '\x07\x05\x82\x02\x40\x00\x00' >> functions/usb_raw.0/desc
   # Interrupt IN endpoint (address 0x83, interval 10ms)
   echo -n -e '\x07\x05\x83\x03\x08\x0a\x00' >> functions/usb_raw.0/desc
   

7. Bind the raw function to your configuration:

   ln -s functions/usb_raw.0 configs/c.1/
   

8. Activate the gadget by binding it to a USB controller:

   # List available controllers first: ls /sys/class/udc/
   echo <your-udc-device> > UDC
   # Example: echo fe000000.usb > UDC
   

1. Ensure the driver is enabled in your kernel (CONFIG_RTL8192U=y or =m). If built as a module, reload it after activating the gadget:

   rmmod r8192u_usb && modprobe r8192u_usb
   

2. Check dmesg for probe triggers or matching logs:

   dmesg | grep -i "r8192\|rtl8192"
   

   You should see a line like rtl8192u_usb 1-1:1.0: rtl8192cu, ... if the probe function was successfully triggered.

• Double-check that idVendor and idProduct exactly match entries in the driver's usb_device_id table. Even a single byte mismatch will prevent matching.
• Verify the interface descriptor's bInterfaceClass, bInterfaceSubClass, and bInterfaceProtocol match what the driver checks. Look for code like if (interface->cur_altsetting->desc.bInterfaceClass != USB_CLASS_VENDOR_SPEC) in r8192u_usb_probe() to confirm.
• Check raw_gadget logs for errors: dmesg | grep -i raw_gadget
• Ensure your USB controller supports gadget mode (some x86 hardware may require enabling OTG support in the BIOS).

内容的提问来源于stack exchange，提问作者stone