public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel@Janik.cz (Pavel Janík)
To: linux-kernel@vger.kernel.org
Cc: Tim Waugh <twaugh@redhat.com>
Subject: parport_serial and serial driver?
Date: Wed, 28 Aug 2002 18:50:50 +0200	[thread overview]
Message-ID: <m3it1vapw5.fsf@Janik.cz> (raw)

Hi,

I use non-modular kernel with parport_serial driver built in (NetMos-based
cards, 2.4.latest-vanilla patched for NetMos PCI IDs). The problem is that
parport_serial is initialized before serial driver and thus both serial
ports on that card are detected as ttyS00. This patch helped me:

--- linux.orig/Makefile	Wed Aug 28 13:46:45 2002
+++ linux/Makefile	Wed Aug 28 13:46:51 2002
@@ -130,12 +130,13 @@
 DRIVERS-  :=
 
 DRIVERS-$(CONFIG_ACPI) += drivers/acpi/acpi.o
-DRIVERS-$(CONFIG_PARPORT) += drivers/parport/driver.o
 DRIVERS-y += drivers/char/char.o \
 	drivers/block/block.o \
 	drivers/misc/misc.o \
 	drivers/net/net.o \
 	drivers/media/media.o
+# Change the order of initialization of parport_serial and serial
+DRIVERS-$(CONFIG_PARPORT) += drivers/parport/driver.o
 DRIVERS-$(CONFIG_AGP) += drivers/char/agp/agp.o
 DRIVERS-$(CONFIG_DRM_NEW) += drivers/char/drm/drm.o
 DRIVERS-$(CONFIG_DRM_OLD) += drivers/char/drm-4.0/drm.o


When the same kernel has parport_serial as a module, everything works
fine, because serial is already initialized.

BTW - Is there a way to specify the order of initialization (module_init)
of certain drivers? What is the proper solution to my problem?
-- 
Pavel Janík

panic("IRQ, you lose...");
                  -- 2.2.16 arch/mips/sgi/kernel/indy_int.c

             reply	other threads:[~2002-08-28 16:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-28 16:50 Pavel Janík [this message]
2002-08-28 17:09 ` parport_serial and serial driver? Tim Waugh

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=m3it1vapw5.fsf@Janik.cz \
    --to=pavel@janik.cz \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox