From: Russell King <rmk@arm.linux.org.uk>
To: Hikaru1@verizon.net
Cc: linux-serial@vger.kernel.org
Subject: Re: 8250/16550 serial driver not being installed if set modular
Date: Thu, 17 Nov 2005 22:55:30 +0000 [thread overview]
Message-ID: <20051117225530.GA20221@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20051115115613.GA10399@roll>
On Tue, Nov 15, 2005 at 06:56:13AM -0500, Hikaru1@verizon.net wrote:
> Hi, I'm emailing you to report a bug with the serial driver in linux kernel
> 2.6.14.2, you are listed as the maintainer in the MAINTAINERS file, so if
> I've sent you this bug report in error please tell me where I should be
> sending it.
>
> I'm using slackware 10.2 on a AMD K7 (XP 2600) this is a 32bit i386
> compatible machine.
>
> in 2.6.14.2's menuconfig, under Device Drivers->Character devices->Serial
> drivers if I select the option 8250/16550 and compatible serial support to
> be compiled into the kernel, it works fine. If I select it to compile as a
> module, the module 'serial' is not installed when I do make modules_install.
> I'm also pretty sure it's not being compiled at all when selected to be
> compiled as a module.
>
> Just to be clear, the help for that option specifically says the module will
> be named 'serial' if the name's wrong, could you tell me what it is named?
>
> I don't know what's wrong with it, nor where to check. Could you give me
> some pointers on what to check so I can give you more information? I
> really prefer to have as much as I can as modules as my computer has to boot
> using a floppy disk.
It's actually called '8250' and it depends on 'serial_core' as well.
I'll fix the docs.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-11-17 22:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 11:56 8250/16550 serial driver not being installed if set modular Hikaru1
2005-11-17 22:55 ` Russell King [this message]
2005-11-17 22:58 ` Russell King
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=20051117225530.GA20221@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=Hikaru1@verizon.net \
--cc=linux-serial@vger.kernel.org \
/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.