search for: conecpt

This is a minor release of Shorewall which rolls up a number of bug fixes. New features include: 1. A NEWNOTSYN option has been added to shorewall.conf. This option determines whether Shorewall accepts TCP packets which are not part of an established connection and that are not ''SYN'' packets (SYN flag on and ACK flag off). 2. The need for the

Hi, we've proof of conecpt system for speech recognition on Asterisk. We would like to send results of recognition back to user in standard way. Currently we're considering using sendtext command and it works with Firefly. But I'm curious what soft or hard ip phones that can connect to Asterisk support such feature...

On 16/01/2017 18:26, Fam Zheng wrote: >> Is the endianness correct for big-endian host here? > > I think so. The fc_host sysfs uses u64 to represent port_name and node_name, > this patch does the same, so using virtio_* helpers for these fields should > handle the endianness correctly. I was suspicious about it because they are defined as "u8 x[8]" in the

On 16/01/2017 18:26, Fam Zheng wrote: >> Is the endianness correct for big-endian host here? > > I think so. The fc_host sysfs uses u64 to represent port_name and node_name, > this patch does the same, so using virtio_* helpers for these fields should > handle the endianness correctly. I was suspicious about it because they are defined as "u8 x[8]" in the

...'roxygenize()') already exists (because it is already part of 'pkga'). My question is hence twofold: 1) What would be possible workarounds that allow me to a) keep using 'roxygen2' and link documentation of pkga::foo() with that of pkgb::foo() (as they do belong together conecptionally) 2) Is there a need to address this problem on a higher level in the future? My feeling is that more people are starting to use S4 which, IMHO, is a good thing as it allows to systematically build upon code of other programmers. But then I guess we would need some sort of an "inter-...

...would read it as a > little-endian u64, 0xcdab896745230150. Maybe your QEMU patch is also > writing things as little-endian 64-bit integers, rather than 8-element > arrays of bytes? Yes, they all used 64-bit integers in a "less surprising" endian. I think there is an endianness conecpt to WWN, as in 0x500123456789abcd; and there is an native endianness to virtio, which is little-endian. If we use a "u8 x[8]" type in the spec and want the WWN's MSB, namely the 0x50 stuff, to be the first byte, is it worth to explicitly document that to avoid confusion? Fam

...'roxygenize()') already exists (because it is already part of 'pkga'). My question is hence twofold: 1) What would be possible workarounds that allow me to a) keep using 'roxygen2' and link documentation of pkga::foo() with that of pkgb::foo() (as they do belong together conecptionally) 2) Is there a need to address this problem on a higher level in the future? My feeling is that more people are starting to use S4 which, IMHO, is a good thing as it allows to systematically build upon code of other programmers. But then I guess we would need some sort of an "inter-...