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: <20090625141752.740e081d@lxorguk.ukuu.org.uk>
Date:	Thu, 25 Jun 2009 14:17:52 +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)

> Which way of stopping the serial layer from grabbing the port did you have
> in mind?
> 
> If I call uart_remove_one_port, I'd need to get struct uart_driver *drv
> and struct uart_port *port from somewhere. Also, it'd be quite ugly to
> have /dev/ttyX appear and magically disappear during boot (since 8250 is
> compiled in with most distro kernels and my driver would be a module which
> would be loaded much later).
> 
> The only alternative I could think of would be to get the serial core to
> check with acpi_check_resource_conflict for ports that have not been
> discovered via PNP/ACPI?

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.

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