Date: Wed, 17 Sep 2008 11:37:32 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-stable@freebsd.org Cc: KAHO Toshikazu <vinwa@rocky.kais.kyoto-u.ac.jp> Subject: Re: alpm(4) I/O range is claimed by ACPI Message-ID: <200809171137.32759.jhb@freebsd.org> In-Reply-To: <200809170258.m8H2wsrO064420@pf2.ed.niigata-u.ac.jp> References: <48CD1C54.7040208@incunabulum.net> <200809131109.06694.jhb@freebsd.org> <200809170258.m8H2wsrO064420@pf2.ed.niigata-u.ac.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 16 September 2008 10:58:54 pm KAHO Toshikazu wrote: > Hello, > > I am sorry to mistake copying message-id and break mail thread. > > >> I tried looking for this device in the DSDT, I don't see anything which > >> obviously resembles it. The equivalent Linux driver has a means of > >> forcing the mapping to be set up if it isn't available: > >> http://www.kernel.org/doc/Documentation/i2c/busses/i2c-ali15x3 > >> > >> It looks like there used to be a means of doing this in the FreeBSD > >> driver but it got nuked. And that ASUS didn't much care about power > >> management support in this machine... > > > >If you can re-enable it in such a way that it uses bus_alloc_resource(), then > >the driver will probably work fine. > > How to re-enable it? Please give me some points. PCIR_BAR is always 0, > even if any values are written by pciconf. Well, bus_alloc_resource() will allocate resources for the BAR and update the BAR for you, the question is if you need to hardcode the range to bus_alloc_resource() or not. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200809171137.32759.jhb>