search for: warting

Hey, all. I'm seriously thinking about doing the VoIP thing at home. The perfect platform seemed to be the Sheeva "wall wart" (http://www.marvell.com/products/embedded_processors/developer/kirkwood/sheevaplug.jsp). It's a cute little doohicky with USB, SD-card, Ethernet, and runs on an ARM CPU. I'd like to avoid SIP to my provider, just 'cause it's always such a

Sprinkling my examples with ''lambda'' has always seemed like a bit of a wart to me. I''ve gotten into the habit of adding ''alias :calling :lambda'' to my spec suites. My examples then look like: calling { Foo }.should raise_error calling { Bar }.should_not raise_error Is there a reason that RSpec core has chosen not to make exception expectations more

Hi Everyone ; I will soon be making a presentation comparing ZFS against Veritas Storage Foundation , do we have any document comparing features ? regards <http://www.sun.com/> http://www.sun.com/emrkt/sigs/6g_top.gif Mertol Ozyoney Storage Practice - Sales Manager Sun Microsystems, TR Istanbul TR Phone +902123352200 Mobile +905339310752 Fax +902123352222 Email

Hello people, I am having difficulties figuring out the POE power draw in watts from a Polycom IP601. I want to know how many IP601's can be powered from the Cisco Catalyst 3560G-48PS. The IP601 wallwart has: Input 120VAC 60hz 19W, Output 24VDC 500mA. I assume the output is appropriate value to figure out how many phones can be powered. The Cisco 3560 datasheet says "the 48-port PoE

On Mon, Jul 30, 2018 at 01:28:03PM +0300, Michael S. Tsirkin wrote: > Let me reply to the "crappy" part first: > So virtio devices can run on another CPU or on a PCI bus. Configuration > can happen over mupltiple transports. There is a discovery protocol to > figure out where it is. It has some warts but any real system has warts. > > So IMHO virtio running on another

On Mon, Jul 30, 2018 at 01:28:03PM +0300, Michael S. Tsirkin wrote: > Let me reply to the "crappy" part first: > So virtio devices can run on another CPU or on a PCI bus. Configuration > can happen over mupltiple transports. There is a discovery protocol to > figure out where it is. It has some warts but any real system has warts. > > So IMHO virtio running on another

Dear List, I have had problems inserting some (not all !) figures via odfWeave (using print(someLatticeFunction)...). The figure was correctly displayed in a R device window but the resulting ODF document displayed the correct space for the figure and an empty frame with a "broken image" icon and a "read error" mention. Exploration of the odf (.odt, in my case) file showed

On Fri, Jul 27, 2018 at 10:58:05AM +0100, Will Deacon wrote: > > I just wanted to say that this patch series provides a means for us to > force the coherent DMA ops for legacy virtio devices on arm64, which in turn > means that we can enable the SMMU with legacy devices in our fastmodel > emulation platform (which is slowly being upgraded to virtio 1.0) without > hanging during

On Fri, Jul 27, 2018 at 10:58:05AM +0100, Will Deacon wrote: > > I just wanted to say that this patch series provides a means for us to > force the coherent DMA ops for legacy virtio devices on arm64, which in turn > means that we can enable the SMMU with legacy devices in our fastmodel > emulation platform (which is slowly being upgraded to virtio 1.0) without > hanging during

On Tue, 2012-05-01 at 19:58 -0500, Peter Bergner wrote: > On Tue, 2012-05-01 at 17:47 -0500, Hal Finkel wrote: > > By default it should build for > > whatever the current host is (no special flags required). To > > specifically build for something else, use: > > -ccc-host-triple powerpc64-unknown-linux-gnu > > or > > -ccc-host-triple

On 9 January 2015 at 11:46, Martin Maechler wrote: | (I've seen .. but not investigated other cases where Travis | would barf about things that were fine for me). I often file that under "Travis has a screw loose for sticking with Ubuntu 12.04". It's a fantastic service, but it has its warts. "Word" is that at some point they'll switch to a new release "at

Yup, I've got one remaining bug that holding up the CellSPU release. It still has a bunch of warts, but so long as I can get it into shape such that llvm-gcc-4.2 compiles all the way through, then we collectively have something with which to work. I'm getting the following error from llc, the attachments have llc's debug and the .ll files, respectively. Can anyone shed some

On Jun 7, 2017, at 1:02 PM, John R Pierce <pierce at hogranch.com> wrote: > > every RPM that interacts with systemd will need to be 'fixed' to do it the old way, with init.d scripts. repositories like postgres, EPEL, etc won't work, either, as their C7 packaged daemons are all configured to use systemd. That?s just skimming the surface. The real hard bits come from the

Hello, I am trying to solve a problem that I can foresee when I deploy Asterisk into a few SOHO situations soon. In Nebraska and in my area of Western Pennsylvania we have violent thunderstorms in spring and summer and sometimes very heavy wet snow in Winter. Both type of event will take out the power of a period of 30sec to 36-hours. So no UPS system would be able to handle a system for over

When I configure and build LLVM (on Linux - Ubuntu 12.04) with the "--enable-shared" option, I get a shared library named "libLLVM-3.2svn.so", regardless of whether I build from sources pulled from the repository (even when pulling from "tags/RELEASE_32/final") or from the release tarballs. Is this correct behavior? Even if this odd naming is what is expected, why

> you can't, you can only get a ConstantAggregateZero.  This is actually kind of > annoying, and means that places expecting a ConstantArray have to remember to > also check for ConstantAggregateZero.  Perhaps there's a good reason for the > current design, but if not it would be great to eliminate this wart. Well, I think the main reason it so reduce the size of .ll / .bc when

On Mon, Jul 30, 2018 at 04:26:32PM +0300, Michael S. Tsirkin wrote: > Real hardware would reuse parts of the interface but by necessity it > needs to behave slightly differently on some platforms. However for > some platforms (such as x86) a PV virtio driver will by luck work with a > PCI device backend without changes. As these platforms and drivers are > widely deployed, some

On Mon, Jul 30, 2018 at 04:26:32PM +0300, Michael S. Tsirkin wrote: > Real hardware would reuse parts of the interface but by necessity it > needs to behave slightly differently on some platforms. However for > some platforms (such as x86) a PV virtio driver will by luck work with a > PCI device backend without changes. As these platforms and drivers are > widely deployed, some

This is a scheduler assertion. It means a value (virtual register) use is somehow scheduled before its definition. Please run llc in gdb. Call dumpSchedule() to print out the schedule. Also please let me know which node it is processing at the time of the assertion. Evan On Oct 15, 2007, at 11:48 PM, Scott Michel <scottm at aero.org> wrote: > Yup, I've got one remaining bug

Hi all, I'm looking for recommendations on ethernet switches for a new install. Ideally would want switches with at least 24 ports, ideally with a GE uplink, and that support PoE (power over ethernet) on every port. I've seen lots of switches, and lots of "power hubs", but the combination, which makes a lot of sense, seems rare. What is out there? Do the switches need to be