lekernel changed the topic of #m-labs to: Mixxeo, Migen, MiSoC & other M-Labs projects :: fka #milkymist :: Logs http://irclog.whitequark.org/m-labs
_whitelogger has joined #m-labs
ohama has joined #m-labs
proppy has joined #m-labs
proppy has joined #m-labs
proppy has quit [Changing host]
proppy has quit [Ping timeout: 240 seconds]
proppy has joined #m-labs
siruf has quit [Remote host closed the connection]
siruf has joined #m-labs
_whitelogger has quit [Ping timeout: 246 seconds]
_whitelogger_ has joined #m-labs
_whitelogger has quit [Ping timeout: 246 seconds]
siruf_ has joined #m-labs
siruf has quit [Write error: Connection reset by peer]
siruf_ is now known as siruf
siruf has quit [Remote host closed the connection]
siruf has joined #m-labs
xiangfu has joined #m-labs
xiangfu has quit [Ping timeout: 265 seconds]
xiangfu has joined #m-labs
xiangfu has quit [Remote host closed the connection]
nicksydney_ has joined #m-labs
nicksydney has quit [Ping timeout: 255 seconds]
proppy has quit [Ping timeout: 264 seconds]
nicksydney has joined #m-labs
nicksydney_ has quit [Ping timeout: 255 seconds]
Alain has joined #m-labs
mumptai has joined #m-labs
<wpwrak>
Alain: (taking it here) yann seems to know more about it than i do :-) i don't know what the RTEMS-side problem is or what it would take to solve it
<wpwrak>
Alain: also, USB on milkymist doesn't work in all circumstances, even if the stack per se is fine. e.g., it doesn't work at all with hubs. if any hubs are involved, including hubs built into the device you're connecting, you'd have to remove them first or use a different device
proppy has joined #m-labs
bvernoux has joined #m-labs
<Alain>
wpwrak: I can confirm you that my mouse works with a compiled binary functional. Unfortunately Yann suppose that there are bugs in the latest Releases of RTEMS. The problem is that not the SHA-1 release RTEMS fonctionnelet we know he did not have time in the coming weeks to correct the problems.
<Alain>
wpwrak: I can confirm you that my mouse works with a compiled binary functional. Unfortunately Yann suppose that there are bugs in the latest Releases of RTEMS. The problem is that we not know the SHA-1 release RTEMS functional and does not have time in the coming weeks to correct the problems.
bvernoux has quit [Quit: Leaving]
<wpwrak>
i don't even have an M1 set up to run, so all i can do is give you ideas for where to look ...
<wpwrak>
but it's good that your mouse works in an old configuration. that way, you can compare the effect of changes.
<wpwrak>
that usually helps a lot with debugging
<Alain>
wpwrak: I want to try to debbuger but it would help me ....
<Alain>
wpwrak: ?
<wpwrak>
hmm ?
<wpwrak>
you want ideas for where to look ? well, the first point would be the driver in rtems that gets data from usb. i think you could add a printf there to see what happens, then watch on the console if there is any activity
<wpwrak>
ideally, you'd first set up an old development system with the code that is known to work, add the printf there, to make sure a) what you're doing works, and b) see the expected output
<wpwrak>
then apply the same to the "modern" environment and look at the results
<wpwrak>
if you get no response at all, change the navre firmware to generate some fake events. see if at least those get through.
<Alain>
I do not have the source code of the binary that works so I can not compare. I did just that bit flickernoise.fbi I had taken it a year ago on the site;
<wpwrak>
you'll have to go back in the repositories. not sure if they've been restructured since, but chances are that not much has changed
<wpwrak>
so the bulk of the changes would be on the rtems side. you'll have to backtrack that. sb0_ may remember whether he made any major changes in repos you'll need on the flickernoise side
<Alain>
wpwrak: Do you know the SHA-1 rtems was functional?