similar to: patch: porting module-init-tools 2/4: index

> You could also try adding "-x usb_set_altinterface" to the command line > (or adding it to ups.conf). The lsusb output implies that the only valid > setting is 0 (bAlternateSetting), but it might need to be set explicitly. I checked with -x usb_set_altinterface and it says nut_usb_set_altinterface: usb_set_altinterface() should not be necessary - please email the

Hi again, > On Sep 8, 2016, at 10:05 AM, Vassilis Virvilis <vasvir at iit.demokritos.gr> > wrote: >> Now that's a problem. I am not sure that I can find >> >> 1) the original software >> 2) a (physical) windows machine in the vicinity of the UPS >> Ha! I jumped several hooks but I think I got it. 01. I contacted the store that sold us the UPS and

Halo, I don't know if this is already done but the following two patches (one for klibc) and a big one (several smaller incorporated to one) to modules-init-tools enables running modprobe and friends in early user space. There are some issues so I post here for discussion The porting strategy was copied from the udev package. I make a file mod_libc_wrapper.{c,h} in order to provide the

[snip hex dump analysis] > > It is possible that the blazer_usb driver initialization has put the UPS > into a bad state. If you can schedule some downtime, you might want to try > usbhid-ups again after powering the UPS down completely and unplugging it > for a little while. (Often, a few seconds after the output is off and the > AC has been removed, you will hear relays

A little deciphering > Looks like the ups always replies > 22 = 16035500 50005300 20004e00 6f002000 41006300 6b00 That is length = 0x16 = 22 type = 0x3 = string Message = "UPS No Ack" Very fun... Regards Vassilis Virvilis

Halo, fnmatch() and getopt_long are necessary to compile module-init-tools with klibc out of the box. Would you consider accepting patches to implement those 2 functions? Can we use the bsd libc functions? is the lisence acceptable to you? .bill

Halo, I was wondering to no avail how to to use the klcc wrapper in order to build udev and module-init-tools. Does klibc has an install target when is embedded in the kernel tree? Is klcc available? .bill

Hi again, Thanks for the prompt reply. Just for the record i am running debian unstable/sid with nut 2.7.4-3 # dpkg -l 'nut*' | grep ^ii ii nut 2.7.4-3 all network UPS tools - metapackage ii nut-client 2.7.4-3 amd64 network UPS tools - clients ii nut-server 2.7.4-3 amd64 network UPS tools - core

On Sep 8, 2016, at 4:26 AM, Vassilis Virvilis <vasvir at iit.demokritos.gr> wrote: > > The 1000 (bcdUSB 1.00) works with blazer_usb while the 1500 (bcdUSB 1.10) > doesn't. > From the lsusb descriptor output, the 1500 seems to implement the HID Power Device Class (PDC) spec - so it might be possible to adapt usbhid-ups to work with it. What happens if you run the driver in

On Sep 8, 2016, at 8:14 AM, Vassilis Virvilis <vasvir at iit.demokritos.gr> wrote: > > Hi again, > > Thanks for the prompt reply. > > Just for the record i am running debian unstable/sid with nut 2.7.4-3 > Thanks, that is useful. > 0.447725 refresh_report_buffer: expected 13 bytes, but got 8 instead This is the first sign of trouble. > 0.447736

On Sep 8, 2016, at 9:25 AM, Vassilis Virvilis <vasvir at iit.demokritos.gr> wrote: > > + failed to claim USB device: could not claim interface 0: Device or > resource busy > + detached kernel driver from USB device... > nut_usb_set_altinterface: skipped usb_set_altinterface(udev, 0) > HID descriptor, method 1: (9 bytes) => 09 21 00 01 00 01 22 70 02 > > ****

On Sep 8, 2016, at 10:05 AM, Vassilis Virvilis <vasvir at iit.demokritos.gr> wrote: > Now that's a problem. I am not sure that I can find > > 1) the original software > 2) a (physical) windows machine in the vicinity of the UPS > > I will give it a try but for now looks like a dead end. I have 3 of these > UPS. Two of them have dead batteries and since they take 4

From: Dejan Latinovic <Dejan.Latinovic at imgtec.com> --- usr/include/arch/mips64/klibc/archconfig.h | 3 + usr/include/arch/mips64/klibc/archsetjmp.h | 39 ++++++ usr/include/arch/mips64/machine/asm.h | 76 ++++++++++ usr/include/fcntl.h | 2 +- usr/include/sys/md.h | 1 + usr/include/sys/resource.h | 4 +-

Hi, I have two ups (Turbo-X 1000SD, Turbo-X 1500SD). The both report themselves as # lsusb Bus 008 Device 002: ID 0001:0000 Fry's Electronics The are produced by MEC and report MEC0002 as product (although the working one report it in dmesg but not in lsusb) The 1000 (bcdUSB 1.00) works with blazer_usb while the 1500 (bcdUSB 1.10) doesn't. I am attaching lsusb and blazer_urb output

This is needed as the basis for the readlink -f option. Signed-off-by: Ben Hutchings <ben at decadent.org.uk> --- --- a/usr/include/stdlib.h +++ b/usr/include/stdlib.h @@ -92,4 +92,6 @@ static __inline__ int grantpt(int __fd) return 0; /* devpts does this all for us! */ } +__extern char *realpath(const char *, char *); + #endif /* _STDLIB_H */ --- a/usr/klibc/Kbuild +++

This patchset applies to klibc mainline. This patchset introduces the ability to kinit to execute scripts or executable files present in in the initramfs before switching over to the root filesystem. It is implemented by first implementing scandir() and alphasort() as present in POSIX.1-2008 in klibc itself, and then using that as the basis for iterating and executing files via a run_scripts()

tags 516774 = patch tags 516294 = upstream thanks Hi! Please find attached a diff closing #516774 by adding mkstemp(3), again with a minimalistic pseudo-arc4random(3) behind it. I?ve revisited the code. An mkstemp testsuite from the ?net shows it works, except for not caring how many ?X?en are in the template. Addressing #516294, it allows compiling and linking an mksh from today?s CVS against

Add support for scandir() and alphasort() as defined in POSIX.1-2008. Signed-off-by: Mike Waychison <mikew at google.com> --- usr/include/dirent.h | 7 +++++ usr/klibc/Kbuild | 2 + usr/klibc/scandir.c | 76 ++++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 84 insertions(+), 1 deletions(-) create mode 100644 usr/klibc/scandir.c diff --git

This fixes a long standing issue where it was not possible to do "make usr/klibc/arch/x86_64/longjmp.o" in the kernel. The principle is that all .o files to be part of klibc are listed with klib-y. For each directory a klib.list file is made that specify all .o file and the final AR then adds all .o files to create libc.a. This patch introduce the infrastructure and converts x86_64 to

Hi, after a year, I decided to hack on klibc again. I?ve reworked both the patch to add mkstemp(), discussing to use AT_RANDOM as cheap entropy source on IRC (if there will ever be another entropy consumer, I can quickly write a minimal arc4random() seeded from it, as it has only 16 octets), capable of making a working mksh (static and shared) on amd64/xen, and the m68k support code, leading to