IRC log of #cubox of Mon 24 Jun 2019. All times are in CEST < Back to index

14:13 Exaga> wb rabeeh
14:13 Exaga> jnettlet: u heard about the raspberry pi 4?
18:34 Humpelstilzchen> I wonder if the i2c finally works in the rpi4
18:53 Exaga> Humpelstilzchen: never been an issue for me
18:54 Exaga> the rpi4 has a new usb controller chip - VLI VL805
18:54 Exaga> might be ok but who cares :>
18:55 Exaga> first thing i thought when i heard about the rpi4 was "why can't the shitheads at rpi trading ltd. be as transparent as solidrun?"
18:56 Exaga> according to rpi trading ltd. (someone told me it was as late as february 2019) there weren't any plans to release any more revisions
18:57 Exaga> apparently there is/was, especially when the rpi4 is released it has 2018 screen-printed on the damned circuit boards!
18:57 Exaga> or at least the official pics of it does
19:01 Exaga> seems that more than just the rpi firmware is closed-source :>
19:03 Humpelstilzchen> Exaga: the rpi can't do clock stretching with i2c, it ends up reading random data
19:05 Exaga> why on earth would you want to perform clock stretching on a rpi?
19:06 Exaga> surely much more suitable devices exist
19:06 Humpelstilzchen> Exaga: the rpi is obviously i2c master and the slave performs the clock stretching
19:07 Exaga> rpi is just a toy. rpi is a poor man's hummingboard :>
19:09 Exaga> i only use i2c for rtc so never had any issues
19:14 nemunaire> except we can't buy hummingboard with 4GB of RAM... :(
19:19 Exaga> hmmm
19:20 Exaga> ddr4 @ 2400MHz too