<kristianpaul> pip :)
<kristianpaul> what??. you thread  Fallenou was hijacked ::(
<kristianpaul> ok,lest compile bsp..
<Fallenou> kristianpaul: yes please try again
<Fallenou> it might be better now
<kristianpaul> Fallenou: ttcp still gave me some fifo overflow..
<kristianpaul> wpwrak: a ttcp test is suposed to take how long?
<wpwrak> kristianpaul: that depends on how fast your link is and how much data you send ;-)
<kristianpaul> hmm i missed the -n and -l..
<kristianpaul> ha ttcp is starting to make sense !
<kristianpaul> 1 OK
<kristianpaul> 10 OK
<kristianpaul> 100 ..
<kristianpaul> Minimac RX FIFO overflow!
<kristianpaul> but test passed
<kristianpaul> oh weird, if i test again seems it freezed.
<kristianpaul> after reset and test again with 100 (buf) all went okay..
<kristianpaul> arggg, pesky bug !
<kristianpaul> 3000, and i still waiting...
<kmj> hey
<kmj> Anyone know video specs for 320x240? I managed to find some CGA specs that listed front/back porches, and so on -- but not a pixel clock speed.  I'm looking at stuff on my LA, and the specs don't appear to match. I'm thinking around 6mhz or so.
<kristianpaul> hm?
<kmj> This is an Amiga 500, 15.7khz horizontal refresh. I measured 63.56us between sync pulses, active video for 52.81us.
<kmj> I divide the active video by around 320-375 or so pixels, and I'm getting 140-160ns period... and there's an available clock into the video chip of 7.15909mhz
<kmj> but this active video of 52.81us doesn't match http://www.student.nada.kth.se/~d94-tan/pckort/videofrq.txt which claims it at 44.4
<wpwrak> (2nd hit for "cga timing" ;-)
<kmj> I obviously did 2389423948 web searches first :)
<wpwrak> yet you didn't find the one that agrees with your observation ? ;-)
<kmj> :)
<kmj> im reading ni.com link now :)
<kmj> most of the links, however, still talk about 640x400
<kmj> or x480
<wpwrak> hmm yes. the link i mentioned says it's jut NTSC timing at 320x200.
<kmj> Which is defined where?
<kmj> i can guess that the pixel clock is half of the 640 rate (so 6.075mhz instead of 12.15mhz)
<kmj> just about every reference I can find starts their "tables" with 640x480
<kmj> or so
<kmj> looks pretty good
<kmj> yeah NTSC matches what I'm seeing pretty clearly. Thanks.
<kmj> i can divide active video by pixels to get pixel clock speed
<kmj> I just don't know if the active video portion would be more than just 320 pixels
<Fallenou> hi :)
<Fallenou> kristianpaul: so you did git pull before compiling right ?
<Fallenou> would you say it is better now?  less crashing ? or the same
<Fallenou> or you can't say because it's totally random :p
<Fallenou> I am reading your e-mail
<Fallenou> ok thanks for all the logs and tests I will have a look after the work :)
<adamw_> roh, have u filled my phone number in tracking #?
<kristianpaul> Fallenou: yeah i pull
<kristianpaul> Fallenou: bette now, dont know, i dont get trought ftpd test (wich is the most important test for me)
<Fallenou> ok !
<Fallenou> thanks for testing anyway :)
<Fallenou> I will have a look definitely
<Fallenou> I am just very busy those days
<kristianpaul> I can support the bug if it get better, as i just dont carsh the board !!! and start sending arp broadcast with no reason
<Fallenou> assignments to turn late to school + internship + just found accomodation in London
<kristianpaul> Just tell me where to look i will
<Fallenou> + talk to prepare for milkymist at the Open source hardware user group in london
<kristianpaul> I just dint read all the extensive documenation about BSP porting or networking
<kristianpaul> so i dont know where to start, more that just from scratch
<Fallenou> you can have a look at the network driver since it is where the bug should be
<kristianpaul> wich will be slow on my side..
<kristianpaul> but wich part? wich function?
<Fallenou> the network driver is a very basic one
<Fallenou> it's kind of small
<Fallenou> but if you don't feel like looking at it (I understand) I will no problem :)
<kristianpaul> What you really think is failing there, you wrote the code, you know what could probably was writtena and could generate a bug like this
<Fallenou> yes sure
<kristianpaul> ok i will look
<Fallenou> it's in c/src/lib/libbsp/lm32/shared/milkymist_network/network.c
<kristianpaul> just look.. i will some days
<kristianpaul> yes sure
<Fallenou> or something like that :)
<kristianpaul> i'm aware..
<kristianpaul> c/src/lib/libbsp/lm32/shared/milkymist_networking/network.c
<Fallenou> yes
<kristianpaul> i must work, read you later
<Fallenou> bye
<kristianpaul> grabed a printed copy of the net driver with him
<Fallenou> ohoh :)
<Fallenou> have fun
<Fallenou> lekernel: it seems milkymist wiki is down
<lekernel> dreamhost db problem it seems
<Fallenou> ok it's back now
<Fallenou> thanks :)
<Fallenou> kristianpaul: about your change in the "flickernoise build instructions" wiki page , adding ';' makes my configure and make fail
<Fallenou> I am removing the ';' from the wiki, it works well without them, and fail with them
<Fallenou> lekernel: woow the flickernoise dependency list has grown crazy
<Fallenou> it's now really long to build flickernoise
<Fallenou> you have to get numerous libraries and compile them :o
<lekernel> well, compare that to LFS :)
<Fallenou> hehe
<Fallenou> well it would be great to have some automated compile tool
<Fallenou> a small script or something
<lekernel> or just rpm packages with the pre-compiled libs for lm32
<Fallenou> doing all of this by hand is annoying
<Fallenou> yes
<lekernel> yeah, feel free :)
<Fallenou> 's todo list is close to overflow
<kristianpaul> Fallenou: hmm
<kristianpaul> Fallenou: ahh.. (;)
<kristianpaul> Fallenou: are yoi copying and pasting from wiki?
<kristianpaul> s/yoi/you
<kristianpaul> comma..
<kristianpaul> i tought i worked, sorry
<kristianpaul> Fallenou: letme know if you got mupdf to compile. i still dont :/ and dint check further as the rest went ok
<kristianpaul> Fallenou: annoying indeed :)
<kristianpaul> Fallenou: how it fail?
<kristianpaul> but at theend it uses the lm32-gcc right?
<Fallenou> well removing the ';' just made it work
<Fallenou> don't have too much time to talk now
<Fallenou> am at work
<kristianpaul> me too ;-)
<kristianpaul> Fallenou: do you already removed the ; ?
<kristianpaul> also i just copy and paste and it works..
<kristianpaul> but is okay better remove comma
<kristianpaul> btw i added comma because i was using gcc instead of lm32-rtems4.11-gcc
<kristianpaul> i'll compile flickernoise again anyway, as i seem my las bsp build broke some things..
<kristianpaul> argg, configure: error: C compiler cannot create executables
<kristianpaul> hates /usr/bin/mmqemu.sh
<kristianpaul> realize a problem with backslashes
<kristianpaul> got stuck with freetype :/
<Fallenou> kristianpaul: which shell are you using ? and linux distribution ?
<Fallenou> I am using stock ubuntu 10.10
<Fallenou> in virtualbox
<nats`> < kristianpaul> argg, configure: error: C compiler cannot create executables <= sometimes it's corrected by a apt-get install build-essential :D
<kristianpaul> nats`: ah??
<kristianpaul> Fallenou: debian stable squeeze
<kristianpaul> not virtualbox
<kristianpaul> nats`: i alredy setup my build enviorment, so thats not the case, actually i was solved by removing some backslashes
<Fallenou> kristianpaul: never tried on debian :o
<Fallenou> oh yes i always type everything on the same line
<Fallenou> no backslash
<kristianpaul> Fallenou: did you managed to compile flicernoise?
<Fallenou> not yet
<kristianpaul> I must doing something wrong, las time freetype dint give me troubles..
<kristianpaul> lasT
<Fallenou> I didn't compile freetype yet
<Fallenou> a lot of dependencies :) will finish after the work
<Fallenou> btw OSHUG has just been announced
<kristianpaul> Fallenou: http://paste.debian.net/107726/
<kristianpaul> Are you living in the uk?