mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Duncan Sands <duncan.sands@math.u-psud.fr>
Cc: linux-kernel@vger.kernel.org, Spang Oliver <oliver.spang@siemens.com>
Subject: Re: drivers/serial/Makefile
Date: Mon, 24 Mar 2003 16:15:51 +0000	[thread overview]
Message-ID: <20030324161551.B10370@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200303241652.50213.duncan.sands@math.u-psud.fr>; from duncan.sands@math.u-psud.fr on Mon, Mar 24, 2003 at 04:52:50PM +0100

On Mon, Mar 24, 2003 at 04:52:50PM +0100, Duncan Sands wrote:
> The serial driver is now compiled as "8250", rather than
> the traditional "serial" (Kconfig says "serial" as well).
> Assuming this was a mistake in the Makefile, I went and
> had a look, but my brain exploded.

It isn't a mistake.  "serial" is meaningless with you've got multiple
serial ports of different types.  It's a general name of a class of
devices, not a specific device.

> What exactly is this intended to do?

Well, core.c is the core driver which knows how to talk to user space,
and on to that bolts the hardware specific bits, 8250.c, sa1100.c,
suncore.c etc.

> PS: 8250_gsc, 8250_pci can be compiled as modules in their
> own right.

In theory they can, and maybe one day we'll teach the Kconfig system
to allow it.  Feel free to send a patch for this. 8)

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2003-03-24 16:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24 15:52 drivers/serial/Makefile Duncan Sands
2003-03-24 16:15 ` Russell King [this message]
2003-03-24 16:33 AW: drivers/serial/Makefile Spang Oliver
2003-03-24 16:41 ` drivers/serial/Makefile 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=20030324161551.B10370@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=duncan.sands@math.u-psud.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver.spang@siemens.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

all inboxes | Powered by JetHome®