From: matthieu castet <castet.matthieu@free.fr>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: acpi-devel@lists.sourceforge.net,
Shaohua Li <shaohua.li@intel.com>, Adam Belay <ambx1@neo.rr.com>,
linux-kernel@vger.kernel.org
Subject: Re: [ACPI] Re: [PATCH] PNPACPI: fix types when decoding ACPI resources [resend]
Date: Thu, 04 Aug 2005 18:08:16 +0200 [thread overview]
Message-ID: <42F23D70.5010201@free.fr> (raw)
In-Reply-To: <200508040957.55485.bjorn.helgaas@hp.com>
Bjorn Helgaas wrote:
> On Thursday 04 August 2005 6:38 am, matthieu castet wrote:
>
>>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 ?
>
>
> I can't think of a case where that would make sense, but I don't
> actually know the answer.
>
>
>>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.
>
>
> True. But fixing that would be pretty far-reaching (changing struct
> resource), so I'm not worried until it is shown to be a problem.
>
Ok, may be you could add a BUG_ON(sizeof(long)==4) for
ACPI_RSTYPE_ADDRESS64.
Matthieu
next prev parent reply other threads:[~2005-08-04 16:09 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
2005-08-03 1:01 ` Shaohua Li
2005-08-03 15:20 ` [ACPI] " Bjorn Helgaas
2005-08-03 21:16 ` matthieu castet
2005-08-03 21:41 ` Bjorn Helgaas
2005-08-04 12:38 ` matthieu castet
2005-08-04 15:57 ` Bjorn Helgaas
2005-08-04 16:08 ` matthieu castet [this message]
2005-08-04 0:51 ` Shaohua Li
2005-08-28 17:40 ` matthieu castet
2005-08-04 0:46 ` Shaohua Li
2005-08-03 1:05 ` [ACPI] " Kenji Kaneshige
2005-08-03 18:29 ` Bjorn Helgaas
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=42F23D70.5010201@free.fr \
--to=castet.matthieu@free.fr \
--cc=acpi-devel@lists.sourceforge.net \
--cc=ambx1@neo.rr.com \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
/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