linux-kernel - Re: [RFC] Pushing device/driver binding decisions to userspace

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: <1163412832.24542.3.camel@frg-rhel40-em64t-03>
Date:	Mon, 13 Nov 2006 11:13:52 +0100
From:	Xavier Bestel <xavier.bestel@...e.fr>
To:	Ben Collins <ben.collins@...ntu.com>
Cc:	Nicholas Miell <nmiell@...cast.net>, linux-kernel@...r.kernel.org
Subject: Re: [RFC] Pushing device/driver binding decisions to userspace

On Sun, 2006-11-12 at 23:10 -0800, Ben Collins wrote:
> Also the other case I gave where there is an alsa driver and a media
> driver for the same chipset, is by design. It can't be helped. There
> actually is a case for wanting one driver or the other in the case of
> the exact same hardware, depending on the users desire.

That one looks ugly. Probably the same driver should have a media
interface as well as an alsa interface (like alsa device are also oss
devices, no need to play evil rmmod/insmod tricks anymore).

	Xav

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