- Subject: Re: Using vme_tsi148 device driver from user space
- From: Martyn Welch <martyn.welch@xxxxxx>
- Date: Mon, 21 Nov 2011 17:23:05 +0000
- Cc: devel@xxxxxxxxxxxxxxxxxxxxxx
- Delivered-to: devel@xxxxxxxxxxxxxxxxxxxxxx
- In-reply-to: <015F864E8D4045B2BE4FA48FE8F0BAE0@zvi3814c1f80be>
- Organization: GE Intelligent Platforms
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15
On 21/11/11 17:18, Zvi Vered wrote:
> Dear Mr. Welch,
>
> I would like to appriciate your reply.
>
> This is what I want to do in the rcS script:
>
> 1. insmod vme_tsi148.ko
> 2. insmod vme_user.ko bus=0
> 3. mdev -s
>
> In kernel configuration , CONFIG_VME_TSI148=m, CONFIG_VME_USER=m so upon 'make
> modules', the 2 modules are built.
>
> Upon rcS completion I expect to find the files: /dev/bus/vme/m0 ...
> /dev/bus/vme/s3
>
> Am I right ?
>
Have you tried that?
Martyn
> Thanks,
> Zvika.
>
> ----- Original Message ----- From: "Martyn Welch" <martyn.welch@xxxxxx>
> To: "Zvi Vered" <veredz72@xxxxxxxxx>
> Cc: <devel@xxxxxxxxxxxxxxxxxxxxxx>
> Sent: Monday, November 21, 2011 13:52
> Subject: Re: Using vme_tsi148 device driver from user space
>
>
>> On 21/11/11 03:02, Zvi Vered wrote:
>>> Hello,
>>>
>>> I'm not a developer and I need help on staging/vme/bridges.
>>> So please bare with me.
>>>
>>> My Core2Duo x86 target contains a TSI148 PCI to VME bridge.
>>> In Kernel configuration I set CONFIG_VME_TSI148=y
>>>
>>> Duding boot, this device is initiated and registered.
>>>
>>> But after 'mdev -s' there is no new device in /dev .
>>>
>>> The vme_tsi148.c does not contain an IOCTL section. Only .probe,.remove.
>>>
>>> So how (on earth !) can I open a new master window ?
>>>
>>
>> The VME bridge drivers do not provide a user space API. They register with the
>> VME core, which provides a kernel space API. This API is documented in
>> "drivers/staging/vme/vme_api.txt".
>>
>>> What major+minor numbers should I use for mknod ?
>>>
>>
>> If you are using udev, the device nodes will be automatically created.
>>
>>> How can I access the VME using this driver ?
>>>
>>
>> Using the in kernel API.
>>
>>> Must I use CONFIG_VME_USER=y also ?
>>>
>>
>> Tf you want access from user space, that module provides some basic access to
>> the VME bus.
>>
>> Martyn
>>
>> --
>> Martyn Welch (Lead Software Engineer) | Registered in England and Wales
>> GE Intelligent Platforms | (3828642) at 100 Barbirolli Square
>> T +44(0)1327322748 | Manchester, M2 3AB
>> E martyn.welch@xxxxxx | VAT:GB 927559189
>
--
Martyn Welch (Lead Software Engineer) | Registered in England and Wales
GE Intelligent Platforms | (3828642) at 100 Barbirolli Square
T +44(0)1327322748 | Manchester, M2 3AB
E martyn.welch@xxxxxx | VAT:GB 927559189
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
[Video for Linux]
[Mplayer Users]
[Linux USB Devel]
[Linux Audio Users]
[Photos]
[Yosemite Photos]
[Free Singles Community]
[Linux Kernel]
[Linux SCSI]
[XFree86]
[Devices]
[Yosemite Backpacking]