From mboxrd@z Thu Jan 1 00:00:00 1970 From: greg@kroah.com (Greg KH) Date: Wed, 11 Nov 2015 14:13:27 -0800 Subject: [PATCH] 8250_pci: Prevent Exar/RTD Boards from binding. In-Reply-To: References: <56059ECA.1070803@rtd.com> <20150926004552.GB10629@kroah.com> <1443444829.2619.7.camel@kernel-dev> <20150928141159.GC20559@kroah.com> <20151111173211.GA20959@kroah.com> <20151111214129.GA24111@kroah.com> Message-ID: <20151111221327.GA24979@kroah.com> To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org On Wed, Nov 11, 2015 at 09:49:11PM +0000, Rob Groner wrote: > > > We all know you are busy. If you want I can try the cleanup and send > > > it to Rob for testing. > > > > Yes please, it should just require a change to the existing 8250 driver code for > > this platform, it should not be a stand-alone driver. > > > > thanks, > > > > greg k-h > > I'm a little confused by that, but I'm happily standing by, ready to > test the result, or any other way I can help. > > As long as our boards that use the Exar chip aren't sucked up by the > kernel 8250 driver, then mission accomplished! It should be sucked up by the 8250 driver, the driver they posted is just a fork of the existing driver with a few small, odd, modifications. the 8250 framework is _so_ flexible that I'm sure it can support this hardware as-is, the hardware just needs to be properly described to the driver. The last time I did this, it took 2 days of reading the driver and figuring it all out, and then only 16 new lines of code/tables added to the driver to support a new device that was a bit "odd" from a normal uart. I expect the same thing would be needed here, but maybe more lines of code :) thanks, greg k-h