Hi,
>>To avoid any locks in qemu backend and not to introduce thread safety
>>into qemu block-layer I open same backend device several times, one
>>device per one MQ. e.g. the following is the stack for a virtio-blk
>>with num-queues=2:
Could it be possible in the future to not open several
Am 25.05.2016 um 01:10 schrieb Eric Blake:
On 05/24/2016 02:40 AM, Peter Lieven wrote:
until now the allocation map was used only as a hint if a cluster
is allocated or not. If a block was not allocated (or Qemu had
no info about the allocation status) a get_block_status call was
issued to
Hello,
What would be the best way to provide GUI for peripheral control?
This is not for linux rather than embedded system running home brew rtos.
For example an GPIO module, I would need an UI to toggle an GPIO and see
the output, like press an button and simulate it turning on an LED.
Would
Am 27.05.2016 um 10:55 schrieb Kevin Wolf:
Am 27.05.2016 um 02:36 hat Fam Zheng geschrieben:
On Thu, 05/26 11:20, Paolo Bonzini wrote:
On 26/05/2016 10:30, Fam Zheng wrote:
This doesn't look too wrong... Should the right sequence of events be
head/after_head or head/after_tail? It's
On 2016-05-29 10:11, Wei Wang wrote:
> Signed-off-by: Wei Wang
> ---
> FutureWorks | 21 +
> 1 file changed, 21 insertions(+)
> create mode 100644 FutureWorks
>
> diff --git a/FutureWorks b/FutureWorks
> new file mode 100644
> index 000..210edcd
>
On 2016年05月30日 14:04, Jean-Christophe DUBOIS wrote:
Le 30/05/2016 04:19, Jason Wang a écrit :
On 2016年05月21日 16:01, Jean-Christophe Dubois wrote:
This patch series adds Gb ENET Ethernet device to the i.MX6 SOC.
The ENET device is an evolution of the FEC device present on the
i.MX25 SOC
Le 30/05/2016 04:19, Jason Wang a écrit :
On 2016年05月21日 16:01, Jean-Christophe Dubois wrote:
This patch series adds Gb ENET Ethernet device to the i.MX6 SOC.
The ENET device is an evolution of the FEC device present on the
i.MX25 SOC
and is backward compatible with it.
Therefore the ENET
201 - 207 of 207 matches
Mail list logo