ftdi-usb-sio-devel Mailing List for FTDI USB Serial Converter Driver (Page 8)
Brought to you by:
bryder
You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
(11) |
Nov
(25) |
Dec
(25) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(16) |
Feb
(98) |
Mar
(46) |
Apr
(35) |
May
(15) |
Jun
(73) |
Jul
(49) |
Aug
(28) |
Sep
(16) |
Oct
(24) |
Nov
(36) |
Dec
(37) |
2004 |
Jan
(40) |
Feb
(21) |
Mar
(32) |
Apr
(27) |
May
(32) |
Jun
(48) |
Jul
(62) |
Aug
(22) |
Sep
(13) |
Oct
(14) |
Nov
(24) |
Dec
(26) |
2005 |
Jan
(15) |
Feb
(14) |
Mar
(31) |
Apr
(19) |
May
(23) |
Jun
(76) |
Jul
(64) |
Aug
(68) |
Sep
(30) |
Oct
(11) |
Nov
(20) |
Dec
(14) |
2006 |
Jan
(7) |
Feb
(5) |
Mar
(10) |
Apr
(10) |
May
(17) |
Jun
(13) |
Jul
(9) |
Aug
(8) |
Sep
(27) |
Oct
(54) |
Nov
(38) |
Dec
(31) |
2007 |
Jan
(21) |
Feb
(4) |
Mar
(3) |
Apr
(3) |
May
(3) |
Jun
(2) |
Jul
(2) |
Aug
(11) |
Sep
(4) |
Oct
(2) |
Nov
(1) |
Dec
|
2008 |
Jan
(2) |
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
(8) |
Sep
|
Oct
(3) |
Nov
(6) |
Dec
(2) |
2009 |
Jan
(14) |
Feb
(3) |
Mar
(4) |
Apr
|
May
(1) |
Jun
(2) |
Jul
(5) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
(5) |
Dec
(6) |
2010 |
Jan
(3) |
Feb
(5) |
Mar
(2) |
Apr
(4) |
May
(1) |
Jun
(7) |
Jul
(7) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
(15) |
Dec
(1) |
2011 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(2) |
2012 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
(1) |
Mar
|
Apr
(9) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
(3) |
2015 |
Jan
|
Feb
|
Mar
|
Apr
(6) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
(9) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: John H. <mis...@gm...> - 2007-08-12 07:55:36
|
This was broken a while back with fedora 7's kernel, and someone told me a patch I could try, but now it is broken again in Linux home 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 i686 i386 GNU/Linux What to do? Can I at least patch or do something to where it works again for now? > > lircd: tty_setdtr: ioctl(TIOCMGET) failed > > lircd: tty_setdtr: Bad address > This is a problem of the ftdi_sio driver. > ftdi_tiocmget is obviously not implemented for your hardware. > You should report this to the driver authors. > > Christoph -- ./lircd -H usb_uirt_raw -d /dev/ttyUSB0 -n -D1 lircd: started server socket lircd: parsing remote lircd: parsing DISH_1 remote lircd: parsing remote lircd: parsing PinnacleSysRemote remote lircd: config file read lircd: lircd(usb_uirt_raw) ready lircd: registering local client lircd: accepted new client on /dev/lircd lircd: writing command 23 lircd: 23 dd lircd: wrote 2 lircd: cmd res 3: lircd: 09 05 01 lircd: lircd: uirt2_raw: checksum error lircd: uirt2: detection of uirt2 failed lircd: uirt2: trying to detect newer uirt firmware lircd: writing command 23 lircd: 23 dd lircd: wrote 2 lircd: cmd res 8: lircd: 09 05 01 01 1a 03 04 cf lircd: lircd: uirt2_raw: UIRT version 0905 ok lircd: writing command 21 lircd: 21 df lircd: wrote 2 lircd: cmd res 1: lircd: 21 lircd: lircd: tty_setdtr: ioctl(TIOCMGET) failed lircd: tty_setdtr: Bad address lircd: uirt2_raw: could not set DTR lircd: tty_setdtr: ioctl(TIOCMGET) failed lircd: tty_setdtr: Bad address lircd: caught signal Terminated On 12 Aug 2007 09:40:00 +0200, Christoph Bartelmus <li...@ba...> wrote: > Hi John, > > on 12 Aug 07 at 02:22, you wrote: > [...] > > lircd: tty_setdtr: ioctl(TIOCMGET) failed > > lircd: tty_setdtr: Bad address > > This is a problem of the ftdi_sio driver. > ftdi_tiocmget is obviously not implemented for your hardware. > You should report this to the driver authors. > > Christoph > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > |
From: Matthew P. <mp...@gm...> - 2007-07-13 23:22:18
|
Is there a way to receive per byte parity errors using this driver? Currently it looks like it will show parity errors for every byte received if any of the bytes in the transmission contain parity errors. I am trying to use the device with a protocol that utilizes mark and space parity to set the wakeup bit for the first byte on each incoming packet. Thanks, Matt Peppin |
From: nicolas r. <nic...@ya...> - 2007-07-10 16:41:29
|
Hi, I read this thread : http://sourceforge.net/mailarchive/message.php?msg_id=200408231132.56743.abbotti%40mev.co.uk and succefully create a ttyUSB0 serial port working at 31250 (on the B38400). But how to configure that port in order to be recognized as a midi device by my ubuntu FF box ? I know this question isn't direcly related to the ftdi dev list, but I'm sure there is some linux gurus that already configure that ? Nicolas Nicolas ROLLAND 9 rue de la Grande Armée 13001 MARSEILLE 0491083231 nic...@ya... _____________________________________________________________________________ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail |
From: Peter S. <sht...@sp...> - 2007-06-05 07:31:31
|
I Had the same problem. In fact when driver is cleaned up in version 1.4.3 the quirks for USB-UIRT and HE-TIRA1 are executed before common initialization and that's why they writes to pointer which points to NULL. I have written this patch in order to get these devices to work. I have USB-UIRT and some other device and both of them are using driver ftdi_sio. With this patch both devices are working perfectly. I have no HE-TIRA1 to see if patch works for that device. If you find it useful please forward it to kernel maintainer for this driver. Regards! |
From: John H. <mis...@gm...> - 2007-06-02 03:32:10
|
help? I've been using this module successfully with fc6 for months with usb-uirt. Upgraded to f7 on my dell e510 and it says the following... Linux home 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 i686 i386 GNU/Linux drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB Serial Device ftdi_sio 3-2:1.0: FTDI USB Serial Device converter detected BUG: unable to handle kernel NULL pointer dereference at virtual address 00000014 printing eip: f8a1740a *pde = 00000000 Oops: 0002 [#1] SMP last sysfs file: /devices/pci0000:00/0000:00:1d.7/usb5/idVendor Modules linked in: ftdi_sio bluetooth snd_seq snd_ac97_codec usblp v4l1_compat fw_core snd_rawmidi sr_mod snd_pcm_oss snd_mixer_oss ac97_bus snd_util_mem usbserial e100 serio_raw snd_seq_device snd_hwdep snd_pcm emu10k1_gp cdrom mii snd_timer gameport snd soundcore iTCO_wdt snd_page_alloc i2c_i801 iTCO_vendor_support pcspkr i2c_core floppy sg joydev usb_storage ata_piix ata_generic libata sd_mod scsi_mod ext3 jbd mbcache ehci_hcd ohci_hcd uhci_hcd CPU: 0 EIP: 0060:[<f8a1740a>] Not tainted VLI EFLAGS: 00010246 (2.6.21-1.3194.fc7 #1) EIP is at ftdi_USB_UIRT_setup+0x34/0x4e [ftdi_sio] eax: 00000000 ebx: f583f400 ecx: f8a17b34 edx: f8a173d6 esi: f8a1dae0 edi: 00000040 ebp: f8a1dae0 esp: f582acdc ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068 Process modprobe (pid: 935, ti=f582a000 task=f5913150 task.ti=f582a000) Stack: f791e464 00000246 f598fb00 f5e823c0 f8a160b5 f898690a f898855b f8a18f6f f5ea06d0 f8a194fa f5ea0600 f5ea4800 f8a1dae0 00000000 00000000 00000001 00000001 f583f400 00000000 c1806d60 00000001 00000001 00000001 00000000 Call Trace: [<f8a160b5>] ftdi_sio_attach+0xf/0x12 [ftdi_sio] [<f898690a>] usb_serial_probe+0x97b/0xdd1 [usbserial] [<c042e748>] lock_timer_base+0x19/0x35 [<c042e7a8>] try_to_del_timer_sync+0x44/0x4a [<c05692c8>] usb_resume_both+0xa1/0xb7 [<c056947c>] usb_autopm_do_device+0xb3/0xbd [<c04ad4dd>] sysfs_create_link+0x128/0x13f [<c0568fd2>] usb_match_one_id+0x1c/0x71 [<c0569d2d>] usb_probe_interface+0x81/0xb2 [<c05529ab>] really_probe+0xc6/0x14f [<c0552a78>] driver_probe_device+0x44/0xa5 [<c0552b72>] __driver_attach+0x0/0xa5 [<c0552be2>] __driver_attach+0x70/0xa5 [<c0551ffb>] bus_for_each_dev+0x37/0x59 [<c055282a>] driver_attach+0x16/0x18 [<c0552b72>] __driver_attach+0x0/0xa5 [<c05522ad>] bus_add_driver+0x5e/0x15f [<c056985c>] usb_register_driver+0x6d/0xd4 [<f89857b5>] usb_serial_register+0x1ed/0x1f6 [usbserial] [<f8806091>] ftdi_init+0x91/0xbe [ftdi_sio] [<c04432e4>] sys_init_module+0x16c3/0x17fa [<c04755f8>] do_sync_read+0xc7/0x10a [<c0468484>] do_mmap_pgoff+0x593/0x6f3 [<c05507e5>] device_remove_file+0x0/0x25 [<c0475531>] do_sync_read+0x0/0x10a [<c0475e85>] vfs_read+0xa6/0x152 [<c0404f70>] syscall_call+0x7/0xb ======================= Code: ee a1 f8 00 74 1c c7 44 24 08 a4 86 a1 f8 c7 44 24 04 b7 88 a1 f8 c7 04 24 d5 88 a1 f8 e8 49 03 a1 c7 8b 43 14 8b 80 8c 01 00 00 <83> 48 14 30 c7 40 08 4d 00 00 00 c7 80 80 00 00 00 0f 00 00 00 EIP: [<f8a1740a>] ftdi_USB_UIRT_setup+0x34/0x4e [ftdi_sio] SS:ESP 0068:f582acdc |
From: Diego R. F. <kat...@gm...> - 2007-05-17 01:30:03
|
Working platform Epia-CN mini-ITX - with Via VT8237R+ chipset thanks again On 5/16/07, Diego Rodrigues Ferreira <kat...@gm...> wrote: > > Hi Everyone! > > I am having trouble accessing FTDI245 with the defaults configurations > used on other LINUX distributions. > Using Mandriva 2007 Spring, kernel 2.6.17-13mdv (ftdi_sio built-in). > > What I have done until now: > > - cp libftd2xx.so.0.4.12 /usr/local/lib > - ln -s libftd2xx.so.0.4.12 /usr/local/lib/libftd2xx.so > - ln -s libftd2xx.so.0.4.12 /usr/lib/libftd2xx.so > - ln -s libftd2xx.so.0.4.12 /usr/local/lib/libftd2xx.so.0 > - ln -s libftd2xx.so.0.4.12 /usr/lib/libftd2xx.so.0 > - Add the following line to /etc/fstab: > none /proc/bus/usb usbfs defaults,mode=0666 0 0 (devmode=0666 does not > work either) > - mount -a > - connected the device to usb port > - with lsusb I can visualize the device connected and when listing > /proc/bus/usb/devices, It recognizes the device with > VID/PID/Serial/Description fields all OK! but no driver!? => Driver=(none) > - Finally run the test program, with the following FTD2XX calls: > > DWORD *numDevs; > FT_STATUS ftStatus = FT_SetVIDPID(VID, PID); > if (ftStatus != FT_OK) > { > return ftStatus; > } > ftStatus=AQUSB_INVALID_PARAMETER; > ftStatus=FT_ListDevices(numDevs,NULL,FT_LIST_NUMBER_ONLY); > if (ftStatus != FT_OK) > { > return ftStatus; } > return numDevs; > > - This returns 0 devices! > > - Researching the system, I could notice that modprobe.alias and > modprobe.usbmap sets driver for PID/VID. So I set PID/VID pointing to > ftdi_sio also. > > - running again the test program, the same error! And still, the driver is > not recognized in /proc/bus/usb/devices. > > PS: The device is externally powered (not through USB). > > Any tips? > > > |
From: Diego R. F. <kat...@gm...> - 2007-05-17 01:24:57
|
Hi Everyone! I am having trouble accessing FTDI245 with the defaults configurations used on other LINUX distributions. Using Mandriva 2007 Spring, kernel 2.6.17-13mdv (ftdi_sio built-in). What I have done until now: - cp libftd2xx.so.0.4.12 /usr/local/lib - ln -s libftd2xx.so.0.4.12 /usr/local/lib/libftd2xx.so - ln -s libftd2xx.so.0.4.12 /usr/lib/libftd2xx.so - ln -s libftd2xx.so.0.4.12 /usr/local/lib/libftd2xx.so.0 - ln -s libftd2xx.so.0.4.12 /usr/lib/libftd2xx.so.0 - Add the following line to /etc/fstab: none /proc/bus/usb usbfs defaults,mode=0666 0 0 (devmode=0666 does not work either) - mount -a - connected the device to usb port - with lsusb I can visualize the device connected and when listing /proc/bus/usb/devices, It recognizes the device with VID/PID/Serial/Description fields all OK! but no driver!? => Driver=(none) - Finally run the test program, with the following FTD2XX calls: DWORD *numDevs; FT_STATUS ftStatus = FT_SetVIDPID(VID, PID); if (ftStatus != FT_OK) { return ftStatus; } ftStatus=AQUSB_INVALID_PARAMETER; ftStatus=FT_ListDevices(numDevs,NULL,FT_LIST_NUMBER_ONLY); if (ftStatus != FT_OK) { return ftStatus; } return numDevs; - This returns 0 devices! - Researching the system, I could notice that modprobe.alias and modprobe.usbmap sets driver for PID/VID. So I set PID/VID pointing to ftdi_sio also. - running again the test program, the same error! And still, the driver is not recognized in /proc/bus/usb/devices. PS: The device is externally powered (not through USB). Any tips? |
From: Derek S. <ds...@cs...> - 2007-05-08 19:54:47
|
Hi, I have a device with a FT232 USB-serial converter that requires a non-standard baud rate of 250kbaud. I am able to open the device and configure it using standard baud rates, but have not been successful in configuring it for the required 250kbaud. The project webpage (http://ftdi-usb-sio.sourceforge.net/) indicates there are ways to set non-standard baudrates, but none of them have worked for me. The approaches listed and the problems I have encountered are as follows: The first suggestion is to "set tty->termios->c_cflag speed to B38400 and then set your real speed in tty->alt_speed". I have not been able find a way to access to the tty structure (tty_struct) to set the "alt_speed" member variable. I found references to a TIOCTTYGSTRUCT ioctl to retrieve a pointer to the tty_struct, but the #define for this is now commented out in /usr/include/asm/ioctls.h and a comment indicates it is for debugging only. I found a reference in the Linux kernel archives suggesting that this ioctl was to be removed. Also, I have not been able to find the header file for "tty_struct" in /usr/include/linux (the kernel source has it in a file called "tty.h"). Is there another way to set "alt_speed"? The second suggestion is to set a custom divisor in the termios structure. However, there is no integer divisor that gives me the required baud rate (even with the various different baud_base settings of HI, VHI, SHI, or WARP). The only other solutions seem cheesy: recompile the driver with the custom buad rate coded in, or perhaps change the crystal frequency in the attached device so that it scales to a standard baud rate... Any suggestions would be appreciated. If there is no elegant way to set non-standard baud rates, could one be added? thanks, Derek |
From: Bill R. <bil...@gm...> - 2007-04-02 19:37:40
|
HI All, You should be able to submit your patch directly to the linux-usb-development list. You should be able to see the details at: http://ftdi-usb-sio.sourceforge.net/ send the patch to mailto:lin...@li... If you like directly send me an email and I'll at least make sure it doesn't break anything obvious. I don't actively maintain the driver anymore but I dabble every so often. On 4/3/07, Allen, Matthew <al...@ul...> wrote: > > I'm not sure anyone is actually doing anything with the driver at this > point. I've seen no real traffic across this list since I joined. Just > questions that are unanswered. > > Is anyone actually maintaining the driver anymore? > > > |
From: Allen, M. <al...@ul...> - 2007-04-02 12:51:56
|
I'm not sure anyone is actually doing anything with the driver at this point. I've seen no real traffic across this list since I joined. Just questions that are unanswered. Is anyone actually maintaining the driver anymore? -----Original Message----- From: ftd...@li... [mailto:ftd...@li...] On Behalf Of r.k...@ya... Sent: Saturday, March 31, 2007 7:52 PM To: ftd...@li... Subject: [Ftdi-usb-sio-devel] stick parity hi, I noticed that this driver (as unfortunately nearly all usb-serial-drivers) does not support mark/space parity, although the chip supports it. And in 2003, someone already posted a patch on this mailinglist to add this feature. (http://sourceforge.net/mailarchive/message.php?msg_id=3D20030619095616.G= B 26200%40ased.x.cce.cz) Is there any reason, why this patch wasn't added? regards, Roland Koebler ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDE V _______________________________________________ Ftdi-usb-sio-devel mailing list Ftd...@li... https://lists.sourceforge.net/lists/listinfo/ftdi-usb-sio-devel |
From: Boris Z. <bs_...@ya...> - 2007-04-01 13:50:00
|
Hello, Well I've found how I could possibly reduce latency: writing to latency_timer file under sysfs. BUT reading/writing this file crashes the kernel. It happens because these lines struct usb_serial_port *port = to_usb_serial_port(dev); struct ftdi_private *priv = usb_get_serial_port_data(port); in all sysfs attribute callbacks produce wrong pointer to usb_serial_port, because "struct device" pointer passed to device_create_file in "create_sysfs_attrs" doesn't points to "struct device" embedded in usb_serial_port.(In my case above "priv" pointer turned out to be NULL and was trapped by kernel producing Oops, but kernel could crash even earlier while dereferencing "port" pointer). This happens with FC6's kernel 2.6.20. best regards, Boris Boris Zingerman <bs_...@ya...> wrote: Hello, I have some device that uses ftdi chip to communicate with host computer. I set low latency flag in this manner struct serial_struct serial_info; ioctl(m_fd, TIOCGSERIAL, &serial_info) ; serial_info.flags |= ASYNC_LOW_LATENCY; ioctl(m_fd, TIOCSSERIAL, &serial_info) ; setserial reports that low_latency flag is indeed set, but round-trip time for short commands is about 15 msec. This device has also regular RS232 input and the same code produces 1.5msec roundtrip time for the same commands (ten times faster !!). Is low_latency flag has no effect on ftdi_sio driver ? If so how can I improve latency. Best regards, Boris Zingerman --------------------------------- Bored stiff? Loosen up... Download and play hundreds of games for free on Yahoo! Games. --------------------------------- 8:00? 8:25? 8:40? Find a flick in no time with theYahoo! Search movie showtime shortcut. |
From: <r.k...@ya...> - 2007-03-31 23:52:06
|
hi, I noticed that this driver (as unfortunately nearly all usb-serial-drivers) does not support mark/space parity, although the chip supports it. And in 2003, someone already posted a patch on this mailinglist to add this feature. (http://sourceforge.net/mailarchive/message.php?msg_id=20030619095616.GB26200%40ased.x.cce.cz) Is there any reason, why this patch wasn't added? regards, Roland Koebler |
From: Boris Z. <bs_...@ya...> - 2007-03-29 17:14:50
|
Hello, I have some device that uses ftdi chip to communicate with host computer. I set low latency flag in this manner struct serial_struct serial_info; ioctl(m_fd, TIOCGSERIAL, &serial_info) ; serial_info.flags |= ASYNC_LOW_LATENCY; ioctl(m_fd, TIOCSSERIAL, &serial_info) ; setserial reports that low_latency flag is indeed set, but round-trip time for short commands is about 15 msec. This device has also regular RS232 input and the same code produces 1.5msec roundtrip time for the same commands (ten times faster !!). Is low_latency flag has no effect on ftdi_sio driver ? If so how can I improve latency. Best regards, Boris Zingerman --------------------------------- Bored stiff? Loosen up... Download and play hundreds of games for free on Yahoo! Games. |
From: Edward D. <Ed....@no...> - 2007-03-15 13:24:07
|
Hello, I work for NOAA (National Oceanic and Atmospheric Administration) in Oak Ridge, TN and we've got a multi-port serial device (ByteRunner USB-8COMi-RM-120V) URL: http://www.byterunner.com/byterunner/product=name:USB-8COMi/title=USB+to+8+Port+Serial+Adapters+(RS422,+RS485) with the FTDI chipset running with the latest version of Fedora Core 6. I don't know the exact kernel, but it is at least 2.6.16. We have been having a few problems about which I would like to ask your opinion. I'll start by outlining the serial loading of each serial port and describing the problems we are having, followed by some questions. Hopefully you can give some insight as to what might be going on. Below are the devices and a description of the amount of serial data and the timing of the data we receive: Device 1 - 35 bytes every 20 ms, baud rate 460800, RS-422 Device 2 - 35 bytes every 20 ms, baud rate 460800, RS-422 Device 3 - 26 bytes every 50 ms, baud rate 115200, RS-232 Device 4 - 12 bytes every 20 ms, baud rate 19200, RS-232 Device 5 - 36 bytes every 50 ms, baud rate 9600, RS-232 Device 6 - 318 bytes every 100 ms, baud rate 115200, RS-232 Device 7 - 238 bytes at 00 ms, 168 bytes every 100 ms until next even second, baud rate 115200, RS-232 Device 8 - 56 bytes every 100 ms, baud rate 115200, RS-232 Here is another look at the sum total of the data, as a function of time: 00 ms - 756 bytes 20 ms - 82 bytes 40 ms - 82 bytes 50 ms - 62 bytes 60 ms - 82 bytes 80 ms - 82 bytes 100 ms - 682 bytes 120 ms - 82 bytes 140 ms - 82 bytes 150 ms - 62 bytes 160 ms - 82 bytes 180 ms - 82 bytes 200 ms - 682 bytes ... and the pattern repeats until the next even second, when the 756 byte burst comes again. I have written c-code to gather data from each device and print it to the screen as a test to see if things are working. The devices are tested individually with separate test programs and once everything is working I run a multi-threaded program to simultaneously collect data from each device and store it to a common data file. I am using an intermediate serial library (SIO from Tim Hudson, http://svn.gnumonks.org/branches/scez-ng/sio/) to provide linkage between the serial drivers and my application code. One other key point is that the traffic is all one-way, receive only. I don't send any data to these devices so the computer just sits back and listens to each device and archives data. Now for the problems... The test code for the first 5 devices works fine when plugged into the USB serial ports. But devices 6, 7, and 8 fail intermittently when plugged into the USB serial ports. In the case of device 7, data flow is fine for several seconds, followed by fairly regular checksum errors, then the program terminates with a segmentation fault error. I can plug the same device into the built-in serial port on the computer (/dev/ttyS0) and the test code runs flawlessly, without the CRC errors or the segmentation fault. I get very lethargic performance with device 8 when it is plugged into the USB serial ports (but at least no segmentation fault!), but flawless performance when plugged into the built-in serial port (again, same test code in both cases). My questions: Are there any differences between the drivers for the "built-in" serial port (/dev/ttyS0) and the FTDI USB devices? I'm thinking about buffer sizes in particular. Also, are there any "tweaks" I can do to the buffer sizes for the USB FTDI driver that might help my particular situation? I'm thinking about handling the serial burst loads that will appear every second and 1/10 second when the full system is up and running. I also noticed some flags in the FTDI serial structure regarding throttling and non-throttling of serial ports. Could there be anything there that might degrade (or improve?) performance? I'm not sure whether the USB interface for this device is 1.0, 1.1, or 2.0, or whether it would make a difference. At this point, any suggestions would be appreciated! Thank you for your time and for developing the FTDI serial drivers! Best regards, Ed Dumas NOAA/ATDD |
From: Craig V. D. <cr...@yo...> - 2007-02-09 22:59:44
|
I am using ftdi_sio with a DLP-2232PB-G protoboard that uses an FT2232C chip. The protoboard includes a PIC16F877A processor with which I am communicating. When I first tried using ftdi_sio, the responses from the device never reached my application code. read() just hung. I traced the problem down to the fact that the protoboard responses did not terminate with newline characters and therefore the buffer transfer from kernel to application was not made. All responses are preceded by a pair of status bytes, the second of which is identified in ftdi_sio.h as: * Byte 1: Line Status * * Offset Description * B0 Data Ready (DR) * B1 Overrun Error (OE) * B2 Parity Error (PE) * B3 Framing Error (FE) * B4 Break Interrupt (BI) * B5 Transmitter Holding Register (THRE) * B6 Transmitter Empty (TEMT) * B7 Error in RCVR FIFO * */ #define FTDI_RS0_CTS (1 << 4) #define FTDI_RS0_DSR (1 << 5) #define FTDI_RS0_RI (1 << 6) #define FTDI_RS0_RLSD (1 << 7) #define FTDI_RS_DR 1 #define FTDI_RS_OE (1<<1) #define FTDI_RS_PE (1<<2) #define FTDI_RS_FE (1<<3) #define FTDI_RS_BI (1<<4) #define FTDI_RS_THRE (1<<5) #define FTDI_RS_TEMT (1<<6) #define FTDI_RS_FIFO (1<<7) I solved my problem by using the FTDI_RS_TEMT bit to tell me if the received data was complete. If it was complete and did not already end in a 0x0A, I added a 0x0A to the data stream as it was processed by ftdi_process_read() in ftdi_sio.c. (Are there some devices that end with just a 0x0D?) The fix is shown here: http://yosemitefoothills.com/Electronics/ftdi_sio.c_fix.html Obviously, one can insist that all devices end their messages with a newline character, but that seems to be completely redundant to the status bytes that already precede the line. The newline character therefore would reduce throughput without adding anything new. With all that background, I am asking: Is my fix is reasonable to apply to the ftdi_sio code? Will any other devices benefit from it? Will it cause trouble for any FTDI-based devices? This may be related to the parity error problem mentioned in the lines following my fix. Maybe that can also be solved now. Craig |
From: Allen, M. <al...@ul...> - 2007-02-09 14:56:08
|
Me from my normal work email: I've narrowed down what the problem is. When I modprobe ftdi_sio with "vendor=3D0x16ff and PID=3D0x0080"(which are the correct VID and PID for = our new device) it works just fine. So it seems that something is going wrong with the probing or the hand off with the serial subsystem. -----Original Message----- From: ftd...@li... [mailto:ftd...@li...] On Behalf Of Matt Allen Sent: Thursday, February 08, 2007 4:45 PM To: ftd...@li... Subject: [Ftdi-usb-sio-devel] New FTDI driver for a FT232R module. Hello, I've recently been hired to work on a "custom" driver for a USB-Serial device that we have here. The device is using the TTL-232R USB - TTL Level Serial converter with the FT232RQ chipset. We're using linux 2.6.16 for the development platform. We've got our own VID and PID but I'm having problems adapting the FTDI_SIO drivers found in the 2.6.16 kernel to work. When I plug in the new serial device it seems like the USB subsystem gets the device and it never gets moved up to the usb-serial or to even further up the FTDI driver. The last messages in /var/log/messages that I'm getting are: Feb 8 16:06:24 r88882-pos02 kernel: usb 6-1: new full speed USB device using uhci_hcd and address 7 Feb 8 16:06:24 r88882-pos02 kernel: usb 6-1: new device found, idVendor=3D16ff, idProduct=3D0080 Feb 8 16:06:24 r88882-pos02 kernel: usb 6-1: new device strings: Mfr=3D1, Product=3D2, SerialNumber=3D3 Feb 8 16:06:24 r88882-pos02 kernel: usb 6-1: Product: UTC PD1200 Feb 8 16:06:24 r88882-pos02 kernel: usb 6-1: Manufacturer: UTC Feb 8 16:06:24 r88882-pos02 kernel: usb 6-1: SerialNumber: 000001 Feb 8 16:06:24 r88882-pos02 kernel: usb 6-1: configuration #1 chosen from 1 choice I figure that it should mention something about usb-serial or the ftdi_sio modules but nothing. I checked to make sure they had been insmod'ed and the drivers are loaded. =20 ________________________________________________________________________ ____________ Looking for earth-friendly autos?=20 Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center. http://autos.yahoo.com/green_center/ ------------------------------------------------------------------------ - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D= 121642 _______________________________________________ Ftdi-usb-sio-devel mailing list Ftd...@li... https://lists.sourceforge.net/lists/listinfo/ftdi-usb-sio-devel |
From: Allen, M. <al...@ul...> - 2007-02-09 14:43:22
|
Testing email. I was getting bounced before. |
From: Matt A. <thr...@ya...> - 2007-02-08 21:45:34
|
Hello, Ive recently been hired to work on a custom driver for a USB-Serial device that we have here. The device is using the TTL-232R USB TTL Level Serial converter with the FT232RQ chipset. Were using linux 2.6.16 for the development platform. Weve got our own VID and PID but Im having problems adapting the FTDI_SIO drivers found in the 2.6.16 kernel to work. When I plug in the new serial device it seems like the USB subsystem gets the device and it never gets moved up to the usb-serial or to even further up the FTDI driver. The last messages in /var/log/messages that Im getting are: Feb 8 16:06:24 r88882-pos02 kernel: usb 6-1: new full speed USB device using uhci_hcd and address 7 Feb 8 16:06:24 r88882-pos02 kernel: usb 6-1: new device found, idVendor=16ff, idProduct=0080 Feb 8 16:06:24 r88882-pos02 kernel: usb 6-1: new device strings: Mfr=1, Product=2, SerialNumber=3 Feb 8 16:06:24 r88882-pos02 kernel: usb 6-1: Product: UTC PD1200 Feb 8 16:06:24 r88882-pos02 kernel: usb 6-1: Manufacturer: UTC Feb 8 16:06:24 r88882-pos02 kernel: usb 6-1: SerialNumber: 000001 Feb 8 16:06:24 r88882-pos02 kernel: usb 6-1: configuration #1 chosen from 1 choice I figure that it should mention something about usb-serial or the ftdi_sio modules but nothing. I checked to make sure they had been insmoded and the drivers are loaded. ____________________________________________________________________________________ Looking for earth-friendly autos? Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center. http://autos.yahoo.com/green_center/ |
<META HTTP-EQUIV=3d"=d2=e8=ef-=f1=ee=e4=e5=f0=e6=e8=ec=ee=e5" CONTENT=3d"= text/html; charset=3dwindows-1251"> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4=2e0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3d=d2=e8=ef-=f1=ee=e4=e5=f0=e6=e8=ec=ee=e5 content=3d"te= xt/html; charset=3dwindows-1251"> <META content=3d"MSHTML 6=2e00=2e2900=2e2802" name=3dGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3d#EAFFEA> <DIV><FONT face=3dArial size=3d2> <TABLE width=3d"100%" border=3d0> <TBODY> <TR> <TD class=3dshrift> <DIV align=3dcenter><STRONG><FONT color=3d#499300 size=3d+2>=d3=f7=e5= =e1=ed=fb=e9 =ea=f3=f0=f1: =cc=e5=e6=e4=f3=ed=e0=f0=ee=e4=ed=fb=e5 =f1=f2= =e0=ed=e4=e0=f0=f2=fb =f4=e8=ed=e0=ed=f1=ee=e2=ee=e9 =ee=f2=f7=e5=f2=ed=ee= =f1=f2=e8 =e8 =e1=f3=f5=e3=e0=eb=f2=e5=f0=f1=ea=ee=e3=ee =f3=f7=e5=f2=e0=2e= </FONT></STRONG></DIV></TD></TR> <TR> <TD> </TD></TR> <TR> <TD class=3dshrift> <DIV align=3djustify>=ce=e7=ed=e0=ea=ee=ec=eb=e5=ed=e8=e5 =f1 =ef=f0= =e8=ed=f6=e8=ef=e0=ec=e8 =f4=ee=f0=ec=e8=f0=ee=e2=e0=ed=e8=ff =f4=e8=ed=e0= =ed=f1=ee=e2=ee=e9=20 =ee=f2=f7=e5=f2=ed=ee=f1=f2=e8 =ef=ee =cc=d1=d4=ce (=cc=d1=c1=d3) =e8= =f4=ee=f0=ec=e0=ec=e8 =ef=f0=e5=e4=f1=f2=e0=e2=eb=e5=ed=e8=ff =ee=f2=f7=e5= =f2=ed=ee=f1=f2=e8=2e =cf=f0=e8=ee=e1=f0=e5=f2=e5=ed=e8=e5=20 =ef=f0=e0=ea=f2=e8=f7=e5=f1=ea=e8=f5 =ed=e0=e2=fb=ea=ee=e2 =f3=f7=e5= =f2=e0 =ee=f2=e4=e5=eb=fc=ed=fb=f5 =e2=e8=e4=ee=e2 =e0=ea=f2=e8=e2=ee=e2 = =e8 =ee=e1=ff=e7=e0=f2=e5=eb=fc=f1=f2=e2 =e2=20 =f1=ee=ee=f2=e2=e5=f2=f1=f2=e2=e8=e8 =f1 =cc=d1=c1=d3=2e =cf=f0=e8=ec= =e5=f0=fb =f1=ee=f1=f2=e0=e2=eb=e5=ed=e8=ff =f4=e8=ed=e0=ed=f1=ee=e2=fb=f5= =20 =ee=f2=f7=e5=f2=ee=e2=2e </DIV></TD></TR> <TR> <TD> </TD></TR> <TR> <TD> <TABLE borderColor=3d#499300 width=3d"100%" border=3d2> <TBODY> <TR> <TD width=3d"19%"><FONT color=3d#499300 size=3d2><STRONG><SPAN=20= class=3dshrift2>=c4=e0=f2=e0 =ef=f0=ee=e2=e5=e4=e5=ed=e8=ff:<= /SPAN></STRONG></FONT> </TD> <TD width=3d"81%"> <DIV align=3djustify><STRONG><SPAN class=3dshrift>16 - 17 =ff= =ed=e2=e0=f0=ff</SPAN></STRONG><SPAN class=3dshrift2><FONT size=3d2>, =ef= =ee 8=20 =e0=ea=e0=e4=e5=ec=e8=f7=e5=f1=ea=e8=f5 =f7=e0=f1=ee=e2 =e2 =e4= =e5=ed=fc, =f1 =ef=e5=f0=e5=f0=fb=e2=ee=ec =ed=e0 =ee=e1=e5=e4 =e8=20 =ea=ee=f4=e5-=e1=f0=fd=e9=ea=2e </FONT></SPAN></DIV></TD= ></TR> <TR> <TD class=3dshrift2><STRONG><FONT color=3d#499300><FONT size=3d= 2>=cc=e5=f1=f2=ee=20 =ef=f0=ee=e2=e5=e4=e5=ed=e8=ff:</FONT> </FONT></STRONG><= /TD> <TD class=3dshrift2><FONT size=3d2>=e3=2e =cc=ee=f1=ea=e2=e0</F= ONT> </TD></TR> <TR> <TD colspan=3d"2" class=3dshrift2><DIV align=3djustify><SPAN cl= ass=3dshrift2><FONT size=3d2>=cc=e5=f2=ee=e4=e8=f7=e5=f1=ea=e8=e5 =e8=20 = =f0=e0=e7=e4=e0=f2=ee=f7=ed=fb=e5 =ec=e0=f2=e5=f0=e8=e0=eb= =fb, =ee=e1=e5=e4=fb-=ea=ee=f4=e5-=e1=f0=fd=e9=ea=e8 =e2=ea=eb=fe=f7=e5=ed= =fb =e2=20 =f1=f2=ee=e8=ec=ee=f1=f2=fc=2e </FONT></SPAN></DIV><= /TD> </TR></TBODY></TABLE></TD></TR> <TR> <TD> <DIV align=3djustify><FONT size=3d2><SPAN class=3dshrift>=ca=f3=f0=f1= =ee=f0=e8=e5=ed=f2=e8=f0=ee=e2=e0=ed =ed=e0=20 =f0=f3=ea=ee=e2=ee=e4=e8=f2=e5=eb=e5=e9 =f4=e8=ed=e0=ed=f1=ee=e2=ee= -=fd=ea=ee=ed=ee=ec=e8=f7=e5=f1=ea=e8=f5 =f1=eb=f3=e6=e1 =ee=f0=e3=e0=ed=e8= =e7=e0=f6=e8=e9, =e3=eb=e0=e2=ed=fb=f5=20 =e1=f3=f5=e3=e0=eb=f2=e5=f0=ee=e2, =e0 =f2=e0=ea=e6=e5 =e2=f1=e5=f5= =e6=e5=eb=e0=fe=f9=e8=f5 =ef=ee=eb=f3=f7=e8=f2=fc =ef=f0=e0=ea=f2=e8=f7=e5= =f1=ea=e8=e5 =e7=ed=e0=ed=e8=ff =ef=ee=20 =ef=f0=e8=ec=e5=ed=e5=ed=e8=fe =cc=d1=d4=ce</SPAN>=2e </FONT><= /DIV></TD></TR> <TR> <TD class=3dshrift> <DIV align=3dcenter><STRONG><FONT color=3d#499300=20 size=3d+1>=d1=ee=e4=e5=f0=e6=e0=ed=e8=e5:</FONT><FONT size=3d+1>&nb= sp;</FONT></STRONG></DIV></TD></TR> <TR> <TD class=3dshrift2> <UL> <LI> <DIV align=3djustify><FONT size=3d2>=ce=e1=f9=e5=e5 =e7=ed=e0=ea=ee= =ec=f1=f2=e2=ee =f1 =cc=e5=e6=e4=f3=ed=e0=f0=ee=e4=ed=fb=ec=e8=20 =f1=f2=e0=ed=e4=e0=f0=f2=e0=ec=e8 =f4=e8=ed=e0=ed=f1=ee=e2=ee=e9 = =ee=f2=f7=e5=f2=ed=ee=f1=f2=e8 =e8 =e1=f3=f5=e3=e0=eb=f2=e5=f0=f1=ea=ee=e3= =ee =f3=f7=e5=f2=e0=2e =cf=f0=e8=ed=f6=e8=ef=fb=20 =f4=ee=f0=ec=e8=f0=ee=e2=e0=ed=e8=ff =f1=f2=e0=ed=e4=e0=f0=f2=ee=e2= =e8 =f1=f2=f0=f3=ea=f2=f3=f0=e0 =f1=f2=e0=ed=e4=e0=f0=f2=ee=e2=2e =d1=e8= =f1=f2=e5=ec=e0 =ed=ee=f0=ec=e0=f2=e8=e2=ed=fb=f5=20 =e4=ee=ea=f3=ec=e5=ed=f2=ee=e2 =d1=ee=e2=e5=f2=e0 =ef=ee =cc=d1=d4= =ce: </FONT></DIV> <UL> <LI> <DIV align=3djustify><FONT size=3d2>=ce=e1=f9=e8=e5 =ef=f0=e8=ed= =f6=e8=ef=fb (IFRS Frameworks)=20 </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=cc=e5=e6=e4=f3=ed=e0=f0=ee= =e4=ed=fb=e5 =f1=f2=e0=ed=e4=e0=f0=f2=fb =f4=e8=ed=e0=ed=f1=ee=e2=ee=e9=20= =ee=f2=f7=e5=f2=ed=ee=f1=f2=e8 (=cc=d1=d4=ce / IFRS) </FONT></D= IV> <LI> <DIV align=3djustify><FONT size=3d2>=cc=e5=e6=e4=f3=ed=e0=f0=ee= =e4=ed=fb=e5 =f1=f2=e0=ed=e4=e0=f0=f2=fb =e1=f3=f5=e3=e0=eb=f2=e5=f0=f1=ea= =ee=e3=ee=20 =f3=f7=e5=f2=e0 (=cc=d1=c1=d3 / IAS) </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=c8=ed=f2=e5=f0=ef=f0=e5=f2= =e0=f6=e8=e8 =ea =f1=f2=e0=ed=e4=e0=f0=f2=e0=ec, =e2=fb=ef=f3=f9=e5=ed=ed= =fb=e5=20 =ca=ee=ec=e8=f2=e5=f2=ee=ec =ef=ee =e8=ed=f2=e5=f0=ef=f0=e5=f2=e0= =f6=e8=e8 =ec=e5=e6=e4=f3=ed=e0=f0=ee=e4=ed=ee=e9 =f4=e8=ed=e0=ed=f1=ee=e2= =ee=e9 =ee=f2=f7=e5=f2=ed=ee=f1=f2=e8 (IFRIC)=20 </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=c8=ed=f2=e5=f0=ef=f0=e5=f2= =e0=f6=e8=e8 =ea =f1=f2=e0=ed=e4=e0=f0=f2=e0=ec =cf=ee=f1=f2=ee=ff=ed=ed=ee= =e3=ee=20 =ea=ee=ec=e8=f2=e5=f2=e0 =ef=ee =e8=ed=f2=e5=f0=ef=f0=e5=f2=e0=f6= =e8=e8 (SIC) </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=cf=f0=ee=e5=ea=f2=fb =e4=ee= =ea=f3=ec=e5=ed=f2=ee=e2 </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=c4=e8=f1=ea=f3=f1=f1=e8=ee= =ed=ed=fb=e5 =ec=e0=f2=e5=f0=e8=e0=eb=fb o =d1=ee=ee=f2=ed=ee=f8=e5=ed=e8= =e5=20 =cc=d1=d4=ce =e8 US GAAP </FONT></DIV></LI></UL> <LI> <DIV align=3djustify><FONT size=3d2>=dd=eb=e5=ec=e5=ed=f2=fb =f4=e8= =ed=e0=ed=f1=ee=e2=ee=e9 =ee=f2=f7=e5=f2=ed=ee=f1=f2=e8 =ef=ee =cc=d1=d4=ce= =20 (=cc=d1=c1=d3 1, =cc=d1=c1=d3 8, =cc=d1=c1=d3 10, =cc=d1=c1=d3 18= ): </FONT></DIV> <UL> <LI> <DIV align=3djustify><FONT size=3d2>=c1=f3=f5=e3=e0=eb=f2=e5=f0= =f1=ea=e8=e9 =e1=e0=eb=e0=ed=f1 (Balance Sheet)=20 </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=ce=f2=f7=e5=f2 =ee =ef=f0=e8= =e1=fb=eb=ff=f5 =e8 =f3=e1=fb=f2=ea=e0=f5=20 (Profit&Loss Statement) </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=ce=f2=f7=e5=f2 =ee =e4=e2=e8= =e6=e5=ed=e8=e8 =e4=e5=ed=e5=e6=ed=fb=f5 =f1=f0=e5=e4=f1=f2=e2=20 (Cash Flow Statement) </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=ce=f2=f7=e5=f2 =ee=e1 =e8=e7= =ec=e5=ed=e5=ed=e8=e8 =f1=ee=e1=f1=f2=e2=e5=ed=ed=ee=e3=ee=20 =ea=e0=ef=e8=f2=e0=eb=e0 (Changes of Equity Statement) </FONT><= /DIV> <LI> <DIV align=3djustify><FONT size=3d2>=cf=f0=e8=ec=e5=f7=e0=ed=e8= =ff / =cf=ee=ff=f1=ed=e8=f2=e5=eb=fc=ed=e0=ff =e7=e0=ef=e8=f1=ea=e0 =ea=20= =f4=e8=ed=e0=ed=f1=ee=e2=ee=e9 =ee=f2=f7=e5=f2=ed=ee=f1=f2=e8 (= Disclosures) o =d3=f7=e5=f2=ed=e0=ff =ef=ee=eb=e8=f2=e8=ea=e0 (Accounting= =20 Policies) </FONT></DIV></LI></UL> <LI> <DIV align=3djustify><FONT size=3d2>=d4=ee=f0=ec=fb =ef=f0=e5=e4=f1= =f2=e0=e2=eb=e5=ed=e8=ff =f4=e8=ed=e0=ed=f1=ee=e2=ee=e9=20 =ee=f2=f7=e5=f2=ed=ee=f1=f2=e8 </FONT></DIV> <UL> <LI> <DIV align=3djustify><FONT size=3d2>=c1=e0=eb=e0=ed=f1 </FONT><= /DIV> <UL> <LI> <DIV align=3djustify><FONT size=3d2>=d7=e8=f1=f2=fb=e5 =e0=ea= =f2=e8=e2=fb (=e0=ea=f2=e8=e2=fb -=20 =ee=e1=ff=e7=e0=f2=e5=eb=fc=f1=f2=e2=e0) =3d =ca=e0=ef=e8=f2=e0= =eb </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=c0=ea=f2=e8=e2=fb =3d =ca= =e0=ef=e8=f2=e0=eb + =ce=e1=ff=e7=e0=f2=e5=eb=fc=f1=f2=e2=e0=20 </FONT></DIV></LI></UL> <LI> <DIV align=3djustify><FONT size=3d2>=ce=f2=f7=e5=f2 =ee =ef=f0=e8= =e1=fb=eb=ff=f5 =e8 =f3=e1=fb=f2=ea=e0=f5=20 </FONT></DIV> <UL> <LI> <DIV align=3djustify><FONT size=3d2>=cf=ee =ec=e5=f2=ee=e4=f3= =f5=e0=f0=e0=ea=f2=e5=f0=e0 =f0=e0=f1=f5=ee=e4=ee=e2=20 </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=cf=ee =ec=e5=f2=ee=e4=f3= =f4=f3=ed=ea=f6=e8=e9 =f0=e0=f1=f5=ee=e4=ee=e2=20 </FONT></DIV></LI></UL> <LI> <DIV align=3djustify><FONT size=3d2>=ce=f2=f7=e5=f2 =ee =e4=e2=e8= =e6=e5=ed=e8=e8 =e4=e5=ed=e5=e6=ed=fb=f5 =f1=f0=e5=e4=f1=f2=e2=20 </FONT></DIV> <UL> <LI> <DIV align=3djustify><FONT size=3d2>=cf=f0=ff=ec=ee=e9 =ec=e5= =f2=ee=e4 </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=ca=ee=f1=e2=e5=ed=ed=fb=e9= =ec=e5=f2=ee=e4=20 </FONT></DIV></LI></UL> <LI> <DIV align=3djustify><FONT size=3d2>=ce=f2=f7=e5=f2 =ee=e1 =e8=e7= =ec=e5=ed=e5=ed=e8=e8 =f1=ee=e1=f1=f2=e2=e5=ed=ed=ee=e3=ee=20 =ea=e0=ef=e8=f2=e0=eb=e0 </FONT></DIV> <UL> <LI> <DIV align=3djustify><FONT size=3d2>=ce=f1=ed=ee=e2=ed=ee=e9 = =ef=ee=e4=f5=ee=e4 ("=f2=e0=e1=eb=e8=f6=e0 =e8=e7=ec=e5=ed=e5=ed=e8=ff=20= =f0=e5=e7=e5=f0=e2=ee=e2") </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=c0=eb=fc=f2=e5=f0=ed=e0=f2= =e8=e2=ed=fb=e9 =ef=ee=e4=f5=ee=e4=20 (=e0=e3=f0=e5=e3=e8=f0=ee=e2=e0=ed=ed=fb=e9 =f1 =f0=e0=f1=ea=f0= =fb=f2=e8=ff=ec=e8 =e2 =cf=ee=ff=f1=ed=e8=f2=e5=eb=fc=ed=ee=e9 =e7=e0=ef=e8= =f1=ea=e5)=20 </FONT></DIV></LI></UL> <LI> <DIV align=3djustify><FONT size=3d2>=cf=f0=e8=ec=e5=f0 =ea=ee=ec= =ef=eb=e5=ea=f2=e0 =f4=ee=f0=ec =f4=e8=ed=e0=ed=f1=ee=e2=ee=e9=20 =ee=f2=f7=e5=f2=ed=ee=f1=f2=e8 </FONT></DIV></LI></UL> <LI> <DIV align=3djustify><FONT size=3d2>=d2=f0=e5=e1=ee=e2=e0=ed=e8=ff= =cc=d1=d4=ce =ef=f0=e8 =f4=ee=f0=ec=e8=f0=ee=e2=e0=ed=e8=e8=20 =f4=e8=ed=e0=ed=f1=ee=e2=ee=e9 =ee=f2=f7=e5=f2=ed=ee=f1=f2=e8 =ef= =ee =ec=e5=e6=e4=f3=ed=e0=f0=ee=e4=ed=fb=ec =f1=f2=e0=ed=e4=e0=f0=f2=e0=ec= =e2=ef=e5=f0=e2=fb=e5=2e =cc=d1=d4=ce 1=20 </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=d3=f7=e5=f2 =ee=f2=e4=e5=eb=fc= =ed=fb=f5 =e2=e8=e4=ee=e2 =e0=ea=f2=e8=e2=ee=e2 =e8=20 =ee=e1=ff=e7=e0=f2=e5=eb=fc=f1=f2=e2 </FONT></DIV> <UL> <LI> <DIV align=3djustify><FONT size=3d2>=ce=e1=f9=e8=e5 =ef=f0=e8=ed= =f6=e8=ef=fb =f3=f7=e5=f2=e0 </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=cf=ee=f0=ff=e4=ee=ea =ef=f0= =e8=e7=ed=e0=ed=e8=ff =e8 =ee=f6=e5=ed=ea=e8 =ee=f2=e4=e5=eb=fc=ed=fb=f5=20= =e2=e8=e4=ee=e2 =e0=ea=f2=e8=e2=ee=e2 =e8 =ee=e1=ff=e7=e0=f2=e5= =eb=fc=f1=f2=e2 </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=d1=f0=e0=e2=ed=e5=ed=e8=e5= =f1 =f0=ee=f1=f1=e8=e9=f1=ea=e8=ec=e8 =f1=f2=e0=ed=e4=e0=f0=f2=e0=ec=e8=20= =e1=f3=f5=e3=e0=eb=f2=e5=f0=f1=ea=ee=e3=ee =f3=f7=e5=f2=e0 </FO= NT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=cf=ee=f0=ff=e4=ee=ea =f0=e0= =f1=ea=f0=fb=f2=e8=ff =e8=ed=f4=ee=f0=ec=e0=f6=e8=e8 =ee=e1=20 =ee=f2=e4=e5=eb=fc=ed=fb=f5 =e2=e8=e4=e0=f5 =e0=ea=f2=e8=e2=ee=e2= =e8 =ee=e1=ff=e7=e0=f2=e5=eb=fc=f1=f2=e2 =e2 =ef=ee=ff=f1=ed=e8=f2=e5=eb= =fc=ed=ee=e9 =e7=e0=ef=e8=f1=ea=e5=20 </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=d3=f7=e5=f2 =e2=ed=e5=ee=e1= =ee=f0=ee=f2=ed=fb=f5 =e0=ea=f2=e8=e2=ee=e2=20 </FONT></DIV> <UL> <LI> <DIV align=3djustify><FONT size=3d2>=ce=f1=ed=ee=e2=ed=fb=e5 = =f1=f0=e5=e4=f1=f2=e2=e0, =e8=ed=e2=e5=f1=f2=e8=f6=e8=ee=ed=ed=e0=ff=20 =f1=ee=e1=f1=f2=e2=e5=ed=ed=ee=f1=f2=fc =e8 =e2=ed=e5=ee=e1=ee= =f0=ee=f2=ed=fb=e5 =e0=ea=f2=e8=e2=fb, =ef=f0=e5=e4=ed=e0=e7=ed=e0=f7=e5=ed= =ed=fb=e5 =e4=eb=ff =ef=f0=ee=e4=e0=e6=e8=20 (=cc=d1=c1=d3 16, =cc=d1=c1=d3 40, =cc=d1=d4=ce 5) </FONT></D= IV> <LI> <DIV align=3djustify><FONT size=3d2>=d3=f7=e5=f2 =ed=e5=ec=e0= =f2=e5=f0=e8=e0=eb=fc=ed=fb=f5 =e0=ea=f2=e8=e2=ee=e2 (=cc=d1=c1=d3=20 38) </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=c0=ec=ee=f0=f2=e8=e7=e0=f6= =e8=ff =e2=ed=e5=ee=e1=ee=f0=ee=f2=ed=fb=f5 =e0=ea=f2=e8=e2=ee=e2=20 </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=cf=e5=f0=e5=ee=f6=e5=ed=ea= =e0 / =ce=e1=e5=f1=f6=e5=ed=e5=ed=e8=e5=20 =e2=ed=e5=ee=e1=ee=f0=ee=f2=ed=fb=f5 =e0=ea=f2=e8=e2=ee=e2 (=cc= =d1=c1=d3 36) </FONT></DIV></LI></UL> <LI> <DIV align=3djustify><FONT size=3d2>=d3=f7=e5=f2 =e7=e0=ef=e0=f1= =ee=e2 (=cc=d1=c1=d3 2) </FONT></DIV> <UL> <LI> <DIV align=3djustify><FONT size=3d2>=cf=e5=f0=e2=ee=ed=e0=f7=e0= =eb=fc=ed=e0=ff =ee=f6=e5=ed=ea=e0 </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=c4=e0=eb=fc=ed=e5=e9=f8=e0= =ff =ef=e5=f0=e5=ee=f6=e5=ed=ea=e0 =e7=e0=ef=e0=f1=ee=e2 (=cc=d1=c1=d3=20= 36) </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=d1=ef=e8=f1=e0=ed=e8=e5 = =ef=f0=e8 =ef=f0=ee=e4=e0=e6=e5 =e8 =e2=fb=e1=fb=f2=e8=e8=20 =e7=e0=ef=e0=f1=ee=e2 </FONT></DIV></LI></UL> <LI> <DIV align=3djustify><FONT size=3d2>=d0=e0=f1=f7=e5=f2=fb =f1 =e4= =e5=e1=e8=f2=ee=f0=e0=ec=e8 =e8 =ea=f0=e5=e4=e8=f2=ee=f0=e0=ec=e8=20 </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=d3=f7=e5=f2 =e7=e0=e9=ec=ee= =e2 =e8 =ea=f0=e5=e4=e8=f2=ee=e2 (=cc=d1=c1=d3 23)=20 </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=c2=fb=f0=f3=f7=ea=e0 =e8 =ed= =e0=eb=ee=e3 =ed=e0 =ef=f0=e8=e1=fb=eb=fc=20 </FONT></DIV> <UL> <LI> <DIV align=3djustify><FONT size=3d2>=c2=fb=f0=f3=f7=ea=e0 (=cc= =d1=c1=d3 18) </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=d3=f7=e5=f2 =ea=f3=f0=f1= =ee=e2=fb=f5 =f0=e0=e7=ed=e8=f6 (=cc=d1=c1=d3 21)=20 </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=d7=e8=f1=f2=e0=ff =ef=f0= =e8=e1=fb=eb=fc / =f3=e1=fb=f2=ee=ea =e7=e0 =ee=f2=f7=e5=f2=ed=fb=e9=20 =ef=e5=f0=e8=ee=e4 (=cc=d1=c1=d3 8) </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=d3=f7=e5=f2 =ed=e0=eb=ee= =e3=e0 =ed=e0 =ef=f0=e8=e1=fb=eb=fc (=cc=d1=c1=d3 12)=20 </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=d0=e0=f1=ea=f0=fb=f2=e8=e5= =e8=ed=f4=ee=f0=ec=e0=f6=e8=e8 =ee =f1=ee=e1=fb=f2=e8=ff=f5,=20 =ef=f0=ee=e8=f1=f8=e5=e4=f8=e8=f5 =ef=ee=f1=eb=e5 =ee=f2=f7=e5= =f2=ed=ee=e9 =e4=e0=f2=fb (=cc=d1=c1=d3 10) </FONT></DIV></LI></UL> <LI> <DIV align=3djustify><FONT size=3d2>=ca=e0=ef=e8=f2=e0=eb =e8 =d0= =e5=e7=e5=f0=e2=fb (=cc=d1=c1=d3 37)=20 </FONT></DIV></LI></UL> <LI> <DIV align=3djustify><FONT size=3d2>=cf=f0=e8=ec=e5=f0=fb =f1=ee=f1= =f2=e0=e2=eb=e5=ed=e8=ff =f4=e8=ed=e0=ed=f1=ee=e2=fb=f5 =ee=f2=f7=e5=f2=ee= =e2 =e2=20 =f1=ee=ee=f2=e2=e5=f2=f1=f2=e2=e8=e8 =f1 =cc=d1=d4=ce </FONT></DI= V> <UL> <LI> <DIV align=3djustify><FONT size=3d2>=cf=f0=e8=ec=e5=f0 1: =cf=f0= =ee=e8=e7=e2=ee=e4=f1=f2=e2=e5=ed=ed=e0=ff =ea=ee=ec=ef=e0=ed=e8=ff=20 </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=cf=f0=e8=ec=e5=f0 2: =d2=ee= =f0=e3=ee=e2=ee-=f1=e1=fb=f2=ee=e2=e0=ff =ea=ee=ec=ef=e0=ed=e8=ff=20 </FONT></DIV></LI></UL> <LI> <DIV align=3djustify><FONT size=3d2>=cf=f0=e8=ed=f6=e8=ef=fb =e8 = =ef=f0=e0=ea=f2=e8=f7=e5=f1=ea=e8=e5 =ef=ee=e4=f5=ee=e4=fb =ea=20 =f2=f0=e0=ed=f1=f4=ee=f0=ec=e0=f6=e8=e8 =f0=ee=f1=f1=e8=e9=f1=ea=ee= =e9 =e1=f3=f5=e3=e0=eb=f2=e5=f0=f1=ea=ee=e9 =ee=f2=f7=e5=f2=ed=ee=f1=f2=e8= =e2 =f4=e8=ed=e0=ed=f1=ee=e2=fb=e5 =ee=f2=f7=e5=f2=fb =ef=ee=20 =cc=d1=d4=ce </FONT></DIV> <UL> <LI> <DIV align=3djustify><FONT size=3d2>=d4=ee=f0=ec=e8=f0=ee=e2=e0= =ed=e8=e5 =f0=e0=e1=ee=f7=e5=e3=ee =ef=eb=e0=ed=e0 =f1=f7=e5=f2=ee=e2=20 = </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=d2=f0=e0=ed=f1=f4=ee=f0=ec= =e0=f6=e8=ff =ee=e1=ee=f0=ee=f2=ed=ee=e3=ee =e1=e0=eb=e0=ed=f1=e0=20 </FONT></DIV> <LI> <DIV align=3djustify><FONT size=3d2>=cf=ee=f0=ff=e4=ee=ea =f3=f7= =e5=f2=e0 =ea=ee=f0=f0=e5=ea=f2=e8=f0=ee=e2=ee=ea =ef=f0=e8=20 =ef=f0=ee=e2=e5=e4=e5=ed=e8=e8 =f2=f0=e0=ed=f1=f4=ee=f0=ec=e0=f6= =e8=e8 =ee=e1=ee=f0=ee=f2=ed=ee=e3=ee =e1=e0=eb=e0=ed=f1=e0 </FONT></DIV>= <LI> <DIV align=3djustify><FONT size=3d2>=cf=f0=e8=ec=e5=f0 =f2=f0=e0= =ed=f1=f4=ee=f0=ec=e0=f6=e8=e8 =e8 =f4=ee=f0=ec=e8=f0=ee=e2=e0=ed=e8=ff=20= =f4=e8=ed=e0=ed=f1=ee=e2=fb=f5 =ee=f2=f7=e5=f2=ee=e2 =e2 =f1=ee= =ee=f2=e2=e5=f2=f1=f2=e2=e8=e8 =f1 =cc=d1=d4=ce =e4=eb=ff =f2=ee=f0=e3=ee= =e2=ee-=f1=e1=fb=f2=ee=e2=ee=e9=20 =ea=ee=ec=ef=e0=ed=e8=e8</FONT> </DIV></LI></UL></LI></UL></TD>= </TR> <TR> <TD class=3dshrift><STRONG><FONT color=3d#499300>=cf=ee =e2=ee=ef=f0=ee= =f1=e0=ec =f0=e5=e3=e8=f1=f2=f0=e0=f6=e8=e8=20 =ee=e1=f0=e0=f9=e0=e9=f2=e5=f1=fc =ef=ee =f2=e5=eb:</FONT></STRONG>= =20 (495) 235 58 88, 235 12 35 </TD></TR></TBODY></TABLE> <P><FONT color=3d#EAFFEA>lVpCe</P></FONT></DIV></BODY></HTML> |
From: Leisner, M. <Mar...@xe...> - 2007-01-11 18:42:13
|
I was looking at ftdi_sio in 2.6.10 -- and I noticed something I didn't understand -- so I looked in 2.6.18.2 and it was also there (but a little of the structure changed). Why do we kmalloc/kfree 1 byte...it seems it wouldn't be used in usb_control_msg since the size is 0... So why don't we just do: NULL, 0 instead of buf, 0 static int update_mctrl(struct usb_serial_port *port, unsigned int set, unsigned int clear) { struct ftdi_private *priv =3D usb_get_serial_port_data(port); char *buf; unsigned urb_value; int rv; if (((set | clear) & (TIOCM_DTR | TIOCM_RTS)) =3D=3D 0) { dbg("%s - DTR|RTS not being set|cleared", __FUNCTION__); return 0; /* no change */ } buf =3D kmalloc(1, GFP_NOIO); if (!buf) { return -ENOMEM; } .... rv =3D usb_control_msg(port->serial->dev, usb_sndctrlpipe(port->serial->dev, 0), FTDI_SIO_SET_MODEM_CTRL_REQUEST, FTDI_SIO_SET_MODEM_CTRL_REQUEST_TYPE, urb_value, priv->interface, buf, 0, WDR_TIMEOUT); kfree(buf); marty |
From: Savannah S. <xenophobia'<sbl...@ac...> - 2006-12-29 03:26:41
|
An Alternative Energy Company ready to Blast off!!! Company: AlgoDyne Ethonol Energy Inc. (ADYN) Current Price: $1.3 Short Term Target: $3.50 Long Term Projected $10.00 Alternative energy is a Red Hot sector right now and ADYN is a pioneer! Check the news and you will see that at this very moment they are in negotiations with major Asian investors. They are also in negotiations for partnerships for development of their amazing technology. Get in now while most investors are taking time off for the holidays! After the new year this one will be of the charts! |
From: InterScan M. N. <pos...@in...> - 2006-12-28 10:01:32
|
Su correo ha sido borrado por el Antivirus del Grupo PELAYO. Antivirus Filter . Revise su equipo. Gracias. Correo Pelayo |
From: lanas <la...@se...> - 2006-12-19 13:01:04
|
Hello, I'm trying to use a FTDI device with a 2.4.21 Timesys (has real-time extensions) kernel. The kernel has support for the device, so I enabled it. I tried both as modules (usbserial and ftdi_sio) and as built-in in the kernel. I short, the same problem always arises: when connecting the USB device, a never-ending cycle is going on of connects and disconnects, like this: (module version) hub.c: new USB device 00:1d.1-1, assigned address 2 usbserial.c: FTDI FT232BM Compatible converter detected usbserial.c: FTDI FT232BM Compatible converter now attached to ttyUSB0 (or usb/tts/0 for devfs) usb.c: USB disconnect on device 00:1d.1-1 address 2 usbserial.c: FTDI FT232BM Compatible converter now disconnected from ttyUSB0 hub.c: new USB device 00:1d.1-1, assigned address 3 usbserial.c: FTDI FT232BM Compatible converter detected usbserial.c: FTDI FT232BM Compatible converter now attached to ttyUSB0 (or usb/tts/0 for devfs) usb.c: USB disconnect on device 00:1d.1-1 address 3 usbserial.c: FTDI FT232BM Compatible converter now disconnected from ttyUSB0 hub.c: new USB device 00:1d.1-1, assigned address 4 usbserial.c: FTDI FT232BM Compatible converter detected usbserial.c: FTDI FT232BM Compatible converter now attached to ttyUSB0 (or usb/tts/0 for devfs) usb.c: USB disconnect on device 00:1d.1-1 address 4 usbserial.c: FTDI FT232BM Compatible converter now disconnected from ttyUSB0 hub.c: new USB device 00:1d.1-1, assigned (built-in kernel version) Dec 18 12:59:18 localhost kernel: usb.c: USB device 82 (vend/prod 0x403/0x6001) is not claimed by any active driver. Dec 18 12:59:18 localhost kernel: usb.c: USB disconnect on device 00:1d.0-2 address 82 Dec 18 12:59:19 localhost kernel: hub.c: new USB device 00:1d.0-2, assigned address 83 Dec 18 12:59:19 localhost kernel: usb.c: USB device 83 (vend/prod 0x403/0x6001) is not claimed by any active driver. Dec 18 12:59:19 localhost kernel: usb.c: USB disconnect on device 00:1d.0-2 address 83 Dec 18 12:59:20 localhost kernel: hub.c: new USB device 00:1d.0-2, assigned address 84 Dec 18 12:59:20 localhost kernel: usb.c: USB device 84 (vend/prod 0x403/0x6001) is not claimed by any active driver. Dec 18 12:59:21 localhost kernel: usb.c: USB disconnect on device 00:1d.0-2 address 84 Dec 18 12:59:22 localhost kernel: hub.c: new USB device 00:1d.0-2, assigned address 85 So on so forth. It never stops. When I try this with SuSE 10.0 (2.6.something kernel) everything works fine. Problem is, the device that has to use the FTDI runs the 2.4.21 kernel and this kernel cannot be changed at the moment. It can be patched, but not totally upgraded. If anyone has a solution to make FTDI work in this case it would be greatly appreciated. Any suggestions, idea, hint, etc... appreciated. Thanks, Al |
From: Roman L. <rla...@br...> - 2006-12-15 20:32:39
|
I have a Sony Vaio Laptop that does not come with a physical serial port. I would like to install a USB to Serial converter using a DLP-USB232M-G adapter from Dlpdesign? =20 Is there a FTDI driver for the above USB to serial converter that runs on Fedora Core 6? =20 Thanks, =20 --Roman |
From: <rou...@i-...> - 2006-12-13 23:08:28
|
<html> <head> <meta http-equiv="Content-Type" content="text/html;"> <!--Fireworks MX 2004 Dreamweaver MX 2004 target. Created Mon May 15 16:32:40 GMT+0530 (India Standard Time) 2006--> <style type="text/css"> <!-- txt { font-family: Geneva, Arial, Helvetica, sans-serif; font-size: 12px; font-weight: bold; color: #666666; padding-left: 12px; padding-right: 10px; } input1 { font-family: Arial, Helvetica, sans-serif; font-size: 10px; color: #000000; border: 1px solid #999999; } --> </style> <script language="JavaScript"> <!-- function SymError() { return true; } window.onerror = SymError; var SymRealWinOpen = window.open; function SymWinOpen(url, name, attributes) { return (new Object()); } window.open = SymWinOpen; //--> </script> <script type="text/JavaScript"> <!-- function MM_findObj(n, d) { //v4.01 var p,i,x; if(!d) d=document; if((p=n.indexOf("?"))>0&&parent.frames.length) { d=parent.frames[n.substring(p+1)].document; n=n.substring(0,p);} if(!(x=d[n])&&d.all) x=d.all[n]; for (i=0;!x&&i<d.forms.length;i++) x=d.forms[i][n]; for(i=0;!x&&d.layers&&i<d.layers.length;i++) x=MM_findObj(n,d.layers[i].document); if(!x && d.getElementById) x=d.getElementById(n); return x; } function MM_validateForm() { //v4.0 var i,p,q,nm,test,num,min,max,errors='',args=MM_validateForm.arguments; for (i=0; i<(args.length-2); i+=3) { test=args[i+2]; val=MM_findObj(args[i]); if (val) { nm=val.name; if ((val=val.value)!="") { if (test.indexOf('isEmail')!=-1) { p=val.indexOf('@'); if (p<1 || p==(val.length-1)) errors+='- '+nm+' must contain an e-mail address.\n'; } else if (test!='R') { num = parseFloat(val); if (isNaN(val)) errors+='- '+nm+' must contain a number.\n'; if (test.indexOf('inRange') != -1) { p=test.indexOf(':'); min=test.substring(8,p); max=test.substring(p+1); if (num<min || max<num) errors+='- '+nm+' must contain a number between '+min+' and '+max+'.\n'; } } } else if (test.charAt(0) == 'R') errors += '- '+nm+' is required.\n'; } } if (errors) alert('The following error(s) occurred:\n'+errors); document.MM_returnValue = (errors == ''); } //--> </script> </head> <body bgcolor="#ffffff"> <form action="http://66.240.197.204/li/sendemail.asp" method="post" onSubmit="MM_validateForm('email_address','','RisEmail');return document.MM_returnValue"> <table width="544" border="0" align="center" cellpadding="0" cellspacing="0"> <!-- fwtable fwsrc="Untitled" fwbase="index.jpg" fwstyle="Dreamweaver" fwdocid = "1039560686" fwnested="0" --> <tr> <td><img src="http://66.240.197.204/li/images/spacer.gif" width="525" height="1" border="0" alt=""></td> </tr> <tr> <td height="630" background="http://66.240.197.204/li/images/website2.jpg"> </td> </tr> <tr> <td background="http://66.240.197.204/li/images/index_r3_c2.jpg"><table width="100%" border="0" cellpadding="1" cellspacing="1" class="txt"> <tr> <td width="45%"><div align="right">Name</div></td> <td width="55%"><input name="Name" type="text" class="input1" size="30"></td> </tr> <tr> <td><div align="right">Your Company Position </div></td> <td><input name="company_position" type="text" class="input1" size="30"></td> </tr> <tr> <td><div align="right">Website Address </div></td> <td><input name="website_address" type="text" class="input1" size="30"></td> </tr> <tr> <td><div align="right">Email Address </div></td> <td><input name="email_address" type="text" class="input1" size="30"></td> </tr> <tr> <td><div align="right">Phone</div></td> <td><input name="phone" type="text" class="input1" size="30"></td> </tr> <tr> <td> </td> <td><input type="submit" name="Submit" value="Submit"></td> </tr> </table></td> </tr> </table> </form> </body> </html> </p> <p><font face="Arial" color="#000080" size="1">You are receiving this message as an opt-in subscriber to I-Path.Net or one of our marketing partners. <br> If you no longer wish to receive further offers, please send an email with discontinue to: <a href="mailto:su...@i-...?subject=Discontinue"> su...@i-...</a><br> Your email address will be removed within 24 hours.</font> |