From: Adam Belay <abelay-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>
To: Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
Cc: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Shaohua Li <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH] PNPACPI: don't complain about vendor-defined resources
Date: Fri, 11 Mar 2005 19:25:27 -0500 [thread overview]
Message-ID: <1110587127.12485.236.camel@localhost.localdomain> (raw)
In-Reply-To: <1110587005.4822.95.camel@eeyore>
On Fri, 2005-03-11 at 17:23 -0700, Bjorn Helgaas wrote:
> On Fri, 2005-03-11 at 19:07 -0500, Adam Belay wrote:
> > On Wed, 2005-03-09 at 00:09 -0500, Len Brown wrote:
> > > Applied.
> > >
> > > thanks,
> > > -Len
> >
> > Just out of curiosity, are we seeing many vendor-defined resources from
> > ACPI?
>
> HP boxes have some. Our host-to-AGP bridge, IOMMU, etc have them to
> tell you where the device's MMIO CSR space is.
Hmm, interesting. I'm asking because I was considering how necessary it
would be to pass this information down to actual drivers.
Thanks,
Adam
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-12 0:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 22:14 [PATCH] PNPACPI: don't complain about vendor-defined resources Bjorn Helgaas
2005-03-09 5:09 ` Len Brown
2005-03-12 0:07 ` Adam Belay
[not found] ` <1110586059.12485.225.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-03-12 0:23 ` Bjorn Helgaas
2005-03-12 0:25 ` Adam Belay [this message]
[not found] ` <1110587127.12485.236.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-03-12 16:54 ` 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=1110587127.12485.236.camel@localhost.localdomain \
--to=abelay-et1tbqhtxzrqt0dzr+alfa@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=bjorn.helgaas-VXdhtT5mjnY@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