philip

Hi, yes, I'd also change the readme text that states to use darthwade.loading which just won't work..

Just compiling a kernel with PTP timestamping support enabled (by default not). Will see if this changes anything. I'm new to kernel topics, so I missed the obvious. Will report...

Built a new kernel according to [docs](https://www.raspberrypi.org/documentation/linux/kernel/building.md) and changed the following settings (through make menuconfig): ```.config CONFIG_NETWORK_PHY_TIMESTAMPING=y # # PTP clock support # CONFIG_PTP_1588_CLOCK=m # CONFIG_DP83640_PHY is not set #...

Ok, thanks! Hoping to be hearing more from you! Just to say, as for the docs, I wouldn't mind signing an NDA to have a look to see if can...

@wowczarek From what I see in the [CM4IO datasheet (page 7)](https://datasheets.raspberrypi.org/cm4io/cm4io-datasheet.pdf) SYNC_IN, SYNC_OUT are available on J2 pins 8+9

many thanks also! Well, simply put I would think that all features might serve one use case or other and thus - optimally - all should be available to make...

> Also how would you test it? I can run ptp4l which I'm assuming would test the hardware timestamping, but may not test the hardware clock interface... Spontaneous ideas... use...

Yes, many thanks for making raveloxmidi! To have the networking functionality separate would indeed be quite nice. I would also add a command line utility reading/writing a midi binary stream...

Actually, it somewhat comes for free as the basic usage page and usage are extracted from the report descriptor which is read here: https://github.com/libusb/hidapi/blob/0ea5e9502f31a1e4dbc71567c0f9a781930f1d38/libusb/hid.c#L644 In my eyes it'd make sense...

Ok, can see to it, but might take a moment