search for: ep0

...t;-(0:((1-d)*nc))/nc + ncl<-length(pc) + ne.old<-ne + ne.old1<-ne.old + ### sweeping forward + for(i in 1:ncl){ + cmin<-cc[1] + cmax<-cc[2] + ### fixed cci<-cmax bug + cci <-1 + lhood<-dbinom((i:ncl)-1,nc,pc[i]) + ne[i:ncl]<-(1+(cci-1)*(lhood/lhood[1])) * ne.old1[i:ncl] + Ep0 <-Epower(nc, d, ne, pc, alpha) + while(abs(Ep0[i]-power)>tol1){ + if(Ep0[i]<power) cmin<-cci + else cmax<-cci + cci<-(cmax+cmin)/2 + ne[i:ncl]<-(1+(cci-1)*(lhood/lhood[1])) * ne.old1[i:ncl] + Ep0<-Epower(nc, d, ne, pc, alpha) + } +  ne.old1<-ne + } + ne1<-ne + ### swee...

...is was discussed to death somewhere, since it's a reversion of an earlier change, but just to beat a dead horse ... I encountered this change in a surprising way: Being new to IPSec, I started by setting up a gif tunnel (without IPSec) between my singly-homed host, fred, running FreeBSD: ep0 192.168.0.2/24 gif0 ${mynet}.27 -> ${mynet}.17 tunnel 192.168.0.2 -> 192.168.0.1 and a dual-homed host, bob, running NetBSD: tlp0 ${mynet}.24/28 tlp1 192.168.0.1/24 gif0 ${mynet}.24 -> ${mynet}.27 tunnel 192.168.0.1 -> 192.168.0.2 I did...

...-----< ups.conf >-------- [ups01] driver = usbhid-ups port = auto desc = "HP R1500 G2" offdelay = 120 ---------------------------- Here is the last part of the log from "/opt/mt/nut-svn/libexec/usbhid-ups -DDDDD -a ups01 -k" ..... opening /dev/usb/3f0.1fe0/0/cntrl0 opening ep0 failed, -1 usb_open_ep0 failed: 16 usb_close(): hdl=0x0 usb_error(): error=22 usb_devices list: 0: 3f0.1fe0/0 0.017204 Checking device (0000/0000) (/dev/usb/3f0.1fe0/0) usb_open: device ptr is 0x4bea8 usb_open: pindex = 0 usb_open(): usb_open_ep0(): opening /dev/usb/3f0.1fe0/0/cntrl0 opening...

....1) subject to the constraint that the intercluster correlation is less than or equal to intracluster correlation for a given level of prevalence (upper threshold =1% and lower threshold=0.1%). For this purpose I have used the following command (which is under mvtBinaryEP in mvtnorm library in R): ep0 = ep(mu=0.1, rho=0.05, n=6, nRep=33, seed=NULL) apply(ep0$y, c(1,2), mean); cor(ep0$y) The above commands produce 198 binary outcomes (33 clusters with cluster size of 6 each) and a matrix (6x6) of bivariate correlations. Since the input among others requires values either for 'rho' along...

....1) subject to the constraint that the intercluster correlation is less than or equal to intracluster correlation for a given level of prevalence (upper threshold =1% and lower threshold=0.1%). For this purpose I have used the following command (which is under mvtBinaryEP in mvtnorm library in R): ep0 = ep(mu=0.1, rho=0.05, n=6, nRep=33, seed=NULL) apply(ep0$y, c(1,2), mean); cor(ep0$y) The above commands produce 198 binary outcomes (33 clusters with cluster size of 6 each) and a matrix (6x6) of bivariate correlations. Since the input among others requires values either for 'rho' along...

Hello guys, I'm at my wits end.. hope someone can help.. this is the deal. I have setup a linux box to serve as a "gateway" for our internal lan. Running 2.0.34 slakware. I have 2 nic cards.. One for our "internal" lan (192.168.2.0) and the "external" lan..I have gotten the OS to see both of them, but when trying to get DHCP to work with both, it kept barfing..

...15 isab0: <PCI to EISA bridge (vendor=0e11 device=0001)> at device 20.0 on pci0 eisa0: <EISA bus> on isab0 mainboard0: <CPQ0551 (System Board)> on eisa0 slot 0 isa0: <ISA bus> on isab0 orm0: <Option ROMs> at iomem 0xc0000-0xc7fff,0xe8000-0xedfff,0xee000-0xeffff on isa0 ep0: <3Com 3C509-Combo EtherLink III> at port 0x320-0x32f irq 10 on isa0 ep0: Ethernet address 00:a0:24:1d:1a:50 fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ata0 at port...

...with the usb connection. After trying "/lib/nut/usbhid-ups -DD -a hp1500" the log says there are "libusb_get_interrupt: Connecion timed out". If you start upsd, what does "upsc hp1500" return? There are two ways to fetch values from a HID UPS - control messages over EP0 (more overhead), and interrupt transfers (usually over EP1IN). It looks like the interrupt transfers are timing out, but after that, the "Quick update" seems to get some normal-looking values via control messages. It is possible that we are not using the right interrupt endpoint, or mayb...

Hello, I've got samba running on a FreeBSD box that has two interfaces, ep0 which is an external interface, and ep1 which is for internal use only. I only want samba to listen on ep1 so if i'm ever portscanned port 137/139 will not show up as open on the external interface. I've added these lines to the global section of my smb.conf file: hosts allow=192.168.0. int...

OpenBSD 6.1/amd64 nut-2.7.4p0 (from OpenBSD package) UPS: Tripp-Lite OMNI1500LCDT I cannot get the driver for the UPS to load without error. Here are the commands, with the output, and the config files: ======================================================= # upsdrvctl start Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication

Linux NUT 2.7.1 Eaton 5PX usbhid-ups It would appear that interrupts are not actually working on my 5PX using the usbhid-ups driver. I will be trying the serial mge-shut driver next. It just seemed like it was working before because of the default pollinterval of 2 seconds. The status update comes in during the pollinterval no matter what I have pollfreq set to. And I can set pollonly and

So, going with the proposed initial design, I created a report descriptor to describe the battery. I thought that I'd then see how NUT responded to it. The good news is that the descriptor showed up and all of the paths were correct. Unfortunately, after that, nothing happened...no reports were requested, and it just kept timing out. Is there some minimum amount of functionality I need to

...0.000000 Starting UPS: usb > Network UPS Tools - Generic HID driver 0.41 (2.7.4) > USB communication driver 0.33 > Using subdriver: TrippLite HID 0.82 > libusb_get_interrupt: Function not implemented The last line is just a warning - usbhid-ups can use both interrupt requests and EP0 control requests. The driver was probably running in the background, per the "Duplicate driver instance" message below. > > > # upsdrvctl -DD start > Network UPS Tools - UPS driver controller 2.7.4 > 0.000000 > If you're not a NUT core developer, chances are that...

Hey folks, I'm designing a power management card for a Raspberry Pi, for an embedded application. Basically, here's the bits and pieces that would be on the card: - A 12V SLA battery charger, which can be powered from a wall wart or solar panel. - A pair of 12V->5V switching regulators, one powering the Pi and the other powering a built-in 4-port USB hub. - A USB capable

...of functionality I need to provide in this report descriptor in order for NUT to work correctly? I assume it's not requesting reports because there is nothing it wants to know about. That sounds vaguely familiar, but I think NUT will still poll the interrupt pipe if present. The requests over EP0 are probably only made if there are HID usage paths mapped to NUT variable names. -- Charles Lepple clepple at gmail _______________________________________________ Nut-upsdev mailing list Nut-upsdev at lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

On Feb 3, 2018, at 7:19 PM, Russell King wrote: > > Input and Output reports are used for interrupt endpoints rather than > control endpoints. HIDGetItemData() only ever requests feature > report IDs, and requesting non-feature report IDs as feature IDs may > lead to undesirable results and errors. This one made me scratch my head a bit. I don't think it's unreasonable

Hi there, OS: (L)ubuntu 12.04 precise LTS Nut: 2.6.3-1ubuntu1.1 Installation Method: Package (apt-get install nut) Hardware: HP R1500 G3 INT Hardware-Specs: http://h18004.www1.hp.com/products/quickspecs/14059_div/14059_div.pdf Problem: I tried to set up nut with our new arrived HP R1500 G3 UPS but there is a failure with the usb connection. After trying "/lib/nut/usbhid-ups -DD -a

...S: usb >> Network UPS Tools - Generic HID driver 0.41 (2.7.4) >> USB communication driver 0.33 >> Using subdriver: TrippLite HID 0.82 >> libusb_get_interrupt: Function not implemented > > The last line is just a warning - usbhid-ups can use both interrupt requests and EP0 control requests. The driver was probably running in the background, per the "Duplicate driver instance" message below. >> >> >> # upsdrvctl -DD start >> Network UPS Tools - UPS driver controller 2.7.4 >> 0.000000 >> If you're not a NUT core devel...

The syntax is beginning (just beginning) to make sense to me now, so I'm looking now to try and implement just a few items in the report descriptor, and then I figured I can progress from there if all goes well. The power HID docs seem to encourage drawing out your system first, and then letting the report descriptor flow from there. So, my very simplified system goes like this:

...tain the current tcp stream ack number. > > A tcp packet trace would be most welcome. I did a write TO the bsd samba server and it was fast, which is in agreement with your SMBwritebraw/rabbit pellet theory. Attached/following is a tcpdump. I started tcpdump with this command: # tcpdump -i ep0 | grep -v ssh > sambareadtcpdump2.log horbot.compound.local is the NetBSD samba server arbosh.compound.local is the WinME client I had started tcpdump, started the copy, waited a few seconds, then cancelled the copy and kill tcpdump. There's nothing else running that should have been gene...