DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=r4lur+K5iEtRlesMEFDuA193zLm3f03VxuANjTO4glxgHpu/7pGFvBNl4B1js60Vbo
         KnQHvy+fGkv4d4k+kP3VVYJ/ZRYe1h+muQd38PT3VyYAyk0WxKt2RApabnbxvsu7xQDh
         GQeIGyMRa0WsMwNijIaXuo8mwfX8KVbf4gv8o=
MIME-Version: 1.0
In-Reply-To: <4C737E9F.7060107@gmail.com>
References: <1277673679-21458-1-git-send-email-jslaby@suse.cz>
	<4C27E965.80508@gmail.com>
	<4C283D84.6080504@suse.cz>
	<20100628171410.GA27367@srcf.ucam.org>
	<4C290245.2040001@suse.cz>
	<20100628204820.GA32503@srcf.ucam.org>
	<AANLkTil-sdbojCXBp6sR_4xL3JIe6ZENqXuueB61VJ8c@mail.gmail.com>
	<4C2A3E27.4060407@suse.cz>
	<AANLkTimkElR1u-iRyFfCEQR5VTZvcyEIGQodfmFNtbC_@mail.gmail.com>
	<4C2B0C73.9050200@suse.cz>
	<4C3278C8.60503@gmail.com>
	<4C447D6D.5060801@suse.cz>
	<AANLkTin9_yEyMZImRbtKTvTeokks8dz0htQCu0B3RqXH@mail.gmail.com>
	<4C456C69.60606@suse.cz>
	<4C737E9F.7060107@gmail.com>
Date: Tue, 24 Aug 2010 17:25:02 -0600
Message-ID: <AANLkTin7eUS7_y9J8iY1XFi2bRnpm+WqFNT_tBopwyCK@mail.gmail.com>
Subject: Re: [PATCH 1/1] ACPI: pci_irq, add PRT_ quirk for IBM Bartolo
From: Robert Hancock <hancockrwd@gmail.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Jiri Slaby <jslaby@suse.cz>, Matthew Garrett <mjg59@srcf.ucam.org>,
        lenb@kernel.org, linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
        linux-kernel@vger.kernel.org, Jesse Barnes <jbarnes@virtuousgeek.org>
Content-Type: text/plain; charset=ISO-8859-1
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 2005
Lines: 49

On Tue, Aug 24, 2010 at 2:11 AM, Jiri Slaby <jirislaby@gmail.com> wrote:
> On 07/20/2010 11:29 AM, Jiri Slaby wrote:
>> On 07/19/2010 09:19 PM, Robert Hancock wrote:
>>> On Mon, Jul 19, 2010 at 10:29 AM, Jiri Slaby <jslaby@suse.cz> wrote:
>>>>>> I still no point in comparing this to Windows' setup. We can't find out
>>>>>> whether it is quirked or better (without some bug) handled there.
>>>>>
>>>>> Well, you can see if Windows shows IRQ 10 or 11 for that device..
>>>>
>>>> But how can I find out which link it is routed to in Windows? Without
>>>> that information the number is meaningless, no?
>>>
>>> If you look at the pattern of which IRQs are shared by what devices in
>>> Linux and compare it to Windows you can get a good idea. Normally the
>>> assignment of devices to interrupt lines is hard-wired on the
>>> motherboard and doesn't change.
>>
>> Ok, thanks for the hint.
>>
>> What we've found out is that it works on 2.6.27 (with slightly changed
>> configuration).
>
> No, this was a false alarm. It never worked with acpi irq routing on
> older kernels in this HW configuration.
>
> So, to sum up:
> 1) acpi routing enabled (no kernel parameter) => ports 4+5 defunct.
> ports 4+5+6+7 are all on irq 11
>
> 2) acpi routing disabled (acpi=noirq) => all ports working, 4+5 on irq
> 10, 6+7 on irq 11
>
> 3) with the quirk [1] and acpi routing enabled => all ports working,
> ports 4+5 on irq 10, 6+7 on irq 11
>
> 4) in windows => 4+5+6+7 are all on irq 9 and the ports are all working.
>
> Any ideas what this means? Especially point 4)?
>
> [1] http://lkml.org/lkml/2010/6/27/85

I think that's the key question. Is Windows actually using ACPI on
that machine at all? (Check the computer type in Device Manager and
see if it mentions ACPI.)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/