linux-kernel - Re: [patch 2/5] Staging: vme: add VME userspace driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4A8291F5.8060406@gefanuc.com>
Date:	Wed, 12 Aug 2009 10:57:09 +0100
From:	Martyn Welch <martyn.welch@...anuc.com>
To:	"Emilio G. Cota" <cota@...ap.org>
CC:	Greg K-H <gregkh@...e.de>, linux-kernel@...r.kernel.org,
	devel@...uxdriverproject.org,
	Sebastien Dugue <sebastien.dugue@...l.net>
Subject: Re: [patch 2/5] Staging: vme: add VME userspace driver

Emilio G. Cota wrote:
> Martyn Welch wrote:
>   
>> Also, it seems that your API doesn't currently support Location
>> Monitors. These are specified in the VME spec, I'd be interested in
>> how
>> you plan to support this feature in a consistent manner with your
>> current API
>>     
>
> What I intend to provide is a sane environment to work with VME
> devices. The first step is to cover the needs of most use cases:
>
> - 1 master Single Board Computer (SBC) running Linux
> - All the other slots have slave devices in them. These devices
>   are controlled by kernel drivers on the SBC.
> - The SBC does DMA, direct I/O access (mapping) to/from the
>   slaves, and handles interrupts from the devices.
>
> Once that's settled we could discuss about further parts of the
> spec. But really today getting the above right is _much_ more
> important than location monitors support.
>   
Right - this is a specific case that you see as important. Depending on 
the number of slots in the rack and the diversity of the cards used, the 
VME core and driver I have suggested already covers this.

However, I also need to consider other cases, such as communications 
between multiple SBCs and potentially a few slave devices. I have a need 
for this *now*, not in the future. To me, slave support and to a lesser 
degree location monitor support is important now, hence why it's 
supported in my driver and core. Hence why I am asking, how do you 
propose to support these features?

Martyn
> E.
>   


-- 
Martyn Welch MEng MPhil MIET (Principal Software Engineer)   T:+44(0)1327322748
GE Fanuc Intelligent Platforms Ltd,        |Registered in England and Wales
Tove Valley Business Park, Towcester,      |(3828642) at 100 Barbirolli Square,
Northants, NN12 6PF, UK T:+44(0)1327359444 |Manchester,M2 3AB  VAT:GB 927559189
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/