Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Philipp Rumpf <prumpf@inwestnet.de>
To: Grant Grundler <grundler@cup.hp.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] CONFIG_SERIAL_GSC
Date: Thu, 10 Feb 2000 10:21:43 +0100	[thread overview]
Message-ID: <20000210102143.A1836@abacus.local> (raw)
In-Reply-To: <200002092100.NAA13944@milano.cup.hp.com>; from grundler@cup.hp.com on Wed, Feb 09, 2000 at 01:00:00PM -0800

> Can someone explain why "#define CONFIG_SERIAL_GSC" is in serial.h?

It shouldn't be.

> Users of asm/serial.h are:
> grundler <765>find . -name '*.[ch]' | xargs fgrep "asm/serial.h"
> ./arch/mips/baget/vacserial.c:#include <asm/serial.h>
> ./drivers/char/ip2main.c:#include <asm/serial.h>
> ./drivers/char/mac_SCC.h:/* MSch: gone to <asm/serial.h> */
> ./drivers/char/synclink.c:#include <asm/serial.h>

> ./drivers/char/serial.c:#include <asm/serial.h>
> ./drivers/gsc/lasi.c:#include <asm/serial.h>

These are the only two that concern us.

> I have the impression it's going to be difficult to build a "PCI"
> serial driver with CONFIG_SERIAL_GSC defined.

Wrong.  The serial driver is designed to handle several busses at the
same time.  That means you can have CONFIG_SERIAL (port based),
CONFIG_SERIAL_GSC, and PCI MMIO based serial all activated at the same
time and one serial port of each variation and everything should work.

All you need to do is call register_serial with a struct serial_struct *req
so req->io_type == SERIAL_IO_MEM and everything should work fine.

Of course newer boxes (c3k, j5k, c3600, j5600) don't have GSC at all, so
you'd like not do define CONFIG_GSC/CONFIG_SERIAL_GSC for those.  (Those
boxes seem to still have an HP-proprietary bus though, but I don't know
anything about that).

	Philipp Rumpf

      reply	other threads:[~2000-02-10  9:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-09 21:00 [parisc-linux] CONFIG_SERIAL_GSC Grant Grundler
2000-02-10  9:21 ` Philipp Rumpf [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=20000210102143.A1836@abacus.local \
    --to=prumpf@inwestnet.de \
    --cc=grundler@cup.hp.com \
    --cc=parisc-linux@thepuffingroup.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