public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
To: "Mark M." <maalox-XzQKRVe1yT0V+D8aMU/kSg@public.gmane.org>
Cc: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: RE: acpi-20031203-2.6.0.diff brokes the battery status readings with 2.6.0 in DELL Inspiron 8500
Date: Wed, 31 Dec 2003 17:43:40 -0800 (PST)	[thread overview]
Message-ID: <20031231174230.R3326@root.org> (raw)
In-Reply-To: <3FF31FB6.7040306-XzQKRVe1yT0V+D8aMU/kSg@public.gmane.org>

I can confirm success for one FreeBSD user with a broken Inspiron also.
Thanks for your work and I hope you can come up with a proper fix and
import it soon!

On Wed, 31 Dec 2003, Mark M. wrote:
> Success! I used the patch below and things seem to be working again.
> Actually, I manually edited my (2.6.0-mm)
> /usr/src/linux/drivers/acpi/dispatcher/dsmthdat.c
> because i don't think the paths in the patch would have worked. I just
> recompiled the kernel and rebooted.
>
> As a side note, I didn't include the before last line of the patch
> "new_obj_desc;", because it wasn't in my version of the file.

We removed that line from FreeBSD since it appears to be a typo.  Patch
was submitted back to Intel.

-Nate


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click

  parent reply	other threads:[~2004-01-01  1:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-31 10:31 RE: acpi-20031203-2.6.0.diff brokes the battery status readings with 2.6.0 in DELL Inspiron 8500 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720C69-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-12-31 19:12   ` Mark M.
     [not found]     ` <3FF31FB6.7040306-XzQKRVe1yT0V+D8aMU/kSg@public.gmane.org>
2004-01-01  1:43       ` Nate Lawson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-18  7:01 Yu, Luming
     [not found] <E1Aa16k-00089f-Ft@sc8-sf-list2.sourceforge.net>
2003-12-26 23:33 ` Mark M.
     [not found]   ` <3FECC541.10001-XzQKRVe1yT0V+D8aMU/kSg@public.gmane.org>
2003-12-30 17:59     ` Nate Lawson

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=20031231174230.R3326@root.org \
    --to=nate-y6vguytwhu0@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=maalox-XzQKRVe1yT0V+D8aMU/kSg@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