public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jurgen Kramer <gtm.kramer-c1aixF9oqgPk1uMJSBkQmQ@public.gmane.org>
To: acpi-devel
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: 2.6.10 and acpi_get_possible_resources?
Date: Fri, 14 Jan 2005 15:40:21 +0100	[thread overview]
Message-ID: <1105713621.10664.8.camel@paragon.slim> (raw)

I am trying to get the WACOM ACPI patches working on 2.6.10 but it bails
out on a missing function "acpi_get_possible_resources". On 2.6.9 the
needed symbol is exported by acpi_ksyms.c but this file no longer exists
in 2.6.10. 

What is the best way to get the acpi_get_possible_resources function
exported properly? It is defined in <acpi/acpxf.h> but adding this to
the wacom source files did not help.

The 2.6.9 version of the wacom patches are from:

http://www.theory.bham.ac.uk/staff/schofield/linux/tc1100/linux-2.6.9-
wacom_acpi.patch


Thanks,

Jurgen
-- 



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

             reply	other threads:[~2005-01-14 14:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-14 14:40 Jurgen Kramer [this message]
     [not found] ` <1105713621.10664.8.camel-AynNu1t4G8oLie942ae2tA@public.gmane.org>
2005-01-16  0:00   ` 2.6.10 and acpi_get_possible_resources? *solved* Jurgen Kramer
     [not found]     ` <1105833637.27841.4.camel-AynNu1t4G8oLie942ae2tA@public.gmane.org>
2005-01-17 19:30       ` Rajesh Shah
     [not found]         ` <20050117113020.A19913-39QZ/XbsZ5/mO6KZMuUCQVaTQe2KTcn/@public.gmane.org>
2005-01-18 18:41           ` Jurgen Kramer

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=1105713621.10664.8.camel@paragon.slim \
    --to=gtm.kramer-c1aixf9oqgpk1umjsbkqmq@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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