<dvdk>
this is very minimalistic. doesn't need binutils, nor lm32-gcc to compile :)
<kyak>
hm, what does it need then to compile? :)
<kyak>
are you trying to make gforth-ec run instead of flickernoise or together with flickernoise?
<dvdk>
kyak: instead of it. just to get a low-level debug console for hacking with (new) SoC components
wpwrak [wpwrak!~werner@94-163-231-201.fibertel.com.ar] has joined #milkymist
<kyak>
dvdk: cool! how do you replace it?
<dvdk>
kyak: currently just booting the gforth-ec image from the bios (press F8 on serial term during bootup, type serialboot, using 'flterm' tool from milkymist.git
<dvdk>
)
* fpgaminer
should get an NES emulator running on Milkymist...
<wolfspraul>
kyak: dvdk both of you here - such an honor!
<wolfspraul>
welcome and good morning from Beijing ;-)
xiangfu [xiangfu!~xiangfu@fidelio.qi-hardware.com] has joined #milkymist
<kyak>
dvdk: i see :)
<kyak>
xiangfu: hi!
<xiangfu>
kyak, Hi.
<xiangfu>
kyak, great to see you here #milkymist :)
<xiangfu>
kyak, Hi. just check the log.
<kyak>
xiangfu: thanks :)
<xiangfu>
kyak, the compile error is because the recently upstream break flickernoise. :(
<xiangfu>
kyak, revert to 'f80b3a3d825110b5d8826f72db3fa47a6d71b66a'
<xiangfu>
git co -b fn f80b3a3d825110b5d8826f72db3fa47a6d71b66a :)
<kyak>
ah, lucky me :)
<xiangfu>
kyak, you can use tftp to replace flickernoise with other images. like the linux
<xiangfu>
kyak, when milkymist boot. press 'ESC', then it will goto bios console.
<xiangfu>
the command 'netboot' will try to load 'boot.bin' from 192.168.0.14
<kristianpaul>
dvdk: no need reset button at least your urjtag really wont work
<kristianpaul>
wow gforth-ec !! tell us more about it
<xiangfu>
all those two patches under milkymist mailing list.
<xiangfu>
the earlier one I have to manually edit a little before apply.
<dvdk`>
oh I hate it. i send via emacs (gnus), maybe that's a bad idea. next time i'll just append the patch as an attachment
<kyak>
xiangfu: thanks! btw, step 6 in README.html should have "milkymist" instead of "milkymist.git"
<dvdk`>
xiangfu: or your mail-reader is just not smart enough to un-encode the mail (quoted-printable or something)
<xiangfu>
dvdk`, try git send-email :)
<dvdk`>
xiangfu: no way :) via smtp. well will have a look.
<xiangfu>
dvdk`, git send-email support smtp.
<wpwrak>
xiangfu: btw, regarding your report patches: you're a bit ahead of me :) the various usb errors you're seeing are "normal". also other devices produce them. so it's hard to tell whether any regression your patches may or may not produce would come from disturbing whatever is wrong in the lower level of usb or whether there's a real bug in them.
<wpwrak>
xiangfu: i also suggested to sebastien to give you commit access to milkymist.git, so that you can send your patches in a topic branch. then it'll be easy to use them in builds, and also to merge them once the stack is a bit more stable.
<xiangfu>
wpwrak, thanks.
<kyak>
xiangfu: hmm, can't find the commit f80b3a3d825110b5d8826f72db3fa47a6d71b66a.. Which repo is it?
<xiangfu>
kyak, the rtems repo.
<GitHub60>
[scripts] xiangfu pushed 1 new commit to master: http://git.io/mTTWtA
<GitHub60>
[scripts/master] update readme with new folder name - Xiangfu Liu
<xiangfu>
kyak, fixed ^ :)
<kyak>
thanks :)
<kyak>
make[7]: *** No rule to make target `/opt/milkymist/rtems/c/src/../../cpukit/score/src/heapiterate.c', needed by `src/libscore_a-heapiterate.o'. Stop.
<kyak>
now it's this error, after i checked out to that commit
<xiangfu>
wpwrak, I will create a branch name softusb-input. then apply those patches to it. is that ok?
<xiangfu>
kyak, just try 'make clean-rtems all'
<wpwrak>
xiangfu: sounds good, yes. or [softusb-]hid
<xiangfu>
wpwrak, hid. small is better. :)
<wpwrak>
hehe :)
<xiangfu>
wpwrak, BTW. I got a mouse that report X/Y size is 12. not 8
<wpwrak>
that will be fun :)
rejon [rejon!~rejon@jp.fabricatorz.com] has joined #milkymist
<wpwrak>
my riitek rf keyboard has no less than 16 bits for the pad. but at least it's a multiple of 8.
<xiangfu>
it's like:
<xiangfu>
Logical Minimum (-2048),
<xiangfu>
Logical Maximum (2047),
<xiangfu>
Report Size (12),
<xiangfu>
Report Count (2),
<kyak>
xiangfu: i'm sorry, which directory? running it in milkymist-scripts says there is no rule to make target
wolfspraul [wolfspraul!~wolfsprau@221.217.225.24] has joined #milkymist
Scopeuk [Scopeuk!~scopeukfr@li187-253.members.linode.com] has joined #milkymist
qi-bot [qi-bot!~qi-bot@turandot.qi-hardware.com] has joined #milkymist
<xiangfu>
totally is 24.
<wpwrak>
lovely :)
<xiangfu>
kyak, under compile-flickernoise
<kyak>
this whole thing is kind of tricky.. some directories in opt, some in milkymist-scripts.. :)
<wpwrak>
the HID designers probably got some extra bonus for making things complicated
<xiangfu>
the factory better follow the boot protocol.
<wpwrak>
i had some hopes for the boot protocol. but if we lose half of a device's functionality with it, then it's not good enough
<xiangfu>
wpwrak, is that last patch works fine with riitek rf keyboard?
<wpwrak>
i didn't try yet
<xiangfu>
dvdk`, oh. just check the email it's 'Content-Transfer-Encoding: quoted-printable'
<dvdk`>
but doesn't git undedrstand that encoding?
<xiangfu>
dvdk`, I don't know so.
<xiangfu>
I don't think so. since I already test it with git am :)
qi-bot [qi-bot!~qi-bot@turandot.qi-hardware.com] has joined #milkymist
Scopeuk [Scopeuk!~scopeukfr@li187-253.members.linode.com] has joined #milkymist
wolfspraul [wolfspraul!~wolfsprau@221.217.225.24] has joined #milkymist
dvdk` [dvdk`!~dvdkhlng@g225032084.adsl.alicedsl.de] has joined #milkymist
xiangfu [xiangfu!~xiangfu@fidelio.qi-hardware.com] has joined #milkymist
wpwrak [wpwrak!~werner@94-163-231-201.fibertel.com.ar] has joined #milkymist
cladamw [cladamw!~Adam@host-222.80-43-115.dynamic.totalbb.net.tw] has joined #milkymist
lekernel_ [lekernel_!~lekernel@g225034118.adsl.alicedsl.de] has joined #milkymist
stekern [stekern!~stefan@nblzone-224-141.nblnetworks.fi] has joined #milkymist
fpgaminer [fpgaminer!181eaf8b@gateway/web/freenode/ip.24.30.175.139] has joined #milkymist
antgreen [antgreen!~user@bas3-toronto06-1177890738.dsl.bell.ca] has joined #milkymist
methril [methril!~methril@188.141.121.132] has joined #milkymist
azonenberg [azonenberg!~azonenber@cpe-67-246-33-188.nycap.res.rr.com] has joined #milkymist
Martoni [Martoni!~chatzilla@ip-167-165.evhr.net] has joined #milkymist
mwalle [mwalle!~mw@services.serverraum.org] has joined #milkymist
guyzmo [guyzmo!~guyzmo@barney.bearstech.com] has joined #milkymist
Fallenou [Fallenou!~sionneau@yozora-irc.net] has joined #milkymist
[florian] [[florian]!~florian@openwrt/developer/florian] has joined #milkymist
kristianpaul [kristianpaul!~kristianp@unaffiliated/kristianpaul] has joined #milkymist
kyak [kyak!~kyak@unaffiliated/kyak] has joined #milkymist
mirko [mirko!~mirko@simulachron-81.in-berlin.de] has joined #milkymist
djbclark [djbclark!~djbclark@fsf/member/djbclark] has joined #milkymist
Gurty [Gurty!~princess@78.250.184.109] has joined #milkymist
sh4rm4 [sh4rm4!~sh4rm@gateway/tor-sasl/sh4rm4] has joined #milkymist
aeris- [aeris-!~aerith@78.246.252.173] has joined #milkymist
whitequark [whitequark!~whitequar@2a00:ab00:1::4464:5550] has joined #milkymist
ximian [ximian!juoni@deviate.fi] has joined #milkymist
larsc [larsc!~lars@eisbaer.ursus-maritimus.org] has joined #milkymist
roh [roh!~roh@yamato.hyte.de] has joined #milkymist
juliusb [juliusb!~ubuntu@ec2-79-125-113-131.eu-west-1.compute.amazonaws.com] has joined #milkymist
bkero [bkero!~bkero2@osuosl/staff/bkero] has joined #milkymist
devn [devn!~devn@rot13.pbqr.org] has joined #milkymist
cxadams [cxadams!~cxadams@li155-180.members.linode.com] has joined #milkymist
radii [radii!foobar@pdpc/supporter/active/radii] has joined #milkymist
togi [togi!~yur@c83-250-142-73.bredband.comhem.se] has joined #milkymist
km2 [km2!~km2@99-7-110-97.lightspeed.lsanca.sbcglobal.net] has joined #milkymist
ChanServ [ChanServ!ChanServ@services.] has joined #milkymist
xiangfu [xiangfu!~xiangfu@fidelio.qi-hardware.com] has joined #milkymist
wpwrak [wpwrak!~werner@94-163-231-201.fibertel.com.ar] has joined #milkymist
Martoni [Martoni!~chatzilla@ip-167-165.evhr.net] has joined #milkymist
mwalle [mwalle!~mw@services.serverraum.org] has joined #milkymist
sh4rm4 [sh4rm4!~sh4rm@gateway/tor-sasl/sh4rm4] has joined #milkymist
roh [roh!~roh@yamato.hyte.de] has joined #milkymist
km2 [km2!~km2@99-7-110-97.lightspeed.lsanca.sbcglobal.net] has joined #milkymist
devn [devn!~devn@rot13.pbqr.org] has joined #milkymist
antgreen [antgreen!~user@bas3-toronto06-1177890738.dsl.bell.ca] has joined #milkymist
azonenberg [azonenberg!~azonenber@cpe-67-246-33-188.nycap.res.rr.com] has joined #milkymist
mirko [mirko!~mirko@simulachron-81.in-berlin.de] has joined #milkymist
ximian [ximian!juoni@deviate.fi] has joined #milkymist
radii [radii!foobar@pdpc/supporter/active/radii] has joined #milkymist
cxadams [cxadams!~cxadams@li155-180.members.linode.com] has joined #milkymist
<wpwrak>
xiangfu: all that matters is "Found MIDI" :-)
<xiangfu>
wpwrak, ok. :)
<wpwrak>
xiangfu: that is, unless you want to debug the lower-layer problem. i suspect it's some timing issue.
<wpwrak>
maybe some weird inter-packet timing requirement. or we're too slow to retrieve data at some point.
<kristianpaul>
where is that built-in logic analizer when needed..
<wpwrak>
yes, indeed :)
<kyak>
xiangfu: the download location for libpng-1.5.6 on SF has changed.. it is project/libpng/libpng15/older-releases/$(LIBPNG_VERSION)/$(LIBPNG)" now (line 259 of compile-flickernoise/Makefile)
<wpwrak>
kristianpaul: right now, you still need a scope with at least 50 MHz bandwidth, deep memory, and support by my USB protocol decoder (that it, unless you happen to have a good USB protocol analyzer, in which case i shall envy you)
<kristianpaul>
dont think so..
<kristianpaul>
and deep memory sounds expensive
<kyak>
/bin/sh: lemon: command not found - the hell is that..
<GitHub43>
[scripts] xiangfu pushed 1 new commit to master: http://git.io/af73Bw
<kyak>
The LEMON LALR Parser Generator used in sqlite 1.69
rejon [rejon!~rejon@jp.fabricatorz.com] has joined #milkymist
<kyak>
it's in AUR.. let's hope this is what i need :)
<kristianpaul>
suck less parser i was told, but seems wpwrak disagree a bit? :)
<wpwrak>
kyak: you'll also need re2c. sebastien tried very hard to avoid the more conventional (f)lex and yacc/bison :)
<wpwrak>
kristianpaul: it's a mixed experience. some things are nice. others not so.
<kyak>
wpwrak: i also need avr-gcc, apparently :)
<wpwrak>
kristianpaul: (deep memory) not terribly so. the rigol ds1000c/cd/d/e series devices all are suitable. (not the 1000b, though)
<wpwrak>
yes, you do :)
<kyak>
ok, it's done
<kyak>
i had to install libftd2xx, urjtag, llvm, clang, avr-gcc, lemon and re2c overall :)
<kyak>
now, is that .fbi file is the one i should tftp to mm?
<xiangfu>
kyak, no. .fbi is for flash
<xiangfu>
the /flickernoise.bin is for tftp
<xiangfu>
run 'make load' under flikernoise/src
<xiangfu>
it will compile .bin file and copy it to /var/lib/tftpboot/boot.bin
<kyak>
oh.. ok.. i have to switch back and forth between /opt/milkymist and milkymist-scripts
<xiangfu>
kyak, in fact make -C compile-flickernoise is only needs once. other time you will always play with milkymist, rtems and flickernoise :)
<kyak>
why did i need to build that flickernoise.fbi?
<kristianpaul>
to use with urjtag
<wpwrak>
kyak: you can also flash it into NOR and then boot from there. slightly slower but you can be sure the code doesn't wander off when you reboot
<kristianpaul>
and flash it
<kristianpaul>
to the NOR harcoded partition for flickernoise
<wpwrak>
maybe not perfectly up to date but close to what i use
<kyak>
still i find it confusing that some files are under milkymist-scripts/compile-flickernoise and some are in /opt/milkymist/flickernoise
<kristianpaul>
milkymist-scripts/compile-flickernoise should be just temporary or sources archives no more i guess? xiangfu ?
<wpwrak>
do you even needs these ?
<xiangfu>
kristianpaul, kyak it's like. after you get the .fbi file. that mean all toolchain and libs are installed in your system. then you have to jump to /opt/milkymist stuff to hack.
<kristianpaul>
but yes now wiki is some behind milkymist.org i guess is time to have a better organized and good looking place? just move
<kyak>
xiangfu: do you mean that once i ran "make -C compile-flickernoise flickernoise.fbi" i can remove the milkymist-scripts/compile-flickernoise and continue in /opt/milkymist/flickernoise?
<kyak>
ok-ok\
<kristianpaul>
doxygen ! (kidding :)
<kyak>
xiangfu: for example, libpng. This is a part of flickernoise, right? Where did it go?
<kyak>
there are no traces of libpng under /opt/milkymist/flickernoise
<kristianpaul>
go to rtems in /opt/rtems*
<kristianpaul>
i remenber..
<xiangfu>
kyak, yes. part of flickernoise. /opt/rtems-4.11/lm32-rtems4.11/milkymist/lib/libpng.a
<kristianpaul>
no no part of FN, rtems have the lib but seems this one is better updated?
<kristianpaul>
i dont remenber whole reason
<kristianpaul>
or just lack it
<wpwrak>
kyak: i would recommend building things directly in the repositories, without trying to do a "world" build
<xiangfu>
kyak, flickernoise is a big APP. that links all those libs and rtems to only one.
<kristianpaul>
BIG app :)
<wpwrak>
kyak: when developing, you'll want selective builds anyway
<kyak>
so does that .bin file contain both RTEMS and flickernoise?
<xiangfu>
kyak, yes.
<kyak>
ok, i got it
<xiangfu>
rtems is not like Linux kernel. it more like libs.
<xiangfu>
link to target.
<kyak>
wpwrak: i understand what you recommend.. i just decided that it is easier to jump in with xiangfu's Makefiles
<kristianpaul>
newlib latelly no?
<kyak>
so it's like a single application linked with a bunch of libs, right?
<kristianpaul>
flickernoise yes
<kyak>
interesting..
<kristianpaul>
yeah !
<kristianpaul>
you could get for example things like lua pretty easy running
<kyak>
i'd like to have busybox running on RTEMS :)
<kristianpaul>
because you already got the board support package from rtems
<kyak>
does it mean that i will have ONLY lua running?
<kristianpaul>
kyak: busybox is ansi c and no mmu, so i guess so you can build in against rtems not ulibc
<kristianpaul>
kyak: yes
<kristianpaul>
jsut straight a lua itnerpreter :)
<kristianpaul>
s/s/to a
<kyak>
yeah, this is all definitely different from Linux..
<kristianpaul>
simpler (at least for me not used to hack linux)
<kyak>
but it's a good opportunity for real-time applications
<kristianpaul>
:-D
<kyak>
ok, time to wake up and go to work.. Wonder when i'm gonna stop jet lagging
rejon_ [rejon_!~rejon@jp.fabricatorz.com] has joined #milkymist
<GitHub71>
[milkymist/hid] pass ep_status to ep process - Xiangfu Liu
<GitHub71>
[milkymist/hid] softusb-input: add GET_HID_REPORT_DESCRIPTOR support - Xiangfu Liu
<GitHub71>
[milkymist/hid] cleanup code style, remove space after if - Xiangfu Liu
<xiangfu>
:D
<wpwrak>
yeah, we already have regressions between july and now. with too many changes on top of the shaky foundation, i'd worry about the thing getting out of control.
<wpwrak>
nice, branch creation worked ! :)
<xiangfu>
(i'd worry about the thing getting out of control.) agree
<xiangfu>
wpwrak, I tried midi2osc yesterday. when I plug-in the LV3 to my laptop. then start ./midi2osc -d 192.168.0.42. then nothing output.
<xiangfu>
nothing output when I press any button on LV3.
<xiangfu>
the code stop at 'while (snd_seq_event_input(midi, &ev)) {' ?
<xiangfu>
I want find out the channel and control on those devices.
<wpwrak>
did you connect it with qjackctl ?
<wpwrak>
(connect it) the LV3 to midi2osc
<wpwrak>
or, if you connect multiple devices, all of them to midi2os
<wpwrak>
and to remap the LV3 controls to things FN can handle, you can use ./midi2osc `sed 's/#.*//' LV3` 192.168.0.42
<wpwrak>
... or use the direct-midi branch :)
<xiangfu>
wpwrak, ah. I have to connect them together. then it will output the values
<xiangfu>
if there a way that no needs qjackctl? just output those channel and control values messages?
<wpwrak>
there probably is ... if you find it, please post how it's done :)
<xiangfu>
connect them means send the LV3 output to midi2osc. midi2osc is not direct open the midi device.
<wpwrak>
in any case, once direct-midi is merged, you'll need midi2osc only if you have more MIDI devices than USB ports. FN won't need remapping anymore.
<cladamw>
wpwrak, if you are available, could you review my dvi email? but take your time. thanks !
<xiangfu>
wpwrak, I want make sure the channel and controls. the encoder change values real small.
<wpwrak>
(remapping) that is ... it still might. e.g., if two devices use the same addresses.
Fallenou_ [Fallenou_!~sionneau@yozora-irc.net] has joined #milkymist
aeris- [aeris-!~aerith@home.aerith.fr] has joined #milkymist
azonenberg [azonenberg!~azonenber@cpe-67-246-33-188.nycap.res.rr.com] has joined #milkymist
mumptai [mumptai!~calle@brmn-4db70443.pool.mediaWays.net] has joined #milkymist
rejon [rejon!~rejon@jp.fabricatorz.com] has joined #milkymist
rejon [rejon!~rejon@jp.fabricatorz.com] has joined #milkymist
cladamwa [cladamwa!~Adam@host-222.80-43-115.dynamic.totalbb.net.tw] has joined #milkymist
<wpwrak>
cladamwa: glad that i could contribute something ;-)
<cladamwa>
wpwrak, u re modest. as usual though. :-)
<cladamwa>
wpwrak, i'm checking joerg's great feedback on audio. any idea from you too ?
elldekaa [elldekaa!~hyviquel@adm02.insa-rennes.fr] has joined #milkymist
<cladamwa>
wpwrak, for all unused inputs, from your last email, i added couple TPs for keeping the DC block footprints
<cladamwa>
(C4 through C8), so that one could solder something external
<cladamwa>
(just in case). from Joerg's idea on two pins with jumper, it's also not bad but occupying pcb space.
<wpwrak>
(audio pins) i was just waiting for that audio ground to return ;-)
<wpwrak>
well, it's just one more pin, so ...
<cladamwa>
mm? Joerg's idea on J23 i think it's pretty good like you want.
<cladamwa>
(J1) i think too.
<cladamwa>
(100R) C19*R17 <-100R-> J2:2,3 and C21*R18 <-100R-> J2:4,5; this i don't understand .
<wpwrak>
(j23) yes. i'm only surprised he didn't suggest it earlier. when we discussed it, i was gently prodding in this direction, but he seemed happy with just the floating ground.
<lekernel__>
wpwrak: what are the remaining regressions?
<lekernel>
let's push out webupdate images soon
<wpwrak>
lekernel: some devices that worked in july not working now, for some unknown reason.
<lekernel>
ok, just USB stuff?
<wpwrak>
lekernel: my plan is to set up a proper record for my mouse collection and then go after those timeouts
<wpwrak>
yes, just USB
<wpwrak>
(mouse collection) i have something like ten different mice now. so that should be a useful base for regression checking. needs careful record-keeping, though, or it'll end up in a big ghost chase
<wpwrak>
(ghost chase) trying to debug imagined regressions, and also overlooking real issues. i'd also imagine that not all problems happen all of the time.
<wpwrak>
cladamwa: he wants to insert 100 Ohm series resistors, in case something nasty is connected
<cladamwa>
lekernel, wpwrak, so 100 Ohm series are okay to you?
<wpwrak>
what's typical line impedance again ? 1 kOhm ? 10 kOhm ?
<lekernel>
phew, imo this whole audio improvement thing is overkill. I'm out of it :)
<cladamwa>
lekernel, overkill ? ;-)
<lekernel>
yes, overdoing things, fixing something that works, etc.
fpgaminer [fpgaminer!181eaf8b@gateway/web/freenode/ip.24.30.175.139] has joined #milkymist
<wpwrak>
i guess as long as all you use is treb, mid, and bass level, then it's indeed overkill ;-)
<cladamwa>
wpwrak, each of LINEOUT has 10 KOhm to AUDIO_AGND. did you try to say this ?
<lekernel>
wpwrak: by the way, we already have a 47 ohm resistor in series with the DCC 5V
<lekernel>
DDC
<lekernel>
if you want to make that thing more resistant, just use a resistor that can dissipate ~500mW permanently... the diode won't protect against short circuits
<wpwrak>
cladamwa: hmm yes, that fits. okay, so adding 100 Ohm just increases overall impedance by 1%. negligible.
<wpwrak>
lekernel: heh, or pick a diode with a large Vf @ 100 mA ;-)
<wpwrak>
but yes, it should be short-circuit proof
<wpwrak>
no clamp diodes in the FPGA ? wow
<wpwrak>
there a "Maximum current through pin using PCI I/O standard when forward biasing the clamp diode.", so that's something else ?
<wpwrak>
(in DS162)
wolfspraul [wolfspraul!~wolfsprau@222.130.118.13] has joined #milkymist
<lekernel>
and the clamp diodes aren't there by default (eg you can apply voltage to the I/Os with VCCIO turned off, and no current will flow)
<lekernel>
we can also use a voltage divider, which solves pull-down and level conversion at the same time... but after we've had so many solder and misplaced component issues, I'm not sure if it's safe
<wpwrak>
(clamps) thanks ! one more thing learned about those tricky fpgas ...
<wpwrak>
how would a voltage divider be less safe than, say, a FET ?
<wpwrak>
i'm sure you can have some hellish smt mishaps with a fet as well :)
<lekernel>
if the bottom resistor isn't there or has the wrong value, the FPGA can get too much voltage
<lekernel>
if the FET isn't there, the FPGA simply doesn't get any signal
<wpwrak>
hmm okay, absence / no connectivity is more likely than other sorts of problems, agreed
<cladamwa>
(J1) wpwrak, have you seen joerg's idea? is okay to you? "rationale: connect unused input to GND -> less noise"
rejon [rejon!~rejon@jp.fabricatorz.com] has joined #milkymist
<cladamwa>
wpwrak, lekernel do you mean that we could use 2N7002 like Q1 to be as level shifter(5V -> 3.3V) ?
<lekernel>
yes
<cladamwa>
lekernel, got it. ;-)
<wpwrak>
(J1) sounds good to me, yes. of course, if you want to detect plug insertion, things may change again. not sure how to do proper plug detection, though.
<wpwrak>
(plug detection) in my LED function description, i carefully avoided mentioning plug detection for almost anything ;-)
<cladamwa>
wpwrak, he. i noticed you were gently avoid. but it's okay. we do this later for overview. ;-)
<cladamwa>
(J1 plug detection) I'd have some phone schematic from China, i'll see how they do such feature. ;-)
<fpgaminer>
Hmmm, trying to compile milkymist gives me a compilation error "unknown field 'fpathconf_h' specified in initializer" when it tries to compile rtems_yaffs.c
<cladamwa>
i didn't change those DC block capacitor's TPs which joerg suggested that we can use 2 pin jumper. since i hope there's enough space to do such but ... ;-)
rejon [rejon!~rejon@jp.fabricatorz.com] has joined #milkymist
<wpwrak>
ah, nice. rtems has a live repository again
<GitHub178>
[milkymist-ng/master] tools: use install and /usr/local (as suggested by David Kuehling) - Sebastien Bourdeauducq
lekernel [lekernel!~lekernel@g225034118.adsl.alicedsl.de] has joined #milkymist
antgreen [antgreen!~user@bas3-toronto06-1177890295.dsl.bell.ca] has joined #milkymist
wolfspraul [wolfspraul!~wolfsprau@222.130.118.13] has joined #milkymist
<wpwrak>
lekernel: when communicating with the user, MIDI channels are commonly one-based. in FN, they're 0-based. what would you think of changing that ?
<lekernel>
ha
<lekernel>
yes, then change it
<lekernel>
hmm, there seems to be some C++ working with clang/lm32 too :) (not that I like C++, but it's nice to see that with LLVM it seems other languages can be made to work without much fuss...)
<lekernel>
lol, why the hell are the new/delete operators internally named "_Znwm/_ZdlPv" in C++? couldn't they think of even less meaningful names?
<wpwrak>
they should have avoided the common _Z prefix. makes it too easy to remember.
<lekernel>
objective-c appears functional, too
<lekernel>
I don't know it much but at least they do not have insane name mangling there :)
wolfspraul [wolfspraul!~wolfsprau@222.130.118.13] has joined #milkymist
wolfspra1l [wolfspra1l!~wolfsprau@222.130.118.13] has joined #milkymist
azonenberg [azonenberg!~azonenber@cpe-67-246-33-188.nycap.res.rr.com] has joined #milkymist