All of lore.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Yurij Perepelytsia <yurij.perepelytsia@gmail.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: dmidecode - Samsung R10P/R41P
Date: Sun, 20 Jan 2008 15:10:21 -0500	[thread overview]
Message-ID: <200801201510.21576.lenb@kernel.org> (raw)
In-Reply-To: <184fd4090801190339y1e2d4deaw881af3240c93464c@mail.gmail.com>

On Saturday 19 January 2008 06:39, Yurij Perepelytsia wrote:
> Hello Len,
> 
> Thank for your answer. I've made as you said with "acpi_osi=!Linux"
> and additional with
> "acpi_osi=Linux" here is dmidecode and acpidump in attachment :
> "acpi_osi=Linux": acpidump0.txt
> "acpi_osi=!Linux":  acpidump1.txt
> 
> Thanks.
> 
> 
> Jan 19 16:32:14 yura kernel: ACPI: Please test with "acpi_osi=!Linux"
> 
> 2008/1/18, Len Brown <lenb@kernel.org>:
> > On Thursday 17 January 2008 07:43, Yurij Perepelytsia wrote:
> > > Hello,
> > >
> > > in my log file I've found "Please send dmidecode to
> > > linux-acpi@vger.kernel.org" my laptop is Samsung R40Plus R40XY0E.
> > > Here is copy past of that.
> >
> > Thank you Yurij.
> > Does  your system behave any differently when booted with this?:
> >
> > acpi_osi=Linux
> >
> > please e-mail me the output from acpidump.
> >
> > thanks,
> > -Len
> >
> > > yura:/home/yura# dmidecode
> > > # dmidecode 2.9
> >
> > >
> > > Handle 0x0001, DMI type 1, 27 bytes
> > > System Information
> > >     Manufacturer: SAMSUNG ELECTRONICS CO., LTD.
> > >     Product Name: R40P/R41P
> > >     Version: 06YE
> > >     Serial Number: 967Y93FP800126
> > >     UUID: 20B7E72E-D21D-B211-8000-9F20205EAF5B
> > >     Wake-up Type: Power Switch
> > >     SKU Number: Not Specified
> > >     Family: Not Specified
> > >
> > > Handle 0x0002, DMI type 2, 8 bytes
> > > Base Board Information
> > >     Manufacturer: SAMSUNG ELECTRONICS CO., LTD.
> > >     Product Name: R40P/R41P
> > >     Version:
> > >     Serial Number: 123490EN400015

Thanks for the acpidump
Looks a lot like that on the Quanta boards from HP...

We need to disable OSI(Linux) on this box if we want
the proposd PNP0C32 to work.

-Len



   Scope (\_SB)
    {
        Name (LINX, 0x00)
        Name (OSTB, Ones)
        OperationRegion (OSTY, SystemMemory, 0x2FE9FF4C, 0x00000001)
        Field (OSTY, AnyAcc, NoLock, Preserve)
        {
            TPOS,   8
        }

        Method (OSTP, 0, NotSerialized)
        {
            If (LEqual (^OSTB, Ones))
            {
                If (CondRefOf (\_OSI, Local0))
                {
                    Store (0x00, ^OSTB)
                    Store (0x00, ^TPOS)
                    If (\_OSI ("Windows 2001"))
                    {
                        Store (0x08, ^OSTB)
                        Store (0x08, ^TPOS)
                    }
...
                    If (\_OSI ("Windows 2006"))
                    {
                        Store (0x40, ^OSTB)
                        Store (0x40, ^TPOS)
                    }

                    If (\_OSI ("Linux"))
                    {
                        Store (0x01, LINX) // NOP -- never refereced after set
                        Store (0x80, ^OSTB)
                        Store (0x80, ^TPOS)
                    }

PHNP0C32 looks for OSTB == 0x40, which this code clobbers,
so OSI(Linux) will disable that:
                    Device (MBTN)
                    {
                        Name (_HID, EisaId ("PNP0C32"))
                        Name (_UID, 0x01)
                        Method (_STA, 0, NotSerialized)
                        {
                            If (LEqual (\_SB.OSTB, 0x40))
                            {
                                Return (0x0F)
                            }
                            Else
                            {
                                Return (0x00)
                            }
                        }

                        Method (GHID, 0, NotSerialized)
                        {
                            If (DMED)
                            {
                                Notify (MBTN, 0x02)
                            }

                            Return (Buffer (0x01)
                            {
                                0x01
                            })
                        }
                    }






      parent reply	other threads:[~2008-01-20 20:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <184fd4090801170441r6d93157gfa1548b737a796c4@mail.gmail.com>
2008-01-17 12:43 ` dmidecode Yurij Perepelytsia
2008-01-18 19:52   ` dmidecode Len Brown
     [not found]     ` <184fd4090801190339y1e2d4deaw881af3240c93464c@mail.gmail.com>
2008-01-20 20:10       ` Len Brown [this message]

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=200801201510.21576.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=yurij.perepelytsia@gmail.com \
    /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.