Previous day | Jump to hour: 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 | Next day

Seconds: Show Hide | Joins: Show Hide | View raw
Font: Serif Sans-Serif Monospace | Size: Small Medium Large

Click in the nick column to highlight everything a person has said.
The Logo icon identifies that the person is a core developer (has commit access).

#rockbox log for 2022-05-13

01:00:44***No seen item changed, no save performed.
01:01:34 Quit Galois (Remote host closed the connection)
01:01:49 Join Galois [0] (
01:15:20 Quit pixelma (Quit: .)
01:15:20 Quit amiconn (Quit: - Chat comfortably. Anywhere.)
01:17:43 Join pixelma [0] (
01:17:43 Join amiconn [0] (
01:18:33 Join ZincAlloy [0] (~Adium@2a02:8108:943f:d824:810a:e613:c267:8665)
01:33:43 Quit ZincAlloy (Quit: Leaving.)
02:06:20 Join ZincAlloy [0] (~Adium@2a02:8108:943f:d824:59ec:6bcc:af3e:2e0b)
02:13:46 Quit ZincAlloy (Quit: Leaving.)
03:00:46***Saving seen data "./dancer.seen"
05:00:48***No seen item changed, no save performed.
05:06:50 Quit amk (Ping timeout: 240 seconds)
05:07:53 Join amk [0] (~amk@
06:18:24 Quit Ckat (Read error: Connection reset by peer)
06:19:20 Quit S|h|a|w|n (Quit: Leaving)
07:00:50***Saving seen data "./dancer.seen"
09:00:54***No seen item changed, no save performed.
09:43:16speachyamachronic: Got a question about the "new" USB control API, when you're available.
09:44:50speachyI presume the intention is that the driver sits on control requests with accompanying data until the data is complete, before handing them to the core?
11:00:55***No seen item changed, no save performed.
11:15:33 Quit speachy (Quit: WeeChat 3.4)
12:39:13 Join ZincAlloy [0] (~Adium@2a02:8108:943f:d824:b174:8bb:55cf:732d)
13:00:58***Saving seen data "./dancer.seen"
14:04:33 Join Ckat [0] (~Ckat@xn--z7x.xn--6frz82g)
14:22:55 Join amachronic [0] (~amachroni@user/amachronic)
14:25:47amachronicspeachy: it's a bit more complicated than that since the driver has to ask the core how much data (if any) to send or receive
14:26:33amachronicthe driver is in control of the request lifetime, but it has to be careful not to destroy or modify it while the core has got a hold of it.
14:27:49amachroniccontrol reads are simplest and the core decides to stall them or ack them, possibly sending some data in return
14:28:27amachroniccontrol writes take two trips through the core:
14:28:53amachronic(1) first the core gets a chance to stall the request, or ask the host to send data (USB_CONTROL_RECEIVE)
14:29:48amachronic(2) assuming the host provides the requested data, the second time around the core gets to use the data and either stall or ack the request (but this ack cannot involve data transfer)
14:33:18 Quit amachronic (Quit: amachronic)
15:00:59***Saving seen data "./dancer.seen"
17:01:01***No seen item changed, no save performed.
18:17:30 Quit ZincAlloy (Quit: Leaving.)
19:00:24 Join massiveH [0] (
19:01:03***Saving seen data "./dancer.seen"
19:33:42 Join cockroach [0] (~blattodea@user/cockroach)
20:30:50 Quit rogeliodh (Quit: The Lounge -
20:31:14 Join rogeliodh [0] (
21:01:07***Saving seen data "./dancer.seen"
21:46:41 Join cockroac1 [0] (~blattodea@user/cockroach)
21:49:55 Nick cockroach is now known as cockroac2 (~blattodea@user/cockroach)
21:50:00 Nick cockroac1 is now known as cockroach (~blattodea@user/cockroach)
22:23:18__builtin_bilgus: yes, that was it
22:23:32__builtin-fcommon seems to have fixed it, thanks :)
22:36:21 Quit cockroac2 (Quit: leaving)
23:01:08***Saving seen data "./dancer.seen"

Previous day | Next day