| 00:20.59 | *** join/#qi-hardware infobot (ibot@rikers.org) |
| 00:20.59 | *** topic/#qi-hardware is Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben/atusb 802.15.4 wireless, anelok and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware |
| 00:20.59 | *** mode/#qi-hardware [+v infobot] by ChanServ |
| 01:20.31 | *** join/#qi-hardware erichvk (~esh@ppp14-2-124-244.lns21.adl6.internode.on.net) |
| 05:02.48 | *** join/#qi-hardware eintopf (~eintopf@unaffiliated/eintopf) |
| 05:07.14 | *** join/#qi-hardware sb0 (~lekernel@182.239.114.131) |
| 06:37.04 | *** join/#qi-hardware erichvk_ (~esh@ppp14-2-121-210.lns21.adl6.internode.on.net) |
| 06:55.07 | *** join/#qi-hardware sb0 (~lekernel@182.239.114.131) |
| 08:55.05 | *** join/#qi-hardware jwhitmore (~jwhitmore@109.76.149.255) |
| 10:14.05 | *** join/#qi-hardware jwhitmore (~jwhitmore@109.76.149.255) |
| 10:50.00 | *** join/#qi-hardware limpkin (~quassel@154.49.213.114) |
| 11:59.29 | DocScrutinizer05 | you didn't change HSYNC but pixel clock, it seems to me |
| 12:03.34 | DocScrutinizer05 | there should be 3 clock lines usually: Hsync, Vsync, and pixel clock |
| 12:04.02 | DocScrutinizer05 | the pixel clock might as well be byte clock or even bit clock |
| 12:05.13 | *** join/#qi-hardware eintopf (~eintopf@unaffiliated/eintopf) |
| 12:31.06 | *** join/#qi-hardware jwhitmore (~jwhitmore@109.76.149.255) |
| 13:14.06 | *** join/#qi-hardware paul_boddie (~paul_bodd@host-37-191-186-243.lynet.no) |
| 13:14.32 | paul_boddie | Actually, I tried changing them all, but in the end it was a stupid mistake I made in my debugging code. |
| 13:15.34 | paul_boddie | I was just referring to "HSYNC meant to go high with first pixel of a line, but in fact it goes low, and went high on last pixel of previous line already" which sounds more like data enable than HSYNC. |
| 13:16.06 | paul_boddie | In fact, inverting data enable made surprisingly little difference. |
| 13:39.41 | paul_boddie | Interesting to see the Qualcomm takeover has been blocked, by the way. |
| 14:07.28 | *** join/#qi-hardware wpwrak (~werner@52-32-17-190.fibertel.com.ar) |
| 14:53.20 | *** join/#qi-hardware jwhitmore (~jwhitmore@109.76.149.255) |
| 16:51.45 | *** join/#qi-hardware jwhitmore (~jwhitmore@109.76.149.255) |
| 18:13.14 | kyak | https://amdflaws.com/ oh for fuck sake |
| 18:13.59 | kyak | pandora's box is opened |
| 18:36.01 | opbolt | what qualcomm take over? |
| 19:04.14 | opbolt | any bugs/doors in older amd cpus? |
| 19:04.40 | opbolt | like AMD Athlon(tm) II X3 440 Processor :) |
| 19:04.54 | opbolt | hope not too bad |
| 19:20.01 | paul_boddie | Broadcom wanted to take over Qualcomm. The fact that it was a megamerger should have been a warning sign, if you ask me. |
| 19:23.46 | *** join/#qi-hardware zcrc (~pcercuei@181.42.18.40) |
| 19:37.21 | *** join/#qi-hardware jwhitmore (~jwhitmore@109.76.149.255) |
| 19:55.21 | DocScrutinizer05 | the fact that Trump (and his offices) think Qualcomm is national-security relevant tells a lot |
| 19:56.07 | DocScrutinizer05 | "we must not lose control over 5G" mhmhmhmhm |
| 20:22.44 | paul_boddie | It's his "go to" excuse for regulation. He used it with the Lattice takeover attempt, where the Chinese investment company then went and bought Imagination instead. |
| 20:23.11 | paul_boddie | I doubt that he has any problems with, say, big companies getting even bigger. |
| 20:23.41 | paul_boddie | Still, it might be good news if you want to use iMX stuff in the future. ;-) |
| 20:46.53 | *** join/#qi-hardware zcrc (~pcercuei@181.42.18.40) |
| 21:32.39 | DocScrutinizer05 | how us iMX related? |
| 21:32.43 | DocScrutinizer05 | is* |
| 21:33.25 | DocScrutinizer05 | who bought NXP? |
| 21:35.29 | paul_boddie | Qualcomm. |
| 21:36.41 | paul_boddie | Qualcomm bought NXP who had bought Freescale whose product iMX is/was. |
| 21:38.41 | DocScrutinizer05 | ooh |
| 21:40.04 | DocScrutinizer05 | https://www.cnbc.com/2018/02/20/qualcomm-raises-offer-for-nxp-semiconductors.html |
| 21:40.24 | paul_boddie | Even though Intel and Samsung are apparently bigger than even a combined Broadcom/Qualcomm, I'm not sure megamergers are really the answer. |
| 21:40.34 | paul_boddie | Especially given Qualcomm's history. |
| 21:42.26 | DocScrutinizer05 | https://seekingalpha.com/article/4101068-qualcomm-making-mistake-buying-nxp-semiconductors |
| 21:43.24 | paul_boddie | Is there a Web page about step 2, by the way? Looked briefly on neo900.org and didn't find anything. |
| 21:43.42 | paul_boddie | (Then again, I doubt that I am at my most perceptive lately.) |
| 21:45.43 | DocScrutinizer05 | not really |
| 21:45.47 | DocScrutinizer05 | ~step2 |
| 21:45.48 | infobot | it has been said that step2 is http://talk.maemo.org/showthread.php?p=1444602, or http://talk.maemo.org/showthread.php?p=1444625 |
| 21:46.17 | paul_boddie | Thanks! |
| 21:48.00 | paul_boddie | So I guess that this Maemo-Leste thing has changed the equations around chipsets and compatibility. That you don't strictly need OMAP3 any more. |