search for: hals

Hi Sam, do you know if there is anything done about cbb(4)? I have many wireless adapters with ath(4), but only the one based on PCMCIA is making problems on FreeBSD. I cannot boot my notebook with the device inserted into the port, or it will render the system unusable (100% load on cbb(4)). And all I can see is the following: Jul 12 14:58:39 link kernel: ath0: ath_chan_set: unable to reset

Hi fellows, I'm really pleased to announce that a first stage of NUT and HAL [1] integration has been reached: NUT drivers (in fact, only newhidups, tripplite_usb and bcmxcp_usb for the moment) can feed HAL data. It's a "quick and dirty" hack, as a proof of concept, and there is still lots of things to be done, both on NUT and HAL sides. But it's a good base, and very

Charles, It looks like the buildbot no longer builds (if it ever did, I don remember) the HAL addons, even if the requirements are met: configure:9680: checking for libhal version via pkg-config (0.5.8 minimum required) configure:9690: result: 0.5.11 found configure:9694: checking for libhal cflags via pkg-config configure:9703: result: -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal

Seems to be broken in the current SVN: [...] x86_64-linux-gnu-gcc -I../include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -DINET6 -O2 -D_REENTRANT -DNETSNMP_USE_INLINE -Wall -Dlinux -I. -I/usr/include -O2 -Wall -Wsign-compare -s -o energizerups energizerups.o ../common/upsconf.o ../common/parseconf.o ../common/state.o main.o dstate.o

Hi Dave and HAL fellows, 2007/3/30, David Zeuthen <david@fubar.dk>: > > Hi! > > On Fri, 2007-03-30 at 11:22 +0200, Arnaud Quette wrote: > > I would really need an "addondir" variable in hal.pc to get to exact > > path to install the NUT addons... > > I just clarified this in the spec with this commit > >

Hi David and fellows, I'm reviving this important thread about a common power management. To sum up, the first aim is to allow a better user experience on Linux by bridging NUT with Linux HAL, and Gnome Power Management / any PM GUI. But it also initiate a bigger investigation about how to integrate NUT support for UPSs into the native OS Power Management infrastructure for all supported

Hi, I cannot have suspend and hibernate working on a Samsung NC10 (netbook) running CentOS 5.4 i386. When I try suspending/hibernating the screen becomes black (with a few logs, like "shrinking memory" for hibernate) and then the computer hangs and I have to force a shutdown with the power button. This wiki page seems to say that it should work out of the box:

Say if we have 8 cores, I want to get which core is running the current program. Thanks. On Thu, Nov 19, 2015 at 3:37 PM, Hal Finkel <hfinkel at anl.gov> wrote: > ----- Original Message ----- > > From: "zhi chen" <zchenhn at gmail.com> > > To: "Hal Finkel" <hfinkel at anl.gov> > > Cc: llvm-dev at lists.llvm.org > > Sent: Thursday,

Ladies and Gentlemen, I have been playing around with Arnaud's new HAL stuff a bit, and have some questions and observations. First my configuration: my UPS (Peter may remember): ups.mfr: APC ups.model: Back-UPS ES 650 ups.productid: 0002 ups.firmware: 818.w1.D ups.firmware.aux: w1 kernel: 2.6.18-92.1.6.el5 hal-0.5.8.1-35.el5, nut based on nut-2.2.2.tar.gz, small changes to

HAL has been deprecated, and this patch removes all HAL specific calls from the configuration scripts. HAL is still present in the Python scripts, but will be removed in a different patch. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- ChangeLog | 3 + configure.ac | 2 - ovirt-node.spec.in | 1 -

I applied the patch to the trunk version successfully, although I get an error in between: 1 out of 1 hunk FAILED -- saving rejects to file lib/Transforms/IPO/CMakeLists.txt.rej Can I ignore the error? The patch exits normally except for that error. Also, I tried to apply the patch to the LLVM 3.0 but does not work at all. Is the trunk version the only one where the patch can be applied?

Hi Hal, Just submitted 27 failing tests on clang version 3.5, trunk 199158. http://llvm.org/bugs/show_bug.cgi?id=16431 I expect that these failures correspond to 2+ unique bugs. Cheers, -moh -----Original Message----- From: Hal Finkel [mailto:hfinkel at anl.gov] Sent: Thursday, January 09, 2014 6:01 AM To: Haghighat, Mohammad R Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] [icFuzz] Help

some notes: - for this kind of discussion, please cc upsdev list (I've added it), - I've fwded the full thread to upsdev, - this subject is part of what I call NUT-NG (next gen.), aka nut 3.0... - I'll study in depth the thread this week end, and complete with my thoughts, - thanks to Stan to have put us all in touch Arnaud 2006/3/10, Stanislav Brabec <sbrabec@suse.cz>: >

I've tried several recipes found with google, but hal likes to grab the USB ups before nut can get it. There are a number of klugey workarounds, like turn off port power until ready to start nut (so that hal doesn't see the UPS). Or killall hal-addon-hid-ups before starting nut. Here is one of recipes I googled: https://github.com/sdgathman/trippfix/blob/master/halpolicy.fdi It

I just installed Centos 5.5 x86_64 on a new Toshiba Satellite L1500D. Everything seems to work (so far) other than the wireless networking; lscpi tells me: 0e:00.0 Network controller: Realtek Semiconductor Co., Ltd. Unknown device 8172 (rev 10) I discovered that I need the realtek driver, so I found and downloaded these: rtl8192se_linux_2.6.0010.1012.2009_64bit.tar.gz

My first attempt to post this bounced -- this is a 2nd try. ----------------------------------------------------------------- I've recently installed a CyberPower OR500 on a CentOS 6.4 system. nut comes RPM'd as nut-hal -- and I've played a little with it - but I'm trying to figure out just what it provides at that point. (looking at the docs, I'm not quite sure) I'd

On Nov 18, 2013, at 10:39 AM, Ben Kamen wrote: > My first attempt to post this bounced -- this is a 2nd try. Sorry about that - Alioth, the server that hosts the lists, was down due to disk failure: http://lists.debian.org/debian-infrastructure-announce/2013/11/msg00001.html > I've recently installed a CyberPower OR500 on a CentOS 6.4 system. > > nut comes RPM'd as nut-hal

Hi Hal, For lowering code that requires inserting branches, you need to use a custom inserter, yes. Theoretically, that does indeed sound like what you want to do here. It's complicated by the general structure of argument passing, though. In particular, there's lots of assumptions about the call sequence stuff. I don't know if things are smart enough (EH in particular worries me) to

----- Original Message ----- > Hal, > > Just posted a package containing 214 small tests showing bugs in the > latest Clang (3.4 trunk 187225) on MacOS X when compiled at -O2. > http://llvm.org/bugs/show_bug.cgi?id=16431 > > These are new tests different from the previously posted ones, but > their root causes could be the same as before or could actually be > new

Hi, everyone, I'm currently the code owner for the PowerPC target. I worked on the PowerPC target for many years, and that was a lot of fun, but I've not been directly involved in development for PowerPC for some time. I would like to nominate Nemanja Ivanovic for the role of PowerPC target code owner. Insofar as a code owner is responsible for making sure that patches are reviewed,