From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.196]) by ozlabs.org (Postfix) with ESMTP id 271D667A6B for ; Fri, 26 May 2006 05:00:42 +1000 (EST) Received: by wx-out-0102.google.com with SMTP id s17so663264wxc for ; Thu, 25 May 2006 12:00:41 -0700 (PDT) Message-ID: <929bf310605251200s66106eaer@mail.gmail.com> Date: Thu, 25 May 2006 21:00:40 +0200 From: "Konstantin Boyanov" To: "Ajit Prem" , linuxppc-embedded@ozlabs.org Subject: Re: VME driver problem on MVME6100 In-Reply-To: <007501c6801c$3b86fde0$0400a8c0@DLAPTOP> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_12963_39416.1148583640438" References: <929bf310605250923i1924c12bj@mail.gmail.com> <007501c6801c$3b86fde0$0400a8c0@DLAPTOP> List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , ------=_Part_12963_39416.1148583640438 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi again, The problem persist even with the new driver for 2.6 ... :( It is obvious that the driver cannot allocate memory for the window... It fails that thing called __ioremap(), whatever it might be used for: [mvme6100]# vme_setoutboundwin -h vme_setoutboundwin Usage: vme_setoutboundwin -w window(where 0<=3Dwindow<=3D6) -m address mode (where 0=3DA16,1=3DA24,2=3DA32,3=3DA64= ,4=3DCRCSR) -p protocol (where 1=3DSCT,2=3DBLT,4=3DMBLT,8=3D2eVME,0x10=3D2eSST) -a VME address -d data width (8, 16, 32, 64) -s window size (where 0 < window_size <=3D 0x400000) -v Be more verbose -h Give this (short) help [mvme6100]# vme_setoutboundwin -w0 -m0 -p8 -a0x8800 -d16 -s400000 -v window =3D 0, mode =3D 0 protocol 0x8 vme_addr =3D 0x8800 data width =3D 16 __ioremap(): phys addr 01000000 is RAM lr d100be34 vmedrv: No memory for outbound window ioctl VME_IOCTL_SET_OUTBOUND failed.: Cannot allocate memory While searching on the web for information about __ioremap I found this: /* * Remap an arbitrary physical address space into the kernel virtual * address space. Needed when the kernel wants to access high addresses * directly. * * NOTE! We need to allow non-page-aligned mappings too: we will obviously * have to convert them into an offset in a page-aligned mapping, but the * caller shouldn't need to know that small detail. */ And another thing - people should not be using __ioremap() unless they have a _good_ _reason_ in their driver. They should be using ioremap() instead. __ioremap() is an architecture implementation detail which has no interface stability guarantees _at all_. How's that? So it seems that the kernel can't translate the accesses to the VME bus propperly. Any ideas how to fix that? Actually I cant figure out why configuring a single outbound window is so damn tough to achieve.e maybe I'm missing some crutial settings. I tried to set up the window attribute register, and the outbound translation offset register in the hope to fit in the needed size for the window, but again failed. I'm trying to get frustrated about that... Best regards, Konstantin ------=_Part_12963_39416.1148583640438 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi again,

The problem persist even with the new driver for 2.6 ... :(
It is obvious that the driver cannot allocate memory for the window... It fails that thing called __ioremap(), whatever it might be used for:

[mvme6100]# vme_setoutboundwin -h
vme_setoutboundwin
Usage: vme_setoutboundwin <options>
        -w <window>  &nb= sp;  window(where 0<=3Dwindow<=3D6)
        -m <mode>       address mode (where 0=3DA16,1=3DA24,2=3DA32,3=3DA64,4=3DCRCSR)
        -p <protocol>   protocol (where 1=3DSCT,2=3DBLT,4=3DMBLT,8=3D2eVME,0x10=3D2eSST)
        -a <VME addr>   = VME address
        -d <data width> data width= (8, 16, 32, 64)
        -s <window size>        window size (where 0 < window_size <=3D 0x400000)
        -v            &= nbsp; Be more verbose
        -h            &= nbsp; Give this (short) help

[mvme6100]# vme_setoutboundwin -w0 -m0 -p8 -a0x8800 -d16 -s400000 -v
window =3D 0, mode =3D 0 protocol 0x8 vme_addr =3D 0x8800 data width =3D 16
__ioremap(): phys addr 01000000 is RAM lr d100be34
vmedrv: No memory for outbound window
ioctl VME_IOCTL_SET_OUTBOUND failed.: Cannot allocate memory

While searching on the web for information about __ioremap I found this: 
/*
 * Remap an arbit=
rary physical address space into the kernel virtual
 * address space. Ne=
eded when the kernel wants to access high addresses
 * directly.
 *
 * NOTE! We need to allow non-page-aligned mappings too: we will obviously<=
br> * have to convert them into an offset in a page-aligned mapping, but th=
e
 * caller shouldn't need to know that small detail.
 */









And another thing - people should not be =
using __ioremap() unless they
have a _good_ _reason_ in their driver.  T=
hey should be using ioremap()
instead.  __ioremap() is an architecture i=
mplementation detail which

has no interface stability guarantees _at all_.

How's that? So it seems that the kernel can't translate the accesses to the=
 VME bus propperly. Any ideas how to fix that?

Actually I cant figure out why configuring a single outbound window is
so damn tough to achieve.e maybe I'm missing some crutial settings. I
tried to set up the window attribute register, and the outbound
translation offset register in the hope to fit in the needed size for
the window, but again failed. I'm trying to get frustrated about that...


Best regards,

Konstantin




------=_Part_12963_39416.1148583640438--