User Details
- User Since
- May 16 2014, 7:29 PM (652 w, 4 d)
Mon, Nov 16
Glad to see others interested in kexec!
Sat, Nov 14
Fri, Nov 13
Tue, Nov 10
I tested this last week on my Talos II (powerpc64le) and got massive corruption on my NVMe drive to the point where I could no longer boot, it even corrupted the boot partition. I could finally recover with Linux, but not even another FreeBSD image (memstick) could recover it.
Mon, Nov 9
Sun, Nov 8
Sat, Nov 7
Oct 19 2026
Oct 16 2026
Oct 15 2026
Oct 8 2026
Aside from the one nit, looks good.
Oct 7 2026
The change looks fine. cr_cpuid != cr_hwref because cr_hwref is the "hardware logical" CPU ID (multithreaded CPUs count by N, not 1). So on e6500 cpu1 to FreeBSD is hwref 2. The "reg" property on e6500 CPUs (T2080, etc) is actually an array of IDs. Since we currently don't support multithreading on Book-E (and I have no plans at this time to add it, but may if I get bored) we only accept the first member in the array. Looking through the code, though, for this platform you're right, that hwref is not used. cr_hwref (and pc_hwref) look to only be used on the AIM platforms (particularly powernv). I had to make a lot of changes to this code when doing the e6500 bringup earlier this year, but it could likely be removed. The only reason this difference between cpuid and hwref is needed is for the openpic interface, but the PIC_AP_INIT() change I added makes that unnecessary, the pc_pic field now takes care of that.
Oct 6 2026
Oct 5 2026
Oct 2 2026
Sep 24 2026
Sep 23 2026
Sep 22 2026
Sep 18 2026
Sep 17 2026
Sep 15 2026
Sep 14 2026
Sep 13 2026
This change is not necessary.
Sep 12 2026
Add missing files linux_emul_md.{c,h}
Address all feedback. Since a lot of time has passed since, I also added more
features, primarily VMX/VSX and signal handling.
Sep 11 2026
Sep 8 2026
Sep 5 2026
Sep 1 2026
Aug 30 2026
Aug 29 2026
Aug 28 2026
Aug 27 2026
Will go a different route--move this functionality into fman_xmdio instead per @mmel.
Aug 26 2026
@mmel this new driver is effectively the mii_fdt.c equivalent on the mdio side. From a physical perspective, my understanding is mdio is the low-level serial interface that can connect "anything", while MII is the higher level bus intended for PHYs, so MII "sits on top of" MDIO in reality, and they're separate entities in our driver architecture.
