similar to: [LLVMdev] [PATCH] Slim Reader/Writer Support

Hello, I have installed SlimServer for Windows on my desktop and Asterisk on a Red Hat Linux machine. I am able to play mp3's for music on hold when mp3s are on the Linux server, and to play streaming mp3's with Windows Media Player and Winamp on Windows using the slim server. I also have mpg123 on my Linux, apparently installed correctly, since it works for local moh. I put the

Hello Everyone, I was wondering does anyone know how I can slim down Centos install, what I mean by slim down is whenever I install Centos with nothing but xen. I have all type stuff that is not needed like bluetooth and etc. This is a server, so I know that bluetooth is not need but I don't have any other menus to remove software when install from cd. So what would be the best way to slim

This patch adds the slim core rproc driver to the STi section of the MAINTAINERS file. Signed-off-by: Peter Griffin <peter.griffin at linaro.org> --- MAINTAINERS | 2 ++ 1 file changed, 2 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 0bbe4b1..5dd3b24 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -1749,6 +1749,7 @@ F: drivers/phy/phy-stih407-usb.c F:

Hi, I am just letting you know that I have not been able to build LLVM using CMake since I ran svn up yesterday. And it would be great if somebody could tell me whether the problem is on my end. What I did was, ~/llvm$ svn up ~/llvm$ mkdir cmakebuild ~/llvm$ cd cmakebuild ~/llvm/cmakebuild$ cmake -DCMAKE_BUILD_TYPE:STRING="Release" -DLLVM_TARGETS_TO_BUILD:STRING="X86" ..

Hello, I downloaded LLVM 2.6 and was attempting to compile it with TDM-GCC 4.4.1-tdm2-sjlj + cmake 2.6.4 and this happened: =============Console=================== C:\projects\game-editor\LLVM\build-root>mingw32-make [ 2%] Built target LLVMSystem [ 5%] Built target LLVMSupport [ 7%] Built target tblgen [ 7%] Built target intrinsics_gen [ 10%] Built target LLVMCore [ 12%] Built target

Hi, I'm confused by the comment and the source code of lib/Support/Mutex.cpp and lib/Support/RWMutex.cpp. In these files there are: // This variable is useful for situations where the pthread library has been // compiled with weak linkage for its interface symbols. This allows the // threading support to be turned off by simply *not linking against -lpthread*. // In that situation, the

Hi, The old llvm::sys::RWMutex use platform-specific lock mechanism to implement read/write lock. For example, SRWLock on Windows and pthread read/write lock on *nix systems. However, in comparison with the approach that implement read/write lock base on std::atomic, the old methods not only has potential performance issue(Sorry I can't provide concrete evidence, any benchmark result is

On Tue, Feb 13, 2018 at 04:56:19PM -0600, Keith Grider via samba wrote: > I am trying to compile samba4 for a raspberry pi. I just want it to be > able to share a folder of files. I do not need or want all the > functionality and features of a full blown samba installation. This i s on > Arch and it is an armv6 raspberry. > I have some partial instructions for compiling without

Author: wroche Repository: /hg/zfs-crypto/gate Revision: 675f4a70198561e1efa783921d9a48232db00bf8 Log message: 6376632 writer and reader of a pipe can race and leave writer process hung. 6396390 FIFOPOLLRBAND flag should not be set to the same value as FIFOISOPEN Files: update: usr/src/uts/common/fs/fifofs/fifosubr.c update: usr/src/uts/common/fs/fifofs/fifovnops.c update:

Hi Lee, Thanks for reviewing. On Tue, 30 Aug 2016, Lee Jones wrote: > On Fri, 26 Aug 2016, Peter Griffin wrote: > > > slim core is used as a basis for many IPs in the STi > > chipsets such as fdma and demux. To avoid duplicating > > the elf loading code in each device driver a slim > > rproc driver has been created. > > > > This driver is designed to

Sorry if these questions are getting tiring, but I want to get the list of servers from "smbtree -NS" from an embedded system (e.g., custom wireless router firmware). Unfortunately, compiling smbtree ends up being a couple of MB large. I've tried a bunch of basic optimizations to shrink the executable size as possible (e.g., using -f{function,data}-sections and --gc-sections,

slim core is used as a basis for many IPs in the STi chipsets such as fdma and demux. To avoid duplicating the elf loading code in each device driver a slim rproc driver has been created. This driver is designed to be used by other device drivers such as fdma, or demux whose IP is based around a slim core. The device driver can call slim_rproc_alloc() to allocate a slim rproc and slim_rproc_put()

I am trying to compile samba4 for a raspberry pi. I just want it to be able to share a folder of files. I do not need or want all the functionality and features of a full blown samba installation. This i s on Arch and it is an armv6 raspberry. I have some partial instructions for compiling without ad-dc and ads but keep getting a failed build. I have been grepping all over and I have been unable

I think this issue is that we were not using the INTERCEPTOR macros to define these functions. The following patch seems to work for me to get the build linking again, however, I cannot test -- when I run check-asan, I get: 2> lit.py: lit.common.cfg:59: fatal: Invalid llvm_tools_dir config attribute: 'E:/llvm/2013/$(Configuration)/bin' ~Aaron On Thu, Oct 23, 2014 at 1:20 PM, Aaron

http://llvm.org/bugs/show_bug.cgi?id=21241 ? 2014-10-23 10:18 GMT-07:00 Aaron Ballman <aaron at aaronballman.com>: > On Thu, Oct 23, 2014 at 1:15 PM, Aaron Ballman <aaron at aaronballman.com> wrote: >> On Thu, Oct 23, 2014 at 1:13 PM, Timur Iskhodzhanov <timurrrr at google.com> wrote: >>> Yes it is. >>> Are you doing a Debug or Release build?

On Fri, 26 Aug 2016, Peter Griffin wrote: > slim core is used as a basis for many IPs in the STi > chipsets such as fdma and demux. To avoid duplicating > the elf loading code in each device driver a slim > rproc driver has been created. > > This driver is designed to be used by other device drivers > such as fdma, or demux whose IP is based around a slim core. > The

On Fri, 26 Aug 2016, Peter Griffin wrote: > slim core is used as a basis for many IPs in the STi > chipsets such as fdma and demux. To avoid duplicating > the elf loading code in each device driver a slim > rproc driver has been created. > > This driver is designed to be used by other device drivers > such as fdma, or demux whose IP is based around a slim core. > The

Hello all, I have prepared a small patch to add support for reading and writing MessagePack in LLVM, and want to propose including it in trunk. MessagePack is a binary object serialization format, with the goal of being more compact than text formats like JSON or YAML. The specification can be found at https://github.com/msgpack/msgpack/blob/master/spec.md There is no use of the code currently

Hi Nick, When changes were brought from lld core to the Universal Driver, calls to NativeReader/NativeWriter code was stripped away. Was this by accident ? Thanks Shankar Easwaran -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation

On Sep 23, 2013, at 10:02 AM, Shankar Easwaran <shankare at codeaurora.org> wrote: > Hi Nick, > > When changes were brought from lld core to the Universal Driver, calls to NativeReader/NativeWriter code was stripped away. This needs to be fixed. Originally, ever run of the linker would have a step were it wrote to native and read that back in. That makes sense for test cases,