I am planing to develop SDIO mmc Host driver for my Host IP Core. It follows standard register interface as per SD specifications. I want to know if there is any reference available in Linux for that. Is there any reference website that can have information on it
Related
I have been working to connect to a device to a dongle using OpenThread.
I am looking for a .Net Implementation of Openthread.
There is a Zigbee implementaion for .net called ZigbeeNet.
Looking at ZigbeeNet it appears to be a library to interface with Zigbee device over a COM port, so I'm assuming you're also targeting .Net on Windows. The equivalent would be a Network Co-Processor host implementation in OpenThread terminology and unfortunately there isn't a direct .Net implementation. Microsoft implemented a Windows 10 NCP driver which would have been a good starting point, but unfortunately they've dropped support. It still may work but YMMV.
It is possible to run the UNIX host wpantund in a VirtualBox VM and run your .Net application in the guest.
I'm developing automated testing for software which needs to eject and reconnect USB devices automatically at the BUS level, not simply software.
This makes a virtual environment optimum because the virtual hardware can be controlled to emulate such behavior. However, I cannot find a way to do this programmatically through VMWare, VirtualBox, or Zen.
Is this kind of functionality implementable? Thank you!
using VSPhere API, it's soap based web service that can do the same thing as you using VSphere client.
there is a interface called: ReconfigVM_Task may be you can use, see ref at:
Vsphere API Reference
Currently I'm trying to create a vm in a Esxi server using Perl SDK provided by the vmware. The Vcenter host and name must be specified in create_vm.pl to create the vms in the Esxi server directly.
Is there any other SDK(like java) supports to install the vm directly on the Esxi serve without specifying the Vcenter.
link:https://www.vmware.com/support/developer/viperltoolkit/doc/utilityappsdoc/vmcreate.html
You just use the IP or hostname of the ESX/i host where it asks for vCenter. Keep in mind write operations are only supported on licensed versions of ESX/i so if you are using the free version it wont work.
I havent used PERL SDK for VMware, but I have used PowerCLI and PyVmomi for my tasks and the APIs require Host/vCenter IP as their host input.
When you provide VC as the host input, you get the objects related to vCenter for that VM, and if you provide ESXi host IP, you can create,manipulate VMs based on the limits of an ESXi server
I am not able to understand this hierarchy. Host OS runs on bare metal. Where does libvirt reside ? where does the Hypervisor reside ? Is libvirt a necessary lib in the creation of a VM or is it just a better abstraction to the core kernel APIs that provide the the service of creation of VMs? what is the libvirt equivalent in windows that is used by Virtualbox ? Does Hypervisor have any role to play in the scheduling of host OS applications or is it just another process handled by the Host OS. These are a few questions that confuse me. Can anyone explain this in a straight manner ? Thanks!
Host OS runs on bare metal - Yes
where does the Hypervisor reside? - It is a software layer on Host OS
Where does libvirt reside? - It is another API layer on the Host to indirectly interface with the hypervisor.
Is libvirt a necessary lib in the creation of a VM or is it just a better abstraction to the core kernel APIs that provide the the service of creation of
VMs? - Standard abstraction
What is the libvirt equivalent in windows that is used by Virtualbox ? - Libvirt can be used to interact with VirtualBox. Libvirt is known to work as a client (not server) on Windows XP (32-bit), and Windows 7 (64-bit).
Does Hypervisor have any role to play in the scheduling of host OS applications or is it just another process handled by the Host OS. - Just another process
References: http://virtualbox.guru
I'm playing with ovs-dpdk package https://github.com/01org/dpdk-ovs and one thing I don't clearly understand is how can I have OVS bridge and VMs connected to it get access to outside, ie. to the network. On a regular openvswitch the bridge device created by vswitch is 'visible' from linux and can be configured by regular tools (ifconfig, ethtool etc.), so I could create TAP interface and add it to vswitch bridge interface and assign the bridge interface IP address. However with ovs-dpdk this is not the case: any bridge created with ovs-vsctl is not avaialble in userspace linux, at least I don't see it with ifconfig or "ip link show".
Is there another method OVS-DPDK does this? Hopefully someone can shed some light for this problem. Thanks.
ovs-dpdk when it is using DPDK to access the NIC will take over the nic and not allow regular kernel drivers to do their thing.
This means that you will not see the interface any more from the linux host if you bind the hardware with the dpdk io driver. But you can bridge/tap/mirror inside ovs these raw dpdk interfaces in dpdk-ovs to your vm's or to another interface which is visible to the kernel's regular drivers. You just can't do it on the dpdk owned interfaces.
The whole point of integrating dpdk into ovs is to bypass all the kernel drivers and get packets to/from the vswitch as fast as possible so it can route them natively through to your VM's and other local interfaces as you set in your bridge configuration.