linux-kernel - Re: [2.6.22 patch] the scheduled removal of OBSOLETE

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]

Message-ID: <45EDF33C.1060806@tmr.com>
Date:	Tue, 06 Mar 2007 18:03:24 -0500
From:	Bill Davidsen <davidsen@....com>
To:	Adrian Bunk <bunk@...sta.de>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [2.6.22 patch] the scheduled removal of OBSOLETE_OSS options

Adrian Bunk wrote:
> On Tue, Mar 06, 2007 at 12:46:22PM -0500, Bill Davidsen wrote:
>   
>> Adrian Bunk wrote:
>>     
>>> This patch contains the scheduled removal of the OBSOLETE_OSS options 
>>> for 2.6.22.
>>>
>>>       
>> If these are drivers for which there are thought to be useful ALSA 
>> drivers, would it be reasonable to leave a stub for a help file naming 
>> the driver which claims to support the hardware?
>>
>> I'm not objection to the removal of the drivers, just noting that 
>> identifying the new drivers can be made easier.
>>     
>
> People compiling their own kernels aren't completely dumb - if you know 
> about people having problems finding the right ALSA driver for their 
> hardware, please name the concrete problems so that we can improve the 
> description and/or help text of these ALSA options.
>   
I'm not sure how my original note might have been clearer, but let me 
try again.

You are about to delete a number of OSS drivers because there are ALSA 
drivers for the hardware. I am assuming that for each of there drivers 
you have some ALSA driver in mind, rather than just just general 
handwaving. I therefore suggest that it would be good if one person, 
that would be you, could do a little Kconfig magic so that when 'make 
oldconfig' on new kernel source fails to support sound, there might be a 
message in the output with a hint, like 'OSS driver XXXX has been 
deleted and ALSA driver YYYY should support this hardware.' So one 
person who I bet knows which replacement drivers are most likely could 
save some effort for many people who otherwise may have to read help on 
a number of drivers (naming is not always obvious), or grep through the 
driver source for board or chipset names giving a clue.

If Kconfig can't do this, fine, I haven't studied it in years, nor ever 
been an expert. If you have no idea what drivers replace the ones you 
are deleting and are only following orders, fine too (but I doubt that). 
But no improvement to ALSA help text would save as many people as much 
time as a one line message telling them the most likely driver to 
support similar hardware and avoiding the need to look at that text, or 
at least let the cautious look as the most likely text first.

Since you are the agent of change in breaking many existing configs I 
thought you might be inclined to at least give a clue if it were small 
effort on your part.

-- 
bill davidsen <davidsen@....com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979

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