linux-kernel - Re: [alsa-devel] [PATCH 2/3] PNP cleanups - Unify the pnp macros to access resources in the pnp resource table

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <474C4B38.6030609@keyaccess.nl>
Date:	Tue, 27 Nov 2007 17:52:08 +0100
From:	Rene Herman <rene.herman@...access.nl>
To:	trenn@...e.de
CC:	ALSA devel <alsa-devel@...a-project.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"yakui.zhao" <yakui.zhao@...el.com>,
	"Li, Shaohua" <shaohua.li@...el.com>,
	akpm <akpm@...ux-foundation.org>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Bjorn Helgaas <bjorn.helgaas@...com>,
	Takashi Iwai <tiwai@...e.de>
Subject: Re: [alsa-devel] [PATCH 2/3] PNP cleanups - Unify the pnp macros
 to access	resources in the pnp resource table

On 27-11-07 17:34, Thomas Renninger wrote:

> On Wed, 2007-11-21 at 10:53 +0100, Takashi Iwai wrote:
>> At Tue, 20 Nov 2007 15:31:26 +0100, Rene Herman wrote:
>>> On 20-11-07 15:19, Thomas Renninger wrote:
>>> 
>>>> At the end is some example code how things could get even more
>>>> cleaned up. It shows how I think pnp layer and one example driver
>>>> would get adjusted. There are not that much drivers making use of 
>>>> pnp_resource_change...
>>> 
>>> The ALSA ISA-PnP drivers do in what I personally consider a bad
>>> layering violation. Brought up not doing that a while ago on
>>> alsa-devel, but no discussion ensued. If the PnP maintainer(s) agree
>>> with me though, I'd be more than happy to rip all of that out of
>>> ALSA.
> 
> Rene: Could you do that, pls.

Yes, I will do this, In fact, I've done a few already but ofcourse a few 
other things intervened again...

>> I'm fine with removal of that stuff now.  It was implemented in that
>> way because there was no proper way to re-assign ISA PnP resources on
>> 2.4 kernel time.  On 2.6, it makes no longer any sense (except for
>> compatibility, but this is almost no problem for PnP boards).
> 
> I wasted some time on thinking about how this pnp_resource_change and
> pnp_manual_config_dev could get workarounded..., but it's impossible
> without changing the (more a workaround than an) interface.
> 
> If you worked on this already, would you mind ripping these out?
> 
> If I understand Takashi correctly, the driver code using
> pnp_resource_change and pnp_manual_config_dev can simply be removed and
> devices could get resources assigned via sysfs "set" interface.

Exactly. ISA-PnP is with respect to the interface it provides exactly as PCI 
and other sane busses. You just ask the system what resources to use -- it 
provides a method for actually changing them as well, but doing so belongs 
isolated in the PnP layer, not anywhere else IMHYUO (*).

Wasn't aware of the original reason for this setup, but yes, in 2.6 it 
certainly isn't needed for anything anymore and in fact just makes for 
inconsistency, especially for the mixed legacy/isapnp drivers where module 
parameters change meaning from "this is where it's at to "_put_ it there" 
between the two card types.

Jaroslav Kysela will have to ack any patches as well, but sound/isa is the 
only user of

- pnp_init_resource_table()
- pnp_resource_change()
- pnp_manual_config_dev()

which eventually then might also want to be unexported and/or deleted.

Rene.

(*) In My Humble Yet Unwavering Opinion...
-
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/