From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: "Andrea Galbusera" <gizero@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: custom parallel interface driver
Date: Wed, 10 May 2006 10:57:47 -0600 [thread overview]
Message-ID: <200605101057.47870.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <f8e53fb0605100224r298d4799q16c088a5ca9918d5@mail.gmail.com>
On Wednesday 10 May 2006 03:24, Andrea Galbusera wrote:
> Here are some specifications of the hardware module to support (not
> developed by me):
> - single unidirectional Centronics-like with control signals interface
> - 1K x 8bit FIFO for data
>
> Minimal driver requirements are:
> - capability to read data from the FIFO (possiblbly through ususal
> device file interfaces and using interrupts)
> - capability to read/write control registers of the interface
If the parallel interface is directly exposed as a PCI device
and it supports the typical 8255 programming model, it should
just work if you add the appropriate vendor and device IDs to
parport_pc_pci_tbl[].
The serial driver has a default case that claims any device that
PCI_CLASS_COMMUNICATION_SERIAL class code. In theory, the parport
driver could claim anything with PCI_CLASS_COMMUNICATION_PARALLEL.
In that case, you wouldn't even need to modify anything. But
maybe there are issues that prevent parport_pc.c from doing this.
The following sites have lots of information that might be useful
to you:
http://www.torque.net/linux-pp.html
http://www.lvr.com/parport.htm
prev parent reply other threads:[~2006-05-10 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 9:24 Andrea Galbusera
2006-05-10 16:57 ` Bjorn Helgaas [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=200605101057.47870.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=gizero@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®