2
I Use This!
Inactive

News

Analyzed 13 days ago. based on code collected 14 days ago.
Posted about 16 years ago by Jacob Moorman
I've gone ahead and moved libnifalcon to beta status. There's really not much point to optimizing more without some sort of testing, so now it's testing time. :) libusb-1.0 has been added to the library for linux usage. Lots of other changes, check the changelog for them.
Posted about 16 years ago by [email protected] (Kyle Machulis)
Released at Sun, 16 Nov 2008 20:32:27 GMT by kmachulisIncludes files: libnifalcon-1.0-beta-1.tar.gz (177453 bytes, 41 downloads to date)[Download] [Release Notes]
Posted about 16 years ago by [email protected]
Posted about 16 years ago by Sabrina
Posted about 16 years ago by Sabrina
Posted over 16 years ago by [email protected]
Posted over 16 years ago by Sabrina
Posted over 16 years ago by Sabrina
Posted over 16 years ago by [email protected] (Kyle Machulis)
In an effort to be as anal about the most boring parts of this driver as possible, I've added a libusb-1.0 based communications core for linux. It's by far the fastest and lightest weight of any of the communication cores, but unfortunately only ... [More] works on linux for the moment. libftdi still seems fine on os x, and ftd2xx will always be the default on windows.More information on libusb-1.0 is available at http://libusb.wiki.sourceforge.net/Libusb1.0The code is in the svn, and will be released as part of alpha 5. Which will hopefully be followed by beta 1. (0 comments) [Less]
Posted over 16 years ago by [email protected] (Kyle Machulis)
In an effort to be as anal about the most boring parts of this driver as possible, I've added a libusb-1.0 based communications core for linux. It's by far the fastest and lightest weight of any of the communication cores, but unfortunately only ... [More] works on linux for the moment. libftdi still seems fine on os x, and ftd2xx will always be the default on windows.More information on libusb-1.0 is available at http://libusb.wiki.sourceforge.net/Libusb1.0The code is in the svn, and will be released as part of alpha 5. Which will hopefully be followed by beta 1. (0 comments) [Less]