search for: offset_

...mation, we are considering two different possibilities for updating the bitcode wrapper specification. The first is to simply add a single 32bit wide field at the end of the existing bitcode wrapper format field. This would result in the new structure looking like this: [Magic_{32}, Version_{32}, Offset_{32}, Size_{32}, CPUType_{32}, BitcodeVersion_{32}] All of the existing fields would keep their current meanings, and the new field BitcodeVersion is simply appended with the format described in the first paragraph. A second idea was to use the existing Version field in the bitcode wrapper format...

...mation, we are considering two different possibilities for updating the bitcode wrapper specification. The first is to simply add a single 32bit wide field at the end of the existing bitcode wrapper format field. This would result in the new structure looking like this: [Magic_{32}, Version_{32}, Offset_{32}, Size_{32}, CPUType_{32}, BitcodeVersion_{32}] All of the existing fields would keep their current meanings, and the new field BitcodeVersion is simply appended with the format described in the first paragraph. A second idea was to use the existing Version field in the bitcode wrapper format...

...>> wrapper specification. >> >> >> >> The first is to simply add a single 32bit wide field at the end of the >> existing bitcode wrapper format field. This would result in the new >> structure looking like this: >> >> [Magic_{32}, Version_{32}, Offset_{32}, Size_{32}, CPUType_{32}, >> BitcodeVersion_{32}] >> >> All of the existing fields would keep their current meanings, and the new >> field BitcodeVersion is simply appended with the format described in the >> first paragraph. >> >> A second idea was to...

Hello all. I've been playing around with theora since it first entered CVS, and I like what I'm seeing. Today I've been fixing xine's theoraplugin to understand theora_info.frame_{width,height} and theora_info.offset_{x,y}. I only got it working after some experimenting and basically copying the code from player_example. A few questions related to this: 1. What are the legal requirement in regard to copying code from your BSD-style license to xine, which is under the GPL. It would seem that the original author...

These assorted patches end up with adding virtio-scsi support to libguestfs. It passes libguestfs-test-tool, but I haven't yet tried to run the full set of tests. In theory > 26 devices can be added, but it's likely that certain parts of the daemon will break if you actually try this. This of course needs to be fixed. Thanks Paolo Bonzini for invaluable help. Rich.

...>>> >>> >>> >>> The first is to simply add a single 32bit wide field at the end of the >>> existing bitcode wrapper format field. This would result in the new >>> structure looking like this: >>> >>> [Magic_{32}, Version_{32}, Offset_{32}, Size_{32}, CPUType_{32}, >>> BitcodeVersion_{32}] >>> >>> All of the existing fields would keep their current meanings, and the >>> new field BitcodeVersion is simply appended with the format described in >>> the first paragraph. >>> >&g...

More comprehensive support for virtio-scsi. Passes all the tests. Rich.

...ssibilities for updating the bitcode wrapper > specification. > > > > The first is to simply add a single 32bit wide field at the end of the > existing bitcode wrapper format field. This would result in the new > structure looking like this: > > [Magic_{32}, Version_{32}, Offset_{32}, Size_{32}, CPUType_{32}, > BitcodeVersion_{32}] > > All of the existing fields would keep their current meanings, and the new > field BitcodeVersion is simply appended with the format described in the > first paragraph. > > A second idea was to use the existing Version fie...

Hi, despite the warnings on the website ;-) I played with the current CVS source of theora on Windows 2000 w/ Microsoft Visual C++. The codec and the "experimental" example programs compiled fine. I also encoded a 33 MB MPEG2 (?) video (3 minute trailer) to a 14 MB .OGG using "mplayer -vo yuv4mpeg -ao pcm" and the "encoderwin" sample program, and play it with the

Introduce Cortex-A7 with a scalable proc_info_list which including cpu id and cpu initialize function. In head.S, search cpu specific MIDR in procinfo and call such initialize function. Currently, support Cortex-A7 and Cortex-A15. Signed-off-by: Bamvor Jian Zhang <bjzhang@suse.com> --- changes since v2 1), define cpu_init function instead of assemble jump code in struct proc_info_list 2),

This still isn't working at the moment. See: http://marc.info/?t=139457409300003&r=1&w=2 This set of patches: - Adds new APIs to support discard in libguestfs. - Adds discard support to virt-format. - Adds discard support to virt-sysprep. - Implements virt-sparsify --in-place. Rich.