Dwayne Fontenot

Show:

What's happening?

  • md5 broken on big-endian

    md5.c makes no provision for big-endian archs. does not return the correct hash.

    2008-05-27 23:01:54 UTC in RHash

  • Followup: RE: how to merge Z-10 support?

    Of the keys not handled by usbhid, the Z-10 has four right under the display simply labeled "1", "2", "3", and "4" and a key labeled "display" "1", "2", "3", and "display" appear to be working fine with (for example) the g15daemon clock plugin. For all I know "4" is already working but not c.

    2007-02-18 08:54:38 UTC in G15Daemon

  • Followup: RE: how to merge Z-10 support?

    It looks good! g15daemon / libg15 now work "out of the box' with my Z-10 speakers. Thanks! jacques.

    2007-02-16 09:20:48 UTC in G15Daemon

  • Followup: RE: how to merge Z-10 support?

    Mike, Thanks for committing the new code. Here are my notes from last night's testing. It's very close now. I'll outline the changes I had to make for it to work. I can provide '-d' output from g15daemon if you need it. shared_device is not being set for Z-10 if I hard-wire it on, it works as intended - no interface 0 errors don't try to set configuration (there's only one anyway):

    2007-02-15 17:56:26 UTC in G15Daemon

  • Followup: RE: how to merge Z-10 support?

    uh, thanks sourcescourge for stripping all the leading spaces. I cannot imagine why somebody thought that was a good idea. jacques.

    2007-02-14 23:36:35 UTC in G15Daemon

  • Followup: RE: how to merge Z-10 support?

    Sorry I didn't get to do much last night. Tonight I should have more time. Meanwhile, I am attaching the 'lsusb -v' output for the Z-10 speakers here. Also, I tried commenting out all the "control endpoint" calls in g15daemon (all the LCD brightness setting, etc.) and that fixed the "did not claim interface 0 before use" errors. For all I know the LCD brightness isn.

    2007-02-14 23:33:59 UTC in G15Daemon

  • Followup: RE: how to merge Z-10 support?

    I'll post a patch tonight when I get home (code is there). One issue I haven't solved is that apparently snd_usb_audio (or whatever the alsa driver is called) and g15daemon both want to access interface 0 (for the control endpoint?). I assume this is for volume control in alsa and display brightness/contrast/etc in g15daemon. Currently g15daemon/libg15 want to detach the alsa driver fr.

    2007-02-13 22:32:59 UTC in G15Daemon

  • how to merge Z-10 support?

    Hi, I have hacked libg15 and g15daemon to (somewhat) support the Z-10 speakers display. This was not pretty as currently libg15 assumes interface and endpoint numbers are the same for all devices. I would like to discuss the best way to get Z-10 support into libg15 and g15daemon. Thanks, jacques.

    2007-02-13 18:09:56 UTC in G15Daemon

  • [bug] page crossing inside insn (like qemu)

    softgun shares a bug with qemu which causes gcc to segfault when compiling certain files with certain options. For explanation and discussion see the thread: http://lists.gnu.org/archive/html/qemu-devel/2005-12/msg00204.html culminating in the experimental patch: http://lists.gnu.org/archive/html/qemu-devel/2005-12/msg00215.html which fixed the segfaults for me on qemu. I...

    2005-12-23 21:56:02 UTC in softgun

  • [bug] softgun does not work with hard-float

    I am unable to boot debian-arm since debian, being debian, is still using hard-float. I think it should be relatively straight-forward to fix this bug - maybe the emulated CPU isn't raising/handling the FP exception properly (I have NWFPE built into the kernel but I still get an illegal instruction error on sfm). Thanks, Dwayne.

    2005-12-11 00:17:27 UTC in softgun

About Me

  • 2001-02-08 (9 years ago)
  • 149777
  • djf (My Site)
  • Dwayne Fontenot

Send me a message