From: Michael Stickel <michael@cubic.org>
To: linux-mips@linux-mips.org
Subject: Re: adding another PCI based serial port board causing errors on db1550
Date: Sat, 25 Jun 2005 00:37:13 +0200 [thread overview]
Message-ID: <42BC8B19.9000400@cubic.org> (raw)
In-Reply-To: <2db32b72050624155127a383a7@mail.gmail.com>
rolf liu wrote:
>the driver for the board also has function "register_serial" and
>"unregister_serial", which are already defined by au1x00-serial.c. So
>there comes "multiple deginition" of these functions. Any idea on this
>issue?
>
>
I also needed another serial port. I have made register_serial and
unregister_serial static in au1x00-serial.c so they will shadow the
external functions with the same name and will not be exported and
changed the name from ttyS to ttySA to avoid conflicts with serial.c.
After that it worked for me.
static struct console sercons = {
.name = "ttySA",
.write = serial_console_write,
.device = serial_console_device,
.setup = serial_console_setup,
.flags = CON_PRINTBUFFER,
.index = -1,
};
next prev parent reply other threads:[~2005-06-24 23:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 22:51 adding another PCI based serial port board causing errors on db1550 rolf liu
2005-06-24 22:37 ` Michael Stickel [this message]
2005-06-25 2:27 ` Ralf Baechle
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=42BC8B19.9000400@cubic.org \
--to=michael@cubic.org \
--cc=linux-mips@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox