From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 916D8C072B5 for ; Fri, 24 May 2019 06:39:19 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 2387B21841 for ; Fri, 24 May 2019 06:39:19 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=duncanthrax.net header.i=@duncanthrax.net header.b="NvmficCX" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388887AbfEXGjS (ORCPT ); Fri, 24 May 2019 02:39:18 -0400 Received: from smtp.duncanthrax.net ([89.31.1.170]:36812 "EHLO smtp.duncanthrax.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388580AbfEXGjS (ORCPT ); Fri, 24 May 2019 02:39:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=duncanthrax.net; s=dkim; h=In-Reply-To:Content-Type:MIME-Version:References :Message-ID:Subject:Cc:To:From:Date; bh=t7FxIPGRaX15FYe2B+VUKDr5S28k9TFwjC3Q6tVuykI=; b=NvmficCXIn3J/9a1TKexfynORT 7Mq7esEQlmqmeiSK5TS3b42fYNpYqjaGPaiij0JGrGOtjuDuEsgX3KcwP8lW7t7f4/n/7SSh2JN82 iFcYAVXahkw+DE435RBwTjzHDtfCtEGfnDdTR+fWuU/6QM8E2eQ55uLKUqwB0tV9X7b4=; Received: from frobwit.duncanthrax.net ([89.31.1.178] helo=t470p.stackframe.org) by smtp.eurescom.eu with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from ) id 1hU3rI-0002m7-43; Fri, 24 May 2019 08:39:16 +0200 Date: Fri, 24 May 2019 08:39:09 +0200 From: Sven Schnelle To: Grant Grundler Cc: Carlo Pisani , John David Anglin , linux-parisc Subject: Re: HPPA problems with the PCI Message-ID: <20190524063909.GA9661@t470p.stackframe.org> References: <21dcf273-929a-6fb1-7978-37145ea62301@bell.net> <483d54a6-cbf4-e366-60b3-ae84d025d0e6@bell.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-parisc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-parisc@vger.kernel.org Hi Grant, On Thu, May 23, 2019 at 04:09:34PM -0700, Grant Grundler wrote: > > AFAIK, parisc never used firmware to route IRQ lines. For starters, > the CPUs never had an IRQ input and always used messages (equivalent > to MMIO writes) directed at a CPUs EIEM register. I think you mean EIRR here? Regards Sven