From: Shaohua Li <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Bjorn Helgaas <bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Adam Belay <ambx1-IBH0VoN/3vPQT0dZR+AlfA@public.gmane.org>,
Matthieu Castet <castet.matthieu-GANU6spQydw@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 08:46:35 +0800 [thread overview]
Message-ID: <1123116395.2929.1.camel@linux-hp.sh.intel.com> (raw)
In-Reply-To: <200508030920.13450.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
On Wed, 2005-08-03 at 09:20 -0600, Bjorn Helgaas wrote:
> On Tuesday 02 August 2005 7:01 pm, Shaohua Li wrote:
> > On Tue, 2005-08-02 at 09:55 -0600, Bjorn Helgaas wrote:
> > > Any objections to the patch below? I posted it last Wednesday,
> > > but haven't heard anything. Once we have this fix, 8250_pnp
> > > should have sufficient functionality that we can get rid of
> > > 8250_acpi.
> > >
> > > Use types that match the ACPI resource structures. Previously
> > > the u64 value from an RSTYPE_ADDRESS64 was passed as an int,
> > > which corrupts the value.
> > >
> > > This is one of the things that prevents 8250_pnp from working
> > > on HP ia64 boxes. After 8250_pnp works, we will be able to
> > > remove 8250_acpi.c.
> > We might always use 'unsigned long'.
>
> Do you have a reason for preferring 'unsigned long' over the
> exact types used in the ACPI resource structures? I thought
> it was useful to use the exact types, because then whatever
> conversion needs to happen is all in one place.
>
> In the existing code, there's implicit conversion when you
> call "pnpacpi_parse_allocated_memresource(..., int mem, int len)"
> and pass u64 values as "mem" and "len". You have to look both
> at the call site and the called code. And gcc doesn't even
> complain about this truncation.
>
> But I guess it doesn't matter much either way.
Either is ok to me.
>
> > Did you have plan to remove other
> > legacy acpi drivers?
>
> No, I didn't -- which ones are you thinking about? Looking at
> the callers of acpi_bus_register_driver(), I see:
>
> arch/ia64/hp/common/sba_iommu.c
> Probably can't be converted because it needs the
> ACPI handle to extract a vendor-specific data
> item from _CRS.
>
> drivers/char/hpet.c
> This probably should be converted to PNP. I'll
> look into doing this.
Great! After then we could push the ACPIPNP hotplug staff.
Thanks,
Shaohua
-------------------------------------------------------
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
WARNING: multiple messages have this Message-ID (diff)
From: Shaohua Li <shaohua.li@intel.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: acpi-devel@lists.sourceforge.net, Adam Belay <ambx1@neo.rr.com>,
Matthieu Castet <castet.matthieu@free.fr>,
linux-kernel@vger.kernel.org
Subject: Re: [ACPI] Re: [PATCH] PNPACPI: fix types when decoding ACPI resources [resend]
Date: Thu, 04 Aug 2005 08:46:35 +0800 [thread overview]
Message-ID: <1123116395.2929.1.camel@linux-hp.sh.intel.com> (raw)
In-Reply-To: <200508030920.13450.bjorn.helgaas@hp.com>
On Wed, 2005-08-03 at 09:20 -0600, Bjorn Helgaas wrote:
> On Tuesday 02 August 2005 7:01 pm, Shaohua Li wrote:
> > On Tue, 2005-08-02 at 09:55 -0600, Bjorn Helgaas wrote:
> > > Any objections to the patch below? I posted it last Wednesday,
> > > but haven't heard anything. Once we have this fix, 8250_pnp
> > > should have sufficient functionality that we can get rid of
> > > 8250_acpi.
> > >
> > > Use types that match the ACPI resource structures. Previously
> > > the u64 value from an RSTYPE_ADDRESS64 was passed as an int,
> > > which corrupts the value.
> > >
> > > This is one of the things that prevents 8250_pnp from working
> > > on HP ia64 boxes. After 8250_pnp works, we will be able to
> > > remove 8250_acpi.c.
> > We might always use 'unsigned long'.
>
> Do you have a reason for preferring 'unsigned long' over the
> exact types used in the ACPI resource structures? I thought
> it was useful to use the exact types, because then whatever
> conversion needs to happen is all in one place.
>
> In the existing code, there's implicit conversion when you
> call "pnpacpi_parse_allocated_memresource(..., int mem, int len)"
> and pass u64 values as "mem" and "len". You have to look both
> at the call site and the called code. And gcc doesn't even
> complain about this truncation.
>
> But I guess it doesn't matter much either way.
Either is ok to me.
>
> > Did you have plan to remove other
> > legacy acpi drivers?
>
> No, I didn't -- which ones are you thinking about? Looking at
> the callers of acpi_bus_register_driver(), I see:
>
> arch/ia64/hp/common/sba_iommu.c
> Probably can't be converted because it needs the
> ACPI handle to extract a vendor-specific data
> item from _CRS.
>
> drivers/char/hpet.c
> This probably should be converted to PNP. I'll
> look into doing this.
Great! After then we could push the ACPIPNP hotplug staff.
Thanks,
Shaohua
next prev parent reply other threads:[~2005-08-04 0:46 UTC|newest]
Thread overview: 27+ 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-02 15:55 ` Bjorn Helgaas
[not found] ` <200508020955.54844.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2005-08-03 1:01 ` Shaohua Li
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
2005-08-03 15:20 ` [ACPI] " Bjorn Helgaas
[not found] ` <200508030920.13450.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2005-08-03 21:16 ` matthieu castet
2005-08-03 21:16 ` [ACPI] " matthieu castet
[not found] ` <42F1343B.70707-GANU6spQydw@public.gmane.org>
2005-08-03 21:41 ` Bjorn Helgaas
2005-08-03 21:41 ` [ACPI] " Bjorn Helgaas
[not found] ` <200508031541.53777.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2005-08-04 12:38 ` matthieu castet
2005-08-04 12:38 ` [ACPI] " matthieu castet
[not found] ` <42F20C5B.3020506-GANU6spQydw@public.gmane.org>
2005-08-04 15:57 ` Bjorn Helgaas
2005-08-04 15:57 ` [ACPI] " Bjorn Helgaas
[not found] ` <200508040957.55485.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2005-08-04 16:08 ` matthieu castet
2005-08-04 16:08 ` [ACPI] " matthieu castet
2005-08-04 0:51 ` Shaohua Li
2005-08-04 0:51 ` [ACPI] " Shaohua Li
2005-08-28 17:40 ` matthieu castet
2005-08-04 0:46 ` Shaohua Li [this message]
2005-08-04 0:46 ` Shaohua Li
2005-08-03 1:05 ` Kenji Kaneshige
2005-08-03 1:05 ` [ACPI] " Kenji Kaneshige
[not found] ` <42F0185A.7060901-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2005-08-03 18:29 ` Bjorn Helgaas
2005-08-03 18:29 ` [ACPI] " Bjorn Helgaas
[not found] ` <200508031229.05343.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2005-08-04 5:18 ` Kenji Kaneshige
2005-08-04 5:18 ` [ACPI] " 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=1123116395.2929.1.camel@linux-hp.sh.intel.com \
--to=shaohua.li-ral2jqcrhueavxtiumwx3w@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=castet.matthieu-GANU6spQydw@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.