[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1508021150520.3825@nanos>
Date: Sun, 2 Aug 2015 11:52:53 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Taichi Kageyama <t-kageyama@...jp.nec.com>
cc: Peter Hurley <peter@...leysoftware.com>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"jiang.liu@...ux.intel.com" <jiang.liu@...ux.intel.com>,
"linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"jslaby@...e.cz" <jslaby@...e.cz>,
"prarit@...hat.com" <prarit@...hat.com>,
Naoya Horiguchi <n-horiguchi@...jp.nec.com>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [RFC PATCH v2 0/3] genirq, serial: 8250: Workaround to avoid
irq=0 for console
On Fri, 31 Jul 2015, Taichi Kageyama wrote:
> On 2015/07/31 8:43, Peter Hurley wrote:
> >> If you look at the actual autoprobe users aside of 8250. That's really
> >> all ancient ISA hardware and hardly interesting. So all we really care
> >> about are the 8250 serial ports.
>
> In this case, I think [patch v2 1/3] is enough.
> console_lock is required in autoconfig_irq() to resolve other race conditions
> before calling probe_irq_on().
Fine with me.
> >> So why are you interested in that serial irq autoprobe crap at all?
> >
> Because RHEL6 uses CONFIG_SERIAL_8250_DETECT_IRQ=y unfortunately.
Doh!
> I already got the following console solutions after discussion with Peter.
> - Force set irq before any APs and getty open /dev/console.
> Users have to know valid irq#.
> - Fix FW to define PNP
> - CONFIG_SERIAL_8250_DETECT_IRQ=n
Ack!
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists