lekernel changed the topic of #milkymist to: Milkymist One, Migen, Milkymist SoC & Flickernoise :: Logs: http://en.qi-hardware.com/mmlogs
jimmythehorn has quit [Quit: jimmythehorn]
sh4rm4 has quit [Remote host closed the connection]
sh4rm4 has joined #milkymist
bhamilton has joined #milkymist
bhamilton has quit [Quit: Leaving.]
bhamilton has joined #milkymist
playthatbeat has quit [Quit: KVIrc 4.1.3 Equilibrium http://www.kvirc.net/]
playthatbeat has joined #milkymist
bhamilton has quit [Quit: Leaving.]
bhamilton has joined #milkymist
lekernel has joined #milkymist
Gurty has joined #milkymist
bhamilton has quit [Quit: Leaving.]
bhamilton has joined #milkymist
antgreen has joined #milkymist
bhamilton has quit [Quit: Leaving.]
bhamilton has joined #milkymist
bhamilton has left #milkymist [#milkymist]
<wpwrak> funny. there doesn't seem to be a "simple" tftp server. well, there's Net::TFTPd ... long live Perl :)
<wpwrak> it's probably a bad sign if (unsuccessfully) searching for a simple tool takes longer than just writing it yourself
<wpwrak> too late :)
<wpwrak> and that's one of the inetd-based ones, probably with tons of security features. just what gets in the way.
<wpwrak> let's see if writing works, too ...
<wpwrak> yup. perfect.
antgreen has quit [Ping timeout: 240 seconds]
<wpwrak> lekernel: mind if i convert all your unsafe types, especially shorts, to uintXX_t ?
<lekernel> no
<lekernel> you can do that
<wpwrak> thanks ! :)
antgreen has joined #milkymist
azonenberg has quit [Read error: Operation timed out]
antgreen has quit [Ping timeout: 256 seconds]
<sh4rm4> wpwrak, we have arpa/tftp.h, this is probably to encourage you to roll your own
<wpwrak> in milkymist-ng ?
<sh4rm4> in glibc
<sh4rm4> and anything that wants to stay compatible... *sigh*
<wpwrak> i don't think there's much of a glibc either :)
<wpwrak> it's a very NIH-heavy environment
<lekernel> come on, copy and paste isn't NIH
<sh4rm4> well, i was just arguing about the rationale of arpa/tftp.h's inclusion into our libc's
<lekernel> and I did look for a bare metal environment that did not suck, but could not find one
<lekernel> what do you recommend instead? newlib lol?
<sh4rm4> i ? musl of course
<lekernel> isn't it linux only?
<sh4rm4> yes
<lekernel> so. I said bare metal.
<sh4rm4> currently
<sh4rm4> indeed
<lekernel> u-boot is horrible, rtems mediocre at best, ...
<sh4rm4> how about a linux syscall emulation layer ? shouldnt be too hard to add to your kernel of choice
<sh4rm4> of course only the important ones
<sh4rm4> nuttx seems to be interesting as well
<lekernel> some of the "NIH" code is actually copy and paste from nuttx ;)
<lekernel> but nuttx doesn't have a LM32 port, and it was faster to just copy and paste the needed bits
<wpwrak> patches are coming ...
<wpwrak> i didn't touch the (bla & 0xff00) >> 8 critters. they're usually unnecessary was well, unless you strive to make your code -Wconvert clean, but that's usually a rather grueling uphill battle
<wpwrak> s/was/as/
<wpwrak> (unnecessry) in the sense that bla >> 8 is just equivalent
bhamilton has joined #milkymist
<lekernel> -strcpy(buf, filename);
<lekernel> -buf += strlen(filename);
<lekernel> +memcpy(buf, filename, len);
<lekernel> +buf += len;
<lekernel> haha, such attention to detail ;) thanks wpwrak
mumptai has joined #milkymist
<GitHub69> [milkymist-ng] sbourdeauducq pushed 10 new commits to master: http://git.io/7OppWA
<GitHub69> milkymist-ng/master 65b807b Werner Almesberger: microudp.c: avoid redundant accesses into multi-level structures
<GitHub69> milkymist-ng/master 0d21711 Sebastien Bourdeauducq: dvisampler/chansync: use Record.raw_bits()
<GitHub69> milkymist-ng/master 36613c7 Werner Almesberger: tftp.c: use symbolic constants for protocol opcodes
<wpwrak> i actually did it to avoid the uint8_t vs. char conflict that would otherwise require a cast ;-0
bhamilton has quit [Quit: Leaving.]
azonenberg has joined #milkymist
azonenberg has quit [Remote host closed the connection]
jimmythehorn has joined #milkymist
azonenberg has joined #milkymist
azonenberg has left #milkymist [#milkymist]
azonenberg has joined #milkymist
<wpwrak> oh, the patches sent someone running ;-)
<larsc> He'll be back
<larsc> hm, the internet doesn't seem to know -Wconvert, what does it do?
<wpwrak> ah, sorry, it's -Wconversion
<wpwrak> it warns you when you may chop off bits
<larsc> You probably don't want to have it enabled by default, but building your code with it once in a while might help to uncover hidden bugs
<larsc> especially the -Wsign-conversion part will probably trigger quite often
<lekernel> grmbl... connecting the logic analyzer on chB makes it work
<lekernel> sometimes
<lekernel> I HATE BUGSA
<wpwrak> we should find some bugs that need a new hw revision. then you could send me your non-chB board ;-) well, it may just magically work here. i've seen that before :)
bhamilton has joined #milkymist
<lekernel> address phase non-acked... same crap as before
<wpwrak> odd. it looked exactly like chan A here.
<wpwrak> maybe your overcooked some chip :)
<lekernel> this hdmi stuff is cursed for maximum wastage of my time
<lekernel> ah it works correctly with the 50MHz clock
<lekernel> mayble the oversampling needs to be > 64 with the 83Mhz
<wpwrak> hmm, could be. the margin is fairly generous, but yes, at almost twice the speed, you may hit some outliers
<wpwrak> maybe it needs to be calculated based on the system clock. else, we may run into conflicts with the I2C clock cycle
<wpwrak> there are also bidirectional level-shifter chips that produce faster edges than this single-transistor solution. but then, almost everyone seems to be happy with this sort of approach. and i didn't find anything obviously wrong or even marginal with your implementation
<larsc> the bidirectional level-shifter make good oscillators
bhamilton has quit [Quit: Leaving.]
<wpwrak> gee, dual-use technology ;-)
<lekernel> wpwrak, have you tested it with the 83MHz clock?
kiwichris has quit [Quit: Leaving]
<lekernel> 128 downsampling does not solve the problem
<wpwrak> no, i only tested with the rather simple build.py
<wpwrak> ... that you say runs at 50 MHz
<lekernel> I guess you have built milkymist-ng for the TFTP... it has the EDID on both ports
<lekernel> and that very problematic 83MHz clock
<wpwrak> what i tested wasn't full mi-ng
<lekernel> well it could even be something different than the clock, in good maximum time wastage tradition more downsampling does nothing
<wpwrak> ;-)
<wpwrak> don't stress yourself :)
<wpwrak> running. mi-ng, i ddc works in port b (without signal)
<wpwrak> enabling signal
<wpwrak> there's no pixel clock blinking, but xrandr still things it can talk to the m1
<wpwrak> s/things/thinks/
jevin has quit [Quit: Textual IRC Client: www.textualapp.com]
<lekernel> yeh, it does not blink anything on the pixel clock...
<wpwrak> looking good here then
<lekernel> yay, a non reproducible bug
<wpwrak> a problem that a) may solve itself, or b) will show up in more controlled experiments as well
<wpwrak> nothing to worry about this far. you already have a number of other problem indicators, like not being able to get a stable frame
<wpwrak> they may or may not be related
<lekernel> meh, now it doesn't work anymore with the 50MHz clock...
<wpwrak> it's having fun with you ;-)
<wpwrak> maybe just write off your chB
<lekernel> maybe this is just yet another mega time wastage schrödinbug that has in fact nothing to do with the clock or mi-ng vs. edid tester
<wpwrak> yeah. you may later discover that some bonding wire in a chip broke. i've actually had that.
bhamilton has joined #milkymist
<wpwrak> oh, and if you did any recent soldering, just let it rest for a while. some types of flux are VERY conductive and easily override pull-ups. i've had a board that never came out of reset before the flux dried.
bhamilton has left #milkymist [#milkymist]
jevin has joined #milkymist
<lekernel> what's really strange is I see signals with the saelae
<lekernel> but sometimes the M1 acks, usually it does not
<lekernel> larsc, do you have any plans to assemble your boards?
<larsc> yes
bhamilton has joined #milkymist
bhamilton has quit [Client Quit]
<wpwrak> lekernel: you may want to get a "real" oscilloscope. considering that the basic but decent ones are ~EUR 1k and the "professional" ones are well in the 10k+ range, i think little is lost if you get a low-end one now, even with the understanding that you're already operating beyond its range
<wpwrak> this will allow you to make at least a coarse assessment. with just digital signals, you're basically blind. i'm actually amazed that you got as far as you did
Scopeuk-AFK is now known as Scopeuk
<GitHub56> [mibuild] sbourdeauducq pushed 2 new commits to master: http://git.io/f_S1Vw
<GitHub56> mibuild/master 29eaf06 Sebastien Bourdeauducq: xilinx_ise: do not attempt to source settings file on Windows
<GitHub56> mibuild/master 31b1960 Sebastien Bourdeauducq: xilinx_ise: add --no-source option to disable sourcing of ISE settings file
antgreen has joined #milkymist
lekernel has quit [Quit: Leaving]
Scopeuk is now known as Scopeuk-AFK
mumptai has quit [Ping timeout: 272 seconds]