Re: usb-uirt problems with ftdi_sio in 2.6.22.1

"John H." <[email protected]>
Newsgroups gmane.linux.usb.devel
Message-ID <[email protected]>
Bill, thanks.

Unfortunately, I got no response from the linux-usb-developers list.
The bugzilla is still outstanding. It's rather ridiculous that the bug
would go unfixed that long, particularly when it USED to work!  In
other words, someone broke it when they changed stuff and they are not
fixing it as of now.

On 8/23/07, Bill Ryder <[email protected]> wrote:
> Hi John,
>
> I have had a good look at the driver and I finally understand the problem.
> However I can't fix or test it because I would need your device. It has to
> do with quirk handling which none of the really old devices I have need.
>
> So unfortunately you are on your own! You need to find a developer who has
> one of your devices.
>
> You should however try the linux usb developers list. That is where people
> have been submitting these patches I suspect. Someone there must have had a
> device the same as yours.
>
> I think you'll be lucky if you can get someone to work on an old kernel
> though.
>
> If you pay for redhat support you should be able to get them to look at it
> though.
>
>
>
>  On 8/24/07, John H. <[email protected]> wrote:
> > Sorry, dan, no one seems interested in fixing it despite this bug
> > being in several kernel versions.
> >
> > The only solution is to use the source from an older kernel, the
> > ftdi_sio.h and ftdi_sio.c.
> >
> > You can see from the bugzilla entry what to do...
> >
> > http://bugzilla.kernel.org/show_bug.cgi?id=8564
> >
> > On 8/23/07, [email protected] < [email protected]> wrote:
> > > Hi John,
> > >
> > > Did you find a solution/patch for the issue below?  I have exactly the
> same problem with my new uirt, and I can't find any references to it apart
> from yours.  I've tried the latest CVS, packaged version for my distro
> (arch), 0.8.2 source from the lirc.org site ... sweet fanny albright with
> all three.
> > >
> > > kind regards,
> > >
> > > -dan
> > >
> > > John H.-2 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/
> > > >
> > > >
> > > Quoted from:
> > >
> http://www.nabble.com/usb-uirt-problems-with-ftdi_sio-in-2.6.22.1-tf4255931.html#a12112175
> > >
> > >
> >
>
>

-------------------------------------------------------------------------
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.