linux-kernel - Re: [RFC/PATCH] Winbond CIR driver for the WPCD376I chip (ACPI/PNP id WEC1022)

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: <20090625143533.19ff85e5@lxorguk.ukuu.org.uk>
Date:	Thu, 25 Jun 2009 14:35:33 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	David Härdeman <david@...deman.nu>
Cc:	linux-kernel@...r.kernel.org, jesse.barnes@...el.com
Subject: Re: [RFC/PATCH] Winbond CIR driver for the WPCD376I chip (ACPI/PNP
                id WEC1022)

On Thu, 25 Jun 2009 15:28:31 +0200 (CEST)
David Härdeman <david@...deman.nu> wrote:

> On Thu, June 25, 2009 15:17, Alan Cox wrote:
> >> Which way of stopping the serial layer from grabbing the port did you
> >> have in mind?
> >
> > You can vanish it with setserial as stands. There isn't a good
> > interface for doing that from kernel side but as you can see from
> > setserial the infrastructure is all there to add it.
> 
> Seems user-unfriendly...wouldn't blacklisting that particular port (using
> ACPI or PNP id or something) be a better solution?

Possibly - what I am saying is that the mechanisms exist internally for
this including flipping a port at run time between IR and normal modes
when appropriate
--
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/