**** BEGIN LOGGING AT Mon Jul 30 03:00:00 2018
Jul 30 03:21:50 <ayjay_t> evil beagle
Jul 30 04:19:50 <kremlin> ee
Jul 30 06:30:45 <ayjay_t> i'm perplexed by the krem
Jul 30 06:31:44 <kremlin> ?
Jul 30 08:20:33 <ayjay_t> why all the ee's
Jul 30 08:20:37 <ayjay_t> eeeee
Jul 30 08:20:41 <ayjay_t> one e two e three e four e
Jul 30 12:44:49 <ayjay_t> O_O
Jul 30 12:44:54 <ayjay_t> the world may never know
Jul 30 13:11:31 <Duality> hi
Jul 30 13:11:32 <ogra> conspiracy of the vowels ...
Jul 30 13:18:16 <ayjay_t> only one vowel
Jul 30 13:19:59 <ogra> i bet the others talked e into it ;)
Jul 30 15:22:08 <royals> hey
Jul 30 19:49:22 <beef_> hello all
Jul 30 19:49:54 <beef_> anyone have information on how to program the i2c interface of the hdmi tx, the tda19988?
Jul 30 19:55:36 <beef_> like a register map of what each address does?
Jul 30 20:07:39 <zmatt> beef_: obnoxiously there's no good public documentation on that, basically the info you can find is:
Jul 30 20:07:55 <zmatt> 1. the public datasheet, which is informative but no register docs
Jul 30 20:08:20 <zmatt> 2. datasheets of related hdmi transmitters... iirc you can find some with register docs but it's been a while so maybe I remember wrong
Jul 30 20:08:37 <zmatt> 3. the linux kernel driver
Jul 30 20:10:04 <zmatt> 4. a standalone (baremetal) driver from nxp that someone put online (quite possibly in violation of an NDA?)
Jul 30 20:17:51 <zmatt> the tda9983b datasheet includes register documentation.  I don't know how similar it is to the tda19988 but it seems plausible that it'll contain at least *some* useful info
Jul 30 20:25:55 <beef_> Thank you zmatt,
Jul 30 20:26:37 <beef_> I'll take a look
Jul 30 20:27:00 <beef_> I sent in a support ticket with nxp to sign an NDA, but I haven't heard anything for a while, must be too low priority
Jul 30 20:28:23 <beef_> I notice a joelagnel on github released an open source driver for beagle, is that the one?
Jul 30 20:29:08 <zmatt> I see not the slightest hint that it's "open source"
Jul 30 20:29:14 <zmatt> but yes that's what I meant
Jul 30 20:29:19 <beef_> Oh sorry, yeah
Jul 30 20:29:30 <beef_> It's very frustrating that NXP still controls such an old chip
Jul 30 20:29:57 <beef_> 10 or so years old? Haha
Jul 30 20:31:06 <zmatt> the integrated hdmi transmitter on many TI SoCs (e.g. omap4/5 and am57xx) is also undocumented
Jul 30 20:31:25 <beef_> That's very frustrating
Jul 30 20:31:33 <zmatt> presumably the HDCP folks have something to do with that
Jul 30 20:32:06 <beef_> Ahh, that makes a bit more sense
Jul 30 20:32:19 <zmatt> even though HDCP 1.x is completely broken
Jul 30 20:32:49 <zmatt> (since 2010)
Jul 30 20:32:58 <beef_> Haha go figure
Jul 30 20:35:45 <zmatt> and by completely broken I mean _completely_ broken.  the system relied on a secret master key (a 40x40 matrix of 56-bit integers), which was recovered and published in september 2010
Jul 30 20:36:32 <zmatt> which lets you produce the private key for any public key in the system
Jul 30 21:40:11 <beagleVision> I am having an issue with the Beaglebone blue not booting when I apply 12V power after a shutdown, to wake up either I apply 5V via usb or press power button, running Debian 9.6. Is this typical behavior?
Jul 30 21:41:19 <zmatt> battery present?
Jul 30 21:41:54 <beagleVision> yes battery is present
Jul 30 21:42:43 <zmatt> then connecting 12v is indeed not a wakeup event
Jul 30 21:43:41 <beagleVision> Thank you for confirming that this is normal
Jul 30 21:44:05 <zmatt> whenever battery *or* 12v is present, the always-on 5v supply is enabled, which is one of the two 5v inputs to the power management IC
Jul 30 21:44:08 <zmatt> (the other one being the usb 5v)
Jul 30 21:47:58 <beagleVision> thank you zmatt, I will continue to use 5V via usb to wake up the board
Jul 31 01:38:25 <black_13_> anyone familiar with this device manual XYG-Cortex-A 7
**** ENDING LOGGING AT Tue Jul 31 03:00:00 2018