linux-kernel - Re: How to access serial port that is set in BIOS as OS Controlled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Wed, 10 Aug 2011 10:46:57 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Jeff Chua <jeff.chua.linux@...il.com>
Cc:	Andrey Panin <pazke@...trinvest.ru>,
	lkml <linux-kernel@...r.kernel.org>,
	Matthew Garrett <mjg@...hat.com>
Subject: Re: How to access serial port that is set in BIOS as OS Controlled

On Fri, Aug 5, 2011 at 7:02 PM, Jeff Chua <jeff.chua.linux@...il.com> wrote:
>
>
> On Fri, Aug 5, 2011 at 11:20 PM, Bjorn Helgaas <bhelgaas@...gle.com> wrote:
>>
>> On Fri, Aug 5, 2011 at 7:59 AM, Jeff Chua <jeff.chua.linux@...il.com>
>> wrote:
>> >
>> > echo "auto" > /sys/bus/pnp/devices/00:0a/resources
>> >
>> > This seems to work.
>>
>> OK.  That's a good clue, and maybe a good enough workaround for your
>> immediate need.
>>
>> But I think the fact that it doesn't "just work" is a Linux bug, and
>> it'd be nice to fix it.  My guess is that running _SRS is what makes
>> the port work, and that Windows does this automatically but Linux does
>> not.  If we can figure out exactly what the difference is, there's a
>> good chance that we can fix several Linux issues by just doing things
>> the way Windows does.
>>
>> Would you mind building with CONFIG_PNP_DEBUG_MESSAGES=y, booting with
>> "pnp.debug", issuing the "auto" command, and attaching the dmesg log
>> to this bug report?
>>
>>  https://bugzilla.kernel.org/show_bug.cgi?id=40612
>>
>> Thanks!
>
> I'll do that next Monday when I get into the office to configure the CV60.

Ping, just a reminder :)

The ACPI spec (v4.0a, sec 6.2) says:

  When OSPM enumerates a device, it calls _PRS to determine the resource
  requirements of the device. It may also call _CRS to find the current resource
  settings for the device. Using this information, the Plug and Play system
  determines what resources the device should consume and sets those
  resources by calling the device’s _SRS control method.

I'm pretty sure Linux only runs _SRS when we actually *change* something, which
doesn't seem to follow the intent of the spec.  So if we can get a
little more evidence
here, I think it'd be worth changing Linux to call _SRS for every device when it
enumerates it.

Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/