I'm also seeing the regression reported by @richard (#42). In particular, the software for the Syscomp CGR-101 isn't seeing the scope on a 64 bit Ubuntu Maverick 10.10. Building the latest version of the ftdio_sio driver from the 2.6.35-8 linux tree didn't fix the bug, but porting the version @tz (#7) found to the new kernel fixed the issue. I've attached the ported version of the older driver for those who need a fix now. The install instructions are the same as before:
To install:
1) open a terminal window
2) install the latest kernel headers:
# sudo apt-get install linux-headers-generic
3) download and uncompress the attached file ftdifix.backport.maverick.tar.gz
4) change to the directory where you uncompressed the file, e.g.
# cd ftdifix.backport.maverick
5) build the driver:
# make
6) install the driver
# sudo make install
Until this is fixed, you may have to repeat these steps each time you install a new version of the kernel.
This isn't a good long-term fix, however - there have been a lot of changes to the driver, many of which add support for new devices. The right fix is probably to do a bisection on the kernel checkins to find the one that broke this driver for this scenario, and then report the bug upstream (ideally with a patch). I'll start the process but I'm not sure how much time I'll be able to devote to it - if some else wants to give this a try, feel free.
I'm also seeing the regression reported by @richard (#42). In particular, the software for the Syscomp CGR-101 isn't seeing the scope on a 64 bit Ubuntu Maverick 10.10. Building the latest version of the ftdio_sio driver from the 2.6.35-8 linux tree didn't fix the bug, but porting the version @tz (#7) found to the new kernel fixed the issue. I've attached the ported version of the older driver for those who need a fix now. The install instructions are the same as before:
To install:
1) open a terminal window
2) install the latest kernel headers:
# sudo apt-get install linux-headers- generic
3) download and uncompress the attached file ftdifix. backport. maverick. tar.gz
4) change to the directory where you uncompressed the file, e.g.
# cd ftdifix. backport. maverick
5) build the driver:
# make
6) install the driver
# sudo make install
Until this is fixed, you may have to repeat these steps each time you install a new version of the kernel.
This isn't a good long-term fix, however - there have been a lot of changes to the driver, many of which add support for new devices. The right fix is probably to do a bisection on the kernel checkins to find the one that broke this driver for this scenario, and then report the bug upstream (ideally with a patch). I'll start the process but I'm not sure how much time I'll be able to devote to it - if some else wants to give this a try, feel free.