On Mon, 2013-02-04 at 22:05 +0100, CeDeROM wrote: > On Mon, Feb 4, 2013 at 9:06 PM, Ian Lepore <i...@freebsd.org> wrote: > > FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 and > > 10; I use it all the time. Sometimes aftermarket vendors who use FTDI's > > parts program different vendor/product info and IDs have to be added to > > code to recognize them, that's the only trouble one usually encounters. > > I also want to use my KT-LINK multipurpose low-level embedded access > multitool based on FT2232H with RS232 port and I was worried there is > no driver - right now I will add the PID and recompile sources to see > if it works - happy to catch this thread :-) > > Some questions as you Ian seem to already have experience with this devices: > 1. Is it possible to compile only uftdi driver and load it into > existing kernel that have this driver compiled-in so I don't have to > recompile whole kernel and all of the modules? > 2. Is it possible to pass VID/PID and/or RS232 channel as kernel > loadable option? This would again spare some build/runtime time for me > :-) > 3. Do you know a good method on kernel module testing other than > rebuilding/rebooting all the time? VirtualBox + USB Attach? > > Any hints appreciated! :-) > Tomek >
If you don't already have the right devices compiled in, just build the usb/ucom and usb/uftdi modules and kldload uftdi and you should be good to go. -- Ian _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
