#asahi-dev · 2023-09-21 02:49
kevans91slightly slanted USB gives me something to be paranoid about in my own assembly... should have the rest of the parts any day now#asahi-dev · 2023-09-21 02:47
kevans91I think jannau's CS case is actually the first image I've seen of an assembled board#asahi-dev · 2023-09-17 04:54
kevans91i think it'll be fine, just need to get used to this again... it's been a couple years#asahi-dev · 2023-09-17 04:35
kevans91yup, this is going to be fun... my hands are nowhere near steady enough to work with the stencil I ordered, starting to think I should've grabbed one of the kapton stencils oshstencil sells instead#asahi-dev · 2023-09-15 00:41
kevans91ponders using stackable headers for the middle board in a stacked setup#asahi-dev · 2023-09-14 01:45
kevans91or rather, I'm pretty sure that's what digikey claimed#asahi-dev · 2023-09-14 01:44
kevans91maz: what's the downside of FUSB302 vs. FUSB302B? I saw that the latter is the former's successor in general, curious if there's much functional different as far as how it's used here#asahi-dev · 2023-09-08 16:59
kevans91I hadn't ordered a stencil for that batch, but I'm not averse to ordering one to throw in and sweeten the pot a bit#asahi-dev · 2023-09-08 16:41
kevans91maz: oh yeah, sorry, didnt mean to give that impression; I'll store them somewhere safe just in case a need arises, I just won't keep broadcasting it here. that works for me, thanks#asahi-dev · 2023-09-08 15:14
kevans91noting at a different time of this day, and probably the last time: I have three of the v3.1 central scrutinizer PCBs unpopulated showing up what looks like tomorrow from OSHPark if anyone's interested in them (for just the cost of shipping to you)#asahi-dev · 2023-08-30 08:22
kevans91I ordered them then realized that the 3.2 BOM is easier for me to source, but the pcb layout is just different enough that it's mot worth my time to figure out if I can pull some hackery to make it work... but OSHPark helpfully expedited my order since they had some extra space#asahi-dev · 2023-08-30 08:15
kevans91on a totally unrelated note, if anyone wants some unpopulated cs v3.1 PCBs for the cost of shipping from the center of the US, I'll havw 3 from OSHPark in a couple weeks#asahi-dev · 2023-08-30 08:14
kevans91maz: perfect, thanks!#asahi-dev · 2023-08-30 04:52
kevans91maz: hey, is the cs v3.2 hardware reasonably functional in its current state?#asahi-dev · 2023-02-25 16:16
kevans91a little bit of fpen bit flipping and we're there#asahi-dev · 2023-02-25 16:16
kevans91kettenis: yeah, it turns out that I was just being dumb... andrew@f.o pointed out that we can't clear hcr_el2.e2h like we're expecting so we were setting up cptr_el2 incorrectly#asahi-dev · 2023-02-25 03:55
kevans91woot, finally figured out where I was being dumb (re: simd registers), just need to work out an issue with USB interrupts w/ more than one cpu enabled then we'll have a very basic usable machine#asahi-dev · 2023-02-24 04:07
kevans91I don't really see anything we do differently than, say, OpenBSD, in response to EXCP_FP_SIMD #asahi-dev · 2023-02-24 03:53
kevans91hardware, even#asahi-dev · 2023-02-24 03:53
kevans91this may be a stupid question, but is there some hardwar prereq for enabling the FPU (M1) that I might be missing? We take our very first floating point exception from el0, setup cpacr_el1, instruction barrier; the subsequent ldp to q0/q1 causes an apparent hang (no exception AFAICT)#asahi-dev · 2022-10-27 23:08
kevans91I guess it's our earlier write to q0 that's hanging, not fpsr/fpcr. afaik we set up cpacr_el1 correctly to disable traps, not sure what else I'm missing#asahi-dev · 2022-10-27 22:44
kevans91it's an apparent stall, quite annoyingly when we first fire up init(8)#asahi-dev · 2022-10-27 22:43
kevans91rmk: nothing obvious, no#asahi-dev · 2022-10-27 21:49
kevans91cpu just kinda falls off a cliff, and I get a different failure mode when run under the hypervisor so it's a bit difficult to debug#asahi-dev · 2022-10-27 21:48
kevans91i'm curious how you arrived there, i'm seeing an issue of sorts when we attempt to restore vfp state and write to fpsr/fpcr in freebsd#asahi-dev · 2022-10-27 21:47
kevans91kettenis: hey, is there anywhere I can find additional context on your fpu rewrite? (https://github.com/openbsd/src/commit/b83a19dd9c2195f11121de7fba7a36fcd6a004f2)#asahi-dev · 2022-10-26 14:34
kevans91u#asahi-dev · 2022-10-08 05:03
kevans91ah, shoot- m1n1's gdbserver is linux-specific at the moment#asahi-dev · 2022-09-30 03:07
kevans91it turns out I had a stale config that was disabling the xhci driver for dwc3, I was inspecting the wrong device entirely#asahi-dev · 2022-09-30 03:02
kevans91woot! da0: <Kingston DataTraveler 70 PMAP> Removable Direct Access SPC-4 SCSI device#asahi-dev · 2022-09-29 21:08
kevans91alright, many thanks- this is progress, I'll harass our usb maintainer a little bit and do some hunting this weekend for possible ordering candidates#asahi-dev · 2022-09-29 21:04
kevans91beyond that, though, still borked#asahi-dev · 2022-09-29 21:04
kevans91yeah, I did find that interrupts were broken just a minute ago (I hacked in multi-die support and forgot to change an 'i' to a 'j', so every irqsrc was... interrupt 0)#asahi-dev · 2022-09-29 20:49
kevans91broken interrupts, I guess#asahi-dev · 2022-09-29 20:47
kevans91which ports did these cover? this is a mini, USB-C ports on the back?#asahi-dev · 2022-09-29 20:47
kevans91apparently we get as far as seeing two hubs, each with two ports, then times out getting a device descriptor#asahi-dev · 2022-09-29 20:36
kevans91it seems likely we're just AFU somewhere earlier#asahi-dev · 2022-09-29 20:35
kevans91just ignoring AC64 in our xhci driver and using 64-bit DMA anyways didn't seem to be the answer, but perhaps I should try that again and see what the symptom is#asahi-dev · 2022-09-29 20:31
kevans91yeah, taht's going to get a bit complicated#asahi-dev · 2022-09-29 20:25
kevans91even if our DART driver's somehow screwing up, pretty sure the version of u-boot we're using configures them all in bypass (haven't paid attention to whether that's still the case in more modern u-boot)#asahi-dev · 2022-09-29 20:24
kevans91sven: ahh, thanks! we're apparently seeing AC64 == 0 in our xhci_init, so I wonder if we're off somewhere... probably need to sanity check these other register reads#asahi-dev · 2022-04-26 16:34
kevans91er#asahi-dev · 2022-04-26 16:34
kevans91ah, interesting#asahi-dev · 2022-04-23 16:31
kevans91kettenis: ok, cool, thanks. we're having a heck of a time with pcie, and I'm afraid I really don't understand pcie well enough to be helpful yet... working on it, though#asahi-dev · 2022-04-23 15:47
kevans91alright, another silly question; what exactly is this reg? is this one of those 'reg describes the PCI RID' things? https://github.com/u-boot/u-boot/blob/master/arch/arm/dts/t8103-j274.dts#L53 (../port02/ethernet0)#asahi-dev · 2022-04-13 06:45
kevans91kettenis: https://github.com/openbsd/src/blob/master/sys/arch/arm64/dev/aplpmgr.c#L146 -> should respect on? I suppose you don't want to disable_all on the way off, though#asahi-dev · 2022-04-11 14:45
kevans91kettenis: ahh, that makes sense, thanks!#asahi-dev · 2022-04-11 05:47
kevans91otoh, linux presumably gets this right#asahi-dev · 2022-04-11 05:45
kevans91so it feels like either i'm reading something wrong, or this is inconsistent and one of those (presumably the iommu-map) are wrong#asahi-dev · 2022-04-11 05:44
kevans91i.e. there's no way a masked rid from <0x0 0x0 0x0 0x0 0x0> could possibly fall into [0x100, 0x101), [0x200, 0x201), or [0x300, 0x301)