public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Hein-Pieter van Braam <hp-KOxqMzujAKlWk0Htik3J/w@public.gmane.org>
To: Stefan Seyfried
	<seife-T+3qhDtrTvDv8lqoKu5MV4HBZQ1bDw0s@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Compaq 2552EA suspend/resume
Date: Wed, 12 Oct 2005 16:20:25 +0200	[thread overview]
Message-ID: <1129126825.6202.27.camel@localhost.localdomain> (raw)
In-Reply-To: <20051012113309.GB9401-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 827 bytes --]

I know C, there's just rather a lot of it in the linux kernel, and I'm
not sure where to start looking :)

On Wed, 2005-10-12 at 13:33 +0200, Stefan Seyfried wrote:
> On Mon, Oct 10, 2005 at 12:37:00PM +0200, Hein-Pieter van Braam wrote:
> > The problem is that I don't really have any idea on where to start...
> > I've got the feeling that my DSDT is really screwed, and I'm trying to
> > learn AML, but it's not a very transparent language :)
> 
> In my experience, suspend to RAM failures are usually not caused by DSDT
> problems (i have yet to see such a case), so you better start learning C.
> 
> > I would really appreciate some pointers, or a couple of links on the
> > subject, I've done a lot of googling already, but I can't really come up
> > with a good place to start.
> 
> /usr/src/linux/ ;-)

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-10-12 14:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-06  6:51 Compaq 2552EA suspend/resume Hein-Pieter van Braam
     [not found] ` <1128581461.8134.7.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-10-06  9:35   ` Pavel Machek
     [not found]     ` <20051006093525.GB10865-u08AdweFZfgxtPtxi4kahqVXKuFTiq87@public.gmane.org>
2005-10-09 19:09       ` Hein-Pieter van Braam
     [not found]         ` <1128884950.12703.3.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-10-10  8:56           ` Pavel Machek
     [not found]             ` <20051010085625.GC2369-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-10-10 10:37               ` Hein-Pieter van Braam
     [not found]                 ` <1128940620.12703.7.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-10-12 11:33                   ` Stefan Seyfried
     [not found]                     ` <20051012113309.GB9401-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>
2005-10-12 14:20                       ` Hein-Pieter van Braam [this message]
     [not found]                         ` <1129126825.6202.27.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-10-12 19:53                           ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2005-10-05 17:13 Hein-Pieter van Braam
     [not found] ` <1128532406.16313.12.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2005-11-03 14:50   ` Pavel Machek

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=1129126825.6202.27.camel@localhost.localdomain \
    --to=hp-koxqmzujaklwk0htik3j/w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=seife-T+3qhDtrTvDv8lqoKu5MV4HBZQ1bDw0s@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