gmane.os.freebsd.devel.arm archive

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

Re: BeagleBone Black does not boot -current (DTB incompatibility?)
Tue, 10 Jan 2023 08:21:42 +0100
Emmanuel Vadot <[email protected]> • #26024
Re: Pi 4 serial ports
Mon, 9 Jan 2023 20:49:10 -0800
Mark Millard <[email protected]> • #26023
Re: Pi 4 serial ports
Mon, 9 Jan 2023 20:54:38 -0700
John Rushford <[email protected]> • #26022
FreeBSD and CM4: use pftf/RPi4 (the EDK2 implementation)?
Mon, 9 Jan 2023 18:15:02 -0800
Mark Millard <[email protected]> • #26021
Pi 4 serial ports
Mon, 9 Jan 2023 13:43:37 -0700
John Rushford <[email protected]> • #26020
Re: (RPi) db> reboot -> cpu_reset failed
Mon, 9 Jan 2023 12:36:28 -0800
Mark Millard <[email protected]> • #26019
Re: (RPi) db> reboot -> cpu_reset failed
Mon, 9 Jan 2023 11:45:37 -0800
Mark Millard <[email protected]> • #26018
Re: (RPi) db> reboot -> cpu_reset failed
Mon, 9 Jan 2023 20:13:45 +0100
Klaus Küchemann <[email protected]> • #26017
Re: BeagleBone Black does not boot -current (DTB incompatibility?)
Mon, 9 Jan 2023 10:08:18 -0800
Mark Millard <[email protected]> • #26016
BeagleBone Black does not boot -current (DTB incompatibility?)
Mon, 09 Jan 2023 10:49:16 -0600
Mike Karels <[email protected]> • #26015
Re: (RPi) db> reboot -> cpu_reset failed
Mon, 9 Jan 2023 08:21:09 -0800
Mark Millard <[email protected]> • #26014
RE: [EXTERNAL] Re: MSI CPU affinity for ARM64
Mon, 9 Jan 2023 15:24:03 +0000
Souradeep Chakrabarti <[email protected]> • #26013
Re: MSI CPU affinity for ARM64
Mon, 9 Jan 2023 11:44:14 +0000
Andrew Turner <[email protected]> • #26012
Re: (RPi) db> reboot -> cpu_reset failed
Mon, 9 Jan 2023 09:15:11 +0100
Klaus Küchemann <[email protected]> • #26011
RE: MSI CPU affinity for ARM64
Mon, 9 Jan 2023 07:13:50 +0000
Souradeep Chakrabarti <[email protected]> • #26010
Re: How to make FreeBSD's kernel boot a RPi4B with modern RPi* firmware
Mon, 9 Jan 2023 02:37:02 +0100
Klaus Küchemann <[email protected]> • #26009
Re: How to make FreeBSD's kernel boot a RPi4B with modern RPi* firmware
Sun, 8 Jan 2023 15:41:27 -0800
Mark Millard <[email protected]> • #26008
Re: (RPi) db> reboot -> cpu_reset failed
Sun, 8 Jan 2023 23:28:53 +0000 (UTC)
"Bjoern A. Zeeb" <[email protected]> • #26007
Re: How to make FreeBSD's kernel boot a RPi4B with modern RPi* firmware
Sun, 8 Jan 2023 23:27:09 +0000 (UTC)
"Bjoern A. Zeeb" <[email protected]> • #26006
Problem reports for [email protected] that need special attention
Sun, 8 Jan 2023 21:01:03 +0000
[email protected] • #26005
Re: (RPi) db> reboot -> cpu_reset failed
Sun, 8 Jan 2023 14:32:34 -0400
Mitchell Horne <[email protected]> • #26004
Re: How to make FreeBSD's kernel boot a RPi4B with modern RPi* firmware
Sun, 8 Jan 2023 18:57:32 +0100
Klaus Küchemann <[email protected]> • #26003
Re: How to make FreeBSD's kernel boot a RPi4B with modern RPi* firmware
Sun, 8 Jan 2023 00:26:48 -0800
Mark Millard <[email protected]> • #26002
Re: How to make FreeBSD's kernel boot a RPi4B with modern RPi* firmware
Sun, 8 Jan 2023 05:01:27 +0100
Klaus Küchemann <[email protected]> • #26001
Re: How to make FreeBSD's kernel boot a RPi4B with modern RPi* firmware
Sat, 7 Jan 2023 16:59:41 -0800
Mark Millard <[email protected]> • #26000
Re: How to make FreeBSD's kernel boot a RPi4B with modern RPi* firmware
Sat, 7 Jan 2023 19:58:55 +0100
Klaus Küchemann <[email protected]> • #25999
Re: How to make FreeBSD's kernel boot a RPi4B with modern RPi* firmware
Sat, 7 Jan 2023 12:33:18 -0800
Mark Millard <[email protected]> • #25998
Re: How to make FreeBSD's kernel boot a RPi4B with modern RPi* firmware
Sat, 7 Jan 2023 19:07:16 +0100
Klaus Küchemann <[email protected]> • #25997
MSI CPU affinity for ARM64
Sat, 7 Jan 2023 14:53:32 +0000
Souradeep Chakrabarti <[email protected]> • #25996
Re: How to make FreeBSD's kernel boot a RPi4B with modern RPi* firmware
Sat, 7 Jan 2023 02:18:37 -0800
Mark Millard <[email protected]> • #25995
Re: How to make FreeBSD's kernel boot a RPi4B with modern RPi* firmware
Sat, 7 Jan 2023 09:37:55 +0100
Klaus Küchemann <[email protected]> • #25994
Re: panic: vm_fault failed: %lx error 1 (from arm64::data_abort)
Sat, 7 Jan 2023 06:50:01 +0100
Klaus Küchemann <[email protected]> • #25993
Re: (RPi) db> reboot -> cpu_reset failed
Sat, 7 Jan 2023 06:19:43 +0100
Klaus Küchemann <[email protected]> • #25992
Re: (RPi) db> reboot -> cpu_reset failed
Fri, 6 Jan 2023 20:42:22 +0100
Klaus Küchemann <[email protected]> • #25991
Re: (RPi) db> reboot -> cpu_reset failed [Klus's crash]
Thu, 5 Jan 2023 21:42:48 -0800
Mark Millard <[email protected]> • #25990
Re: (RPi) db> reboot -> cpu_reset failed [Klus's crash]
Fri, 6 Jan 2023 05:41:36 +0100
Klaus Küchemann <[email protected]> • #25989
Re: panic: vm_fault failed: %lx error 1 (from arm64::data_abort)
Thu, 5 Jan 2023 19:58:03 -0800
Mark Millard <[email protected]> • #25988
Re: panic: vm_fault failed: %lx error 1 (from arm64::data_abort)
Thu, 5 Jan 2023 22:57:34 +0000 (UTC)
"Bjoern A. Zeeb" <[email protected]> • #25987
Re: (RPi) db> reboot -> cpu_reset failed [Klus's crash]
Thu, 5 Jan 2023 12:43:58 -0800
Mark Millard <[email protected]> • #25986
Re: (RPi) db> reboot -> cpu_reset failed
Thu, 5 Jan 2023 20:23:32 +0000 (UTC)
"Bjoern A. Zeeb" <[email protected]> • #25985
Re: panic: vm_fault failed: %lx error 1 (from arm64::data_abort)
Thu, 5 Jan 2023 20:21:53 +0000 (UTC)
"Bjoern A. Zeeb" <[email protected]> • #25984
Re: (RPi) db> reboot -> cpu_reset failed
Thu, 5 Jan 2023 20:32:58 +0100
Klaus Küchemann <[email protected]> • #25983
Re: (RPi) db> reboot -> cpu_reset failed
Thu, 5 Jan 2023 19:01:11 +0100
Klaus Küchemann <[email protected]> • #25982
(RPi) db> reboot -> cpu_reset failed
Thu, 5 Jan 2023 16:37:41 +0000 (UTC)
"Bjoern A. Zeeb" <[email protected]> • #25981
panic: vm_fault failed: %lx error 1 (from arm64::data_abort)
Thu, 5 Jan 2023 16:11:18 +0000 (UTC)
"Bjoern A. Zeeb" <[email protected]> • #25980
Re: Named reporting port in use on 12.4-STABLE r372838 GENERIC arm
Thu, 5 Jan 2023 06:22:03 -0800
bob prohaska <[email protected]> • #25979
Named reporting port in use on 12.4-STABLE r372838 GENERIC arm
Wed, 4 Jan 2023 21:18:49 -0800
bob prohaska <[email protected]> • #25978
Re: rpi3b+ ue0 too late to be configured on boot?
Mon, 2 Jan 2023 00:36:06 +0000 (UTC)
"Bjoern A. Zeeb" <[email protected]> • #25977
Problem reports for [email protected] that need special attention
Sun, 1 Jan 2023 21:00:12 +0000
[email protected] • #25976
Re: rpi3b+ ue0 too late to be configured on boot?
Sun, 01 Jan 2023 13:56:56 -0600
Mike Karels <[email protected]> • #25975
Re: lsof crashes in Arm Optimized Routines
Sun, 1 Jan 2023 17:30:25 +0000
John F Carr <[email protected]> • #25974
Re: Volterra Dev Kit Updates
Sun, 1 Jan 2023 18:13:20 +0100
Robert Clausecker <[email protected]> • #25973
Volterra Dev Kit Updates
Sun, 1 Jan 2023 17:45:22 +0100
Robert Clausecker <[email protected]> • #25972
Re: lsof crashes in Arm Optimized Routines
Sun, 1 Jan 2023 13:49:12 +0100
Ronald Klop <[email protected]> • #25971
Re: rpi3b+ ue0 too late to be configured on boot?
Fri, 30 Dec 2022 21:17:28 -0700
Warner Losh <[email protected]> • #25970
[Bug 268660] RPI4 8GB floating issue - booting failed from USB HDD connected on SupTronics X825 board
Sat, 31 Dec 2022 00:29:10 +0000
[email protected] • #25969
Re: rpi3b+ ue0 too late to be configured on boot?
Fri, 30 Dec 2022 16:16:38 -0600
Mike Karels <[email protected]> • #25968
Re: rpi3b+ ue0 too late to be configured on boot?
Fri, 30 Dec 2022 22:03:34 +0000 (UTC)
"Bjoern A. Zeeb" <[email protected]> • #25967
Re: rpi3b+ ue0 too late to be configured on boot?
Thu, 29 Dec 2022 13:01:15 -0800
Mark Millard <[email protected]> • #25966
Re: rpi3b+ ue0 too late to be configured on boot?
Thu, 29 Dec 2022 14:51:17 -0600
"Mike Karels" <[email protected]> • #25965
Re: rpi3b+ ue0 too late to be configured on boot?
Thu, 29 Dec 2022 12:38:20 -0800
Mark Millard <[email protected]> • #25964
Re: rpi3b+ ue0 too late to be configured on boot?
Thu, 29 Dec 2022 13:39:36 -0600
Mike Karels <[email protected]> • #25963
[Bug 268631] FreeBSD-13.1 fails to boot on raspberry pi and the U-boot saveenv command does not work
Thu, 29 Dec 2022 05:30:34 +0000
[email protected] • #25962
[Bug 268631] FreeBSD-13.1 fails to boot on raspberry pi and the U-boot saveenv command does not work
Thu, 29 Dec 2022 02:38:21 +0000
[email protected] • #25961
[Bug 268630] FreeBSD-13.1 fails to boot on raspberry pi and the U-boot saveenv command does not work
Thu, 29 Dec 2022 02:37:44 +0000
[email protected] • #25960
rpi3b+ ue0 too late to be configured on boot?
Wed, 28 Dec 2022 22:42:33 +0000 (UTC)
"Bjoern A. Zeeb" <[email protected]> • #25959
RPi4B: booting USB3 SSD media vs. config.txt in FreeBSD snapshot builds (and relelase builds): avoiding error=USB_ERR_TIMEOUT
Tue, 27 Dec 2022 12:31:56 -0800
Mark Millard <[email protected]> • #25958
RPi4B's: 13.* boot "'failed to allocate bus number" message vs. main's [so: 14's] lack of such, also related Device Tree content
Tue, 27 Dec 2022 10:26:29 -0800
Mark Millard <[email protected]> • #25957
Re: ofw_pci: Fix incorrectly sized softc causing pci(4) out-of-bounds reads (Should it have been MFC'd?)
Mon, 26 Dec 2022 20:21:27 -0800
Mark Millard <[email protected]> • #25956
RE: ofw_pci: Fix incorrectly sized softc causing pci(4) out-of-bounds reads (Should it have been MFC'd?)
Mon, 26 Dec 2022 19:54:57 -0800
Mark Millard <[email protected]> • #25955
Re: snapshot 1st aarcch64 boot got devd error message: "sh: /usr/libexec/hyperv/hyperv_vfattach: not found"
Sun, 25 Dec 2022 17:23:22 -0800
Mark Millard <[email protected]> • #25954
Re: snapshot 1st aarcch64 boot got devd error message: "sh: /usr/libexec/hyperv/hyperv_vfattach: not found"
Sun, 25 Dec 2022 16:55:30 -0700
Warner Losh <[email protected]> • #25953
snapshot 1st aarcch64 boot got devd error message: "sh: /usr/libexec/hyperv/hyperv_vfattach: not found"
Sun, 25 Dec 2022 15:28:38 -0800
Mark Millard <[email protected]> • #25952
Problem reports for [email protected] that need special attention
Sun, 25 Dec 2022 21:00:43 +0000
[email protected] • #25951
Re: How to make FreeBSD's kernel boot a RPi4B with modern RPi* firmware
Sun, 25 Dec 2022 08:37:52 -0800
Mark Millard <[email protected]> • #25950
I Posted first Review about file scandir.c /usr/src/lib/libc/gen
Sun, 25 Dec 2022 02:43:03 -0800
Fred Finster <[email protected]> • #25949
Re: How to make FreeBSD's kernel boot a RPi4B with modern RPi* firmware
Sat, 24 Dec 2022 20:14:57 -0800
Mark Millard <[email protected]> • #25948
Re: Still did not succeed to boot on Lenovo Yoga C630
Sat, 24 Dec 2022 21:10:26 -0700
Warner Losh <[email protected]> • #25947
How to make FreeBSD's kernel boot a RPi4B with modern RPi* firmware
Sat, 24 Dec 2022 19:15:43 -0800
Mark Millard <[email protected]> • #25946
Re: Still did not succeed to boot on Lenovo Yoga C630
Sun, 25 Dec 2022 11:55:10 +0900
Hiroo Ono (小野寛生) <[email protected]> • #25945
Re: Still did not succeed to boot on Lenovo Yoga C630
Sun, 25 Dec 2022 10:46:37 +0900
Hiroo Ono (小野寛生) <[email protected]> • #25944
Re: Still did not succeed to boot on Lenovo Yoga C630
Sat, 24 Dec 2022 22:18:45 +0900
Hiroo Ono (小野寛生) <[email protected]> • #25943
Re: Still did not succeed to boot on Lenovo Yoga C630
Sat, 24 Dec 2022 22:11:30 +0900
Hiroo Ono (小野寛生) <[email protected]> • #25942
Re: Still did not succeed to boot on Lenovo Yoga C630
Sat, 24 Dec 2022 10:35:12 +0900
Hiroo Ono (小野寛生) <[email protected]> • #25941
Re: Still did not succeed to boot on Lenovo Yoga C630
Fri, 23 Dec 2022 18:03:07 -0700
Warner Losh <[email protected]> • #25940
Re: Still did not succeed to boot on Lenovo Yoga C630
Sat, 24 Dec 2022 09:48:57 +0900
Hiroo Ono (小野寛生) <[email protected]> • #25939
[Bug 268521] [PATCH] arm64 libc: fix longjmp with 0 value
Thu, 22 Dec 2022 23:36:00 +0000
[email protected] • #25938
Problem reports for [email protected] that need special attention
Sun, 18 Dec 2022 21:00:58 +0000
[email protected] • #25937
Re: Still did not succeed to boot on Lenovo Yoga C630
Sun, 18 Dec 2022 13:33:23 -0700
Warner Losh <[email protected]> • #25936
RPi4B boot -v "pci0: failed to allocate bus number" and "device_attach: pci0 attach returned 6"; more
Sun, 18 Dec 2022 11:10:45 -0800
Mark Millard <[email protected]> • #25935
Still did not succeed to boot on Lenovo Yoga C630
Sun, 18 Dec 2022 20:31:01 +0900
Hiroo Ono (小野寛生) <[email protected]> • #25934
Re: armv6/armv7/aarch64 vs. FreeBSD images (retitled from an arch reply, moving to freebsd-arm list)
Thu, 15 Dec 2022 16:26:30 -0800
Mark Millard <[email protected]> • #25933
Would like to help you, Victor, with building FreeBSD 13.0 for Nitrogen8m ARM64 imx8 board
Thu, 15 Dec 2022 16:24:15 -0800
Fred Finster <[email protected]> • #25932
Re: armv6/armv7/aarch64 vs. FreeBSD images (retitled from an arch reply, moving to freebsd-arm list)
Wed, 14 Dec 2022 00:41:13 -0800
Mark Millard <[email protected]> • #25931
armv6/armv7/aarch64 vs. FreeBSD images (retitled from an arch reply, moving to freebsd-arm list)
Tue, 13 Dec 2022 22:45:14 -0800
Mark Millard <[email protected]> • #25930
FreeBSD support for Nitrogen 8M Plus SOM and EVK carrier board
Tue, 13 Dec 2022 23:24:24 +0000
<[email protected]> • #25929
Re: FreeBSD 14: Poll armv6 deprecated or removed (just a reference to the new message on freebsd-arch)
Tue, 13 Dec 2022 13:41:37 -0700
Warner Losh <[email protected]> • #25928
Re: FreeBSD 14: Poll armv6 deprecated or removed (just a reference to the new message on freebsd-arch)
Tue, 13 Dec 2022 12:28:56 -0800
bob prohaska <[email protected]> • #25927
Re: FreeBSD 14: Poll armv6 deprecated or removed (just a reference to the new message on freebsd-arch)
Tue, 13 Dec 2022 11:57:42 -0700
Warner Losh <[email protected]> • #25926
Re: FreeBSD 14: Poll armv6 deprecated or removed (just a reference to the new message on freebsd-arch)
Tue, 13 Dec 2022 10:48:02 -0800
Mark Millard <[email protected]> • #25925
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.