I've added Martyn and Manohar to the CC list. It's trivial to only allow it to be built as a module, of course, but probably it's better to fix the bug. regards, dan carpenter On Thu, Feb 21, 2013 at 09:42:30AM +0100, ternaryd wrote: > Hi, > > I'm aware, that vme_user is meant to be a debugging tool more than an > end-user module, but as it is a skeleton for individual developments as > well, this still may be considered as a bug. > > The point is, that vme_user must not be compiled into the kernel, it > needs to be built as a module. Otherwise, vme_user is executed before > vme_tsi148 (and probably any other hardware driver) and hence can't > find any device at all. > > As this is the skeleton we are supposed to use, it would be nice if > there was a solution to this problem. If not, a well exposed > comment/warning may save others a lot of time. > > I've come so far to understand, that a master window is configured by > opening /dev/bus/vme/m0 and making an ioctl call with the > VME_SET_MASTER command. But besides 0, any base address (VME space) for > that window is rejected. Would it be possible, that someone posted a > few lines, showing how it is done correctly? As vme_user was used for > debugging vme_tsi148, there should be a way to set up such a window and > write/read a few demo values, right? > > Thanks, > > -- > Christoph > _______________________________________________ > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxx > http://driverdev.linuxdriverproject.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
