The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: USB: symbolserial: log the ioctl commands
Date: Sun, 5 Apr 2009 22:40:14 -0700	[thread overview]
Message-ID: <20090406054014.GB12019@kroah.com> (raw)
In-Reply-To: <20090326194421.41816289@lxorguk.ukuu.org.uk>

On Thu, Mar 26, 2009 at 07:44:21PM +0000, Alan Cox wrote:
> 
> > +static int symbol_tiocmget(struct tty_struct *tty, struct file *file)
> > +{
> > +	struct usb_serial_port *port = tty->driver_data;
> > +	struct device *dev = &port->dev;
> > +
> > +	/* TODO */
> > +	/* probably just need to shadow whatever was sent to us here */
> > +	dev_info(dev, "%s\n", __func__);
> > +	return 0;
> > +}
> 
> If you don't have a modem you don't provide these methods. If you do have
> a modem you return the values for the modem. Please do not try and stick
> in stuff faking responses, it just makes a nasty mess in the longer term
> and I've already cleared the same out of a ton of drivers - with I note
> no breakages of user space.

I'm trying to get this driver working properly for a USB device that is
being controlled by a Windows program running under WINE.  Right now
there are some ioctls being called by either WINE or the serial program
on Windows that the driver isn't handling and so it's not working
properly.  This change was so that I could get feedback from the user
with this situation to try to work it all out.

I've now got a trace of an attempt and will work to try to implement the
needed ioctls to get it running properly.

thanks,

greg k-h

  reply	other threads:[~2009-04-06  5:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200903261929.n2QJTUX1009811@hera.kernel.org>
2009-03-26 19:44 ` USB: symbolserial: log the ioctl commands Alan Cox
2009-04-06  5:40   ` Greg KH [this message]
2009-04-06  9:16     ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090406054014.GB12019@kroah.com \
    --to=greg@kroah.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox