kyak changed the topic of #qi-hardware to: 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
infobot has quit [Read error: Connection reset by peer]
fdcx has quit [Ping timeout: 240 seconds]
infobot has joined #qi-hardware
erichvk has joined #qi-hardware
eintopf has quit [Ping timeout: 264 seconds]
eintopf has joined #qi-hardware
sb0 has joined #qi-hardware
sb0 has quit [Client Quit]
erichvk_ has joined #qi-hardware
erichvk has quit [Ping timeout: 256 seconds]
sb0 has joined #qi-hardware
sb0 has quit [Quit: Leaving]
jwhitmore has joined #qi-hardware
jwhitmore has quit [Ping timeout: 264 seconds]
jwhitmore has joined #qi-hardware
limpkin has quit [Ping timeout: 268 seconds]
limpkin has joined #qi-hardware
erichvk_ has quit [Ping timeout: 264 seconds]
jwhitmore has quit [Ping timeout: 246 seconds]
<DocScrutinizer05> you didn't change HSYNC but pixel clock, it seems to me
<DocScrutinizer05> there should be 3 clock lines usually: Hsync, Vsync, and pixel clock
<DocScrutinizer05> the pixel clock might as well be byte clock or even bit clock
eintopf has quit [Ping timeout: 260 seconds]
eintopf has joined #qi-hardware
jwhitmore has joined #qi-hardware
paul_boddie has joined #qi-hardware
<paul_boddie> Actually, I tried changing them all, but in the end it was a stupid mistake I made in my debugging code.
<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.
<paul_boddie> In fact, inverting data enable made surprisingly little difference.
jwhitmore has quit [Ping timeout: 268 seconds]
<paul_boddie> Interesting to see the Qualcomm takeover has been blocked, by the way.
wpwrak has quit [Ping timeout: 240 seconds]
wpwrak has joined #qi-hardware
jwhitmore has joined #qi-hardware
jwhitmore has quit [Ping timeout: 246 seconds]
jwhitmore has joined #qi-hardware
jwhitmore has quit [Ping timeout: 240 seconds]
<kyak> https://amdflaws.com/ oh for fuck sake
<kyak> pandora's box is opened
<opbolt> what qualcomm take over?
<opbolt> any bugs/doors in older amd cpus?
<opbolt> like AMD Athlon(tm) II X3 440 Processor :)
<opbolt> hope not too bad
<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.
zcrc has joined #qi-hardware
jwhitmore has joined #qi-hardware
<DocScrutinizer05> the fact that Trump (and his offices) think Qualcomm is national-security relevant tells a lot
<DocScrutinizer05> "we must not lose control over 5G" mhmhmhmhm
<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.
<paul_boddie> I doubt that he has any problems with, say, big companies getting even bigger.
<paul_boddie> Still, it might be good news if you want to use iMX stuff in the future. ;-)
zcrc has quit [Ping timeout: 260 seconds]
zcrc has joined #qi-hardware
zcrc has quit [Quit: AtomicIRC: The nuclear option.]
<DocScrutinizer05> how us iMX related?
<DocScrutinizer05> is*
<DocScrutinizer05> who bought NXP?
<paul_boddie> Qualcomm.
<paul_boddie> Qualcomm bought NXP who had bought Freescale whose product iMX is/was.
<DocScrutinizer05> ooh
<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.
<paul_boddie> Especially given Qualcomm's history.
<paul_boddie> Is there a Web page about step 2, by the way? Looked briefly on neo900.org and didn't find anything.
<paul_boddie> (Then again, I doubt that I am at my most perceptive lately.)
<DocScrutinizer05> not really
<DocScrutinizer05> ~step2
<paul_boddie> Thanks!
<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.
paul_boddie has quit []