similar to: next version

I scanned the website with linkchecker and found quite a lot of dead links. This commit fixes or removes them. --- developers.html | 2 +- documentation_tasks.html | 2 +- download.html | 12 ++++++------ faq.html | 2 +- features.html | 2 +- feeds/feed.xml | 8 ++++++++ format.html | 8 ++++----

I scanned the website with linkchecker and found quite a lot of dead links. This commit fixes or removes them. --- developers.html | 2 +- documentation_tasks.html | 2 +- download.html | 14 +++++++------- faq.html | 2 +- features.html | 2 +- feeds/feed.xml | 8 ++++++++ format.html | 8 ++++----

I'm copying the flac-dev list to see if anyone has any feedback also... --- Juhana Sadeharju <kouhia@nic.funet.fi> wrote: > Hello again. I had time to check the paper out. I have filled the > steps given in the paper with formulae, and then written a piece of > C code. It is not complete code, but could be a reasonable start. > Maybe there is one typo in the paper -- I have

Great to hear that things are going smoothly, Josh. My $.02 is that it is worth making 110% sure that you/we've tweaked the codec for speed/compression as much as can be done *before* 1.0, since we're really not under any kind of deadline. Sure, it would be nice to get it out the door, but why not have it rival Shorten and Monkey's right from the start? I'm *still* working on

To those interested: You mention on the website that you use a Rice style encoding scheme for residual error encoding. After some experimentation, I believe I've have discovered a method which might be more efficient. Take the signs away from the errors storing them each as a one bit prefix. Now say we consider two errors. Each error will require at least one bit (probably more) of

Hi Jean, On 04/08/2017 20:19, Jean-Philippe Brucker wrote: > This is the continuation of my proposal for virtio-iommu, the para- > virtualized IOMMU. Here is a summary of the changes since last time [1]: > > * The virtio-iommu document now resembles an actual specification. It is > split into a formal description of the virtio device, and implementation > notes. Please find

Hi Eric, > -----Original Message----- > From: Auger Eric [mailto:eric.auger at redhat.com] > Sent: Tuesday, September 12, 2017 10:43 PM > To: Jean-Philippe Brucker <jean-philippe.brucker at arm.com>; > iommu at lists.linux-foundation.org; kvm at vger.kernel.org; > virtualization at lists.linux-foundation.org; virtio-dev at lists.oasis-open.org > Cc: will.deacon at

Hello everyone, I wasn't planning on sending out v0.4 until ENOSPC was fixed, but Frank Groeneveld narrowed down a bug with the file data checksumming code on highmem 32bit machines. Basically the way I was using cryptomgr made it incorrectly calculate checksums on highmem pages. So to simplify things, I've switched over to plain libcrc32c. Anyone running on a 32 bit with highmem is

Hello everyone, I wasn't planning on sending out v0.4 until ENOSPC was fixed, but Frank Groeneveld narrowed down a bug with the file data checksumming code on highmem 32bit machines. Basically the way I was using cryptomgr made it incorrectly calculate checksums on highmem pages. So to simplify things, I've switched over to plain libcrc32c. Anyone running on a 32 bit with highmem is

Hi jean, On 04/08/2017 20:19, Jean-Philippe Brucker wrote: > This is the continuation of my proposal for virtio-iommu, the para- > virtualized IOMMU. Here is a summary of the changes since last time [1]: > > * The virtio-iommu document now resembles an actual specification. It is > split into a formal description of the virtio device, and implementation > notes. Please find

Hi all, I am interested in building a stand alone Rice Encoder/Decoder, using FLAC source code as a starting point. I've read the theory behind it, and I am very interested in info theory. However, I am struggling with how exactly I would implement the theory in code. I'm a newbie to computer science (only 1 year experience). I have read the format and documentation links on the FLAC

Hello. I thought I'd introduce myself. I'm the guy that wrote kexis way back when. For those of you that dont know, kexis was written before flac, and pretty much does what flac does, although its not nearly as nice or robust. I wrote kexis actualy cause I was interested in playing around with lossless compression and shorten was about the only tool that was linux friendly, but had a

Maybe I was too quick here. Does gcc record the incoming edge to a phi? If so, won’t those change when you delete blocks in a non-trivial manner? How are those updated? From: David Callahan <dcallahan at fb.com<mailto:dcallahan at fb.com>> Date: Saturday, January 30, 2016 at 7:02 AM To: Daniel Berlin <dberlin at dberlin.org<mailto:dberlin at dberlin.org>>, Hal Finkel

Pigeonhole download page has links for extdata plugin up to v0.4 but nothing more and no link to the master repository https://pigeonhole.dovecot.org/download.html I want to use with dovecot 2.3.2rc1 but v0.4 won't compile with it. Thanks for helping ------------------------------------------------- ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's

Hi Jean, On Mon Oct 23, 2017 at 10:32:41AM +0100, Jean-Philippe Brucker wrote: > This is version 0.5 of the virtio-iommu specification, the paravirtualized > IOMMU. This version addresses feedback from v0.4 and adds an event virtqueue. > Please find the specification, LaTeX sources and pdf, at: > git://linux-arm.org/virtio-iommu.git viommu/v0.5 >

Hi Linu, On 24/10/17 07:27, Linu Cherian wrote: > Hi Jean, > > On Mon Oct 23, 2017 at 10:32:41AM +0100, Jean-Philippe Brucker wrote: >> This is version 0.5 of the virtio-iommu specification, the paravirtualized >> IOMMU. This version addresses feedback from v0.4 and adds an event virtqueue. >> Please find the specification, LaTeX sources and pdf, at: >>

In practice, APT is not faster to build than rdf. The df calculator we use is linear time and quite fast. Updating is also pretty trivial since it's only deletes of dead and unreachable code. So anything it reached can be replaced with undef in most cases. Cd-dce is not slower in GCC than dce On Fri, Jan 29, 2016, 8:31 PM David Callahan <dcallahan at fb.com> wrote: > I think you

I have the following code and data data.csv "","Goal","Frequency","Weight","Group" "1","Move",13,0.245283018867925,"Public" "2","Create",10,0.188679245283019,"Public" "3","Strengthen",30,0.566037735849057,"Public"

On my lists of things to do for 1.0 were 1) improve seeking; and 2) speed up both encoding and decoding. Seeking seems better now (I added the SEEKTABLE and tweaked the search algorithm). On the way, one of my encoding experiments worked. By taking advantage of a relatively unused area in the Rice parameter space, I added an escape code for switching to flat encoding within a partition.

thanks you AKi for alway responding! >> Pigeonhole download page has links for extdata plugin up to v0.4 but >> nothing more and no link to the master repository >> >> https://pigeonhole.dovecot.org/download.html >> >> I want to use with dovecot 2.3.2rc1 but v0.4 won't compile with it. > > Seems to need v0.5 for it. What are you using it for? For a