Re: [Ftdi-usb-sio-devel] usb-uirt problems with ftdi_sio in 2.6.22.1

Oh, i had to patch the driver for that kernel.  I am using that kernel
again because with my upgrade to fedora 7 and the first kernel it had,
ftdi_sio stopped working right with usb-uirt.  I had to patch the
kernel I am currently using to work at all with it.  I had gotten
pointers on either the ftdi_sio list or the usb-uirt list a few months
ago, they said to comment out something and i did so, then recompiled
the module and got it working.

 uname -a
Linux home 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
i686 i386 GNU/Linux


On 8/16/07, Bill Ryder <[email protected]> wrote:
> Hi John,
>
> What does your uname -a say? I need to see what point release redhat is
> using.
>
>
> I'll have a look at the 2.6.21 driver.
>
> It says it's a FT232BM and I think that's supposed to work.
>
>
>
>
> On 8/16/07, John H. <[email protected]> wrote:
> > dmesg |grep FT
> > 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
> > /usr/src/redhat/BUILD/kernel-2.6.21/linux-2.6.21.i386
> /drivers/usb/serial/ftdi_sio.c:
> > Detected FT232BM
> > usb 3-2: FTDI USB Serial Device converter now attached to ttyUSB0
> >
> /usr/src/redhat/BUILD/kernel-2.6.21/linux-2.6.21.i386/drivers/usb/serial/ftdi_sio.c:
> > v1.4.3:USB FTDI Serial Converters Driver
> >
> >
> > On 8/16/07, Bill Ryder <[email protected]> wrote:
> > > I don't think  Christoph can help you.
> > >
> > > Did your dmesg so your chip type was FT232RL?
> > >
> > >
> > >
> > >
> > > On 8/16/07, John H. < [email protected]> wrote:
> > > > Christoph, do you have any ideas?  Any new kernels available have this
> > > > problem, meaning I can't use lirc with them:(
> > > >
> > > > On 8/13/07, Bill Ryder <[email protected]> wrote:
> > > > > Actually I just downloaded the 2.6.22.2 kernel and had a look at
> that
> > > > > driver.
> > > > >
> > > > > I'm pretty certain now you have a device I don't have and hence
> can't
> > > check
> > > > > out a fix for at all.
> > > > >
> > > > > However - you can probably patch it yourself
> > > > >
> > > > > First you want to
> > > > >
> > > > > dmesg  | grep Detected
> > > > >
> > > > > after you have plugged in whatever it is you are using (or after
> booting
> > > > > your system).
> > > > >
> > > > > For my device I get:
> > > > >
> > > > > drivers/usb/serial/ftdi_sio.c: Detected FT8U232AM
> > > > >
> > > > > The chip type is FT8U232AM for me. That is supported.
> > > > >
> > > > > I'm guessing you are a FT232RL
> > > > >
> > > > > Maybe it will work just by adding
> > > > >
> > > > > case FT232RL:
> > > > >
> > > > > to the ftdi_tiocmget function  (under case FT2232C:)
> > > > >
> > > > > If that doesn't work then you really are in trouble because the chip
> > > isn't
> > > > > talking in the same way as the other ones and FTDI may not have
> released
> > > the
> > > > > spec.
> > > > >
> > > > > If all of that works you can just request that change to the linux
> usb
> > > > > developers mailing list since it's a safe one line change.
> > > > >
> > > > > As I say I don't maintain the driver at all any more and don't have
> time
> > > to
> > > > > work on it (and only have very old devices for testing anyway).
> > > > >
> > > > > Good luck!
> > > > >
> > > > >
> > > > >
> > > > > On 8/14/07, Bill Ryder <[email protected] > wrote:
> > > > > > Hi  guys,
> > > > > >
> > > > > > So I don't run fedora and the TIOCMGET ioctl works fine in the
> stock
> > > > > 2.6.20.11 kernel which is the only kernel I run.
> > > > > >
> > > > > > Hmm, OK. Thanx for that Christoph.
> > > > > >
> > > > > >
> > > > > > tiocmget certainly works for the old devices I have with
> 2.6.20.11.
> > > > > >
> > > > > > John -
> > > > > > What was the patch that fixed it last time?
> > > > > >
> > > > > > It might provide a hint.
> > > > > >
> > > > > > I'm guessing a new chip type was added but tiocmget wasn't
> updated.
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 13 Aug 2007 17:27:00 +0200, Christoph Bartelmus <
> > > [email protected]>
> > > > > wrote:
> > > > > > > Hi Bill,
> > > > > > >
> > > > > > > the document you are refering to describes an _internal_ kernel
> API
> > > > > > > change. I don't see how it should influence the userspace
> interface.
> > > > > > > The TIOCMGET ioctl is supported and I can't find any hints in
> the
> > > > > > > current kernel sources that it is deprecated.
> > > > > > >
> > > > > > > Please get your driver fixed.
> > > > > > > The place to look at would be:
> > > > > > >
> > > > >
> > >
> http://lxr.linux.no/source/drivers/usb/serial/ftdi_sio.c#L2040
> > > > > > >
> > > > > > > Christoph
> > > > > > >
> > > > > > > on 13 Aug 07 at 16:46, you wrote:
> > > > > > > > Ooops.
> > > > > > > >
> > > > > > > > Sending this to Christoph too:
> > > > > > > >
> > > > > > > > To be a little more succinct - it turns out the TIOCMGET
> ioctls
> > > and
> > > > > such are
> > > > > > > > deprecated:
> > > > > > > >
> > > > > > > >   http://www.linuxjournal.com/article/7000
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On 8/13/07, John H. < [email protected] > wrote:
> > > > > > > >>
> > > > > > > >> Bill, did you BCC christoph?  IT doesn't show that this email
> > > went to
> > > > > > > >> anyone but me.
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> On 8/12/07, Bill Ryder < [email protected]> wrote:
> > > > > > > >>> Hi Christoph,
> > > > > > > >>>
> > > > > > > >>> To be a little more succient - it turns out the TIOCMGET
> ioctls
> > > and
> > > > > such
> > > > > > > >> are
> > > > > > > >>> deprecated:
> > > > > > > >>>
> > > > > > > >>>  http://www.linuxjournal.com/article/7000
> > > > > > > >>>
> > > > > > > >>>
> > > > > > > >>>
> > > > > > > >>>
> > > > > > > >>> On 8/13/07, John H. < [email protected]> wrote:
> > > > > > > >>>> Christoph, it seems that this is an issue with lircd and
> not
> > > the
> > > > > > > >>>> current ftdi_sio implementation that works with usb-uirt?
> > > > > > > >>>>
> > > > > > > >>>> On 8/12/07, Bill Ryder <[email protected] > wrote:
> > > > > > > >>>>> Hi Again,
> > > > > > > >>>>>
> > > > > > > >>>>> Actually - is this lircd thing doing a TIOCMGET ioctl or
> is he
> > > > > using
> > > > > > > >> the
> > > > > > > >>>>> tiocmget callback?
> > > > > > > >>>>>
> > > > > > > >>>>> According to this:
> > > > > > > >>>>>
> > > > > > > >>>>> http://www.linuxjournal.com/article/7000
> > > > > > > >>>>>
> > > > > > > >>>>> Greg Koah-Hartman is one of the main usb serial
> programmers so
> > > > > > > >>> essentially
> > > > > > > >>>>> his word is law.
> > > > > > > >>>>>
> > > > > > > >>>>> This has happened:
> > > > > > > >>>>>
> > > > > > > >>>>> Along with the tty structure changes, a few tty ioctls
> have
> > > been
> > > > > > > >>> removed,
> > > > > > > >>>>> specifically the TIOCMGET, TIOCMBIS, TIOCMBIC and TIOCMSET
> > > ioctls.
> > > > > > > >>>>>
> > > > > > > >>>>> And looking at the driver the TIOCMSET/GET ioctls are not
> > > > > supported.
> > > > > > > >>> Only
> > > > > > > >>>>> the modern callbacks.
> > > > > > > >>>>>
> > > > > > > >>>>> So the lircd person needs to update his stuff to use the
> newer
> > > > > API.
> > > > > > > >> I
> > > > > > > >>> think
> > > > > > > >>>>> you'll be very lucky to get anyone to support an old API
> > > > > officially
> > > > > > > >> in
> > > > > > > >>> the
> > > > > > > >>>>> kernel when Greg has said they are no longer supported.
> > > > > > > >>>>>
> > > > > > > >>>>>
> > > > > > > >>>>>
> > > > > > > >>>>> On 8/12/07, John H. < [email protected] > wrote:
> > > > > > > >>>>>>
> > > > > > > >>>>>> 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 <
> > > > > > > >> [email protected]
> > > > > > > >>>>
> > > > > > > >>>>> 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/
> > > > > > > >>>>>>>
> > > > > > > >>>>>>
> > > > > > > >>>>>>
> > > > > > > >>>>>
> > > > > > > >>>
> > > > > > > >>
> > > > >
> > >
> -------------------------------------------------------------------------
> > > > > > > >>>>>> 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/
> > > > > > > >>>>>>
> > > _______________________________________________
> > > > > > > >>>>>> Ftdi-usb-sio-devel mailing list
> > > > > > > >>>>>> [email protected]
> > > > > > > >>>>>>
> > > > > > > >>>>>
> > > > > > > >>>
> > > > >
> > >
> https://lists.sourceforge.net/lists/listinfo/ftdi-usb-sio-devel
> > > > > > > >>>>>>
> > > > > > > >>>>>
> > > > > > > >>>>>
> > > > > > > >>>>
> > > > > > > >>>
> > > > > > > >>>
> > > > > > > >>
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> >
>
>

-------------------------------------------------------------------------
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/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel