From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758998AbcG1QB7 (ORCPT ); Thu, 28 Jul 2016 12:01:59 -0400 Received: from imap.thunk.org ([74.207.234.97]:53398 "EHLO imap.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758898AbcG1QBw (ORCPT ); Thu, 28 Jul 2016 12:01:52 -0400 Date: Thu, 28 Jul 2016 12:01:45 -0400 From: "Theodore Ts'o" To: Greg KH Cc: Max Staudt , One Thousand Gnomes , linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] 8250: option 'force_polling' for buggy IRQs Message-ID: <20160728160145.GB27400@thunk.org> Mail-Followup-To: Theodore Ts'o , Greg KH , Max Staudt , One Thousand Gnomes , linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org References: <1469468175-15704-1-git-send-email-mstaudt@suse.de> <20160725174712.GA5752@kroah.com> <20160726150856.GA15676@kroah.com> <20160727130923.4c20524b@lxorguk.ukuu.org.uk> <2b140616-c210-e754-a854-cd6a5675277d@suse.de> <20160727133348.GB20032@thunk.org> <20160728144704.GA12984@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160728144704.GA12984@kroah.com> User-Agent: Mutt/1.6.0 (2016-04-01) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: tytso@thunk.org X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 28, 2016 at 07:47:04AM -0700, Greg KH wrote: > > I agree, and I thought about it, but since this is meant for a very limited > > audience, I think a catch-all is the easiest solution - both in terms of > > implementation as well as ease of use. > > > > It's not meant for general consumption anyway. > > Then I really don't want to have to maintain and support such a kernel > option for 20+ years, just because of one broken system out there like > this. There are workarounds for this, as you have seen, including > booting with a "real" userspace, so I don't want to take this patch. One way to make this a bit more general purpose would be too add a way to configure ttyS0 completely --- e.g., being able to specify the port, irq, uart type, flags, etc. It still wouldn't be needed except for very rarely (since either serial ports use self-configuring buses --- e.g., USB, PCI, etc.) or they use the legacy x86 ports. So perhaps Greg might be more willing to take that kind of change, but even then, it could be argued that the maintaining such a kernel option for just a few non-standard or broken systems is still not worth it, but it would at least be somewhat more general purpose. - Ted