mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Andrea Galbusera" <gizero@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: custom parallel interface driver
Date: Wed, 10 May 2006 11:24:54 +0200	[thread overview]
Message-ID: <f8e53fb0605100224r298d4799q16c088a5ca9918d5@mail.gmail.com> (raw)

In the context of a PowerPC Linux project I am required to support a
custom parallel interface. The hardware module implementing such
interface lives on a FPGA board connected to the PowerPC by the PCI
bus.

I'm reading developer's docs about the parport subsystem: I'm asking
myself how to use (if possible) all that already available code. Do I
have to develop a new low-level driver using pci and parport
interfaces? Or may I expect to be able to use parport_pc?
Unfortunately I still don't have the hardware available and I'm
evaluating the complexity of this task.

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

These may sound as very preliminar questions. In fact, they are! My
kernel development experience is just at the beginning, but I have a
basic knowledge of kernel module writing and I read Rubini's book on
the subject.

Hope somebody can suggest me how to approach the problem, to avoid
re-inventing the wheel...

TIA

             reply	other threads:[~2006-05-10  9:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-10  9:24 Andrea Galbusera [this message]
2006-05-10 16:57 ` Bjorn Helgaas

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=f8e53fb0605100224r298d4799q16c088a5ca9918d5@mail.gmail.com \
    --to=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®