Would it be possible to also support memory-mapped UART this way? Intel >=Skylake and all aarch64 systems use mmio.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Dec 6 2019
Dec 3 2019
In D18028#493129, @greg_unrelenting.technology wrote:Is it just me or did setting epp break in the latest version?
Now calling from IOAPIC suspend/resume functions (if there's any better place "close to the nexus" I haven't found it.)
Nov 25 2019
Is it just me or did setting epp break in the latest version?
Nov 10 2019
Nov 8 2019
Just installed libsigsegv on a machine and the pkg message was: "Note that the stackoverflow handling functions of this library need procfs mounted on /proc."
Nov 7 2019
In D22275#486869, @emaste wrote:Do we know what if any ports actually use procfs?
Nov 4 2019
Rebased on top of the ASID changes
In D21564#485874, @hselasky wrote:Who will submit this patch?
Nov 3 2019
ping
Diff broken by rS354193 'Set the userspace execute never bit on kernel mappings' (looks like that sets UXN in the else case instead).
Oct 29 2019
Rebased on top of the powerpc64 change
Oct 18 2019
Maybe at some point they can even become PIE executables by default! :)
Oct 9 2019
The pmap_change_attr() API is private on arm64
Oct 7 2019
In D16698#478767, @imp wrote:So with the suggested changes, I'm not able to get very far with the patches in this review. With wulf's code I'm able to get the device probed. With this code, I see the following
Oct 3 2019
In D21863#477929, @hselasky wrote:Likely this Google device is not USB certified
Oct 2 2019
Oct 1 2019
Sep 27 2019
Sep 22 2019
oh, i915 is reloadable, right. Everything works fine, can adjust brightness after reloading.
Yeah, I was wondering about devmatch in D21612
Sep 21 2019
ping
Sep 16 2019
Sep 15 2019
Works fine on the Google Pixelbook (i7-7Y75) (where the old EST does not work because there aren't any acpi_perf devices).
Looks like this was merged as rS351480 but phabricator didn't count that for closing this review (full URL shouldn't be in "Differential Revision:"??)
Sep 12 2019
Sep 8 2019
Aug 28 2019
In D20789#467032, @hselasky wrote:Can you update my patch and test an again? Thank you!
panic: vm_fault_hold: fault on nofault entry, addr: 0xffff00006e1ff000 in gfx_v8_0_kiq_resume
Aug 27 2019
ping
Aug 18 2019
Aug 16 2019
In D20974#462987, @emaste wrote:Can you show a diff of the NetBSD version to this? i.e. what you had to change in the port?
(I assume that we don't want to treat this as contrib code and will just adopt it.)
In D21167#463001, @emaste wrote:This is just another "upstream only considered Linux, we need to be included in the same way as Linux" case.
But I mean this was already the case for the presumably-working amd64/i386 cases?
Aug 13 2019
Builds fine on aarch64 CURRENT, tested building ripgrep with it, fine.
I'm building on aarch64 right now, llvm is done, so I'm expecting success
Aug 8 2019
Aug 7 2019
btw, kms-drm patch: https://github.com/FreeBSDDesktop/kms-drm/pull/163
Aug 6 2019
In D21168#460060, @imp wrote:Have you run this and does it work?
Seems fine so far, thanks
bump
oh, also, msi_enabled is actually a public flag used by the i915 driver:
We need pdev->irq = rle->start still (and, for completeness, similarly in the disable function), otherwise it tries to request LINUX_IRQ_INVALID:
This causes panics in ZFS. Just doing an installkernel or cp -r /boot/kernel /boot/kernel.something results in:
Jul 30 2019
In D20974#458088, @emaste wrote:In D20974#457245, @greg_unrelenting.technology wrote:Would be nice to test on ThunderX2 :)
Does not attach on ThunderX2 (no sbsawdt0 in dmesg).
Jul 28 2019
Jul 26 2019
Update: added pdev->msi_enabled flag that's used by i915kms.
Jul 25 2019
In D20974#457235, @emaste wrote:I can confirm this attaches on my eMAG but I cannot verify the watchdog functionality - were you able to test it?
In D20974#457221, @emaste wrote:@greg_unrelenting.technology do you have a git repo available with your work in it? It'd be slightly easier for me to just add your repo and grab changes directly.
Jul 24 2019
Jul 22 2019
In D21018#456270, @ngie wrote:Could you please test this change out on amd64?
Jul 21 2019
We probably wouldn't want that on big armv8 boxes, maybe || defined(__aarch64__) should be added to if defined(__amd64__) in that case..
Jul 20 2019
Jul 18 2019
In D16698#455093, @nikola.lecic_anthesphoria.net wrote:In D16698#454859, @greg_unrelenting.technology wrote:In D16698#454202, @nikola.lecic_anthesphoria.net wrote:
- I compiled this driver with EVDEV support (https://gist.github.com/johalun/3c67a678e740b82512cec52bfe926092). How can I make use of it? I see no difference with and without this patch.
If there's a new device in /dev/input, it is working. You can run libinput debug-events to see the input events. To consume evdev devices from xorg, use xf86-input-libinput. There were patches for autodetection (one adding evdev autodetection to the devd backend, another switching to the udev backend with libudev-devd). The devd one might have been merged?? (I don't follow Xorg, I use Wayland exclusively)
Thanks; I thought that kldload evdev was enough; but kernel with EVDEV_SUPPORT was needed.
Jul 17 2019
In D16698#454202, @nikola.lecic_anthesphoria.net wrote:
- I compiled this driver with EVDEV support (https://gist.github.com/johalun/3c67a678e740b82512cec52bfe926092). How can I make use of it? I see no difference with and without this patch.
Jul 16 2019
Jul 15 2019
Jul 8 2019
please commit?
Jul 4 2019
Sure. I've actually made a couple more changes recently btw. I hope PATCH_SITES is okay here
Jul 2 2019
Jun 29 2019
Jun 28 2019
UPDATE: actually this miiiight have been preventing the GPU from working.
hm, just looked at linux — regular, _nocache and _wt are all PROT_DEVICE_nGnRE. Let's change them all then.
Jun 27 2019
In D20765#449718, @bcran wrote:I just tried booting with this patch applied and with EDK2 firmware built from master yesterday, and I still don't see any output - both with devicetree and acpi.
Tested on += Marvell MACCHIATObin (Armada8k) [upstream EDK2, atf-marvell, ECAM shift removed, ACPI mode]