Quoting Robert Millan (2015-09-15 22:11:15)
> like, how to service ioctls without libtrivfs?
Is there a reason why you don't want to use libtrivfs?
Cheers,
Justus
Robert Millan, le Thu 17 Sep 2015 21:55:32 +0200, a écrit :
> As for the rest of PCI devices, AFAICT they're free to be used by whoever
> wants them. My understanding is there's no need for an arbiter / multiplexer
> as long as all the code playing with PCI devices is well-aware of its limits.
Yes
Hi Samuel,
El 17/09/15 a les 17:35, Samuel Thibault ha escrit:
For me, the idea could be that you run a rump translator per PCI device,
That doesn't fit very well with the way Rump works. With Rump you select
drivers rather than specific devices. So for example if you start a Rump
instance an
Diego Nieto Cid, le Thu 17 Sep 2015 12:50:10 -0300, a écrit :
> From what he said
>
> > The other problem I had is that I don't know how to make a single translator
> > service two separate device nodes (obviously you don't want to start a
> > different Rump instance for /dev/audio, /dev/mixer, et
2015-09-17 12:35 GMT-03:00 Samuel Thibault :
> Diego Nieto Cid, le Thu 17 Sep 2015 12:25:21 -0300, a écrit :
>> In that way there are several sound related translators separating the
>> concerns
>> while the hardwarde is still accessed by a single translator avoiding the
>> conflicts Robert mentio
Diego Nieto Cid, le Thu 17 Sep 2015 12:25:21 -0300, a écrit :
> In that way there are several sound related translators separating the
> concerns
> while the hardwarde is still accessed by a single translator avoiding the
> conflicts Robert mentioned.
Which conflict?
For me, the idea could be th
2015-09-16 20:06 GMT-03:00 Samuel Thibault :
> Diego Nieto Cid, le Wed 16 Sep 2015 22:12:19 +, a écrit :
>> Except for how to know which one the send right was obtained from in
>> the translator when a message from a client comes?
>
> term is probably easier to have a look at: see the file_set_
