public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Johan Borkhuis <j.borkhuis@dutchspace•nl>
To: Konstantin Boyanov <kkboyanov@gmail•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: Driver for device behind a PCI-VME bridge
Date: Mon, 20 Aug 2007 10:45:30 +0200	[thread overview]
Message-ID: <46C954AA.7050609@dutchspace.nl> (raw)
In-Reply-To: <929bf310708200140w6efc57f6k81a1339845059e2d@mail.gmail.com>

Hello Konstantin,

Konstantin Boyanov wrote:
> Hi list,
>
> I'm currently reading the LDD 3rd Edition and trying to create a 
> device driver for a custom device located on VME bus. I have already 
> linux 2.6.15 running on the master board, as well as the device driver 
> for the PCI-VME bridge. The main problem I have is understanding how 
> to "attach" my driver for the custom device to the bridge device driver.
> The bridge device driver is implemented as a class, i.e. doesn't 
> define a new bus type. Should I define a new class for my driver, or 
> should I connect it somehow to the existing one (maybe by something as 
> "subclass")?
> All I want to do is to redirect I/O reads and writes to the VME bus, 
> but I got no clue as to how to use the existing VME bridge driver for 
> this purpose. After I get through this I think all other things (VME 
> interrupt registration & handling, etc.) will be straightforward.
> The LDD 3rd book states that defining a new bus type is the last thing 
> one would like to do, instead defining a class is far better approach. 
> Why is that?
>
> Any recommendations and sharing of practical experience are highly 
> appreciated.
I am also working on a VME-board. What I did was use mmap to map 
specific parts of the VME-memory into user space.

BTW: what kind of board and Linux-flavor are you using?

Kind regards,
    Johan Borkhuis

  reply	other threads:[~2007-08-20  8:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-20  8:40 Driver for device behind a PCI-VME bridge Konstantin Boyanov
2007-08-20  8:45 ` Johan Borkhuis [this message]
2007-08-20  8:58   ` Konstantin Boyanov
     [not found]     ` <929bf310708210055k3970c3chfc097ff776af439a@mail.gmail.com>
2007-08-21  7:56       ` Konstantin Boyanov
2007-08-21  8:32         ` Johan Borkhuis
2007-08-21  9:49           ` Konstantin Boyanov
     [not found]             ` <46CAE973.6040306@dutchspace.nl>
2007-08-23  7:47               ` Konstantin Boyanov
2007-08-23  8:24                 ` Johan Borkhuis

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=46C954AA.7050609@dutchspace.nl \
    --to=j.borkhuis@dutchspace$(echo .)nl \
    --cc=kkboyanov@gmail$(echo .)com \
    --cc=linuxppc-embedded@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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