public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Michael Renzmann <mrenzmann@compulan.de>
To: mtd@infradead.org
Subject: DOC socket misuseable?
Date: Fri, 07 Jul 2000 17:22:35 +0200	[thread overview]
Message-ID: <3965F5BB.195CE244@compulan.de> (raw)

Hi all.

I know that my question is not ontopic, but maybe some of the hardware-
and programming wizards could at least give some tips.

My problem is that I have to connect a lcd (liquid crystal display) to
two different types of PC. Up to now I did this by connecting them with
an appropriate cable to the parallel port which normally is used as
printer port. A scheme of the cable and the needed "drivers" for the
lcd´s for linux can easily be found (I´ll tell the link if someone wants
it). It worked fine by now.

The solution of connecting the displays to the parport can no longer be
used, due to different problems. Now I am looking for another way to
connect the lcd to the pc´s. I know that the driver for the lcd has to
be rewritten after that, but thats the lesser problem. The bigger
problem is to find an interface that provides at least 10 outout lines
(8 for data transmission and 2 or 3 for toggling different states,
depending on the display type). As both pc types are so called thin
clients, they both feature a doc socket. So I wonder if it was possible
to "misuse" this socket to connect the lcd to it. As the DOCs have to
send and/or receive data as well there should be a way to use this
socket in my opinion. But I don´t know how this could be done, maybe one
of the wizards in here could help with that...?

If this is not the right way (i.e. the socket can not be used for this
purpose), does anyone have another idea how to connect the lcd to the
pc? As said before, I need 10 or 11 output lines, no input needed. Any
help appreciated and sorry for this (mostly) offtopic mail.

Bye, Mike


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

                 reply	other threads:[~2000-07-07 15:22 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=3965F5BB.195CE244@compulan.de \
    --to=mrenzmann@compulan.de \
    --cc=mtd@infradead.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