--- Log for 26.04.123  Server: copper.libera.chat  Channel: #rockbox
--- Nick: rb-logbot  Version: Dancer V4.16  Started: 5 days and 4 hours ago

00.10.08 Quit    troglodito (Ping timeout: 248 seconds)
00.10.54 Join    troglodito [0] (~cave@81.4.123.134)
00.24.45 Quit    troglodito (Ping timeout: 240 seconds)
00.35.08 Join    troglodito [0] (~cave@81.4.123.134)
00.37.11 Quit    m01 (Quit: Konversation terminated.)
00.39.38 Join    m01 [0] (~quassel@vps-b172b88b.vps.ovh.net)
01.46.52 Quit    Bobathan (Quit: ZNC 1.8.2+deb2+b1 - https://znc.in)
01.50.35 Join    Bobathan_ [0] (~admin@65.29.248.157)
01.53.12 ***     Saving seen data "./dancer.seen"
02.04.17 Quit    Bobathan_ (Quit: ZNC 1.8.2+deb2+b1 - https://znc.in)
02.04.35 Join    Bobathan_ [0] (~admin@cpe-65-29-248-157.wi.res.rr.com)
03.53.14 ***     Saving seen data "./dancer.seen"
04.28.16 Quit    Bobathan_ (Ping timeout: 252 seconds)
04.30.41 Quit    ats (Ping timeout: 246 seconds)
04.37.30 Join    ats [0] (~ats@cartman.offog.org)
04.39.29 Join    Bobathan_ [0] (~admin@cpe-65-29-248-157.wi.res.rr.com)
05.20.45 Quit    Bobathan_ (Ping timeout: 255 seconds)
05.26.17 Join    Bobathan_ [0] (~admin@cpe-65-29-248-157.wi.res.rr.com)
05.29.59 Join    advcomp2019 [0] (~advcomp20@user/advcomp2019)
05.32.36 Quit    advcomp2019_ (Ping timeout: 250 seconds)
05.53.15 ***     Saving seen data "./dancer.seen"
07.53.18 ***     No seen item changed, no save performed.
08.07.26 Quit    speachy (Quit: WeeChat 3.6)
08.37.20 Join    speachy [0] (~speachy@tunnel658658-pt.tunnel.tserv12.mia1.ipv6.he.net)
08.37.21 Quit    speachy (Changing host)
08.37.21 Join    speachy [0] (~speachy@rockbox/developer/speachy)
08.37.21 Mode    "#rockbox +v speachy" by ChanServ (ChanServ@services.libera.chat)
09.00.03 Quit    _bilgus (Quit: Leaving)
09.01.43 Join    _bilgus [0] (~bilgus@162.154.213.134)
09.53.22 ***     Saving seen data "./dancer.seen"
11.22.52 Join    jacobk [0] (~quassel@64.189.201.150)
11.36.57 Quit    tchan (Read error: Connection reset by peer)
11.51.44 Join    advcomp2019_ [0] (~advcomp20@user/advcomp2019)
11.53.26 ***     Saving seen data "./dancer.seen"
11.55.00 Quit    advcomp2019 (Ping timeout: 252 seconds)
12.05.12 Quit    jacobk (Ping timeout: 250 seconds)
13.24.36 Join    tchan [0] (~tchan@c-98-206-114-113.hsd1.il.comcast.net)
13.49.14 Join    Dackor [0] (~Dackor@host81-159-238-12.range81-159.btcentralplus.com)
13.53.30 ***     Saving seen data "./dancer.seen"
13.54.11 Quit    Dackor (Quit: Connection closed)
14.34.28 Nick    l is now known as launchd[m] (launchd@bitbot/launchd)
14.35.54 Nick    launchd[m] is now known as l (launchd@bitbot/launchd)
15.53.34 ***     Saving seen data "./dancer.seen"
16.14.12 Join    Nyaa [0] (~Nyaaori@cyberia.club/meow/nyaaori)
16.14.32 #       <Nyaa> oops forgot to put channel in autojoin list
16.17.15 Join    paulk [0] (~paulk@vpn-0-22.aquilenet.fr)
16.17.43 #       <jssfr> speachy, oh? what displays?
16.18.18 #       <jssfr> I have a bunch of embedded projects behind me and I have a loose TODO item to get a daisy and mess with it and maybe rockbox it once my current hardware project is finished.
16.18.25 #       <speachy> https://boardsandsensors.com/products/3-units-1-3-inch-tft-ips-lcd-display-module-240x240-spi-for-arduino-rasppi
16.18.55 #       <speachy> 16-bit, 1.3", 240x240 IPS (supposedly), SPI interface
16.18.57 #       <jssfr> right, let's see if I can find something like that in europe.
16.19.27 #       <speachy> it's easy to find parallel-bus-attached displays, but SPI-attached ones are trickier.
16.19.48 #       <speachy> (well, there's a ton of really low-res/monochrome ones...)
16.20.24 #       <jssfr> haha, there's an adafruit breakout based on the same driver IC and they just slapped a μSD card plus pinout on it apparently?
16.20.28 #       <jssfr> *card slot
16.20.32 #       <jssfr> https://eckstein-shop.de/Adafruit15422240x240WideAngleTFTST7789LCDDisplayEN
16.21.18 #       <jssfr> that would go well with a daisy
16.21.20 #       <speachy> not a "standard" SD clot
16.21.35 #       <jssfr> micro SD
16.21.44 #       <speachy> 1-bit interface only, and even then it might only work in SPI mode, which not everything works with
16.21.51 #       <speachy> (at least that's been my experience...)
16.21.59 #       <jssfr> huh?
16.22.08 #       <jssfr> I see six pins dedicated to the SD
16.22.10 #       <speachy> the full SD card pinout isn't brought out to the header
16.22.18 #       <jssfr> (plus presumably Vcc and Gnd)
16.22.31 #       <jssfr> (I never used SD on microcontrollers, so I know nothing)
16.23.12 #       <speachy> let me double check on adafruit
16.23.23 #       <jssfr> good idea
16.26.11 #       <jssfr> ack, it doesn't seem to be fully wired out on the pin header
16.26.32 #       <jssfr> well, wouldn't matter with the pod for development
16.27.55 #       <speachy> I think it only has a CS for the SD card, the rest are shared.
16.28.09 #       <jssfr> ohhh
16.28.11 #       <jssfr> well
16.28.16 #       <jssfr> "suboptimal", as they say
16.28.18 #       <speachy> that's why I didn't bother with some of the similar display boards I'd encountered.
16.29.09 #       <speachy> that's a nicer display than what I picked up, granted.  adafruit also has a nice 240x320 2" screen with similar I/O.
16.29.42 #       <speachy> Using SD cards in SPI mode is a real PITA.  
16.31.43 #       <speachy> heh, I've always wondered if an e-ink display might not be a bad idea
16.32.48 #       <jssfr> yeah eink would be pretty neat
16.34.54 #       <speachy> anyway -- SPI normally isn't ideal but we should be able to use the hardware's native SPI +DMA to refresh the screen with zero CPU interaction.
16.35.29 #       <speachy> (leave it to auto-refresh whenever the display is on, or only get triggered when necessary, both are doable..)
16.35.40 #       <speachy> could even double-buffer things to keep it seamless.  :D
16.36.08 #       <speachy> the STM32 dma engines are really capable.
16.37.22 #       <speachy> huh, 16 bit @ 240x240 yields just shy of 1Mbit per frame, which means @1MHz we'd get 1fps.
16.41.56 #       <speachy> if I read the datasheet correctly we can drive the SPI interace to 62.5MHz, which basically means we're going to be limited by how fast we can drive the STM32's SPI interface.
16.45.04 #       <speachy> that depends on the clock tree we use, but 24-32MHz should be no problem at all, and in theory it can hit at least 133MHz. :D
16.46.10 #       <speachy> but that would mean using a PLL, and I don't know if we'd have one to sapre.
16.59.31 Quit    Bobathan_ (Ping timeout: 240 seconds)
17.02.30 Join    Bobathan_ [0] (~admin@cpe-65-29-248-157.wi.res.rr.com)
17.13.07 Quit    Bobathan_ (Ping timeout: 255 seconds)
17.14.28 Join    Bobathan [0] (~admin@cpe-65-29-248-157.wi.res.rr.com)
17.44.31 Quit    Sundiver (Ping timeout: 240 seconds)
17.52.03 Join    Sundiver [0] (~jaro@73.88.42.145)
17.52.04 Quit    Sundiver (Changing host)
17.52.04 Join    Sundiver [0] (~jaro@user/sundiver)
17.53.15 Quit    Trzyzet (Ping timeout: 248 seconds)
17.53.31 Join    Trzyzet [0] (~Trzyzet@cpc110919-live30-2-0-cust650.17-2.cable.virginm.net)
17.53.37 ***     Saving seen data "./dancer.seen"
18.53.01 Join    massiveH [0] (~massiveH@2600:4040:a99f:1f00:acde:11e5:8baf:6367)
19.46.25 Quit    troglodito (Ping timeout: 240 seconds)
19.53.38 ***     Saving seen data "./dancer.seen"
19.54.56 Join    troglodito [0] (~cave@81.4.123.134)
21.36.28 Quit    massiveH (Quit: Leaving)
21.53.40 ***     Saving seen data "./dancer.seen"
22.07.10 #       <hactar|ant> 1.3" ips?
22.07.11 #       <hactar|ant> wow
22.11.00 Quit    speachy (Quit: WeeChat 3.6)
23.53.41 ***     Saving seen data "./dancer.seen"