Re: FT232BM usb2serial not working

[Alex Villací­s Lasso <avillaci@xxxxxxxxxxxxxxxxxxxxxxx>]

Ari Kohtamäki escribió:
> Don't know, but it does when my remote receiver(/sender) is
> plugged to my /dev/ttyS0:
>
> write(2, "accepted new client on /dev/lirc"..., 33accepted new client
> on /dev/lircd) = 33
> write(2, "\n", 1
> )                       = 1
> stat64("/dev/lirc", {st_mode=S_IFCHR|0777, st_rdev=makedev(61, 0), ...}) = 0
> open("/dev/lirc", O_RDWR)               = 7
> ioctl(7, I2OGETIOPS, 0x80625a8)         = 0
> time(NULL)                              = 1201025316
> write(5, "Jan 22 20:08:36 dell.localdomain"..., 83) = 83
> write(2, "lircd: ", 7lircd: )                  = 7
> write(2, "driver supports both sending and"..., 42driver supports both
> sending and receiving) = 42
>   
Please watch your strace carefully:

open("/dev/lirc", O_RDWR)               = 7

This means that the program issued an open() system call on /dev/lirc 
(NOT /dev/ttyS0), and received file descriptor 7 as a result.
Later on:

ioctl(7, I2OGETIOPS, 0x80625a8)         = 0

The first parameter is the file descriptor (see ioctl(2) for details). 
Remember that descriptor 7 results from opening /dev/lirc (as shown 
earlier), NOT /dev/ttyS0. So the standard serial port does not 
understand I2OGETIOPS either - /dev/lirc does (which is managed by the 
LIRC kernel driver).


-- 
perl -e '$x=2.4;print sprintf("%.0f + %.0f = %.0f\n",$x,$x,$x+$x);'


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
linux-usb-devel@xxxxxxxxxxxxxxxxxxxxx
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel