ACPI 5 PCI removal
qhwt+dragonfly-submit at les.ath.cx
Thu Jul 1 21:10:37 PDT 2004
First of all -- I tried your patch, and found that suspend via acpiconf
still works, and nothing seems to have changed so far, so I don't have
strong objection in removing pci codes from the build.
On Fri, Jul 02, 2004 at 12:09:12AM +0200, Joerg Sonnenberger wrote:
> On Fri, Jul 02, 2004 at 01:52:03AM +0900, YONETANI Tomokazu wrote:
> > How "broken" is it for you by the way? And is it broken for other people
> > as well?
> I'm not sure _how_ broken exactly it is. It can't work as intended, because
> DF works still differently than FreeBSD 5 [and will be]. The reason I want
> to not include or disable it is to ensure that it doesn't cause problems
> and to avoid the clutter it generates e.g. by adding another nexus-pci
> Let me ask the question reverse, do you know of any use of this specific
Not exactly. I wanted to know whatever breakage my (older) patch has
introduced, that is not so obvious on my PCs. Apologies to you if my words
had any offensive tone, that's not what I intended.
> I can live with Matt's suggestion to switch the default meaning of
> the driver [and use a tunable in hw.acpi or so for it], but right now
> don't want to work on a patch, if I can simple skip this code with the
> same result.
The problem I can think of is what subsystem to disable by default: PCI code
doesn't work for you, thermal code locks up other peoples' PC, and so on.
So the safest way is to disable everything by default, and let users to
decide what subsystems to activate.
More information about the Submit