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

Date:	Tue, 27 Nov 2007 17:34:51 +0100
From:	Thomas Renninger <trenn@...e.de>
To:	Rene Herman <rene.herman@...access.nl>
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 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.
> 
> 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.

Thanks,

   Thomas

-
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/