#
f5e3329a |
|
20-Jan-2024 |
Gordon Bergling <gbe@FreeBSD.org> |
usb: Fix two typos in source code comments - s/bascially/basically/ - s/assistence/assistance/ MFC after: 3 days
|
#
71625ec9 |
|
16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
sys: Remove $FreeBSD$: one-line .c comment pattern Remove /^/[*/]\s*\$FreeBSD\$.*\n/
|
#
fc43ff08 |
|
06-Aug-2015 |
Ian Lepore <ian@FreeBSD.org> |
Add support to the uftdi driver for reading and writing the serial eeprom that can be attached to the chips, via ioctl() calls.
|
#
74855db6 |
|
25-Apr-2014 |
Ian Lepore <ian@FreeBSD.org> |
Remove device type from the uftdi_devs table, enhance the jtag-skip feature. Device type and revision is now determined from the bcdDevice field and doesn't need to be in the table at all. The feature that skips creation of /dev/ttyU* entries for jtag and gpio interfaces is enhanced: - The feature is now optional, but enabled by default. A tunable and sysctl are available to control it: hw.usb.uftdi.skip_jtag_interfaces. - We no longer assume interface #0 is the only jtag interface. Up to eight interfaces per chip can be flagged as jtag. (Current ftdi chips support a max of 4 interfaces; this leaves room for growth.) - Some manufacturers don't change the product ID or use the same ID for different devices intended for both serial-comms and jtag/gpio use. Often while the product ID is the same, the product name string is different, so it's now possible to search for the product name in a table of strings and get the set of non-tty interfaces from that table.
|
#
a9d84a2b |
|
05-Apr-2014 |
Ian Lepore <ian@FreeBSD.org> |
Add ioctl(2) calls to uftdi(4) to access bitbang, MPSSE, CPU_FIFO, and other modes supported by the FTDI serial adapter chips. In addition to adding the new ioctls, this change removes all the code that reset the chip at attach and open/close time, and also the code that turned on RTS/CTS flow control on open without any permission to do so (that was just always a bug in the driver). When FTDI chips are configured as GPIO or MPSSE or other special-purpose uses by an attached serial eeprom, the chip will power on with certain pins driven or floating, and it's important that the driver not do anything to the chip to perturb that unless it receives a specific command to do so. When used for "plain old serial comms" the chip powers on into the right mode and never needs to be reset while it's running to operate properly, so this change is transparent to most users.
|
#
9537ab6c |
|
01-Apr-2014 |
Ian Lepore <ian@FreeBSD.org> |
Support serial speeds up to 12mbaud with newer FTDI chips. Recent FDTI chips have the ability to operate at up to 12mbps. The newer chips with faster clocks have the same usb vendor/product IDs as the older chips; the bcdDevice field must be used to detect the newer versions. This change includes a new function to do that instead of using just the IDs from the vendor/product table. The code to choose the baud clock divisor is completely rewritten. In addition to supporting the new higher clock rates, the rewrite fixes a longstanding bug in the old code which put the high bits of the fractional part of the divisor into the wrong place in the wIndex field. That bug was mostly harmless -- it accidentally didn't affect standard baud rates and would only show up when using relatively fast non-standard rates.
|
#
26f370d0 |
|
20-Sep-2012 |
Kevin Lo <kevlo@FreeBSD.org> |
Fix typo: s/protocl/protocol
|
#
3426950e |
|
05-Aug-2012 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
Update the list of devices supported by the FTDI driver. It might be that the wrong UART reference clock will be used for a few of the IDs. It is currently not possible to figure that out because the Linux FTDI driver detects this run-time and not compile time based on the bcdDevice field of the USB device descriptor. Some of the ID's in usbdevs are not sorted according to the product ID value. Please feel free to fix this. I'm out of my xemacs magic today. This syncronises us with the linux kernel at kernel.org (HEAD). MFC after: 2 weeks
|
#
f3b44896 |
|
18-Jun-2012 |
Marius Strobl <marius@FreeBSD.org> |
Refine r237102 a bit: - Anounce JTAG interfaces deliberately skipped. - Bring back empty lines too eagerly removed. MFC after: 3 days
|
#
a589806b |
|
14-Jun-2012 |
Marius Strobl <marius@FreeBSD.org> |
- Add support for the FT2232 based egnite Turtelizer 2 JTAG/RS232 Adapter. This includes adding support for skipping FTDI interfaces used for JTAG leaving them for userland and just attaching to the RS232 half, similarly to how the corresponding Linux drivers handles these kind of adapters. While at it, sort uftdi_devs and return BUS_PROBE_SPECIFIC (because uftdi_probe() alters the instance variables for better or worse as do other probe routines of USB drivers) instead of 0. - Remove duplicated entries for BeagleBone. - Use DEVMETHOD_END. - Use NULL instead of 0 for pointers. - Remove some stray lines. MFC after: 3 days
|
#
a7d5f7eb |
|
19-Oct-2010 |
Jamie Gritton <jamie@FreeBSD.org> |
A new jail(8) with a configuration file, to replace the work currently done by /etc/rc.d/jail.
|
#
02ac6454 |
|
23-Feb-2009 |
Andrew Thompson <thompsa@FreeBSD.org> |
Move the new USB stack into its new home.
|