From: Marcus Meissner <Marcus.Meissner@caldera.de>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Marcus Meissner <Marcus.Meissner@caldera.de>,
linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] misplaced pci_enable_device()s in drivers/sound/
Date: Wed, 18 Apr 2001 19:20:36 +0200 [thread overview]
Message-ID: <20010418192036.A30279@caldera.de> (raw)
In-Reply-To: <20010418182944.A25024@caldera.de> <3ADDC716.7F5B43C8@mandrakesoft.com>
In-Reply-To: <3ADDC716.7F5B43C8@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Wed, Apr 18, 2001 at 12:55:50PM -0400
On Wed, Apr 18, 2001 at 12:55:50PM -0400, Jeff Garzik wrote:
> Marcus Meissner wrote:
> > Several pci_enable_device()s in drivers/sound happen _after_ accessing
> > PCI resources. I have moved them before the relevant first accesses.
>
> cool
>
> > if (!RSRCISIOREGION(pcidev, 0))
> > return -1;
>
> can you replace this mess while you are cleaning stuff up. this, for
> example, should be
> if (!(pci_resource_flags(pcidev,) & IORESOURCE_IO))
>
> There is also pci_resource_start and pci_resource_len.
>
> > iobase = SILLY_PCI_BASE_ADDRESS(pcidev);
>
> pci_resource_start
THere is also some pci dma stuff which probably got changed.
> patch looks ok to me, but those would be nice additions...
I am a bit afraid to break stuff doing this without testing, but I will
do it for the cards I have access to.
Is there a 'HOW TO DO IT' PCI driver?
drivers/net/pci-skeleton.c looks up to date, is it?
Ciao, Marcus
prev parent reply other threads:[~2001-04-18 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-18 16:29 [PATCH] misplaced pci_enable_device()s in drivers/sound/ Marcus Meissner
2001-04-18 16:55 ` Jeff Garzik
2001-04-18 17:20 ` Marcus Meissner [this message]
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=20010418192036.A30279@caldera.de \
--to=marcus.meissner@caldera.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@mandrakesoft.com \
--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