From owner-acpi-jp@jp.freebsd.org  Wed Oct 24 17:38:58 2001
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id RAA68132;
	Wed, 24 Oct 2001 17:38:58 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id RAA68107;
	Wed, 24 Oct 2001 17:38:39 +0900 (JST)
	(envelope-from max@vega.com)
Received: from vega.vega.com (h42.227.dialup.iptcom.net [212.9.227.42])
	by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id LAA25519;
	Wed, 24 Oct 2001 11:37:41 +0300 (EEST)
	(envelope-from max@vega.com)
Received: (from max@localhost)
	by vega.vega.com (8.11.6/8.11.3) id f9O8bAV99173;
	Wed, 24 Oct 2001 11:37:10 +0300 (EEST)
	(envelope-from sobomax@FreeBSD.org)
From: Maxim Sobolev <sobomax@FreeBSD.ORG>
Message-Id: <200110240837.f9O8bAV99173@vega.vega.com>
To: msmith@FreeBSD.ORG (Mike Smith)
Date: Wed, 24 Oct 2001 11:36:29 +0300 (EEST)
Cc: sobomax@FreeBSD.ORG (Maxim Sobolev),
        iwasaki@jp.FreeBSD.org (Mitsuru IWASAKI), ache@nagual.pp.ru,
        current@FreeBSD.ORG, acpi-jp@jp.FreeBSD.org
In-Reply-To: <no.id> from "Mike Smith" at Oct 24, 2001 12:52:50 AM
X-Mailer: ELM [version 2.5 PL5]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+010328
X-Sequence: acpi-jp 1363
Subject: [acpi-jp 1363] Re: ACPI: problem with fdc resource allocation
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: sobomax@FreeBSD.ORG

> 
> > > The problem is still here as of today's kernel. Please do
> > > something about it.
> > 
> > Should I reapeat how sad it is that this longstanding
> > problem is being completely ignored by the acpi
> > maintainer(s)?
> 
> No, I'd prefer that you found something constructive to do with your time.
> I'm not interested in being bitched out over something as trivial as this 
> when I have so much on my plate already; if you can't contribute, do me 
> the least favour and save me the angst.

What you expect me to do "constructive" about this? I've submitted
detailed report, tested some patches proposed by the Japanese
ACPI developers and so on. I do not see what else I could do to get
this problem resolved apart from bugging you from time to time.
Perhaps you have any better ideas, then please let me know. Also
if the problem is as trivial as you are describing, then it is highly
unclear why it is not fixed yet (some 6 weeks are passed since
initial report). I know several local guys with exactly the same
bug (some time ago I've convinced some them to swith to -current
and test/report any problems) and it is very sad to see my efforts
vanished, especially considering that the source of the problem is
located and as you said it is a "trivial" one.

-Maxim
