--- Log for 04.01.123  Server: calcium.libera.chat  Channel: #rockbox
--- Nick: rb-logbot  Version: Dancer V4.16  Started: 9 days and 10 hours ago

00.08.28 ***     Saving seen data "./dancer.seen"
02.08.31 ***     No seen item changed, no save performed.
02.20.20 Join    mink [0] (~mink@2a07:3e00:81:0:7b6:4663:f93b:9fae)
02.20.26 Quit    mink (Remote host closed the connection)
02.21.14 Join    mink [0] (~mink@193.134.219.71)
02.27.07 Quit    mink (Remote host closed the connection)
02.32.00 Join    mink [0] (~mink@2a07:3e00:81:0:7b6:4663:f93b:9fae)
04.08.35 ***     Saving seen data "./dancer.seen"
05.06.46 Quit    hexadecagram (Ping timeout: 272 seconds)
05.26.30 Join    hexadecagram [0] (~acc@user/hexadecagram)
06.08.37 ***     Saving seen data "./dancer.seen"
07.14.49 Join    CH23_ [0] (~CH23@84-107-29-234.cable.dynamic.v4.ziggo.nl)
07.34.14 Quit    mink (Remote host closed the connection)
07.38.30 Join    mink [0] (~mink@193.134.219.72)
07.38.34 Quit    mink (Remote host closed the connection)
07.45.19 Join    mink [0] (~mink@2a07:3e00:81:0:7b6:4663:f93b:9fae)
07.45.29 Quit    mink (Remote host closed the connection)
08.08.38 ***     Saving seen data "./dancer.seen"
08.10.14 Quit    CH23_ (Quit: CH23 was blown up by NO CONNECTION)
09.18.48 Join    massiveH [0] (~massiveH@2600:4040:a992:a300:9906:16bb:1e8b:35d1)
10.08.39 ***     Saving seen data "./dancer.seen"
11.08.53 Quit    massiveH (Quit: Leaving)
11.09.31 Join    dconrad_web [0] (~dconrad_w@entr-34279.desm.netins.net)
11.12.35 #       <dconrad_web> speachy: (logs) I caved and ordered a surfans f20, hopefully I get the 2.7 version. Assuming we can get the native port working to the same level as the older players, it sounds like the hardware changes are significant enough they may warrant a whole separate configuration/port. Do you have any thoughts on how to differentiate between the two? Or
11.12.35 #       <dconrad_web> would it be too complicated?
11.22.04 Quit    fourHZ (Quit: Client closed)
12.08.42 ***     Saving seen data "./dancer.seen"
13.18.49 Join    lebellium [0] (~lebellium@2a01cb040109a600485ab91645988fae.ipv6.abo.wanadoo.fr)
13.45.08 Join    fourHZ [0] (~fourHZ@92-52-40-121.dynamic.orange.sk)
14.08.45 ***     No seen item changed, no save performed.
14.32.41 Quit    fourHZ (Quit: Client closed)
15.17.35 Quit    jacobk (Ping timeout: 260 seconds)
16.08.47 ***     Saving seen data "./dancer.seen"
16.42.25 Quit    dconrad_web (Quit: Connection closed)
16.46.01 #       <Trzyzet> I think the old ones has just the micro USB sockets
16.46.33 #       <Trzyzet> I mean, all the pictures on the internet and even auctions shows the Surfans players with micro USB socket
17.33.23 Quit    lebellium (Quit: Leaving)
17.36.01 Quit    GeekShadow (Ping timeout: 252 seconds)
17.37.03 Join    GeekShadow [0] (~antoine@82-64-164-139.subs.proxad.net)
17.41.22 Quit    hexadecagram (Quit: ZNC 1.8.2 - https://znc.in)
18.08.50 ***     Saving seen data "./dancer.seen"
18.19.19 Join    jacobk [0] (~quassel@2603-8080-b200-7b02-77cb-6304-f9db-dda1.res6.spectrum.com)
18.37.05 Quit    jacobk (Ping timeout: 260 seconds)
18.53.15 Join    jacobk [0] (~quassel@2603-8080-b200-7b02-77cb-6304-f9db-dda1.res6.spectrum.com)
19.12.32 Quit    jacobk (Ping timeout: 255 seconds)
19.13.36 Join    hexadecagram [0] (~acc@user/hexadecagram)
19.15.47 #       <_bilgus> Or do you mean how to do so in the firmware?
20.08.53 ***     Saving seen data "./dancer.seen"
20.18.16 Quit    prg_ (Quit: ZNC 1.8.2 - https://znc.in)
20.21.20 #       <rb-bluebot> Build Server message: 3New build round started. Revision ea33e66021, 303 builds, 7 clients.
20.22.21 Join    prg_ [0] (~prg@xannode.com)
20.42.05 #       <rb-bluebot> Build Server message: 3Build round completed after 1245 seconds.
20.42.09 #       <rb-bluebot> Build Server message: 3Revision ea33e66021 result: All green
20.47.25 Join    advcomp2019_ [0] (~advcomp20@user/advcomp2019)
20.50.39 Quit    advcomp2019 (Ping timeout: 260 seconds)
21.27.03 Join    speachy [0] (~speachy@tunnel658658-pt.tunnel.tserv12.mia1.ipv6.he.net)
21.27.04 Quit    speachy (Changing host)
21.27.04 Join    speachy [0] (~speachy@rockbox/developer/speachy)
21.27.04 Mode    "#rockbox +v speachy" by ChanServ (ChanServ@services.libera.chat)
21.28.04 #       <speachy> dconrad:  There's no known way to distinguish between the different HW revisions (in software)
21.28.42 #       <speachy> the fact that none of the various OEMs seem to support field-upgrading older devices with newer firmware seems to indicate it might not be possible either.
21.28.57 #       <speachy> (or they just hardcoded the kernel stuff instead of using proper devicetrees etc)
21.30.02 #       <speachy> I know of two basic HW revs; the newer one uses different line out configuration.  I don't know if the USB-C equipped ones are different beyond the physical connector.
21.39.57 #       <speachy> that said I'd be shocked if there wasn't a way to detect them at the board level, HW designers are usually very good about that sort of thing.
22.03.02 #       <rb-bluebot> Build Server message: 3New build round started. Revision 9367ef1ed6, 303 builds, 7 clients.
22.08.54 ***     Saving seen data "./dancer.seen"
22.21.49 #       <rb-bluebot> Build Server message: 3Build round completed after 1127 seconds.
22.21.51 #       <rb-bluebot> Build Server message: 3Revision 9367ef1ed6 result: All green
22.35.00 Join    jacobk [0] (~quassel@47-186-81-17.dlls.tx.frontiernet.net)
23.37.16 Quit    m01 (Quit: Konversation terminated.)
23.39.27 Join    m01 [0] (~quassel@vps-b172b88b.vps.ovh.net)