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
| ||
|
Date: Tue, 7 Jul 2015 16:04:18 +0300 From: Dmitry Kalinkin <dmitry.kalinkin@...il.com> To: Alessio Igor Bogani <alessioigorbogani@...il.com> Cc: Martyn Welch <martyn.welch@...com>, devel@...verdev.osuosl.org, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Igor Alekseev <igor.alekseev@...p.ru>, LKML <linux-kernel@...r.kernel.org>, Manohar Vanga <manohar.vanga@...il.com> Subject: Re: [PATCHv3 08/16] staging: vme_user: provide DMA functionality > On 07 Jul 2015, at 15:51, Alessio Igor Bogani <alessioigorbogani@...il.com> wrote: > <snip> >> Current VME stack links windows not to the boards, but to device drivers. >> Driver >> could potentially minimise window usage within it’s scope (any sort of >> window >> reusing, like mapping whole A16 once to be used with all boards), but this >> won’t >> work across multiple drivers. Even if all of your drivers are window-wise >> economic, >> they will still need some amount of windows per each driver. Not that we >> have that >> many kernel drivers... > > Yes you can share a window/image between all boards of the same type > (in effect we are porting our drivers in this way) *but* it isn't the > expected way to work (see Documentation/vme_api.txt struct > vme_driver's probe() and match() functions and the GE PIO2 VME > driver). And vme_pio2 can’t handle more than 8 boards. This shows that the current design needs some adjustments. Also would be great if probe() and match() allowed for void *private data field. Cheers, Dmitry-- 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/
Powered by blists - more mailing lists