From: Matthew Wilcox <matthew@wil.cx>
To: parisc-linux@parisc-linux.org
Subject: [parisc-linux] Anyone maintaining Mux?
Date: Wed, 20 Sep 2006 20:51:29 -0600 [thread overview]
Message-ID: <20060921025129.GK2585@parisc-linux.org> (raw)
Ryan's listed as the MODULE_AUTHOR for Mux, but I haven't seen anything
from him since he changed jobs.
I recently did an allmodconfig build and I'm looking at the missing
symbols. A modular Mux looks for:
WARNING: "pdc_iodc_putc" [drivers/serial/mux.ko] undefined!
That's funny (mostly in the sense of odd, with a tinge of amusing)
because mux is supposed to be an output driver ... why's it calling pdc
to write bytes for it?
Turns out, that's in mux_console_write() -- ie only used if
CONFIG_SERIAL_MUX_CONSOLE is set. It's an exact duplicate of the code
in pdc_cons.c.
We have five options that I see for solving this:
1. Make CONFIG_SERIAL_MUX a bool. No more mux-as-module.
2. Make CONFIG_SERIAL_MUX_CONSOLE only available if CONFIG_SERIAL_MUX is y.
3. Export pdc_iodc_putc. What's one more symbol between friends?
4. Delete CONFIG_SERIAL_MUX_CONSOLE and make pdc console work right.
5. Rewrite the Mux console to actually use the mux rather than PDC.
I'd like somebody else to be enthusiastic enough to do #5, but I'm
concerned that we don't really have a maintainer for this code right
now, and nobody's going to have time/inclination to do it.
BTW, owning this hardware is not required to work on this driver -- we
have a K-class with remote power in the Fort Collins test-ring.
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
reply other threads:[~2006-09-21 2:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060921025129.GK2585@parisc-linux.org \
--to=matthew@wil.cx \
--cc=parisc-linux@parisc-linux.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.