public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Valdis.Kletnieks@vt.edu
Cc: Petr Konecny <pekon@informatics.muni.cz>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.5[01]]: Xircom Cardbus broken (PCI resource collisions)
Date: Fri, 13 Dec 2002 17:36:56 +0000	[thread overview]
Message-ID: <20021213173656.GC1633@suse.de> (raw)
In-Reply-To: <200212131718.gBDHIw27008173@turing-police.cc.vt.edu>

On Fri, Dec 13, 2002 at 12:18:58PM -0500, Valdis.Kletnieks@vt.edu wrote:
 > On Fri, 13 Dec 2002 17:33:00 +0100, Petr Konecny <pekon@informatics.muni.cz>  said:
 > > > I see why the if/continue was added - you don't want to be
 > > > calling device_register()/pci_insert_device() if
 > > > pci_enable_device() loses.  I don't see why 2.5.50 moved the
 > > > code up after pci_setup_device(). There's an outside chance
 > > > that the concept of moving the call was correct, but that it
 > > > should have been moved to between the calls to
 > > > pci_assign_resource() and pci_readb().  If that's the case,
 > > > then you're correct as well....
 > > I can confirm that this indeed works. I moved the two lines before
 > > pci_readb and the card works (every character you now read went through
 > > it). Who shall submit a patch to Linus ?
 > 
 > The problem is this from the 2.5.50 Changelog that Linus posted:
 > 
 > Dave Jones <davej@suse.de>:
 > ...
 >   o make cardbus PCI enable earlier
 > 
 > I'm willing to submit a patch, but I think Dave has to make the call whether
 > it should be backed out entirely, or moved after pci_assign_resource().
 > I certainly don't understand the code *or* PCI well enough to decide between
 > those two option...

It's my understanding that pci_enable_device() *must* be called
before we fiddle with dev->resource, dev->irq and the like.

		Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  reply	other threads:[~2002-12-13 17:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-12 22:47 2.5.5[01]]: Xircom Cardbus broken (PCI resource collisions) Valdis.Kletnieks
2002-12-13  0:43 ` Greg KH
2002-12-13  4:22   ` Valdis.Kletnieks
2002-12-13 10:10 ` Arjan van de Ven
2002-12-13 13:45   ` Valdis.Kletnieks
2002-12-13 16:17     ` Petr Konecny
     [not found]     ` <200212131633.gBDGX0617899@anxur.fi.muni.cz>
2002-12-13 17:18       ` Valdis.Kletnieks
2002-12-13 17:36         ` Dave Jones [this message]
2002-12-13 18:46           ` Valdis.Kletnieks
2002-12-14  0:18             ` Zwane Mwaikambo
2002-12-13 19:03           ` Jeff Garzik
2002-12-14  3:43             ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-12-14 17:28 ALESSANDRO.SUARDI
2002-12-16 14:54 ` Valdis.Kletnieks
2002-12-12 14:10 Alessandro Suardi

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=20021213173656.GC1633@suse.de \
    --to=davej@codemonkey.org.uk \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pekon@informatics.muni.cz \
    /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