From: Russell King <rmk@arm.linux.org.uk>
To: Marek Michalkiewicz <marekm@amelek.gda.pl>
Cc: twaugh@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: parport_serial / serial init order wrong?
Date: Mon, 5 Aug 2002 22:58:05 +0100 [thread overview]
Message-ID: <20020805225805.C16793@flint.arm.linux.org.uk> (raw)
In-Reply-To: <E17boyC-0004rp-00@alf.amelek.gda.pl>; from marekm@amelek.gda.pl on Mon, Aug 05, 2002 at 11:00:52PM +0200
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
next prev parent reply other threads:[~2002-08-05 21:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 21:00 parport_serial / serial init order wrong? Marek Michalkiewicz
2002-08-05 21:58 ` Russell King [this message]
2002-08-14 9:11 ` Marek Michalkiewicz
2002-08-14 9:14 ` Tim Waugh
2002-08-14 9:21 ` Marek Michalkiewicz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020805225805.C16793@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marekm@amelek.gda.pl \
--cc=twaugh@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.