public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Jochen Friedrich <jochen@scram.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	dahinds@users.sourceforge.net
Subject: Re: PCI1410 Interrupt Problems
Date: Fri, 8 Aug 2003 09:51:26 +0100	[thread overview]
Message-ID: <20030808095126.B32585@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0308080739400.6802-100000@gfrw1044.bocc.de>; from jochen@scram.de on Fri, Aug 08, 2003 at 07:40:19AM +0200

On Fri, Aug 08, 2003 at 07:40:19AM +0200, Jochen Friedrich wrote:
> Hi Russel,

Grumble.

> > I notice your lspci didn't list a subvendor / subdevice ID for your
> > cardbus bridges - can you confirm by reporting the output of:
> >
> > # setpci -s bus:slot.func 0x40.l
> 
> rt1-sp:~# setpci -s 00:11.0 0x40.l
> 00000000

Ok, so no subvendor/subdevice IDs to identify the hardware variant.
Hmm, this isn't going to be an easy one to automatically fix up.
Maybe we can pick up on the host bridge IDs - can you send me the
complete output of lspci -vv please?

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2003-08-08  8:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-03 20:15 PCI1410 Interrupt Problems Jochen Friedrich
2003-08-03 21:23 ` Russell King
2003-08-03 21:52   ` Jochen Friedrich
2003-08-06 23:09     ` Russell King
2003-08-08  5:40       ` Jochen Friedrich
2003-08-08  8:51         ` Russell King [this message]
2003-08-08 17:09           ` Jochen Friedrich
2003-08-11 18:33       ` Jochen Friedrich
2003-08-11 19:00         ` David Hinds
2003-08-12  8:59           ` Russell King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030808095126.B32585@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=dahinds@users.sourceforge.net \
    --cc=jochen@scram.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox