gmane.os.freebsd.devel.arm archive

7702 archived articles, newest first (page 39 of 78). Latest articles →

Re: fsck segfaults on rpi3 running 13-stable (and on 14-CURRENT analyzing the same file system that resulted from the 13-STABLE crash)
Sat, 18 Feb 2023 13:06:10 -0800
bob prohaska <[email protected]> • #26124
Re: fsck segfaults on rpi3 running 13-stable (and on 14-CURRENT analyzing the same file system that resulted from the 13-STABLE crash)
Fri, 17 Feb 2023 16:23:59 -0800
Mark Millard <[email protected]> • #26123
Re: fsck segfaults on rpi3 running 13-stable (and on 14-CURRENT analyzing the same file system that resulted from the 13-STABLE crash)
Fri, 17 Feb 2023 15:25:37 -0800
bob prohaska <[email protected]> • #26122
Re: Armv7 panic on -current, rpi2 buildworld
Thu, 16 Feb 2023 11:35:45 -0800
Mark Millard <[email protected]> • #26121
[Bug 267361] EINVAL accessing fpcsr for armv7 process on arm64 kernel
Thu, 16 Feb 2023 11:32:13 +0000
[email protected] • #26120
Re: fsck segfaults on rpi3 running 13-stable (and on 14-CURRENT analyzing the same file system that resulted from the 13-STABLE crash)
Wed, 15 Feb 2023 11:39:13 -0800
Mark Millard <[email protected]> • #26119
Re: fsck segfaults on rpi3 running 13-stable (and on 14-CURRENT analyzing the same file system that resulted from the 13-STABLE crash)
Wed, 15 Feb 2023 11:08:56 -0800
bob prohaska <[email protected]> • #26118
Re: fsck segfaults on rpi3 running 13-stable (and on 14-CURRENT analyzing the same file system that resulted from the 13-STABLE crash)
Wed, 15 Feb 2023 09:40:51 -0800
Mark Millard <[email protected]> • #26117
Re: fsck segfaults on rpi3 running 13-stable (and on 14-CURRENT analyzing the same file system that resulted from the 13-STABLE crash)
Wed, 15 Feb 2023 07:44:24 -0800
bob prohaska <[email protected]> • #26116
Re: Armv7 panic on -current, rpi2 buildworld
Tue, 14 Feb 2023 23:16:03 -0800
Mark Millard <[email protected]> • #26115
Re: Armv7 panic on -current, rpi2 buildworld
Tue, 14 Feb 2023 21:16:51 -0700
Warner Losh <[email protected]> • #26114
Armv7 panic on -current, rpi2 buildworld
Tue, 14 Feb 2023 18:57:41 -0800
bob prohaska <[email protected]> • #26113
Re: fsck segfaults on rpi3 running 13-stable (and on 14-CURRENT analyzing the same file system that resulted from the 13-STABLE crash)
Tue, 14 Feb 2023 18:50:40 -0600
Mike Karels <[email protected]> • #26112
Re: fsck segfaults on rpi3 running 13-stable (and on 14-CURRENT analyzing the same file system that resulted from the 13-STABLE crash)
Tue, 14 Feb 2023 16:29:46 -0800
bob prohaska <[email protected]> • #26111
Re: fsck segfaults on rpi3 running 13-stable (and on 14-CURRENT analyzing the same file system that resulted from the 13-STABLE crash)
Tue, 14 Feb 2023 15:27:46 -0800
John-Mark Gurney <[email protected]> • #26110
Re: fsck segfaults on rpi3 running 13-stable (and on 14-CURRENT analyzing the same file system that resulted from the 13-STABLE crash)
Tue, 14 Feb 2023 13:06:01 -0800
bob prohaska <[email protected]> • #26109
Re: fsck segfaults on rpi3 running 13-stable (and on 14-CURRENT analyzing the same file system that resulted from the 13-STABLE crash)
Tue, 14 Feb 2023 11:29:28 -0800
John-Mark Gurney <[email protected]> • #26108
Re: fsck segfaults on rpi3 running 13-stable (and on 14-CURRENT analyzing the same file system that resulted from the 13-STABLE crash)
Tue, 14 Feb 2023 10:38:27 -0800
John-Mark Gurney <[email protected]> • #26107
Re: fsck segfaults on rpi3 running 13-stable (and on 14-CURRENT analyzing the same file system that resulted from the 13-STABLE crash)
Tue, 14 Feb 2023 08:14:15 -0800
bob prohaska <[email protected]> • #26106
Re: detecting qemu/HVF on Apple M1 silicon
Tue, 14 Feb 2023 01:48:10 -0800
John-Mark Gurney <[email protected]> • #26105
Re: detecting qemu/HVF on Apple M1 silicon
Tue, 14 Feb 2023 10:24:02 +0100 (CET)
Ronald Klop <[email protected]> • #26104
detecting qemu/HVF on Apple M1 silicon
Tue, 14 Feb 2023 00:05:30 -0800
John-Mark Gurney <[email protected]> • #26103
Re: fsck segfaults on rpi3 running 13-stable (and on 14-CURRENT analyzing the same file system that resulted from the 13-STABLE crash)
Mon, 13 Feb 2023 16:15:17 -0800
Mark Millard <[email protected]> • #26102
Re: fsck segfaults on rpi3 running 13-stable (and on 14-CURRENT analyzing the same file system that resulted from the 13-STABLE crash)
Mon, 13 Feb 2023 15:25:19 -0800
John-Mark Gurney <[email protected]> • #26101
Re: fsck segfaults on rpi3 running 13-stable (and on 14-CURRENT analyzing the same file system that resulted from the 13-STABLE crash)
Sun, 12 Feb 2023 13:25:32 -0800
Mark Millard <[email protected]> • #26100
Problem reports for [email protected] that need special attention
Sun, 12 Feb 2023 21:00:17 +0000
[email protected] • #26099
Re: fsck segfaults on rpi3 running 13-stable
Sun, 12 Feb 2023 11:53:24 -0800
bob prohaska <[email protected]> • #26098
Re: fsck segfaults on rpi3 running 13-stable
Sun, 12 Feb 2023 11:31:59 -0800
Mark Millard <[email protected]> • #26097
Re: fsck segfaults on rpi3 running 13-stable
Sun, 12 Feb 2023 11:13:08 -0800
bob prohaska <[email protected]> • #26096
Re: fsck segfaults on rpi3 running 13-stable
Sun, 12 Feb 2023 10:30:43 -0800
Mark Millard <[email protected]> • #26095
Re: fsck segfaults on rpi3 running 13-stable
Sun, 12 Feb 2023 09:21:20 -0800
Mark Millard <[email protected]> • #26094
Re: fsck segfaults on rpi3 running 13-stable
Sun, 12 Feb 2023 08:53:33 -0800
bob prohaska <[email protected]> • #26093
Anyone willing to commit the tiny patches from https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268835 ?
Sun, 12 Feb 2023 00:02:58 -0800
Mark Millard <[email protected]> • #26092
Re: fsck segfaults on rpi3 running 13-stable
Sat, 11 Feb 2023 21:21:29 -0800
Mark Millard <[email protected]> • #26091
Re: fsck segfaults on rpi3 running 13-stable
Sat, 11 Feb 2023 20:35:24 -0800
bob prohaska <[email protected]> • #26090
Re: fsck segfaults on rpi3 running 13-stable
Sat, 11 Feb 2023 18:57:41 -0800
Mark Millard <[email protected]> • #26089
[Bug 269487] 13.2-PRERELEASE csh dumps core
Sun, 12 Feb 2023 00:04:40 +0000
[email protected] • #26088
fsck segfaults on rpi3 running 13-stable
Sat, 11 Feb 2023 14:40:57 -0800
bob prohaska <[email protected]> • #26087
[Bug 269487] 13.2-PRERELEASE csh dumps core
Sat, 11 Feb 2023 08:47:18 +0000
[email protected] • #26086
Re: gobject-introspection build fails on armv7 / main
Wed, 8 Feb 2023 20:27:36 -0800
Mark Millard <[email protected]> • #26085
It looks like graphics/drm-510-kmod should be marked broken for aarch64: no FreeBSD build server package-builds finished under 13.1 release
Wed, 8 Feb 2023 10:32:36 -0800
Mark Millard <[email protected]> • #26084
gobject-introspection build fails on armv7 / main
Wed, 8 Feb 2023 10:50:27 +0200
Andriy Gapon <[email protected]> • #26083
[Bug 206048] 11.0-CURRENT -r293227 (and others) arm (rpi2/BeagleBone Black) amd64 etc: swapfile usage hangs; swap partition works
Mon, 06 Feb 2023 16:23:26 +0000
[email protected] • #26082
Rock64 snapshot main-n260538-6f52f8504814 gets mx2510 related "lock order reversal: (sleepable after non-sleepable)" during boot
Sun, 5 Feb 2023 14:24:25 -0800
Mark Millard <[email protected]> • #26081
Problem reports for [email protected] that need special attention
Sun, 5 Feb 2023 21:00:29 +0000
[email protected] • #26080
Re: Compiling device tree overlays (finding the *.dts* sources for the specific RPi* firmware FreeBSD is set up to use)
Thu, 2 Feb 2023 19:50:35 -0800
Mark Millard <[email protected]> • #26079
Re: My ARM64 boot just broke (undefined instruction)
Thu, 2 Feb 2023 16:49:17 +0000
Andrew Turner <[email protected]> • #26078
Re: My ARM64 boot just broke (undefined instruction)
Thu, 2 Feb 2023 11:11:10 -0500
Martin Cracauer <[email protected]> • #26077
Re: My ARM64 boot just broke (undefined instruction)
Thu, 2 Feb 2023 15:57:07 +0000
John F Carr <[email protected]> • #26076
My ARM64 boot just broke (undefined instruction)
Thu, 2 Feb 2023 05:13:55 -0500
Martin Cracauer <[email protected]> • #26075
Re: Compiling device tree overlays
Tue, 31 Jan 2023 21:54:54 -0800
Mark Millard <[email protected]> • #26074
Compiling device tree overlays
Tue, 31 Jan 2023 20:15:59 -0700
John Rushford <[email protected]> • #26073
Re: hyperv.conf devd suddenly installed?
Tue, 31 Jan 2023 15:39:47 -0700
Warner Losh <[email protected]> • #26072
Re: BeagleBone Black does not boot -current (DTB incompatibility?)
Tue, 31 Jan 2023 22:18:20 +0000 (UTC)
"Bjoern A. Zeeb" <[email protected]> • #26071
Re: hyperv.conf devd suddenly installed?
Tue, 31 Jan 2023 12:10:51 -0700
Warner Losh <[email protected]> • #26070
Re: hyperv.conf devd suddenly installed?
Tue, 31 Jan 2023 11:05:59 -0800
Mark Millard <[email protected]> • #26069
hyperv.conf devd suddenly installed?
Tue, 31 Jan 2023 18:39:37 +0000 (UTC)
"Bjoern A. Zeeb" <[email protected]> • #26068
Problem reports for [email protected] that need special attention
Sun, 29 Jan 2023 21:00:47 +0000
[email protected] • #26067
Re: GPIO inputs on Pis?
Sat, 28 Jan 2023 09:58:40 -0500
Karl Denninger <[email protected]> • #26066
sys/uart fdt Here is pointers to the code we should be using Hope this helps, John. FreeBSD, UART and Raspberry Pi 3 B+
Thu, 26 Jan 2023 09:49:24 -0800
Fred Finster <[email protected]> • #26065
Re: GPIO inputs on Pis?
Thu, 26 Jan 2023 04:04:51 +0000
"Dr. Rolf Jansen" <[email protected]> • #26064
Re: GPIO inputs on Pis?
Wed, 25 Jan 2023 11:45:28 -0500
Karl Denninger <[email protected]> • #26063
FYI: RPi4B "C0T" vs. "B0T" (Inbound from PCIe 3 GiByte limit for XHCI use) in various Operating System/Firmware combinations
Tue, 24 Jan 2023 15:13:22 -0800
Mark Millard <[email protected]> • #26062
Re: Testing All 5 Uarts on Raspberry Pi 4B
Tue, 24 Jan 2023 12:55:10 -0700
John Rushford <[email protected]> • #26061
Re: GPIO inputs on Pis?
Tue, 24 Jan 2023 14:17:58 -0500
Karl Denninger <[email protected]> • #26060
Re: GPIO inputs on Pis?
Tue, 24 Jan 2023 19:15:30 +0000
"Dr. Rolf Jansen" <[email protected]> • #26059
Re: Enabling Raspberry Pi 4B Uarts, specifically uart3
Tue, 24 Jan 2023 11:43:56 -0700
John Rushford <[email protected]> • #26058
Re: Enabling Raspberry Pi 4B Uarts, specifically uart3
Tue, 24 Jan 2023 10:11:20 -0700
John Rushford <[email protected]> • #26057
Re: GPIO inputs on Pis?
Tue, 24 Jan 2023 11:58:31 -0500
Karl Denninger <[email protected]> • #26056
Re: GPIO inputs on Pis?
Tue, 24 Jan 2023 15:43:52 +0000
"Dr. Rolf Jansen" <[email protected]> • #26055
Re: GPIO inputs on Pis?
Tue, 24 Jan 2023 10:35:56 -0500
Karl Denninger <[email protected]> • #26054
Re: GPIO inputs on Pis?
Tue, 24 Jan 2023 15:35:02 +0000
"Dr. Rolf Jansen" <[email protected]> • #26053
Advertising FreeBSD 14.0 on Raspberry Pi on BSDnow.tv Podcast , a raspberryi.com forum post
Tue, 24 Jan 2023 06:21:55 -0800
Fred Finster <[email protected]> • #26052
Enabling Raspberry Pi 4B Uarts, specifically uart3
Tue, 24 Jan 2023 05:09:00 -0800
Fred Finster <[email protected]> • #26051
Testing All 5 Uarts on Raspberry Pi 4B
Tue, 24 Jan 2023 04:53:44 -0800
Fred Finster <[email protected]> • #26050
Re: Raspberry Pi 4B is now booting single user mode on FreeBSD 14.0 aarch64. Does it work for you?
Mon, 23 Jan 2023 13:41:28 -0800
Mark Millard <[email protected]> • #26049
Re: Raspberry Pi 4B is now booting single user mode on FreeBSD 14.0 aarch64. Does it work for you?
Mon, 23 Jan 2023 06:53:52 -0800
Fred Finster <[email protected]> • #26048
GPIO inputs on Pis?
Mon, 23 Jan 2023 09:41:45 -0500
Karl Denninger <[email protected]> • #26047
[Bug 269104] The uarts2 - uarts5 do not function on raspberry pi 4B
Sun, 22 Jan 2023 21:36:36 +0000
[email protected] • #26046
Problem reports for [email protected] that need special attention
Sun, 22 Jan 2023 21:00:46 +0000
[email protected] • #26045
arm.armv7 crashing
Sun, 22 Jan 2023 12:13:11 -0500
Michael Jung <[email protected]> • #26044
Re: Pi 4 uarts
Sat, 21 Jan 2023 20:27:38 -0700
John Rushford <[email protected]> • #26043
Re: Pi 4 uarts
Sat, 21 Jan 2023 19:18:03 -0800
Mark Millard <[email protected]> • #26042
Pi 4 uarts
Sat, 21 Jan 2023 19:34:59 -0700
John Rushford <[email protected]> • #26041
Re: Raspberry Pi 4B not booting single user mode on FreeBSD 14.0 aarch64. Does it work for you?
Sat, 21 Jan 2023 17:12:22 -0800
Mark Millard <[email protected]> • #26040
[Bug 269085] USB device not recognized
Sat, 21 Jan 2023 20:18:16 +0000
[email protected] • #26039
Raspberry Pi 4B not booting single user mode on FreeBSD 14.0 aarch64. Does it work for you?
Fri, 20 Jan 2023 06:22:36 -0800
Fred Finster <[email protected]> • #26038
[Bug 268995] Hardware Probe dies on pci_host_generic_core_alloc_resource FAIL
Tue, 17 Jan 2023 00:26:34 +0000
[email protected] • #26037
Problem reports for [email protected] that need special attention
Sun, 15 Jan 2023 21:00:44 +0000
[email protected] • #26036
Re: RPI I2C (bcm2835_bsc) patch
Sat, 14 Jan 2023 23:15:05 +0000 (UTC)
"Bjoern A. Zeeb" <[email protected]> • #26035
RPI I2C (bcm2835_bsc) patch
Sat, 14 Jan 2023 23:14:28 +0000 (UTC)
"Bjoern A. Zeeb" <[email protected]> • #26034
Re: Gpiopps module
Fri, 13 Jan 2023 16:27:42 -0700
John Rushford <[email protected]> • #26033
Re: FYI: vendor/device-tree possibly missing 2 tags
Fri, 13 Jan 2023 09:11:35 +0100
Emmanuel Vadot <[email protected]> • #26032
Re: Gpiopps module
Fri, 13 Jan 2023 15:56:59 +1030
"Daniel O'Connor" <[email protected]> • #26031
Gpiopps module
Thu, 12 Jan 2023 16:33:03 -0700
John Rushford <[email protected]> • #26030
FYI: vendor/device-tree possibly missing 2 tags
Wed, 11 Jan 2023 07:29:45 -0800
Mark Millard <[email protected]> • #26029
Re: Pi 4 serial ports
Tue, 10 Jan 2023 11:19:19 -0700
John Rushford <[email protected]> • #26028
Re: FreeBSD and CM4: use pftf/RPi4 (the EDK2 implementation)?
Tue, 10 Jan 2023 12:05:05 +0100
Klaus Küchemann <[email protected]> • #26027
Re: [EXTERNAL] MSI CPU affinity for ARM64
Tue, 10 Jan 2023 09:49:27 +0000
Andrew Turner <[email protected]> • #26026
Re: Pi 4 serial ports
Tue, 10 Jan 2023 08:35:20 +0100
Emmanuel Vadot <[email protected]> • #26025
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.