From: Keith Owens <kaos@ocs.com.au>
To: pyrenees@club-internet.fr
Cc: linux-kernel@vger.kernel.org
Subject: Re: The moxa.c module is not compiled in 2.4.7 kernel.
Date: Tue, 24 Jul 2001 14:38:11 +1000 [thread overview]
Message-ID: <23760.995949491@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 23 Jul 2001 23:49:17 +0200." <01072323491700.00616@linux>
On Mon, 23 Jul 2001 23:49:17 +0200,
"J.L.Carlet" <pyrenees@club-internet.fr> wrote:
>I have a problem with the 2.4.7 kernel only, not with the 2.4.6.
>In the 2.4.6, using make xconfig, I select Moxa Intellio support, in the
>Character devices menu. I made make dep, make clean, make modules, make
>modules_install, and then I obtained the moxa.o file in
>/lib/modules/2.4.6/kernel/drivers/char directory.
>If I make the same operations with 2.4.7 kernel, I don't obtain moxa.o
>The file is not compiled and not installed.
It compiles and installs for me on 2.4.7, using make xconfig.
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=y
# CONFIG_SERIAL_CONSOLE is not set
CONFIG_SERIAL_EXTENDED=y
# CONFIG_SERIAL_MANY_PORTS is not set
# CONFIG_SERIAL_SHARE_IRQ is not set
# CONFIG_SERIAL_DETECT_IRQ is not set
# CONFIG_SERIAL_MULTIPORT is not set
# CONFIG_HUB6 is not set
CONFIG_SERIAL_NONSTANDARD=y
# CONFIG_COMPUTONE is not set
# CONFIG_ROCKETPORT is not set
# CONFIG_CYCLADES is not set
# CONFIG_DIGIEPCA is not set
# CONFIG_DIGI is not set
# CONFIG_ESPSERIAL is not set
CONFIG_MOXA_INTELLIO=m
# CONFIG_MOXA_SMARTIO is not set
# CONFIG_ISI is not set
# CONFIG_SYNCLINK is not set
# CONFIG_N_HDLC is not set
# CONFIG_RISCOM8 is not set
# CONFIG_SPECIALIX is not set
# CONFIG_SX is not set
# CONFIG_RIO is not set
# CONFIG_STALDRV is not set
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
prev parent reply other threads:[~2001-07-24 4:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 21:49 The moxa.c module is not compiled in 2.4.7 kernel J.L.Carlet
2001-07-24 4:38 ` Keith Owens [this message]
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=23760.995949491@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pyrenees@club-internet.fr \
/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