From: Christoph Hellwig <hch@ns.caldera.de>
To: kai@tp1.ruhr-uni-bochum.de (Kai Germaschewski)
Cc: linux-kernel@vger.kernel.org, kaos@ocs.com.au
Subject: Re: 2.4.8-pre4, lots of compile warnings
Date: Mon, 6 Aug 2001 14:13:50 +0200 [thread overview]
Message-ID: <200108061213.f76CDoE05527@ns.caldera.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0108061155480.8689-100000@chaos.tp1.ruhr-uni-bochum.de>
In article <Pine.LNX.4.33.0108061155480.8689-100000@chaos.tp1.ruhr-uni-bochum.de> you wrote:
> On Mon, 6 Aug 2001, Keith Owens wrote:
>
>> Add attribute unused plus a BIG comment saying that the code should be
>> moved to the new pci infrastructure ASAP. Add the code to the janitor
>> list.
>
> Moving to the new pci infrastructure is not an option for the
> drivers/isdn/hisax driver. For historical reasons, it doesn't use
> autoprobing, changing that now will break initializiation on probably
> every distribution out there (if it supports ISDN).
There is another way to at lest use the pci tables without going for
the full hotplug API.
Just replace code like:
if ((dev_avm = pci_find_device(PCI_VENDOR_ID_AVM,
PCI_DEVICE_ID_AVM_A1, dev_avm))) {
/* initialize card */
}
with something like:
pci_for_each_dev(dev_avm) {
if (pci_match_device(avm_pci_tbl, dev_avm)) {
/* initialize card */
}
}
This will need per-card instead of the current global hisax pci tables,
but I think it's a good cleanup.
> I'll break this compatibility in 2.5, though.
Nice! Does this mean the hisax subdrivers will finally be able to be
individual modules? Are there also other ISDN changes planned, e.g.
going from the global cli/sti to better locking schemes?
Christoph
--
Whip me. Beat me. Make me maintain AIX.
next prev parent reply other threads:[~2001-08-06 12:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-06 5:46 2.4.8-pre4, lots of compile warnings Keith Owens
2001-08-06 9:49 ` Kai Germaschewski
2001-08-06 9:52 ` Keith Owens
2001-08-06 10:54 ` Kai Germaschewski
2001-08-06 12:13 ` Christoph Hellwig [this message]
2001-08-06 12:50 ` Kai Germaschewski
2001-08-06 22:25 ` Matthew Gardiner
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=200108061213.f76CDoE05527@ns.caldera.de \
--to=hch@ns.caldera.de \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=kaos@ocs.com.au \
--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