USB FT232 driver on M1 mini I've scored a couple Nanos with FT232RL chips but can't see them on my brand new M1 mini. Can someone point me at how to determine whether v11.1 supports this USB chip?
It appears that the device is being instantiated but the Arduino IDE gets no response to the Get Board Info.
FT232R USB UART:

  Product ID:   0x6001
  Vendor ID:    0x0403  (Future Technology Devices International Limited)
  Version:  6.00
  Serial Number:    AR0JT9YB
  Speed:    Up to 12 Mb/s
  Manufacturer: FTDI
  Location ID:  0x02214000 / 20
  Current Available (mA):   500
  Current Required (mA):    90
  Extra Operating Current (mA): 0

Executing the ioreg mentioned by @st2000 gives;
+-o Root  &lt;class IORegistryEntry, id 0x100000100, retain 31&gt;
  +-o AppleT8103USBXHCI@00000000  &lt;class AppleT8103USBXHCI, id 0x100000291, registered, matched, active, busy 0 (1676 ms), retain 328&gt;
  | +-o Extreme SSD@00200000  &lt;class IOUSBHostDevice, id 0x10000081d, registered, matched, active, busy 0 (219 ms), retain 132&gt;
  +-o AppleT8103USBXHCI@01000000  &lt;class AppleT8103USBXHCI, id 0x100000295, registered, matched, active, busy 0 (4 ms), retain 39&gt;
  +-o AppleT8103USBXHCIFL1100@02000000  &lt;class AppleT8103USBXHCIFL1100, id 0x1000006eb, registered, matched, active, busy 0 (1220 ms), retain 494&gt;
    +-o Keyboard Hub@02100000  &lt;class IOUSBHostDevice, id 0x10000071c, registered, matched, active, busy 0 (164 ms), retain 30&gt;
    | +-o Apple Keyboard@02120000  &lt;class IOUSBHostDevice, id 0x100000805, registered, matched, active, busy 0 (162 ms), retain 32&gt;
    +-o 4-Port USB 2.0 Hub@02200000  &lt;class IOUSBHostDevice, id 0x100000730, registered, matched, active, busy 0 (826 ms), retain 46&gt;
    | +-o 4-Port USB 2.0 Hub@02230000  &lt;class IOUSBHostDevice, id 0x100000785, registered, matched, active, busy 0 (11 ms), retain 42&gt;
    | +-o 4-Port USB 2.0 Hub@02220000  &lt;class IOUSBHostDevice, id 0x100000791, registered, matched, active, busy 0 (16 ms), retain 43&gt;
    | | +-o Backup+ Hub@02223000  &lt;class IOUSBHostDevice, id 0x1000007dc, registered, matched, active, busy 0 (6 ms), retain 41&gt;
    | +-o 4-Port USB 2.0 Hub@02210000  &lt;class IOUSBHostDevice, id 0x10000079d, registered, matched, active, busy 0 (776 ms), retain 43&gt;
    | | +-o FT232R USB UART@02214000  &lt;class IOUSBHostDevice, id 0x100007622, registered, matched, active, busy 0 (75 ms), retain 23&gt;
    | +-o 4-Port USB 2.0 Hub@02240000  &lt;class IOUSBHostDevice, id 0x1000007b6, registered, matched, active, busy 0 (12 ms), retain 42&gt;
    +-o 4-Port USB 3.0 Hub@02600000  &lt;class IOUSBHostDevice, id 0x100000749, registered, matched, active, busy 0 (231 ms), retain 46&gt;
      +-o 4-Port USB 3.0 Hub@02620000  &lt;class IOUSBHostDevice, id 0x10000075e, registered, matched, active, busy 0 (170 ms), retain 43&gt;
      | +-o Backup+ Hub@02623000  &lt;class IOUSBHostDevice, id 0x1000007c3, registered, matched, active, busy 0 (155 ms), retain 41&gt;
      |   +-o Backup+ Hub BK@02623100  &lt;class IOUSBHostDevice, id 0x1000007ee, registered, matched, active, busy 0 (147 ms), retain 131&gt;
      +-o 4-Port USB 3.0 Hub@02640000  &lt;class IOUSBHostDevice, id 0x100000763, registered, matched, active, busy 0 (15 ms), retain 42&gt;
      +-o 4-Port USB 3.0 Hub@02630000  &lt;class IOUSBHostDevice, id 0x100000775, registered, matched, active, busy 0 (15 ms), retain 42&gt;
      +-o 4-Port USB 3.0 Hub@02610000  &lt;class IOUSBHostDevice, id 0x1000007a9, registered, matched, active, busy 0 (16 ms), retain 42&gt;

Which does not appear to contain the device afai can see. Any know if this means a new device for Big Sur is indicated as per Majenko♦ ?
A MAC is usually (unless it is really old) running a derivative of Unix. I would open a console install and use &quot;lsusb&quot; to list out all the USB connected devices.
A (Linux) example of lsusb:
$ lsusb 
Bus 001 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port

I would do this with and with out the Arduino FTDI chip connected and look for the difference. This stackexchange question/answer contains how to do this on a MAC or use other MAC commands to do the same.  As pointed out in the comments the more native MAC command is:
ioreg -p IOUSB

Note, if you have fake FTDI chips there was a time when the FTDI driver that Windows ran would brick the fake FTDI chip. I think it would assign the vendor and device IDs both to zero. You should be able to see this with the &quot;lsusb&quot; command.