Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 5 Aug 2002 17:54:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 5 Aug 2002 17:54:32 -0400 Received: from caramon.arm.linux.org.uk ([212.18.232.186]:28946 "EHLO caramon.arm.linux.org.uk") by vger.kernel.org with ESMTP id ; Mon, 5 Aug 2002 17:54:31 -0400 Date: Mon, 5 Aug 2002 22:58:05 +0100 From: Russell King To: Marek Michalkiewicz Cc: twaugh@redhat.com, linux-kernel@vger.kernel.org Subject: Re: parport_serial / serial init order wrong? Message-ID: <20020805225805.C16793@flint.arm.linux.org.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from marekm@amelek.gda.pl on Mon, Aug 05, 2002 at 11:00:52PM +0200 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1195 Lines: 26 On Mon, Aug 05, 2002 at 11:00:52PM +0200, Marek Michalkiewicz wrote: > I suspect that the parport_serial driver should be initialized after > the serial driver, so it can register the detected UARTs properly. > (I have the necessary drivers compiled into the kernel, no modules.) You are correct; the same bug just got fixed in the 2.5 series. > I suspect the NM9835 may be a quite popular chip - any chances of > making support for it available in 2.4.x kernel series? Unfortunately its all controlled by the link ordering, and serial is buried in within drivers/char. Moving it before parport needs some careful analysis and may very well end up breaking other stuff. The simple answer for 2.4 may well be to move serial.c into drivers/serial so it can be ordered into the right place on its own. -- Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux http://www.arm.linux.org.uk/personal/aboutme.html - 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/