freenode/#mezzano - IRC Chatlog
Search
14:30:17
froggey
generate-mouse-buf-code should use (compile nil `(lambda ...)) instead of (eval `(function (lambda ...))). eval is a bit overkill if you just want to compile a function and might give you a interpreted function instead of a compiled function
14:31:11
froggey
it'd be nice if the asdf system name was in some kind of mezzano-related namespace, just "usb" is a bit generic. asdf might complain though, it seems very particular about how systems are named
14:31:19
froggey
adjust-array could be extended to support doing what buffers::search-free-list is doing (changing the size & element type of a memory array). not very important, just a small improvement to how memory arrays work
16:41:04
fittestbits__
OK, I'll make the eval->compile change and type-of -> array-element changes, I'll save them up for a single PR comments commit.
19:12:11
froggey
fittestbits__: I'm getting a crash during probe (big crash, vbox gives up with a guru meditation error)
19:13:09
froggey
I think it's because you're doing 16-bit accesses to the registers with pci-io-region/16, the spec says accesses must be done with 32-bit accesses
19:14:57
froggey
specifically the crash occurs when +command-controller-reset+ is written to +ohci-command-status+, exactly on the write instruction & with a vbox error that looks like it doesn't know how to handle the access
19:53:58
froggey
though I got an error the first time I tried: https://gist.github.com/froggey/b083976cf5c2bc43f5539d596bcfea77
19:54:56
fittestbits__
Wow - OK I'll look at the /16 thing. I use it in a number of places. I'll take a look at the OHCI spec as well.
20:05:39
fittestbits__
I don't know why there are /16 references, all of the registers are 32-bit registers. Who wrote that code??
20:14:12
froggey
it doesn't seem to detect devices that're already connected on boot. I have to disconnect/reconnect to trigger a rescan, then everything gets picked up
20:15:58
fittestbits__
Are you configuring VBox so that it always picks up the USB mouse? Rather than having to go through the menus after boot?
20:19:48
fittestbits__
I'm looking at your gist now ... not sure what went wrong. I'd like to understand what went wrong, not just put in a check for NIL.
20:22:05
froggey
I haven't been able to reproduce it and I didn't see any more information in the log
20:23:49
froggey
it might have happened because I added the device partway through boot, maybe the controller was only half-configured at the time
20:23:58
froggey
but don't read too much into that, I might have actually clicked the button after the system had finished booting. I'm not really sure
20:31:43
fittestbits__
Oh, I wonder if I'm missing a with-hcd-access somewhere ... or a race condition in tear down.
20:46:10
fittestbits__
froggey: What did you have in mind for a better name for the system: drivers-usb? lispos-usb? The file name and system name should match for asdf searching to work ...
20:52:18
froggey
I didn't think that far ahead. I guess mezzano-usb? to indicate that it's mezzano-specific
20:56:55
froggey
I can reproduce various errors by attaching a device late during boot, after DHCP lease acquisition or shortly after the old controller is deleted
20:57:57
froggey
https://gist.github.com/froggey/b083976cf5c2bc43f5539d596bcfea77#file-gistfile2-txt
21:06:10
fittestbits__
Thanks for the log. I took a quick look at finding devices on boot. I think it's going to take a while to work through supporting that.