linux-kernel - Re: [PATCH 0/3] PNP: Allow PNP resources to be disabled (interface)

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CAErSpo7Xt2Pz5EqDO_NJGyRkPMrY21vzWJBK1ORwu=j+9t55Gg@mail.gmail.com>
Date:	Tue, 27 Mar 2012 14:57:08 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Witold Szczeponik <Witold.Szczeponik@....net>
Cc:	abelay@....edu,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] PNP: Allow PNP resources to be disabled (interface)

On Tue, Mar 20, 2012 at 12:49 PM, Witold Szczeponik
<Witold.Szczeponik@....net> wrote:
> Hello everybody,
>
> this simple patch series continues the work begun in commit
> 18fd470a48396c8795ba7256c5973e92ffa25cb3 where ACPI PNP resource templates
> with empty/disabled resources are handled.
>
> The aim of this patch series is to allow to set resources as "disabled" using
> the "/sys/bus/pnp/devices/*/resources" interface.  Such "disabled" resources
> are needed by some vintage IBM ThinkPads like the 600E where some resources
> need to have their IRQs disabled in order to support all the devices the 600E
> has.

If I understand this correctly, even with this patches, you still have
to manually muck around with "/sys/bus/pnp/devices/*/resources" to get
these ThinkPads to work?  If that's the case, there must be more PNP
work we could do to make them Just Work.  And that's fine; I'm just
trying to understand the current situation better.  Is there a
bugzilla or other URL with more details?

> To this end, some preparatory work is done, simplifying the code and allowing
> for more flexibility in the definition of these resources.
>
> Here's a brief description of these patches.
>
> [1/3] - Factor out common some code
> [2/3] - Perform the actual setting
> [3/3] - Generalize handling of resource flags
>
> The patches are applied against Linux 3.3.x.
>
> Comments are, as always, welcome.  :-)
>
>
> --- Witold
>
--
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/