Recent changes to FAQ

FAQ modified by Miso kopera

Miso kopera — Sat, 27 Apr 2013 19:20:00 -0000

--- v5
+++ v6
@@ -2,7 +2,7 @@
 ----

 Q: What OS are supported? 
-A: This "wrapper" is based on [libFTDI](http://www.intra2net.com/en/developer/libftdi/download.php) and it is based on libUSB. So probably only linux/unix are/will be supported. 
+A: At the moment only linux. This "wrapper" is based on [libFTDI](http://www.intra2net.com/en/developer/libftdi/download.php) and it is based on libUSB. So probably others may be supported in the future. 

 Q: When will be implemented missing function like "ftdi_write_eeprom".. 
 A: Well, I can add them but I need some cheap device on which I can test it. At the moment I have only quite expensive one and I don't want to destroy it :-)

FAQ modified by Miso kopera

Miso kopera — Thu, 25 Apr 2013 17:36:53 -0000

--- v4
+++ v5
@@ -19,7 +19,7 @@

 *SUBSYSTEM=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", MODE="0664", GROUP="plugdev"*

-This say "users in plugdev group can access usb devices where idVendor is 0403 and idProduct is 6001". Then open terminal, type "dmesg" and find log for your device. It should be something this: 
+This say "users in plugdev group can access usb devices where idVendor is 0403 and idProduct is 6001". Then open terminal, type "dmesg" and find log for your device. It should be something like: 

 *\[ 661.375369\] usb 5-1: New USB device found, idVendor=0403, idProduct=6001*

FAQ modified by Miso kopera

Miso kopera — Wed, 24 Apr 2013 08:02:48 -0000

--- v3
+++ v4
@@ -1,4 +1,5 @@
 FAQ:
+----

 Q: What OS are supported? 
 A: This "wrapper" is based on [libFTDI](http://www.intra2net.com/en/developer/libftdi/download.php) and it is based on libUSB. So probably only linux/unix are/will be supported.

FAQ modified by Miso kopera

Miso kopera — Wed, 24 Apr 2013 07:50:50 -0000

--- v2
+++ v3
@@ -20,6 +20,6 @@

 This say "users in plugdev group can access usb devices where idVendor is 0403 and idProduct is 6001". Then open terminal, type "dmesg" and find log for your device. It should be something this: 

-*[ 661.375369] usb 5-1: New USB device found, idVendor=0403, idProduct=6001*
+*\[ 661.375369\] usb 5-1: New USB device found, idVendor=0403, idProduct=6001*

 match if the idVendor and idProduct are the same as in "99-libftdi.rules". There is a "bug" in "libftdi.x86_64" package that use ATTRS{idProduct}=="6010" instead of "6001". What is also ftdi chipset device but may not be what you have

FAQ modified by Miso kopera

Miso kopera — Wed, 24 Apr 2013 07:49:49 -0000

--- v1
+++ v2
@@ -1 +1,25 @@
-HELLO faq
+FAQ:
+
+Q: What OS are supported? 
+A: This "wrapper" is based on [libFTDI](http://www.intra2net.com/en/developer/libftdi/download.php) and it is based on libUSB. So probably only linux/unix are/will be supported. 
+
+Q: When will be implemented missing function like "ftdi_write_eeprom".. 
+A: Well, I can add them but I need some cheap device on which I can test it. At the moment I have only quite expensive one and I don't want to destroy it :-) 
+
+Q: How to install libFTDI? 
+A: Depending on your distribution. But generaly you should use package manager to find and install it.
+For 64 bit Fedora linux you can use "yum install libftdi.x86_64".
+
+Q: I have installed libFTDI but I can't access device. What is wrong? 
+A: You probably don't have permision to access the USB device. Are you in the right group (plugdev in Fedora linux)? 
+
+Q: Yes I'm. But I still have problems to acccess it. 
+A: Check udev rules. For fedora: go to "/etc/udev/rules.d", search for file "99-libftdi.rules" It should contains line like this:
+
+*SUBSYSTEM=="usb", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", MODE="0664", GROUP="plugdev"*
+
+This say "users in plugdev group can access usb devices where idVendor is 0403 and idProduct is 6001". Then open terminal, type "dmesg" and find log for your device. It should be something this: 
+
+*[ 661.375369] usb 5-1: New USB device found, idVendor=0403, idProduct=6001*
+
+match if the idVendor and idProduct are the same as in "99-libftdi.rules". There is a "bug" in "libftdi.x86_64" package that use ATTRS{idProduct}=="6010" instead of "6001". What is also ftdi chipset device but may not be what you have

FAQ modified by Miso kopera

Miso kopera — Wed, 24 Apr 2013 07:22:21 -0000

HELLO faq