From: keith <kmannth-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: external hotplug mem list
<lhms-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Cc: naveen.b.s-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
acpi-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: acpi_memhotplug driver is not working for me. Any ideas?
Date: Thu, 10 Nov 2005 18:45:35 -0800 [thread overview]
Message-ID: <1131677135.20603.22.camel@knk> (raw)
In-Reply-To: <1131399845.6313.73.camel@knk>
On Mon, 2005-11-07 at 13:44 -0800, keith wrote:
> Hello,
> I have recently acquired an IBM x460 to work with. The hardware is
> completing it's hot add memory event just fine but the acpi code is
> retuning errors. (I implemented some stub functions the acpi code
> expects the arch to have)
>
Ok I have found out more.
The current driver is pretty complex perhaps too complex for my acpi
hardware event. The current event handler calls acpi_memory_get_device
which presently fails.
My event resource contains the ACPI_MEMORY_RANGE with the value of the
memory range that is hot-added. It seem like I have enough information
to call add_memory.
acpi_bus_get_device
acpi_get_parent
acpi_bus_get_device
are generic acpi functions that fail for my event. Can someone please
explain what these are all about. (Really I don't understand the acpi
API this handler was coded too.) I assume it is trying align itself to
a bus and parent but there really isn't a bus in this case and I don't
have any idea what the parent would be. My SSDT doesn't really layout
any such relationships so I don't think the memory driver should require
them.
I am working on a minimalisic event driver that works for my hardware
and will hopefully post code tomorrow sometime.
Thanks,
Keith Mannthey
LTC xSeries
--
keith <kmannth-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
next prev parent reply other threads:[~2005-11-11 2:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 21:44 acpi_memhotplug driver is not working for me. Any ideas? keith
2005-11-11 2:45 ` keith [this message]
2005-11-12 5:03 ` [RFC][PATCH] patch to fix acpi_memhotplug.c for my hardware keith
2005-11-15 5:36 ` [PATCH 1/1] patch to fix acpi_memhotplug.c keith
2005-11-15 9:29 ` [Lhms-devel] " KAMEZAWA Hiroyuki
[not found] ` <4379AA86.5040901-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2005-11-15 9:33 ` KAMEZAWA Hiroyuki
2005-11-16 2:49 ` keith
2005-11-16 3:26 ` KAMEZAWA Hiroyuki
2005-11-15 10:20 ` Yasunori Goto
[not found] ` <20051115171221.7E99.Y-GOTO-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2005-11-17 4:18 ` keith
2005-11-17 6:08 ` KAMEZAWA Hiroyuki
[not found] ` <437C1E6C.6000404-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2005-11-18 2:22 ` keith
2005-11-18 2:56 ` KAMEZAWA Hiroyuki
[not found] ` <437D42F1.6080407-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2005-11-18 18:54 ` keith
2005-11-17 7:01 ` Yasunori Goto
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=1131677135.20603.22.camel@knk \
--to=kmannth-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=lhms-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=naveen.b.s-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