From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Vojtech Pavlik <vojtech@suse.cz>,
Peter Osterlund <petero2@telia.com>,
Patrick Mochel <mochel@osdl.org>, Tobias Diedrich <ranma@gmx.at>,
Alessandro Suardi <alessandro.suardi@oracle.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.5.20 - Xircom PCI Cardbus doesn't work
Date: Fri, 14 Jun 2002 15:31:40 -0400 [thread overview]
Message-ID: <3D0A449C.5030304@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0206141308100.31514-100000@chaos.physics.uiowa.edu>
Kai Germaschewski wrote:
> On Fri, 14 Jun 2002, Linus Torvalds wrote:
>
>
>>I suspect that forcing resource assignment into "pci_enable_device()"
>>should fix that too.
>>
>>Although there should probably be some way for the driver to tell which
>>resources it cares about (some drivers care about the PCI ROM's, for
>>example, others don't. Some drivers don't care about the IO region, and
>>others don't care about the MEM region). So the _right_ answer might be to
>>pass in a bitmap to "pci_enable_device()", which tells the enable code
>>which parts the driver really cares about..
>
>
> That reminds me of some idea I had been thinking about for some time:
>
> What about adding some pci_request_irq() and pci_request_{,mem_}_region,
> which would allow for some cleanup of ever-recurring code sequences in
> drivers, and which at the same time would allow for the above?
> pci_request_mem_region() might even include the ioremap() as well ;)
We already have pci_request_regions() and currently PCI drivers should
use that.
Auto-ioremap would be bad, though... you would wind up wasting address
space for any case where MMIO areas are not 100% utilized (like network
cards that require use of PIO due to hardware bugs, but still export an
MMIO region for their NIC registers)
Jeff
next prev parent reply other threads:[~2002-06-14 19:35 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-03 11:07 2.5.20 - Xircom PCI Cardbus doesn't work Alessandro Suardi
2002-06-06 17:08 ` Peter Osterlund
2002-06-09 9:17 ` Tobias Diedrich
2002-06-09 10:55 ` Peter Osterlund
2002-06-10 15:44 ` Patrick Mochel
2002-06-10 19:28 ` Peter Osterlund
2002-06-14 16:33 ` Linus Torvalds
2002-06-14 17:20 ` Peter Osterlund
2002-06-14 17:47 ` Linus Torvalds
2002-06-14 17:53 ` Vojtech Pavlik
2002-06-14 18:05 ` Linus Torvalds
2002-06-14 18:12 ` Kai Germaschewski
2002-06-14 18:18 ` Linus Torvalds
2002-06-14 19:37 ` Jeff Garzik
2002-06-15 18:48 ` Linus Torvalds
2002-06-15 19:05 ` Linus Torvalds
2002-06-15 19:39 ` Kai Germaschewski
2002-06-15 19:58 ` Jeff Garzik
2002-06-15 23:00 ` Kai Germaschewski
2002-06-15 20:07 ` Jeff Garzik
2002-06-15 22:51 ` Kai Germaschewski
2002-06-14 19:31 ` Jeff Garzik [this message]
2002-06-14 23:25 ` Kai Germaschewski
2002-06-14 23:53 ` Jeff Garzik
2002-06-15 8:25 ` Ingo Oeser
2002-06-14 19:34 ` Jeff Garzik
2002-06-14 18:30 ` Peter Osterlund
2002-06-14 18:51 ` Linus Torvalds
2002-06-14 20:07 ` Peter Osterlund
2002-06-15 2:42 ` Paul Mackerras
2002-06-15 21:58 ` Cardbus Linus Torvalds
2002-06-16 7:01 ` Cardbus Eric W. Biederman
2002-06-16 8:18 ` Cardbus Paul Mackerras
2002-06-10 20:59 ` 2.5.20 - Xircom PCI Cardbus doesn't work Alessandro Suardi
2002-06-16 4:57 ` Linus Torvalds
2002-06-16 7:40 ` Peter Osterlund
2002-06-16 18:16 ` Linus Torvalds
2002-06-16 18:42 ` Martin Dalecki
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=3D0A449C.5030304@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alessandro.suardi@oracle.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=petero2@telia.com \
--cc=ranma@gmx.at \
--cc=torvalds@transmeta.com \
--cc=vojtech@suse.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