From: Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
To: "Li, Shaohua" <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
"Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH] ACPI: Fix resource allocation for fixed hardware in MMIO
Date: Mon, 24 Oct 2005 08:53:46 -0600 [thread overview]
Message-ID: <200510240853.46382.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <59D45D057E9702469E5775CBB56411F1AF6FCF@pdsmsx406>
On Sunday 23 October 2005 7:24 pm, Li, Shaohua wrote:
> Hi Bjorn,
> >> ACPI supports fixed hardware (PM_TMR, GPE blocks, etc) in either
> >> I/O port or MMIO space, but used to always request the regions from
> >> I/O space, even for MMIO hardware.
> >
> ><poke> any news on this or the following few patches? Should I
> >resend them?
> I missed this before. Should we do the same thing in
> 'acpi_reserve_io_ranges' and in pnp system.c?
Yes, probably so. Thanks for pointing that out. I'll update
the patch.
> The resources listed in
> acpi_gbl_FADT generally also listed in motherboard devices (PNP0C01,
> PNP0C02). We doubly request it is to workaround some buggy BIOS.
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
next prev parent reply other threads:[~2005-10-24 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-24 1:24 [PATCH] ACPI: Fix resource allocation for fixed hardware in MMIO Li, Shaohua
2005-10-24 14:53 ` Bjorn Helgaas [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-16 17:34 Bjorn Helgaas
[not found] ` <200509161134.24735.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2005-10-20 18:43 ` Bjorn Helgaas
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=200510240853.46382.bjorn.helgaas@hp.com \
--to=bjorn.helgaas-vxdhtt5mjny@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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