similar to: some more Spec questions

Hi, I need another clarification regarding the standard. In floor0 header decode (setup), the point no.7 says that if any of [floor0_order], [floor0_rate], [floor0_bark_map_size], floor0_amplitude_bits], [floor0_amplitude_offset] or [floor0_number_of_books] are less than zero, the stream is not decodable But as we see, all those values are read as unsigned integers. Now I'm not able to

Since documentation is now becoming an important step in the Xiph roadmap, I figure we might as well have a thread to discuss possible problems. I'd like to bring attention to the following tickets in Trac: * 1158 [1] * 1159 [2] * 1169 [3] They all seem like sensible concerns and possible solutions should be discussed here. -Ivo [1] https://trac.xiph.org/ticket/1158 [2]

Hi there ! I'm kinda "yet another guy who tries to implement a vorbis decoder from scratch only by using the vorbis spec". (pure Java, OO-style) (I downloaded the long-awaited-all-in-one-PDF) The data structures are quite ready, I can successfully load the codec setup packet and all its components it's containing. <p><p>So far so good.... Here's my first note

Hello, It seems there is an error in the algorithm for floor0 decode in section 6.2.2 of the Vorbis specification. Here's the relevant part: 3 3) [coefficients] is an empty, zero length vector 4 4) [booknumber] = read an unsigned integer of ilog( [floor0_number_of_books] ) bits 5 5) if ( [booknumber] is greater than the highest number decode codebook ) then

Hello I'm working on a fix-point decoder for AOS/Bluebottle - the proprietary OS of ETH Zurich. I've some problems with Floor0-curve-computation: I don't know what the little omega [cos(w)] stands for, line 3 of the official Vorbis documentation. Does anybody knows what this value means? I've tried to get the answer from the jOrbis and Tremor, but both seem to do - among

We expose multiple char devices ("ports") for simple communication between the host userspace and guest. Sample offline usages can be: poking around in a guest to find out the file systems used, applications installed, etc. Online usages can be sharing of clipboard data between the guest and the host, sending information about logged-in users to the host, locking the screen or session

We expose multiple char devices ("ports") for simple communication between the host userspace and guest. Sample offline usages can be: poking around in a guest to find out the file systems used, applications installed, etc. Online usages can be sharing of clipboard data between the guest and the host, sending information about logged-in users to the host, locking the screen or session

Hello, This is a new iteration of the patches that implement virtio-serial. Changes include: * Adding support for port hot-add * Creating ports at specific ids that can be bound to specific apps / usage * Cleanups This code still doesn't get rid of the support for assigning names to ports but it just has to be ripped out. Comments welcome. Thanks, Amit.

Hello, This is a new iteration of the patches that implement virtio-serial. Changes include: * Adding support for port hot-add * Creating ports at specific ids that can be bound to specific apps / usage * Cleanups This code still doesn't get rid of the support for assigning names to ports but it just has to be ripped out. Comments welcome. Thanks, Amit.

Hello all, This are the latest version of the patches. Lots of things have changed since the last submission. A few of which I remember: - VNC copy / paste works* (* conditions apply) - client vnc copies get propagated to guest port 3 (/dev/vmch3) - guest writes to port 3 (/dev/vmch3) go straight to client's clipboard - sysfs hooks to autodiscover ports - support for 64 ports in this

Hello all, This are the latest version of the patches. Lots of things have changed since the last submission. A few of which I remember: - VNC copy / paste works* (* conditions apply) - client vnc copies get propagated to guest port 3 (/dev/vmch3) - guest writes to port 3 (/dev/vmch3) go straight to client's clipboard - sysfs hooks to autodiscover ports - support for 64 ports in this

Hello, This is the patch that I have for adding support for multiple ports to virtio_console. It's pretty stable in my testing so far and the memory corruption that I had earlier has been resolved in linux-next so I'm proposing this for inclusion. This currently uses device major number 60 from the experimental range; Alan could you please reserve a new major number for virtio_console?

Hello, This is the patch that I have for adding support for multiple ports to virtio_console. It's pretty stable in my testing so far and the memory corruption that I had earlier has been resolved in linux-next so I'm proposing this for inclusion. This currently uses device major number 60 from the experimental range; Alan could you please reserve a new major number for virtio_console?

Hello! First, I must also congratulate the R core team with their accomplishment! I have gotten to like R a lot, and I have recommended it for inclusion in an "Astronomy for Linux"-distribution which is in use by many professional astronomers and observatories. I'm currently working on importing data from files created by a C program (that I have not written myself, I have the

Hello all, Here is a new iteration of the patch series that implements a transport for guest and host communications. I've tested for compatibility (old qemu & new kernel, new qemu & old kernel, new qemu & new kernel) and it all works fine*. There are a few items on my todo list but this works well. New since last send: - live migration support** - write path in the guest

Hello all, Here is a new iteration of the patch series that implements a transport for guest and host communications. I've tested for compatibility (old qemu & new kernel, new qemu & old kernel, new qemu & new kernel) and it all works fine*. There are a few items on my todo list but this works well. New since last send: - live migration support** - write path in the guest

Hello all, Here is a new iteration of the patch series that implements a transport for guest and host communications. The code has been updated to reuse the virtio-console device instead of creating a new virtio-serial device. I've tested for compatibility (old qemu & new kernel, new qemu & old kernel, new qemu & new kernel) and it all works fine. There are a few items on my

Hello all, Here is a new iteration of the patch series that implements a transport for guest and host communications. The code has been updated to reuse the virtio-console device instead of creating a new virtio-serial device. I've tested for compatibility (old qemu & new kernel, new qemu & old kernel, new qemu & new kernel) and it all works fine. There are a few items on my