public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: "David S. Miller" <davem@redhat.com>
Cc: Jeff.Wiedemeier@hp.com, jgarzik@pobox.com,
	ink@jurassic.park.msu.ru, willy@debian.org,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 2.5] tg3.c: pci_{save,restore}_extended_state
Date: Sat, 25 Jan 2003 01:41:02 +0300	[thread overview]
Message-ID: <20030125014102.A825@localhost.park.msu.ru> (raw)
In-Reply-To: <20030124.133434.66251483.davem@redhat.com>; from davem@redhat.com on Fri, Jan 24, 2003 at 01:34:34PM -0800

On Fri, Jan 24, 2003 at 01:34:34PM -0800, David S. Miller wrote:
> Right, the whole issue is that we're generally MSI ignorant in our PCI
> layer right now.  And you're trying to make use of MSI on some
> platform :-)

Right. Alpha is way ahead, as usual. ;-)

> So because the driver has no way to ask the platform "are you going
> to use MSI for this device?" there is no way for tg3 to portably
> deal with this issue.
> 
> That being said, why don't we add "pci_using_msi(pdev)" to asm/pci.h?
> Once we have that, tg3.c can then go and set the tg3 specific MSI
> enable bit to match whatever pci_using_msi(pdev) returns.  This, plus
> the extended state save/restore, should solve all the problems.

I don't understand the issue, really. The config register says:
"MSIs are enabled". Which means: "My platform is *really* going to
use MSI". Why do you want to ignore that?
In the case when firmware has MSI enabled by mistake and it's known
that this platform cannot support MSI, we'll have a quirk that
fixes the config register. No?

Ivan.

  reply	other threads:[~2003-01-24 22:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-24 18:27 [patch 2.5] tg3.c: pci_{save,restore}_extended_state Ivan Kokshaysky
2003-01-24 19:31 ` Jeff Garzik
2003-01-24 19:34   ` David S. Miller
2003-01-24 20:00   ` Wiedemeier, Jeff
2003-01-24 19:53     ` David S. Miller
2003-01-24 20:04       ` Wiedemeier, Jeff
2003-01-24 20:05     ` Jeff Garzik
2003-01-24 20:24       ` Wiedemeier, Jeff
2003-01-24 20:34         ` Jeff Garzik
2003-01-24 20:46           ` Wiedemeier, Jeff
2003-01-24 20:51             ` David S. Miller
2003-01-24 21:33               ` Wiedemeier, Jeff
2003-01-24 21:34                 ` David S. Miller
2003-01-24 22:41                   ` Ivan Kokshaysky [this message]
2003-01-24 22:32                     ` David S. Miller
2003-01-24 22:51                       ` Jeff Garzik
2003-01-25  0:33                       ` Wiedemeier, Jeff
2003-01-25  1:42                         ` David S. Miller
2003-01-24 22:56                 ` Jeff Garzik

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=20030125014102.A825@localhost.park.msu.ru \
    --to=ink@jurassic.park.msu.ru \
    --cc=Jeff.Wiedemeier@hp.com \
    --cc=davem@redhat.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@debian.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