The SMBus standard specifies an address resolution protocol (SMBus ARP.) It has two key features :
* Handle I2C slave address collisions. If two SMBus slaves would use the same I2C address, ARP lets one of them pick a different address to avoid the address collision.
This will greatly enhance the usefulness of QEMU virtual serial ports, because the Linux kernel interprets a break on the serial console as a SysRq, but there is currently no way to pass this signal over a pseudo-terminal.
In short, give second breath to http://hall.suse.de/bugs/defects.cgi.
Long version: Create a generated page reflecting SUSE organizational structure and containing links to useful generated Bugzilla queries and charts like:
Dochazka is a long-term project to replace the obsolete Attendance & Time Tracking system used by the Prague office since 2007. Dochazka is a complex system consisting of three major components:
- RESTful backend App::Dochazka::REST (with lots of help from Web::MREST)
The goal of the project is making the gdb able to open compressed kernel dump - access its memory contents at the very least.
If one wants to open compressed kernel dump (that's what our customers are sending mostly when reporting kernel panics nowadays), he has to use crash. Crash is a brilliant tool with many kernel-specific hacks, but at the same time, it has a huge functionality overlap with gdb, it is hard (even impossible in many cases) to extend it.
Package a basic, stripped down version of sysvinit for emergency cases, so you can repair a failed system without interference. My goal is not to replace systemd with sysvinit again, but to provide a sysvinit-base package that does not have any dependencies at all and can just be installed on any system. sysvinit will only be used in exception situations by specifying the kernel parameter "init=/sbin/init" or something like that. The package will come with the binary, a minimal inittab and a basic boot script that does only the really needed stuff.
Experiment with an extension to have sysvinit execve systemd, so people can boot into their allmighty uber-daemon once the system has been fixed.
Each of the core dump upload servers in Europe and USA could be improved if the shell scripts were combined so that the same tasks can be performed on each site, e.g. downloading of all packages needed for crash usage with a specified core dump by allowing for configurable (or even automated) selection of locations to obtain data packages from.
gdb-kdump (and libkdumpfile) needs a plenty of improvements and tasks to be done. For HackWeek 13, Vlastimil chose to work on SLAB memory support, Petr, amongst other things, reorganized the libkdumpfile code and alnovak begun with libkdumpfile's ppc64 support. Our status in 4/5 of HackWeek 13:
L3 workflow is implemented in a custom, developed in-house, tool called SolidGround
Explore possibilities to implement existing L3 workflow in Jira to determine whether it could potentially replace SolidGround, thus reducing the effort needed to develop and maintain SolidGround.
over 4 years
4 hacker ♥️.
Has no hacker:
In previous hack weeks, the first few days ended up being wasted on just getting it working. I'm pleased to share that the code quality has improved dramatically since the last hack week and there are now extensive test cases for both unit testing and testing against real vmcores, and we'll use both mypy and pylint (if installed) to perform static analysis. Packages for those are available in openSUSE or as part of the crash-python OBS repo for SLE15. It has been tested with kernels from 3.0 to 5.1.
The only Mediatek "hacker" board available is from 96 Boards . Unfortunately up to now there is nearly no mainline support.
Idea would be to improve this situation. The idea would be to get the pin-controller merged first and then hopefully most of the other stuff can be just added (fingers crossed...)
over 3 years
3 hacker ♥️.
Has no hacker:
Banana-pi R2 has quite a good upstream support in the kernel, but lacks a u-boot support.
The idea is to sit down at get working on that. This would be a good starting point to get u-boot support for other Mediatek SoCs as well.
(was: Create a DRM driver for Matrox G200)
Even after 20 years, the Matrox G200 series is still an excellent 2d graphics card. Unfortunately, there's only an fbdev driver and a user-space driver. Both are obsolete, as modern Linux uses the DRM framework for managing graphics cards. There already is a DRM driver for the G200 server series. This driver is under-maintained and doesn't work with desktop chips.
As we have grown in our remote and non official office at Gran Canaria we had to rent another space. This new office is almost empty and we need a little bit of love to improve the sensation of relax and commodity while we do what we love most.
The main target of this project is to kickstart the decoration process, creating a minimum plan of what we want to achieve and step the first steps :smile:
strace can parse syscall arg structures and print them in user-friendly way. For ioctl syscalls there is greater variety of the structures and not all are supported. Let's start with covering autofs data.
Back in the late 90s to early 2000s, SiS graphics chips were fairly common and found in many low-end devices. Today, the chips are still capable enough for simple graphics needs, but the graphics cards were on PCI and AGP buses. They are not usable in modern computers.
However, there exist USB-based graphics cards with a SiS 315 graphics chip. Those are around on Ebay et al  and easily usable with current computers. I already do have a driver for the old PCI-based SiS drivers and have long been struggling to find something useful to do with it. Converting it to serve USB devices would finally make it useful.
When we experience a early boot crash, we are not able to analyze the kernel dump, as user-space wasn't able to load the crash system. The idea is to make the crash system compiled into the host kernel (think of initramfs) so that we can create a kernel dump really early in the boot process.