<kristianpaul>
hours of not ending experimentation to make something looks cool? :-)
<wpwrak>
look there - it finally becomes clear why the altars of madness are called that ;-)
<wpwrak>
well, all the patches look a bit like that :)
<wpwrak>
but what i meant was that the line had a syntax error
<wpwrak>
(in the original)
<wpwrak>
/nick lurkersbane
wolfspraul [wolfspraul!~wolfsprau@p5B0AAF27.dip.t-dialin.net] has joined #milkymist
xiangfu [xiangfu!~xiangfu@fidelio.qi-hardware.com] has joined #milkymist
mumptai [mumptai!~calle@brmn-4d0acd59.pool.mediaWays.net] has joined #milkymist
kilae [kilae!~chatzilla@catv-161-018.tbwil.ch] has joined #milkymist
xiangfu [xiangfu!~xiangfu@fidelio.qi-hardware.com] has joined #milkymist
r33p [r33p!~rep@bon31-2-89-85-157-97.dsl.sta.abo.bbox.fr] has joined #milkymist
barbu-uucp [barbu-uucp!~lekernel@g225035227.adsl.alicedsl.de] has joined #milkymist
<wpwrak>
hmm, i'm only 35 commits ahead of origin. need to make more changes.
<wpwrak>
barbu-uucp: is it intentional that you feed TOK_ERROR into Parse in fpvm_parse ? (parser_helper.c)
<xiangfu>
wpwrak, Hi I can help on flicekrnoise 's commits.
<wpwrak>
sebastien: okay if xiangfu commits ?
<wpwrak>
xiangfu: also milkymist.git ? the beginning of the patch series is there. then things move over to flickernoise.git
<xiangfu>
wpwrak, no commit right in milkymist.git, only flickernoise.git.
<wpwrak>
ah, then we have to wait
<xiangfu>
wpwrak, better Sebastien review a little on soc and milkymist.git code. I have no idea about soc.
<xiangfu>
wpwrak, one little thing. the code that fix my rapoo 1800 also fix the full-speed mouse. just FYI. in case you have some clues :)
<wpwrak>
yeah, i know what to do with your devices. need to write a report parser. that way, the USB stack can understand the message format better.
<wpwrak>
i'll do that after i'm done with the first batch of compiler changes. it's already looking pretty decent, so hope that won't be long now. maybe 1-2 days.
<xiangfu>
wpwrak, (report parser) what can I do on this.
<xiangfu>
if it not that complicate like 'compiler changes' maybe I can just finish it. :D
<xiangfu>
wpwrak, it maybe also help on full-speed right?
<wpwrak>
if you understand how the report descriptors defined in the HID specification work, you could write that parser, yes. they're a little tricky, though.
<wpwrak>
(full-speed) doesn't matter. both full- and low-speed use the same protocol
<xiangfu>
wpwrak, ok. I will try first.
<wpwrak>
i think we have a low-speed speed regression that causes some devices that used to work with the old firmware to have timing issues with the current version. not sure yet where the problem is. alas, none of my devices exhibit that issue. so i think i'll go mouse shopping next week. see if i can find anything that doesn't work.
wolfspra1l [wolfspra1l!~wolfsprau@p5B0AEFC6.dip.t-dialin.net] has joined #milkymist
<xiangfu>
wpwrak, my stuff works fine , no errors so far.
<wpwrak>
yeah, the bugs only happen to those who can't fix them :)
<barbu-uucp>
wpwrak: i'll have a look at your patches tomorrow. thanks for them! I'm focusing a bit on Migen atm
<wpwrak>
ok, thanks !
<barbu-uucp>
TOK_ERROR... I don't remember. this is february 2009 code :p
<barbu-uucp>
xiangfu: maybe you can fix the FTP bugs? shouldn't be a very difficult task...
<wpwrak>
okay. i'll move it and see what happens :)
<barbu-uucp>
but I don't think it should make a difference... we're destroying the parser immediately after seeing this token
<xiangfu>
barbu-uucp, will try to fix the FTP bugs next few days.
<wpwrak>
yeha. it just tries to force a parser error in addition to the scanner error
<wpwrak>
my regression tests like the change :)
elldekaa [elldekaa!~hyviquel@83.159.32.56] has joined #milkymist
<xiangfu>
the ftp bug relate to recently change on stack size. trying now.
<wolfspra1l>
wpwrak: any news regarding the rc4 package to you?
<wolfspra1l>
I just emailed you a more detailed invoice in case that helps you
<wpwrak>
wolfspra1l: (package) thu and fri were holidays. so tomorrow is the first day i can go to customs and try to get it
<wolfspra1l>
ok maybe the invoice I sent you helps
<wpwrak>
polling ...
<wolfspra1l>
sorry about this, it's definitely a mistake on my end to not put a real invoice in in the first place. I got complacent with so many packages without problems...
<wolfspra1l>
good reminder to never let down
<wolfspra1l>
really sorry to waste your time
<wolfspra1l>
I hate those trips to customs offices as well, must have done a lot in my life in Germany, and that cannot possibly be as bad as in Argentina, though the time-waste aspect is similar I guess.
<wolfspra1l>
feels like in a time machine
<wolfspra1l>
like going to an economic museum or so, the way they are equipped and think
<wpwrak>
(time machine) yeah. the one for regular mail also gives you a nice taste of how it must be / have been in communist countries
<wpwrak>
the good thing there is that they're generally set up to let things pass. so it's inconvenient and a waste of time, but low risk
<wolfspra1l>
with the invoice I sent you now it would probably have passed
<wolfspra1l>
too late though
<wolfspra1l>
100% my mistake
<wolfspra1l>
in Munich it's quite funny as the customs museum and customs office are in the same building complex
<wpwrak>
the one at the airport is inconvenient, a waste of time, and high risk. also because it seems that regular people are only supposed to approach them for a small set of transactions (like lugagge). for anything else, you should go through a custom broker. so if they insist on this, it can get arbitrarily messy
<wpwrak>
hmm .. still no mail .. checking the spam folder ...
<wolfspra1l>
so the customs museum explains you how things were in the past, with trains arriving and all sorts of job titles who have long disappeared processing the goods through this and that stage
<wolfspra1l>
and then you can just proceed left down the floor, up a stay, to the right, to the left, and ...
<wolfspra1l>
the remants are still alive :-)
<wolfspra1l>
up the stairs
<wpwrak>
ah. now it arrived.
<wolfspra1l>
beautiful old building though, very nice architecture etc. late 19th century
<wolfspra1l>
only the few guys still wandering the halls and nagging people today are a bit fallen out of the times
<wolfspra1l>
the extension of the museum, so to speak
<wolfspra1l>
they must be looking forward to retirement
<wpwrak>
(invoice) great, thanks !
<wpwrak>
(customs in munich) ;-)))
<wolfspra1l>
it sounds like fedex did hand it over to a broker, not sure which one though
<wolfspra1l>
maybe you can just email/fax that invoice to the broker and all else goes remotely? probably not...
<wpwrak>
i think they just don't have a category for "left in limbo"
<wolfspra1l>
oh fedex happily declares it as "delivered"
<wolfspra1l>
good for statistics I'm sure :-)
<wpwrak>
what normally happens is that the shipment sits at the customs depot and you then have to try to get it out yourself or find a broker. there's a building where they roost just a short walk away
<wpwrak>
"delivered" = documents delivered :)
<wpwrak>
well, you should see how this works with DHL. there, they only bring you a letter. then you have to go to the DHL office and pay them some USD 100 to get the real paperwork.
<wpwrak>
fedex at least have the decency of not adding to your misery
* kristianpaul
had bad experience with DHL in past
<kristianpaul>
They want squeezy your last penny,like adding to taxes value the shipment it self !! (knowing they we're the carrier!!)
<wpwrak>
ah, but that's how such things are often taxed
<kristianpaul>
but not in fedex i remenber
azonenberg [azonenberg!~azonenber@cpe-67-246-33-188.nycap.res.rr.com] has joined #milkymist
<wpwrak>
that's not DHL but your government who puts the tax value on value of goods plus cost of shipping
<wpwrak>
yeah, also here, those calculations vary :)
<kristianpaul>
Thats why i like airmail,
<wpwrak>
airmail and EMS here have the problem that they often don't process customs for you. so you have to go there yourself.
<wpwrak>
fedex usually do that. (unless there's a problem)
<kristianpaul>
the max i have to do about aimail/EMS was pay taxes when a product weight was more than 2KG
<kristianpaul>
s/have/had
<kristianpaul>
but yeah, still that risk tought..
<wpwrak>
oh, anything < 2 kg is free ? that's convenient ;-)
<GitHub157>
[migen/master] bus: Wishbone to CSR bridge - Sebastien Bourdeauducq
<kristianpaul>
hmm, letss see if there is quick way to disable USB suppport in mm bios..
<kristianpaul>
okay fake IRQ_USB and not calling usb_init hope works..
r33p [r33p!~rep@bon31-2-89-85-157-97.dsl.sta.abo.bbox.fr] has joined #milkymist
<kristianpaul>
yeah, m1nor very handy no more hacked batchfiles :) Thanks a lot wpwrak !
<lars_>
barbu-uucp: this is sort of dangerous:
<lars_>
class StatementList:
<lars_>
def __init__(self, l=[]):
<lars_>
self.l = l
<lars_>
x = StatementList()
<lars_>
y = StatementList()
<lars_>
x.l.append(1)
<lars_>
print y.l => [1]
<lars_>
i'm a bit surprised that it hasn't caused any problems for you yet
<lars_>
unless it's what you want, but i somehow doubt it
elldekaa [elldekaa!~hyviquel@83.159.32.56] has joined #milkymist
elldekaa [elldekaa!~hyviquel@83.159.32.56] has joined #milkymist
<barbu-uucp>
lars_: it did create some problems, but they're not in the critical path yet, so I have not looked at them closely. what's the solution? :)
elldekaa [elldekaa!~hyviquel@abo-168-129-68.bdx.modulonet.fr] has joined #milkymist
r33p [r33p!~rep@bon31-2-89-85-157-97.dsl.sta.abo.bbox.fr] has joined #milkymist
<Thihi>
I'm making my first flickernoise patch :P
<wpwrak>
whee ! :)
<Thihi>
SO far I'm just rotating a wave with a per_frame rot=rot+0.1*sin(bass) and zooming it with a zoom=zoom+0.1*sin(mid/treb) :p
<Thihi>
Having fun so far :)
<kristianpaul>
Seems you are under control :-)
<kristianpaul>
s/under/having
<Thihi>
:D
<wpwrak>
if you have a MIDI controller, you may want to throw this into the mix as well. it's a lot more fun if you can interactively tweak your patch
<Thihi>
I don't have one handy atm.
<Thihi>
But I will certainly test a kaossilator or something with this :P
<kristianpaul>
yeah, patches with varibles looks more fun
<kristianpaul>
also when you cant screen enought to make some sound variables to boost ;)
<wolfspra1l>
Thihi: oh wow, good!
<Thihi>
:)
elldekaa [elldekaa!~hyviquel@abo-168-129-68.bdx.modulonet.fr] has joined #milkymist
<wpwrak>
re2c has amazingly awkward way of adding conditions. unlike lex, where you only instrument the rules you care about, it requires you to instrument them all
<kristianpaul>
no suckless at all then?
<wpwrak>
it's also not very documented. well, it shows that these things don't have the age and maturity of lex and yacc yet
<kristianpaul>
i also wonder how suckless-like will they be if reach that maturity :)
<wpwrak>
i haven't had them flat out fail, but when you push them, they show weaknesses
<wpwrak>
;-))
<barbu-uucp>
GNU flex and GNU bison have some weaknesses when you push them too ...
<wpwrak>
true. in different areas, though
<wpwrak>
lemon looks kinda promising. it probably just needs better documentation
<wpwrak>
e.g., it's not clear how to get out when you have an error. what i've done is use lemon's own parse error exit mechanism
<wpwrak>
and, according to google, i'm not the only one with that problem
_whitelogger [_whitelogger!~whitelogg@2a00:ab00:1::4464:5550] has joined #milkymist