kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [PATCH] 8250_pci: Prevent Exar/RTD Boards from binding.
Date: Fri, 25 Sep 2015 11:37:29 -0700	[thread overview]
Message-ID: <20150925183729.GA3269@kroah.com> (raw)
In-Reply-To: <CO2PR04MB603413224F06D305E83FCB2A6420@CO2PR04MB603.namprd04.prod.outlook.com>

On Fri, Sep 25, 2015 at 05:37:03PM +0000, Rob Groner wrote:
> 
> > -----Original Message-----
> > From: Valdis.Kletnieks at vt.edu [mailto:Valdis.Kletnieks at vt.edu]
> > Sent: Friday, September 25, 2015 12:48 PM
> > To: Rob Groner <rgroner@RTD.com>
> > Cc: kernelnewbies at kernelnewbies.org
> > Subject: Re: [PATCH] 8250_pci: Prevent Exar/RTD Boards from binding.
> > 
> > On Fri, 25 Sep 2015 11:46:29 -0400, Rob Groner said:
> > > Serial boards made by RTD using the Exar XR17V358 chip rely on the
> > > extra capabilities of the Exar-provided driver to allow configuration
> > > of the board.  When support for the Exar chip was added to the kernel
> > > 8250_pci driver, this then prevented easy use of the board by
> > > customers for anything other than standard serial usage in RS232 mode.
> > 
> > Was it your intent to also prevent the use of this board in standard serial
> > usage in RS232 mode (which I'd expect is the most common use case)?
> 
> That is a byproduct of giving the non-average user the ability to
> reconfigure their board.  This will basically move us back to pre-3.8,
> where the customer would simply have to insmod the provided Exar
> driver.  The small inconvenience to that more common user seems (to us
> in Tech Support) outweighed by the much greater inconvenience to the
> user who wants to reconfigure.

Where is the exar driver, in the kernel already?

confused,

greg k-h

  reply	other threads:[~2015-09-25 18:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-25 15:46 [PATCH] 8250_pci: Prevent Exar/RTD Boards from binding Rob Groner
2015-09-25 16:47 ` Valdis.Kletnieks at vt.edu
2015-09-25 17:37   ` Rob Groner
2015-09-25 18:37     ` Greg KH [this message]
2015-09-25 19:08       ` Rob Groner
2015-09-25 19:14         ` Greg KH
2015-09-25 19:21           ` Rob Groner
2015-09-26  0:45             ` Greg KH
2015-09-28 12:53               ` Rob Groner
2015-09-28 14:11                 ` Greg KH
2015-09-28 15:33                   ` Rob Groner
2015-10-26 12:28                   ` Rob Groner
2015-11-11 15:46                     ` Rob Groner
2015-11-11 17:32                       ` Greg KH
2015-11-11 18:15                         ` Rob Groner
2015-11-11 18:20                         ` Sudip Mukherjee
2015-11-11 21:41                           ` Greg KH
2015-11-11 21:49                             ` Rob Groner
2015-11-11 22:13                               ` Greg KH
2015-11-12 13:28                                 ` Rob Groner
2015-09-25 17:18 ` Greg KH
2015-09-25 17:30   ` Rob Groner

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=20150925183729.GA3269@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).