[lkml]   [2010]   [Oct]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[-next] staging/vme: various fixes + new driver model for VME
Hi Greg,

This contains first a whole bunch of fixes to the existing vme
code in staging, to then introduce a new driver model for VME
in patch 27.

I have a short list of things to do after this patchset gets

- provide a saner API for VME drivers that just want to
map/unmap chunks of memory (knowing nothing about underlying
hardware features, such as windows). This is already
implemented in the out-of-tree driver in [1].

- Make DMA work on the tsi148 (it's the only bridge I've got).
This will probably involve changing or extending the
current API.

- Test the whole thing with real hardware and a real VME driver
(currently out of tree as well, see [2]), which I'll try
to get merged, too--currently we just have vme_user.c which
really isn't a kosher driver.

Note that the appended applies on top of linux-next.

The patchset can be pulled from:
git:// vme-next





drivers/staging/vme/bridges/vme_ca91cx42.c | 222 ++++++------
drivers/staging/vme/bridges/vme_ca91cx42.h | 2 +-
drivers/staging/vme/bridges/vme_tsi148.c | 259 +++++++-------
drivers/staging/vme/bridges/vme_tsi148.h | 2 +-
drivers/staging/vme/devices/vme_user.c | 159 ++++-----
drivers/staging/vme/vme.c | 569 +++++++++++++++-------------
drivers/staging/vme/vme.h | 229 ++++++++++-
drivers/staging/vme/vme_bridge.h | 175 ---------
8 files changed, 831 insertions(+), 786 deletions(-)

 \ /
  Last update: 2010-10-22 09:33    [W:0.196 / U:4.576 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site