Taha Aziz Ben Ali

I'll take all the help I can get :) I've been quite busy maintaining some of my other projects so I couldn't get around to finishing up #10

Hey there! Will you do a check for me to confirm if the following files exist within any given PCI domain in `/sys/bus/pci/devices/`: - `class` - `device` - `revision` -...

Theoretically speaking, ppc64le shouldn't fail. All the files aparato reads from are available for this architecture. s390x however is a different story; aparato doesn't really rely on any APIs other...

Can you run the following code snippet on ppc64le and paste the output? (create a test project and throw it in main.rs) It'll help me figure out what's actually going...

The only alarming thing I see is: `Device Name: 53c885` It's not supposed to ever return the original value, so let's see if this is an internal error or this...

Yeah, this confirms the device name isn't being properly parsed. As for the rest, I don't really understand why the tests would fail as they're reporting correct information and the...

I've skimmed through `/usr/share/hwdata/pci.ids` to find your device, the device ID is there, but it doesn't have a name (or the name is the highlighted text) I don't want to...

> That fails to compile as-is Sorry about that, forgot to replace the standard `{}` with `{:?}` for **device_id**. Encoding `[0, 13]` as a hexadecimal string gives back `000d`, Matching...

@davide125 I'm in the midst of rewriting the parser, I can't give you a date for when these changes will land, but I am working on it :)

I'm also experiencing this on every `/quit`. It happens both when starting `weechat` normally, as well as with a running `weechat-headless`. For me, the steps to reproduce are: 1. With...