From: Christoph Plattner <christoph.plattner@gmx.at>
To: Ryan Bradetich <rbradetich@uswest.net>
Cc: "parisc-linux@lists.parisc-linux.org"
<parisc-linux@lists.parisc-linux.org>
Subject: [parisc-linux] MUX driver for multiple ports (lines)
Date: Sat, 14 Sep 2002 00:25:10 +0200 [thread overview]
Message-ID: <3D8265C6.16ECEBB@gmx.at> (raw)
Hallo Ryan,
have you already got docu on the serial MUX board ?
Or where do you have the information about `#define's
from. Is the MUX_LINE_OFFSET (= 0x80) the key point.
I have tried to access the board at
membase + MUX_OFFSET + line * MUX_LINE_OFFSET,
but the first write access to /dev/ttyB1 results in
a hang up (completely, even no network interrupts
were processed !).
Operates the MUX driver in polling mode ? Not in IRQ mode ?
Christoph
--
-------------------------------------------------------
private: christoph.plattner@gmx.at
company: christoph.plattner@alcatel.at
next reply other threads:[~2002-09-13 22:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-13 22:25 Christoph Plattner [this message]
2002-09-14 0:04 ` [parisc-linux] Re: MUX driver for multiple ports (lines) Ryan Bradetich
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=3D8265C6.16ECEBB@gmx.at \
--to=christoph.plattner@gmx.at \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=rbradetich@uswest.net \
/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