Re: [DNG] kernel drivers [WAS: How long should I expect to wait for openrc to be ready in devuan ascii]

2017-07-14 Thread Didier Kryn
Le 14/07/2017 à 11:26, Didier Kryn a écrit : Something like 10^18 neutrinos cross everyone of us ( depends on individual size :-) ), comming from the thermonuclear reactor at the core of the sun. 10^18 per second. ___ Dng mailing list

Re: [DNG] kernel drivers [WAS: How long should I expect to wait for openrc to be ready in devuan ascii]

2017-07-14 Thread Didier Kryn
Le 13/07/2017 à 18:03, Enrico Weigelt, metux IT consult a écrit : On 12.07.2017 15:23, Didier Kryn wrote: Le 11/07/2017 à 21:22, Jamey Fletcher a écrit : That sounds suspiciously like you're working on the LHC! Or perhaps the VLA... Particle Physics, although not LHC :-) Neutrino

Re: [DNG] kernel drivers [WAS: How long should I expect to wait for openrc to be ready in devuan ascii]

2017-07-13 Thread Enrico Weigelt, metux IT consult
On 12.07.2017 15:23, Didier Kryn wrote: Le 11/07/2017 à 21:22, Jamey Fletcher a écrit : That sounds suspiciously like you're working on the LHC! Or perhaps the VLA... Particle Physics, although not LHC :-) Neutrino Physics. Ah, did you folks find a way for catching large quantities of

Re: [DNG] kernel drivers [WAS: How long should I expect to wait for openrc to be ready in devuan ascii]

2017-07-13 Thread Enrico Weigelt, metux IT consult
On 11.07.2017 19:07, Didier Kryn wrote: The system isn't a server open to the public. It's a kind of industrial process (though it's for fundamental research). Only a limited number of users have an account on the hosts and only members of the vme group are given permission to access the

Re: [DNG] kernel drivers [WAS: How long should I expect to wait for openrc to be ready in devuan ascii]

2017-07-12 Thread Didier Kryn
Le 11/07/2017 à 21:22, Jamey Fletcher a écrit : That sounds suspiciously like you're working on the LHC! Or perhaps the VLA... Particle Physics, although not LHC :-) Neutrino Physics. Didier ___ Dng mailing list Dng@lists.dyne.org

Re: [DNG] kernel drivers [WAS: How long should I expect to wait for openrc to be ready in devuan ascii]

2017-07-11 Thread Jamey Fletcher
> Le 11/07/2017 à 14:30, Enrico Weigelt, metux IT consult a écrit : > We have two detectors running. On each of them, a sophisticated > trigger logic decides when interesting data has been seen and triggers > 400 channels of waveform digitizers (like 400 synchronous oscilloscope > channels).

Re: [DNG] kernel drivers [WAS: How long should I expect to wait for openrc to be ready in devuan ascii]

2017-07-11 Thread Didier Kryn
Le 11/07/2017 à 14:30, Enrico Weigelt, metux IT consult a écrit : On 05.07.2017 23:30, Didier Kryn wrote: > And there are a whole menagerie of addressing and transfer protocols, > including chained dma transfers Especially things like DMA are naturally kernel domain. I wouldn't ever allow

Re: [DNG] kernel drivers [WAS: How long should I expect to wait for openrc to be ready in devuan ascii]

2017-07-11 Thread Enrico Weigelt, metux IT consult
On 05.07.2017 23:30, Didier Kryn wrote: > And there are a whole menagerie of addressing and transfer protocols, > including chained dma transfers Especially things like DMA are naturally kernel domain. I wouldn't ever allow any direct access to dma controllers from userland. > In our case it

Re: [DNG] kernel drivers [WAS: How long should I expect to wait for openrc to be ready in devuan ascii]

2017-07-05 Thread Didier Kryn
Sorry if this is becommint a very specialized discussion. I think this thread will not need to continue very long. Le 05/07/2017 à 22:53, Enrico Weigelt, metux IT consult a écrit : On 05.07.2017 06:38, Didier Kryn wrote: Also the API of their driver looked in contradiction with the

Re: [DNG] kernel drivers [WAS: How long should I expect to wait for openrc to be ready in devuan ascii]

2017-07-05 Thread Enrico Weigelt, metux IT consult
On 05.07.2017 06:38, Didier Kryn wrote: Also the API of their driver looked in contradiction with the one of Gabriel Paubert who has been developping a discontinued suite of free VME drivers for Debian. I talked with Gabriel Paubert more than a decade ago because I have been using his

Re: [DNG] kernel drivers [WAS: How long should I expect to wait for openrc to be ready in devuan ascii]

2017-07-04 Thread Didier Kryn
Le 04/07/2017 à 02:55, Enrico Weigelt, metux IT consult a écrit : Motorolla/Emerson used to provide VME drivers for free, but OOT despite the fact that the specs of the Tundra PCI-VME bridge were public. They didn't do it for all releases. Why didn't the work with the community to get

Re: [DNG] kernel drivers [WAS: How long should I expect to wait for openrc to be ready in devuan ascii]

2017-07-03 Thread Enrico Weigelt, metux IT consult
On 07/01/17 22:50, Didier Kryn wrote: Precisely, the domain of embedded devices is one where HW vendors write drivers. Most of the time you don't wanna use them. Especially not proprietary ones. Just look eg. at fsl's gpu drivers: totally insecure and harmful. (back when I read their adreno

Re: [DNG] kernel drivers [WAS: How long should I expect to wait for openrc to be ready in devuan ascii]

2017-07-01 Thread Didier Kryn
Le 01/07/2017 à 22:09, Enrico Weigelt, metux IT consult a écrit : On 07/01/17 14:43, Didier Kryn wrote: > They preserve the external API but change all the rest. Yes, that's the way we support zillions of different devices, especially in the embedded world, w/ relatively small efforts (OF was

[DNG] kernel drivers [WAS: How long should I expect to wait for openrc to be ready in devuan ascii]

2017-07-01 Thread Enrico Weigelt, metux IT consult
On 07/01/17 14:43, Didier Kryn wrote: > They preserve the external API but change all the rest. Yes, that's the way we support zillions of different devices, especially in the embedded world, w/ relatively small efforts (OF was probably one of the most important steps) and still offer good