similar to: Linux flavor?

Is there anyway to turn off the call waiting beep in the grandstream and/or cisco ata186? I have a dial statement in my extensions.conf that rings 5 phones at the same time by combining them with the & in the dial statement. i.e.) exten => blah,blah,Dial(SIP/GS1&SIP/GS2&SIP/GS3&SIP/ata186a&SIP/ata186b,25,t) If one of those lines is being used, then the user gets a really

I am running ntpd on the same machine as asterisk in order for the grandstream phones to display the time. After a while the time display fails until the phone is re-booted. Has anyone run into this problem before? Is it simply a bug in the GS firmware? Sean

Almost any distro will do, since 2.6 kenels are bleeding edge you might have to spend more time getting everything working, and in most cases you are best served by determining which distro your hardware manufacturer supports, Dell typically supports only redhat, HP supports suse on many boxes. While there are workarounds, having the hardware manufacturer deal with driver issues is a bonus.

I'm running RH7.1 and Samba 2.2.2 . I would like to offer a VFAT partition on the server hard drive for universal read-write access. I mount the partition in fstab with /dev.hda5 /sys vfat defaults,rw,uid=1001,gid=1001 0 0 It mounts fine and shows up on the Windows 98 machine and can be opened. I can't write to it however. User and group 1001 are smbuser account, and they

Hi, I think lld needs to have an infrastructure as part of the build process to build specific flavors and specific targets. For this I was thinking that the Registry expand to consider flavors and targets that are part of the build process. So each flavor/target would register and the Driver would walk through the list of handlers to check if there is a handler defined for that

On Mon, Jan 7, 2013 at 9:44 AM, Shankar Easwaran <shankare at codeaurora.org> wrote: > Also the linker script functionality is only needed by ELF and not anything > else. It should be contained only within ELF. I agree with your point about encapsulation and separation of concerns. However, I believe that GNU ld will accept and use linker scripts even for the non-ELF formats it

On Wed, Oct 8, 2014 at 11:45 AM, Alex Rosenberg <alexr at leftfield.org> wrote: > This it totally "armchair quarterbacking," but I am a little frustrated > that we've come to conflate flavors and targets. > > The original intent of flavors was to internally translate each flavor > into a neutral lld-native command line syntax. We now have baked in >

On 10/7/2014 4:10 PM, Nick Kledzik wrote: > Shankar, > > Can you give provide a scenario where you want this? I’m not sure what you want here. a) LLVM could be built just for one target(LLVM_TARGETS_TO_BUILD) b) With LTO this case might happen more often, where an user would have compiled LLVM just for one architecture and lld would support other architectures that LLVM would not

Rodger Combs wrote: > I've run into some issues using Opus with source files in channel layouts > other than the default 8. For instance, 2.1 isn't supported, so I have to > either downconvert to 2.0 or upconvert to 5.1 (which usually involves adding > empty channels, which prevents the playback device from upconverting to the > native layout). > To address this,

On Wed, Jan 9, 2013 at 1:54 PM, Alex Rosenberg <alexr at leftfield.org> wrote: > I agree that processing of linker scripts is a "flavor" issue. We have an in-house linker that processes them and has a different command line than GNU ld, so we'll want to process them in that "flavor" as we'll. Is it the same language that GNU ld accepts? -- Sean Silva

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 2848 bytes Desc: image001.jpg Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20050111/b2d08439/attachment.jpeg -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type:

Here is my system: POWER SUPPLY 450W ALLIED ATX450P4 R(41) MB NFORCE2 A7N8X DELUXE ASUS RTL(Standard) CPU AMD|2500/333 ATHLON XP BARTON R(Standard) DDRAM 256M|DDR333 PC-2700 -K %(Standard) HD 40GB|WD 7200RPM 8MB WD400JB%(70) VGA ASUS|V8170MAGICII/T 64M MX440SE(58) CD ROM 56X|AOPEN CD-956 RTL(22) Besides the above parts, i have 2 X100P FXO PCI cards, and 1 TDM40B I bought 2 phones from radio

Dear *, we are stuck and cannot find anything on the Net or the documentation. Background ---------- We are currently working on a project that aims to migrate Servers from a Windows NT domain to a Samba based domain. The migration, as always, should be completely tranparent to the Windows Desktops and their users. There are about 300 users and may be 20 groups. Issue ----- The current domain

The `isBranch` flag is already set on the branch instructions. Furthermore, we do use the `isBranch()` query in a few places in the PPC back end, so this does work. Perhaps there's something specific about the lldb usage? Is it somehow possible that the `isBranch()` query is called on the wrong instruction? Would you be able to provide a test case that reproduces the issue? On Thu, Nov 30,

Hi, We have a significant regression since llvm 5.0.0 in the x86 assembler. The following snippets fail: 1) .intel_syntax 0: jmp 0b 2) .intel_syntax and edi, 0b010101 when running through `llvm-mc -arch x86-64`. This regression was introduced in r301390, which was driven by PR27884. I think https://llvm.org/PR36144 describes this very well, and I think we should get this fixed, since

I agree that processing of linker scripts is a "flavor" issue. We have an in-house linker that processes them and has a different command line than GNU ld, so we'll want to process them in that "flavor" as we'll. Sent from my iPad On Jan 8, 2013, at 11:44 PM, Sean Silva <silvas at purdue.edu> wrote: > On Mon, Jan 7, 2013 at 9:44 AM, Shankar Easwaran >

> But where is the flat set? Maybe I can debug and check what is going on. The MCInstrDesc are in a table in lib/Target/PowerPC/PPCGenInstrInfo.inc of your build directory. > Some additional information: > > MCInst opcode: 0x7cb > Decode Index: 0x1e I had assumed this would have dissembled to '// Inst #234 = BC' which does have the branch flag set, but I think that

On Fri, 2012-09-14 at 13:10 -0500, Will Schmidt wrote: > Hi all, > > I've been poking at AsmParser support for powerpc64 > (ppc64-elf-linux-abi) and have run into some behavior I don't understand > with the ptr_rc references coming out of the PPC*.td files when > generating the asm-matcher files. > > For instance : > $ ./build/bin/llvm-tblgen

Than my question is this? Now that I have switchtowerized and migrate enabled my app I can start down a new path if need be on a different OS as the base of the system. We have already tried CentOS and found it to have more issues than those mentioned about fedora and through it away faster than one could shake a stick at. Here are our requirements for a stage/dev box and production:

Thanks! On Fri, Jun 24, 2016 at 3:49 PM, Tanya Lattner <tanyalattner at llvm.org> wrote: > Done. > > -Tanya > > > On Jun 23, 2016, at 2:37 AM, Sean Silva <chisophugis at gmail.com> wrote: > > > > Hi Tanya, > > > > Could you add 4 basic categories "COFF", "ELF", "MachO",under the "LLD" > product? (we