Re: driver migration

Hello Kind of Driver: Driver for a dongle usb-> serial Manufacturer: Io-Data Device: USB-RSA (based on EZUSB-CHip) Reference: My last post from 2016-04-02 19:49:40 GMT Description: The blocking behaviour that I reported in my last post seems to be induced by the set_bit and submit_urb in

Re: driver migration

Hi Greg Kind of Driver: Driver for a dongle usb-> serial Manufacturer: Io-Data Device: USB-RSA (based on EZUSB-CHip) Goal: Port the driver that was working on kernel version 3.17 to current kernel version Problem Description: - The driver initializes properly, and downloads the firmware. - When

Re: driver migration

Konstantin Shkolnyy writes: > Just a wild guess - this 30-second delay before close can happen because usbserial is waiting for data to be > transmitted, before closing the port. > If you know that your data have been transmitted, perhaps you didn't properly tell

RE: driver migration

> -Original Message- > From: linux-usb-ow...@vger.kernel.org [mailto:linux-usb- > ow...@vger.kernel.org] On Behalf Of tilman > Sent: Tuesday, March 29, 2016 04:02 > To: linux-usb@vger.kernel.org > Subject: Re: driver migration > > Greg KH <greg@...> writes: &

Re: driver migration

Greg KH writes: Dear Greg > > I moved the initialization and clean up code from the init_callback/release > > callback to the port_init/port_remove callback. I am referring to your last posting on Feb 25th: gkh> Release your port data in the port_remove callback, not the release gkh>

Re: driver migration

On Sun, Mar 27, 2016 at 11:40:51PM +, tilman wrote: > I moved the initialization and clean up code from the init_callback/release > callback to the port_init/port_remove callback. We have no context here at all, sorry, so there's really nothing we can do to help you out... good luck, greg

Re: driver migration

I moved the initialization and clean up code from the init_callback/release callback to the port_init/port_remove callback. This did not help. What prevents the driver from crashing is to initialize the spinlock via spin_lock_init(>lock). Not sure if I originally had forgotten the command, and the

Re: driver migration

On Wed, Feb 24, 2016 at 11:22:49PM +, tilman wrote: > > > I suggest staying away from eclipse, that's not needed for kernel > > development. Other than that, it's just normal debugging, good luck > > with that :) > I resorted to good old vi as the editor that starts up fastest :-) > > And

Re: driver migration

> I suggest staying away from eclipse, that's not needed for kernel > development. Other than that, it's just normal debugging, good luck > with that :) I resorted to good old vi as the editor that starts up fastest :-) And I traced down the problem -- but not the root cause: In

Re: driver migration

On Mon, Feb 22, 2016 at 07:34:08AM +, tilman wrote: > > Hello > > > You can use ftrace to help you watch the flow of your driver before it > > crashes, or just printk, as you have found out, is the best way to debug > > things. > Thanks for the hints. I will give ftrace a go. > It takes me

Re: driver migration

Hello > You can use ftrace to help you watch the flow of your driver before it > crashes, or just printk, as you have found out, is the best way to debug > things. Thanks for the hints. I will give ftrace a go. It takes me around 5-7 minutes to see the kernel crash, and then reboot, make

Re: driver migration

On Fri, Feb 19, 2016 at 08:55:33PM +, tilman wrote: > Greg KH writes: > > > > > On Fri, Feb 19, 2016 at 06:49:50AM +, tilman wrote: > > > Hello > > > > > > I configured and setup a more recent kernel: V4.5.0-rc4 > > > > > > The driver compiles and inserts. > > > > What

Re: driver migration

Greg KH writes: > > On Fri, Feb 19, 2016 at 06:49:50AM +, tilman wrote: > > Hello > > > > I configured and setup a more recent kernel: V4.5.0-rc4 > > > > The driver compiles and inserts. > > What driver? You have provided no context here :( My apologies -- what I meant to

Re: driver migration

On Fri, Feb 19, 2016 at 06:49:50AM +, tilman wrote: > Hello > > I configured and setup a more recent kernel: V4.5.0-rc4 > > The driver compiles and inserts. What driver? You have provided no context here :( > When I plugin the USB-Dongle, the machine > freezes (not sure whether it

Re: driver migration

Hello I configured and setup a more recent kernel: V4.5.0-rc4 The driver compiles and inserts. When I plugin the USB-Dongle, the machine freezes (not sure whether it freezes during the firmware download or after it once it has reenumerated). I could observe a kernel oops message starting

Re: driver migration

Greg KH writes: > > On Mon, Feb 15, 2016 at 11:30:43PM +, tilman wrote: > > Dear all > > > > a couple of years ago I wrote a driver for a serial dongle. > > I did not add it to the linux source because the dongle requires a firmware > > to be downloaded to the device (ezusb). >

Re: driver migration

On Mon, Feb 15, 2016 at 11:30:43PM +, tilman wrote: > Dear all > > a couple of years ago I wrote a driver for a serial dongle. > I did not add it to the linux source because the dongle requires a firmware > to be downloaded to the device (ezusb). > The manufacturer, IO-DATA, did not want me

driver migration

Dear all a couple of years ago I wrote a driver for a serial dongle. I did not add it to the linux source because the dongle requires a firmware to be downloaded to the device (ezusb). The manufacturer, IO-DATA, did not want me to use their firmware. I am now in the process to move the driver