Message-ID: <c17c39d3458ffa3aebee03ff26d90c23.squirrel@www.hardeman.nu>
In-Reply-To: <20090625134946.46109bac@lxorguk.ukuu.org.uk>
References: <20090624213645.GA18843@hardeman.nu>
    <20090624234501.3d35642f@lxorguk.ukuu.org.uk>
    <55ca74318001aae803805a7bccfaca36.squirrel@www.hardeman.nu>
    <20090625134946.46109bac@lxorguk.ukuu.org.uk>
Date: Thu, 25 Jun 2009 15:14:36 +0200 (CEST)
Subject: Re: [RFC/PATCH] Winbond CIR driver for the WPCD376I chip (ACPI/PNP 
          id WEC1022)
From: David =?iso-8859-1?Q?H=E4rdeman?= <david@hardeman.nu>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, jesse.barnes@intel.com
User-Agent: SquirrelMail/1.4.15
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1037
Lines: 26

On Thu, June 25, 2009 14:49, Alan Cox wrote:
> You can certainly stop the serial layer grabbing it (or undo that)
> providing the port isn't the console (which in this case would make no
> sense).

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?

-- 
David H?rdeman

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/