From: matthieu castet <castet.matthieu-GANU6spQydw@public.gmane.org>
To: Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Shaohua Li <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Adam Belay <ambx1-IBH0VoN/3vPQT0dZR+AlfA@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Re: [PATCH] PNPACPI: fix types when decoding ACPI resources [resend]
Date: Thu, 04 Aug 2005 14:38:51 +0200 [thread overview]
Message-ID: <42F20C5B.3020506@free.fr> (raw)
In-Reply-To: <200508031541.53777.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
Hi,
Bjorn Helgaas wrote:
> On Wednesday 03 August 2005 3:16 pm, matthieu castet wrote:
>
>>Bjorn Helgaas wrote:
>> > drivers/char/hpet.c
>> > This probably should be converted to PNP. I'll
>> > look into doing this.
>>IIRC, I am not sure that the pnp layer was able to pass the 64 bits
>>memory adress for hpet correctly. But it would be nice if it works.
>
>
> You're right, this was broken. But I've been pushing a PNPACPI
> patch to fix this.
>
>
Yes but is ACPI_RSTYPE_ADDRESS64 possible on 32 bit machine ?
In this case your patch won't work as res->mem_resource[i].start and
res->mem_resource[i].end are unsigned long, and 64 bit value won't fit.
Matthieu
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next prev parent reply other threads:[~2005-08-04 12:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 15:55 [PATCH] PNPACPI: fix types when decoding ACPI resources [resend] Bjorn Helgaas
[not found] ` <200508020955.54844.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2005-08-03 1:01 ` Shaohua Li
[not found] ` <1123030861.2937.4.camel-ECwVeV2eNyQD0+JXs3kMbRL4W9x8LtSr@public.gmane.org>
2005-08-03 15:20 ` Bjorn Helgaas
[not found] ` <200508030920.13450.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2005-08-03 21:16 ` matthieu castet
[not found] ` <42F1343B.70707-GANU6spQydw@public.gmane.org>
2005-08-03 21:41 ` Bjorn Helgaas
[not found] ` <200508031541.53777.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2005-08-04 12:38 ` matthieu castet [this message]
[not found] ` <42F20C5B.3020506-GANU6spQydw@public.gmane.org>
2005-08-04 15:57 ` Bjorn Helgaas
[not found] ` <200508040957.55485.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2005-08-04 16:08 ` matthieu castet
2005-08-04 0:51 ` Shaohua Li
2005-08-28 17:40 ` [ACPI] " matthieu castet
2005-08-04 0:46 ` Shaohua Li
2005-08-03 1:05 ` Kenji Kaneshige
[not found] ` <42F0185A.7060901-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2005-08-03 18:29 ` Bjorn Helgaas
[not found] ` <200508031229.05343.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2005-08-04 5:18 ` Kenji Kaneshige
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=42F20C5B.3020506@free.fr \
--to=castet.matthieu-ganu6spqydw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ambx1-IBH0VoN/3vPQT0dZR+AlfA@public.gmane.org \
--cc=bjorn.helgaas-VXdhtT5mjnY@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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