search for: littles

Thanks for the answer. So data are stored in little-endian format on the WAVE file. But have I to encode in big endian format or little endian is ok?! Thanks ---------- Original Message ---------------------------------- From: "John Miles" <jmiles@pop.net> Date: Tue, 23 May 2006 12:15:05 -0700 >You are probably reading little-endian samples on a big-endian platform, and

List, A recent discussion over on XiphWiki is trying to decide if OggPCM should support only little-endianness or the usual combo of big and little. It started with the following statement by an user (Qqq): "Portable players are usually ARM, which is usually little-endian. The Macintosh is now little-endian. Obviously the PC is little-endian. Clearly there is a winner. It's long past

Hi, all, I have a question about encoding/decoding in big/little endian machines. I have a client running in an old PowerBook G4 with big-endian CPU, the audio stream is encoded then transmitted to a Mac Mini with little-endian CPU, and decoded in this Mac Mini. I am wondering the decoded stream is in big-endian or little-endian? What kind of necessary steps I need to process when I build the

Hi, > > static const uint32_t virtio_gpu_cursor_formats[] = { > > +#ifdef __BIG_ENDIAN > > + DRM_FORMAT_BGRA8888, > > +#else > > DRM_FORMAT_ARGB8888, > > +#endif > > DRM formats are supposed to be little endian, so this isn't really > correct. Well, maybe they where *intended* to be little endian at some point in the past. The actual code

Hi, > > static const uint32_t virtio_gpu_cursor_formats[] = { > > +#ifdef __BIG_ENDIAN > > + DRM_FORMAT_BGRA8888, > > +#else > > DRM_FORMAT_ARGB8888, > > +#endif > > DRM formats are supposed to be little endian, so this isn't really > correct. Well, maybe they where *intended* to be little endian at some point in the past. The actual code

Hello all, I am running dovecot- 2.3.5.2 with mdbox storage. I deleted the dovecot.index* from all my folders, which led to mails not being displayed. I rebuilt the indexes for all the users after that, using: doveadm force-resync -u user at domain "*" However, the problem now is that Outlook,configured for IMAP, is not able to sync the mails with the server. I can login to the server

I am seeing the following errors in my logs, which I believe are preventing Outlook from syncing. How do I solve these? Can I just delete the index.cache?? Jun 18 11:23:34 imap(technical at mydomain.co.ke)<59754><g5UC1JSLPhkpUFt/>: Error: Corrupted record in index cache file /var/spool/virtual/ mydomain.co.ke/technical/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.cache: UID 29:

Hi Daniel, I know you only did a small change to support big/little endian reference outputs, but maybe you can help me. I'm running the test-suite on AArch64 and it's correctly detecting little-endian, even setting the ENDIAN=little on configure and Makefiles alike, but it still generates "big-endian" from Makefile.programs. Here's the first lines of: sandbox/test-...$

Hello. Using the ":include", which generates a "LEFT OUTER JOIN" SQL command, it is possible to eagerly preload second order data objects (children) for a given association. I wanted to know, if it is possible to eagerly preload and cache third order (or more) data objects, which are little-children or little-little-children. As I''ve seen. it is possible to add

We have dropped dovecot in place of UW-IMAP for about 40000 users and have solved our immediate problem: disk I/O overload, mainly from people doing POP3 and "leave mail on server". Thank you! Now i got loads of dovecot error messages in the logs and don't know if there is any significance. Here are a few examples: The most common event is: 2007-12-06 16:00:17.837654500 dovecot:

Ivo Emanuel Gon?alves wrote: > List, > > A recent discussion over on XiphWiki is trying to decide if OggPCM > should support only little-endianness or the usual combo of big and > little. > > It started with the following statement by an user (Qqq): > > "Portable players are usually ARM, which is usually little-endian. The > Macintosh is now little-endian.

On Tue, Apr 21, 2015 at 06:22:20PM +0200, Greg Kurz wrote: > On Tue, 21 Apr 2015 16:06:33 +0200 > "Michael S. Tsirkin" <mst at redhat.com> wrote: > > > On Fri, Apr 10, 2015 at 12:20:21PM +0200, Greg Kurz wrote: > > > The VNET_LE flag was introduced to fix accesses to virtio 1.0 headers > > > that are always little-endian. It can also be used to

On Tue, Apr 21, 2015 at 06:22:20PM +0200, Greg Kurz wrote: > On Tue, 21 Apr 2015 16:06:33 +0200 > "Michael S. Tsirkin" <mst at redhat.com> wrote: > > > On Fri, Apr 10, 2015 at 12:20:21PM +0200, Greg Kurz wrote: > > > The VNET_LE flag was introduced to fix accesses to virtio 1.0 headers > > > that are always little-endian. It can also be used to

Dear R user, I am running R under Windows 2000. I am looking for a routine for importing - shape files (ESRI) into R - dbase files (FOXPRO) into R and I am looking for time-space models for description and prediction of Bernoulli-, Binomial- and Poissonvaraibles. Thank's a lot for a reply. Sincerely yours, Ekkehardt Altpeter Swiss Federal Office of Public

> > And in the test file there is a line: > > XFAIL: powerpc64, s390x, mips, sparc > > This is a crude attempt at "XFAIL: big-endian". The mips entry here is just > wrong if the system is little-endian - the test passes on little-endian machines > and fails on big-endian. This is obviously a problem. 'XFAIL: mips' counts as an XFAIL for all mips targets

Hi, I am wondering why we dont support PPC32 LE? Here is the output of llvm-mc --version, in which only PPC32, PPC64 & PPC64LE are supported. $ llvm-mc --version LLVM (http://llvm.org/): LLVM version 3.6.2 Optimized build with assertions. Built Aug 2 2015 (11:39:46). Default target: x86_64-apple-darwin15.4.0 Host CPU: core-avx2 Registered Targets: aarch64 - AArch64

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everybody, I have a little problem, when i am trying to read an email via imap my thunderbird is trying (for ever) to read it. My dovecot tells me : dovecot: Apr 29 22:47:23 Error: IMAP(ebalaskas): FETCH for mailbox oreilly UID 24 got too little data: 2041 vs 2471 dovecot: Apr 29 22:47:24 Error: IMAP(ebalaskas): FETCH for mailbox oreilly UID 24

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everybody, I have written a little Howto, to set up to ADDCa together with bind9 as DNS-Backend. You will find all commands in the right order. I have tested it with debian jessie and Ubuntu-Server. It's in english ;-) https://www.kania-online.de/wp-content/uploads/2016/10/samba-bind-dlz.tx t Stefan -----BEGIN PGP SIGNATURE-----

Hello, Sorry if I am off topic a little. I am looking for an email host provider that supports dovecot, sieve and manage sieve. Ideally with the roundcube webmail and managesieve plugin Better if it is in Europe or switzerland. I don't mind paying a little. Thanks, Andr?.

When I compile klibc on little-endian mips, I get: KLIBCLD klibc/libc.so ld: klibc/arch/mips/crt0.o: compiled for a little endian system and target is big endian ld: klibc/arch/mips/crt0.o: endianness incompatible with that of the selected emulation ld: failed to merge target specific data of file klibc/arch/mips/crt0.o When I change "elf32-tradbigmips" to