> Date: Fri, 23 May 2025 22:00:41 +0200
> From: Andrea Biscuola
>
> Hi all.
>
> I'm working on trying to get OpenBSD to boot on the new C5. As of
> now, I have a u-boot fimware for the board built.
>
> Given that I'm a newbie into this, advices and suggestions are
> appreciated :).
>
> Anyway,
> From: joshua stein
> Date: Wed, 7 May 2025 21:52:24 -0500
>
> Before MII reads/writes, make sure it's not busy like the docs say
> to.
Why? We already have a check at the end of dwge_mii_readreg() and
dwge_mii_writereg() to make sure the request completed. So unless
we're issuing concurrent
> Date: Sat, 10 May 2025 22:43:19 -0500
> From: joshua stein
>
> On Sat, 10 May 2025 at 14:25:54 +0200, Mark Kettenis wrote:
> > > +static const struct rkpmic_regdata rk818_regdata[] = {
> > > + { "DCDC_REG1", 0x2f, 0x3f, 0, 0, rk808_vsel_range1 },
> From: joshua stein
> Date: Wed, 7 May 2025 21:52:21 -0500
>
> Use RK3128_CRU_GLB_SOFTRST_1 to implement cpuresetfn
> ---
> sys/dev/fdt/rkclock.c| 590 ++-
> sys/dev/fdt/rkclock_clocks.h | 52 +++
> 2 files changed, 634 insertions(+), 8 deletions(-)
Th
> Feedback-ID: i5cf14421:Fastmail
> From: joshua stein
>
> ---
> sys/dev/fdt/rkpinctrl.c | 305 +++-
> 1 file changed, 303 insertions(+), 2 deletions(-)
A few comments on this one.
>
> diff --git a/sys/dev/fdt/rkpinctrl.c b/sys/dev/fdt/rkpinctrl.c
> index 6
> From: joshua stein
> Date: Wed, 7 May 2025 21:52:30 -0500
>
> ---
> sys/dev/fdt/rkpmic.c | 27 ++-
> 1 file changed, 26 insertions(+), 1 deletion(-)
Spotted a mistake...
>
> diff --git a/sys/dev/fdt/rkpmic.c b/sys/dev/fdt/rkpmic.c
> index 0094b61e6b9..ccfa50abbf8 10
> Feedback-ID: i5cf14421:Fastmail
> From: joshua stein
>
> ---
> sys/arch/armv7/conf/GENERIC | 1 +
> sys/dev/fdt/rkusbphy.c | 25 +
> 2 files changed, 26 insertions(+)
ok kettenis@
> diff --git a/sys/arch/armv7/conf/GENERIC b/sys/arch/armv7/conf/GENERIC
> index 9
> From: joshua stein
> Date: Wed, 7 May 2025 21:52:28 -0500
>
> Not sure yet why transfers fail but this gets things going
I wonder if that's because you don't actually switch the bus into
4-bit mode?
> ---
> sys/dev/fdt/dwmmc.c | 5 -
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
>
> From: joshua stein
> Date: Wed, 7 May 2025 21:52:29 -0500
>
> Otherwise the dwmmc on the RK3128 fails to "switch func mode 0"
> ---
> sys/dev/sdmmc/sdmmc_mem.c | 18 +-
> 1 file changed, 9 insertions(+), 9 deletions(-)
I'm honestly not trying to find an issue with every diff
> From: joshua stein
> Cc: joshua stein
>
> ---
> sys/dev/mii/miidevs | 1 +
> sys/dev/mii/miidevs.h | 4 +++-
> sys/dev/mii/rlphy.c | 2 ++
> 3 files changed, 6 insertions(+), 1 deletion(-)
Two nits below. ok kettenis@ with those fixed.
> diff --git a/sys/dev/mii/miidevs b/sys/dev/mii/m
> Feedback-ID: i5cf14421:Fastmail
> From: joshua stein
>
> ---
> sys/dev/fdt/rkiic.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
This diff should not be necessary. The devicetree bindings indicate
that the "rockchip,rk3128-i2c" will also list "rockchip,rk3288-i2c" as
the compatib
> Date: Thu, 8 May 2025 08:38:31 -0500
> From: joshua stein
>
> On Thu, 08 May 2025 at 11:52:51 +0200, Mark Kettenis wrote:
> > > From: joshua stein
> > > Date: Wed, 7 May 2025 21:52:22 -0500
> > >
> > > This is found on the XPI-3128
> >
> From: joshua stein
> Date: Wed, 7 May 2025 21:52:22 -0500
>
> This is found on the XPI-3128
I'm fairly confident this is the same chip that is already supported
by abcrtc(4). The registers match and the datasheet for the Abracon
AB18X5 RTC that I can find has a disclaimer that says:
AB18X
> Date: Fri, 25 Apr 2025 19:28:05 +
> From: Miod Vallat
>
> > My RK3128 came up with no ci_flush_bp assigned, because cpu0 never
> > attached, because the reg values in the DTB were 0x000-0x003 rather
> > than 0xf00-0xf03. This caused a "Fatal kernel mode prefetch abort"
> > because it wa
> Date: Fri, 25 Apr 2025 14:25:40 -0500
> From: joshua stein
>
> My RK3128 came up with no ci_flush_bp assigned, because cpu0 never
> attached, because the reg values in the DTB were 0x000-0x003 rather
> than 0xf00-0xf03. This caused a "Fatal kernel mode prefetch abort"
> because it was tryin
> Date: Thu, 17 Apr 2025 17:56:13 -0500
> From: joshua stein
>
> On Wed, 16 Apr 2025 at 11:54:57 +0200, Mark Kettenis wrote:
> > You're accessing the UART registers using their physical address. But
> > as soon as you turn on the MMU you need a virtiual address. So
> Date: Tue, 15 Apr 2025 16:26:27 -0500
> From: joshua stein
Hi Joshua,
> I'm trying to bring up OpenBSD/arm on an RK3128 in the Pomera DM250.
> I was able to update its shipped U-Boot from 2014.10 to 2017.09 so
> it would have EFI support, and I can boot BOOTARM.EFI.
>
> It hangs when enter
> From: Vincent Legoll
> Date: Sun, 6 Apr 2025 19:12:55 +
>
> Hi Mark,
>
> On Sun, Apr 6, 2025 at 7:08 PM Mark Kettenis
> wrote:
>
> We don't have support for the RK3528 SoC yet. In particular there is
> no support for this SoC in the rkclock(4) and
> From: Vincent Legoll
> Date: Sun, 6 Apr 2025 17:46:29 +
Hi Vincent,
We don't have support for the RK3528 SoC yet. In particular there is
no support for this SoC in the rkclock(4) and rkpinctrl(4) drivers
yet. That is probably why some of the devices don't work properly.
Adding support s
> Date: Fri, 31 Jan 2025 00:51:12 +0900
> From: FUKAUMI Naoki
>
> On 1/30/25 23:59, Patrick Wildt wrote:
> > On Thu, Jan 30, 2025 at 10:07:43PM +0900, FUKAUMI Naoki wrote:
> >> On 1/30/25 19:36, Patrick Wildt wrote:
> >>> While I was sleeping Jared made some more progress with NetBSD, see:
> >>>
> Date: Thu, 30 Jan 2025 11:36:38 +0100
> From: Patrick Wildt
Hi Patrick,
After staring at the ARM ARM for a bit, I don't think the agtimer(4)
bits are entirely correct. See below.
The xhci(4) bits look good (but I know you're working on a better
diff). So the SErrors happen because the hardw
> Date: Wed, 22 Jan 2025 15:34:45 +0900
> From: FUKAUMI Naoki
>
> So, what is this panic?
It's some sort of hardware error. We've seen this happen when memory
is mapped with the wrong memory attributes. Could be the result of
the kernel mapping memory that isn't accessable (which in turn could
> Date: Wed, 22 Jan 2025 14:36:04 +0900
> From: FUKAUMI Naoki
>
> On 1/22/25 11:49, FUKAUMI Naoki wrote:
> > I found the key to enable the SPCR table in EDK2. I rebuilt the UEFI and
> > the SPCR table started to appear. But on OpenBSD things got worse, I
> > lost output on both serial and HDMI.
> Date: Mon, 20 Jan 2025 10:25:49 +0900
> From: FUKAUMI Naoki
Hi Naoki,
> Hi Mark,
>
> On 1/20/25 00:27, Mark Kettenis wrote:
> >> Date: Sun, 19 Jan 2025 12:35:59 +0900
> >> From: FUKAUMI Naoki
> >
> > Hello,
> >
> >> Hi,
&g
> Date: Sun, 19 Jan 2025 12:35:59 +0900
> From: FUKAUMI Naoki
Hello,
> Hi,
>
> I'm trying to boot OpenBSD/arm64 on a Radxa Orion O6.
>
> UEFI has a "O/S Hardware Description Selection" menu where I can choose
> "Device Tree" or "ACPI". "ACPI" allows me to boot a mainline Linux kernel.
>
> Wi
> Date: Wed, 08 Jan 2025 13:03:56 +0100
> From: Kirill A. Korinsky
Hi Kirill,
> arm@,
>
> My Honor Magicbook Art 14 Snapdragon basicly working and I've started poking
> around to answer question why "nothing works".
>
> Here no battery status, nor "cpu speed", nor almot anything.
>
> sysctl h
> Date: Sat, 21 Dec 2024 11:04:52 +0100
> From: Kirill A. Korinsky
>
> On Fri, 20 Dec 2024 23:26:35 +0100,
> Kirill A. Korinsky wrote:
> >
> > On Fri, 20 Dec 2024 14:02:38 +0100,
> > Kirill A. Korinsky wrote:
> > >
> > > Sorry for misslead you. Indeed bsd.mp leads to ddb. I can't use keyboard
> Date: Tue, 22 Oct 2024 12:15:18 +0200
> From: Tobias Heider
>
> On Mon, Oct 21, 2024 at 10:10:44PM GMT, Mark Kettenis wrote:
> > > Date: Mon, 21 Oct 2024 20:40:38 +0200
> > > From: Tobias Heider
> > >
> > > On Mon, Oct 21, 2024 at 08:33:53PM G
> Date: Mon, 21 Oct 2024 20:40:38 +0200
> From: Tobias Heider
>
> On Mon, Oct 21, 2024 at 08:33:53PM GMT, Mark Kettenis wrote:
> > > Date: Mon, 21 Oct 2024 14:12:33 +0200
> > > From: Tobias Heider
> > >
> > > On Mon, Oct 21, 2024 at 01:04:10PM GM
> Date: Mon, 21 Oct 2024 14:12:33 +0200
> From: Tobias Heider
>
> On Mon, Oct 21, 2024 at 01:04:10PM GMT, Stuart Henderson wrote:
> > On 2024/10/21 13:54, Sylvain Saboua wrote:
> > > Are we to understand that the default wireless device
> > > of the Apple M1 is not functional yet with openbsd ?
>
> Date: Sun, 11 Aug 2024 01:41:32 +0200
> From: Thomas Dettbarn
>
> Hello.
>
> So, I am currently trying to run my favourite operating system
> on my shiny new BananaPI BPI-R3. Thus far, I was able to Frankenstein
> a u-boot image with the miniroot75.img and got into the OpenBSD
> bootloader.
>
> From: Steffen Beyer
> Date: Mon, 5 Aug 2024 13:55:09 +0200
>
> > On 4. Aug 2024, at 16:28, Steffen Beyer wrote:
> >
> > rkgpio0 at rkpinctrl0
> > rkgpio1 at rkpinctrl0
> > rkgpio2 at rkpinctrl0
> > rkgpio3 at rkpinctrl0
> > rkgpio4 at rkpinctrl0
>
> Is it possible to access GPIO and the conn
> From: Steffen Beyer
> Date: Sat, 3 Aug 2024 14:11:34 +0200
>
> Good evening,
>
> I’m running into trouble getting OpenBSD 7.5 to run on my R6S. The
> instructions in INSTALL.arm64 only mention RK356x explicitly, so I
> went with that:
>
> # pkg_add u-boot-rk3588
> # cp /usr/local/share/u-bo
As indicated here:
https://social.treehouse.systems/@AsahiLinux/112449204541186432
The system firmware that comes with macOS Sonoma 14.5 triggers a bug
in the m1n1 bootloader that is used to boot OpenBSD on these machines.
The bug will prevent OpenBSD from booting on some machines after the
mac
> Date: Sun, 21 Apr 2024 18:09:58 +0100
> From: Mihai Dragan
>
> Hi,
>
> First off, a big thank you for adding support for Nanopi R6S board.
> The hardware's perfect for little home networking projects.
>
> Everything runs fine so far, but I noticed that the reported CPU
> frequency is a fixed
> From: Slava Voronzoff
> Date: Wed, 24 Apr 2024 11:58:39 +0300
Sorry, but this is probaly bad advice:
> Hi, Evan
>
> In situations like this (I too like to play with
> not-very-mainstream/noname boards) I have little tricks:
> 1. You can use official linux images to extract needed parts of dat
> Date: Sat, 16 Mar 2024 00:56:52 +1100
> From: Jonathan Gray
>
> On Fri, Mar 15, 2024 at 02:35:52PM +0100, Mark Kettenis wrote:
> > > Date: Fri, 15 Mar 2024 23:06:31 +1100
> > > From: Jonathan Gray
> > >
> > > On Fri, Mar 15, 2024 at 11:29:28A
> Date: Fri, 15 Mar 2024 23:06:31 +1100
> From: Jonathan Gray
>
> On Fri, Mar 15, 2024 at 11:29:28AM +0100, Marcin Juszkiewicz via arm wrote:
> > W dniu 15.03.2024 o 03:30, Jonathan Gray pisze:
> > > > OpenBSD 7.3 boots fine on all core types. OpenBSD 7.4 fails on
> > > > Neoverse-V1/N2/max. Same
> Date: Tue, 27 Feb 2024 20:52:58 +0100
> From: Rob Schmersel
>
> On Wed, 14 Feb 2024 23:29:26 +0100
> Mark Kettenis wrote:
>
> > > Date: Wed, 14 Feb 2024 20:15:25 +0100
> > > From: Rob Schmersel
> > >
> > > On Tue, 13 Feb 2024 14:19:31
> Date: Tue, 27 Feb 2024 15:03:39 +0100
> From: Sylvain Saboua
>
> https://lore.kernel.org/devicetree-spec/1a9657a715f2929793c1687baf801...@free.fr/T/#u
I don't think you're going to get a lot of help from there.
Anyway, from the output you showed, it is clear it still using an
ancient U-Boot v
> Date: Sun, 18 Feb 2024 12:45:21 +0100
> From: Sylvain Saboua
Hi Sylvain,
> It seems I was right to purchase a shorter micro-USB cable.
> Now the output of `cu -s 150 -l /dev/cuaU0' displays correctly.
>
> I am still unable to boot from the micro-SD card.
> I had succeeded once when the em
Driver for the onboard Ethernet on many boards with an Allwinner SoCs.
If you have one, please make sure your network connection still works
after applying this patch.
Thanks,
Mark
Index: dev/fdt/if_dwxe.c
===
RCS file: /cvs/src/sy
> Date: Wed, 14 Feb 2024 20:15:25 +0100
> From: Rob Schmersel
>
> On Tue, 13 Feb 2024 14:19:31 +0100
> Mark Kettenis wrote:
>
> > You can try to disable ohci by typing "boot -c" at the "boot>" prompt
> > and then "disable ohci" fo
> Date: Tue, 13 Feb 2024 12:16:25 +0100
> From: Rob Schmersel
>
> On Sat, 28 Oct 2023 16:44:06 -0600
> jone...@hrothgars.net wrote:
>
> > I am trying to boot the OpenBSD installer on an Orangepi 5 board. I
> > know the board is yet not in the upstream u-boot and Linux, but I
> > thought I would
> Date: Sun, 11 Feb 2024 09:59:20 +0900
> From: SASANO Takayoshi
>
> Hello,
>
> Here is new diff, ok?
Not exactly what I had in mind, but ok kettenis@
Imay send a follow-up to unify things a bit more.
Thanks,
Mark
> Index: ehci_fdt.c
> ==
> Date: Tue, 06 Feb 2024 22:37:50 +0900
> From: SASANO Takayoshi
>
> Hello,
>
> I am working for H616 since OrangePi Zero2...
>
> Here's the diff. sximmc.c is reconstructed.
Hi,
> Index: ehci_fdt.c
> ===
> RCS file: /cvs/src/sys
> Date: Tue, 06 Feb 2024 22:37:50 +0900
> From: SASANO Takayoshi
>
> Hello,
>
> I am working for H616 since OrangePi Zero2...
>
> Here's the diff. sximmc.c is reconstructed.
Hi Takayoshi,
Apologies; seems I have missed your earlier mails about H616.
I'd like to take a closer look at the ehci
> From: Tobias Fiebig
> Date: Mon, 05 Feb 2024 22:46:41 +0100
Hi Tobias,
> Moin,
> i got my hands on a small stack of OrangPi Zero 3 2GB.
>
> After having a working Armbian setup, i thought i'd
> give OpenBSD 7.4 a go. I borrowed the DTB and uboot from my
> armbian builds, and prepared a miniro
> Date: Tue, 30 Jan 2024 13:10:46 +
> From: Stuart Henderson
>
> On 2024/01/29 23:37, Krystian Lewandowski wrote:
> > Just made a dumb attempt to boot OpenBSD 7.4 on a Raspberry Pi 5, and
> > thought I may share if anyone was wondering.
> >
> > Maybe with newer u-boot? I'm not even sure wha
Yesterday I committed apldcp(4) and apldrm(4). Together these drivers
provide KMS (kernel mode setting) for the display subsystem on Apple
M1/M2 machines. These drivers rely on up-to-date apple-boot firmware.
If you're not using sysupgrade(4) to update, you'll need to run the
following commands b
> Date: Tue, 26 Dec 2023 12:57:06 +0100
> From: Mizsei Zoltán
>
> Next issue:
>
> I have a USB drive with OpenBSD 7.4 ARM64 already installed. I copied the dtb
> file to the EFI partition, and now i can boot OpenBSD from the USB reliable.
> However there is a main differece: in BSD.MP the eMMC
> Date: Thu, 21 Dec 2023 17:26:36 +0100
> From: Patrick Wildt
>
> On Thu, Dec 21, 2023 at 01:29:32PM +, Miod Vallat wrote:
> > > Hello Miod,
> > >
> > > Thank you for your reply.
> > >
> > > It would appear that, at least in my case, /dev/tty00 is not mapped to
> > > any driver.
> >
> > Oo
> Date: Mon, 27 Nov 2023 09:33:30 +0100
> From: Mizsei Zoltán
>
> Interestingly console input works in UKC but not in the install prompt.
> Possibly UKC still uses the serial console initialised by U-Boot and
> the Installer prompt is after OBSD takes over and re-initializes the
> serial port. St
> Date: Thu, 23 Nov 2023 13:18:21 -0500
> From: Ian Darwin
>
> Anybody got OpenBSD running on this box yet? Tiny little RK3568 box with
> 4 network ports (2@2.5Gb+2@1Gb), 4 USB, Wifi, 4K HDMI out.
>
> https://media.digikey.com/pdf/Data%20Sheets/Seeed%20Technology/102110777_Web.pdf
>
There isn
se boards really become usable.
> On Tuesday, February 21st, 2023 at 06:32, Mark Kettenis
> wrote:
> > Since several folks asked me in private about the rk3588, here is a
> > little teaser. This is with a hacked up U-Boot and a hacked up device
> > tree, so not
> Date: Fri, 12 May 2023 20:45:43 +0900
> From: SASANO Takayoshi
>
> Hi,
>
> We have to enable axppmic on i2c/rsb bus to use ethernet
> on OrangePi One Plus (Allwinner H6),
>
> GENERIC is already supported but RAMDISK not yet.
>
> ok to fix?
ok kettenis@
> Index: RAMDISK
>
> From: Patrick Wildt
> Date: Mon, 8 May 2023 14:14:27 +0200
>
> > Am 07.05.2023 um 19:54 schrieb Klemens Nanni :
> >
> > On Sun, May 07, 2023 at 06:30:55PM +0200, Mark Kettenis wrote:
> >> As I've said before, the u-boot developers have poor quality co
> Date: Sun, 7 May 2023 17:54:17 +
> From: Klemens Nanni
>
> On Sun, May 07, 2023 at 06:30:55PM +0200, Mark Kettenis wrote:
> > As I've said before, the u-boot developers have poor quality control
> > and this will almost certainly break some targets.
> >
> Date: Sat, 6 May 2023 17:36:53 +0200
> From: Patrick Wildt
>
> On Fri, Nov 18, 2022 at 12:53:44PM +, Klemens Nanni wrote:
> > On Mon, Nov 14, 2022 at 11:37:05PM +0100, Patrick Wildt wrote:
> > > Hi,
> > >
> > > the u-boot and dtb ports haven't been updated in a while, mostly because
> > >
> Date: Sun, 7 May 2023 11:27:09 +0300
> From: kodcode
>
> Hello,
>
> I've installed on a SD card OpenBSD 7.3 on a OrangePI PC.
>
> This are the steps I took:
> dd if=miniroot-am335x-7*.img of=/dev/rsdXc
> mount /dev/sdXi /mnt
> cp /usr/local/share/dtb/arm/sun8i-h3-orangepi-pc.dtb /mnt/
> umoun
> Date: Tue, 21 Feb 2023 20:12:46 +0100
> From: Jan Stary
>
> This is current/arm64 on MacBook Air (dmesg below).
> The machine seems to be _losing_ battery charge even when on AC.
> I have been watching sysctl hw for a few minutes (also below):
>
> hw.sensors.aplsmc0.amphour0=0.20 Ah (remaining
Since several folks asked me in private about the rk3588, here is a
little teaser. This is with a hacked up U-Boot and a hacked up device
tree, so not ready for normal users yet. But this Rock 5B is running
multi-user.
OpenBSD 7.2-current (GENERIC.MP) #47: Mon Feb 20 22:11:33 CET 2023
kett
> Date: Tue, 31 Jan 2023 23:40:03 +0100
> From: Mark Kettenis
>
> > From: Edward Vielmetti
> > Date: Tue, 31 Jan 2023 09:22:29 -0500
> >
> > Thanks to @phessler@bsd.network (Peter Hessler) for
> > the pointer to the group.
> >
> > By
> From: Edward Vielmetti
> Date: Tue, 31 Jan 2023 09:22:29 -0500
>
> Thanks to @phessler@bsd.network (Peter Hessler) for
> the pointer to the group.
>
> By way of introduction, I worked on the "Works on Arm"
> project at Packet (and then Equinix) for a couple of years,
> doing platform enablemen
> Date: Sun, 22 Jan 2023 20:47:03 +0900
> From: SASANO Takayoshi
>
> Hi,
>
> Two issues.
>
> 1. I am trying to build ATF v2.8 with modified ports' Makefile.
>
> Only A64's ATF fails to build with follwing errors:
>
> aarch64-none-elf-ld.bfd: address 0x500dd of /usr/ports/pobj/arm-trusted-fir
> Date: Thu, 26 Jan 2023 23:37:31 +0100
> From: Jan Stary
>
> Ah, sory for the noise: I had AUDIODEVICE set up in /etc/profile
> to point to another machine (before audio started working on this macbook),
> which I only realized now that _that_ machine is up :-)
>
> Recording still doesn't work
> From: Lwazi Dube
> Date: Wed, 4 Jan 2023 12:21:16 -0500
>
> I am trying to install this:
> https://cdn.openbsd.org/pub/OpenBSD/snapshots/armv7/
> I want my rootfs on sd1. The bootloader can live on the MMC - I know I
> have no choice.
Here are basically your options:
* Wipe your uSD-card and
> Date: Fri, 2 Dec 2022 18:44:27 +
> From: Peter Stuge
>
> Jan Stary wrote:
> > > > > Replacing the DTBs with those from the dtb package is not supposed to
> > > > > work.
> >
> > Is this specific to the Raspberry, or is that true in general?
>
> I think this was specifically in response to
Joel Carnat reported that using both disk slots of the ODROID-HC4
doesn't work with OpenBSD. I never tried that in mine, but could
indeed reproduce the issue.
The machine seems to hang on doing disk I/O, so I started looking at
interrupts. PCIe interrupts on this machine have always been fishy.
> From: Justin Yang
> Date: Fri, 25 Nov 2022 09:19:42 +0800
>
> Hi,
>
> I'm now considering to purchase a NanoPi R5S board to run OpenBSD, which is
> listed on "Supported Hardware" on OpenBSD arm64 page. However, I could not
> find more details, for instance, should I flash u-boot manually? Ther
> Date: Fri, 25 Nov 2022 00:52:24 +
> From: Peter Stuge
>
> Jan Stary wrote:
> > Here is the cpsw problem:
> >
> > -cpsw0 at omsysc46: version 1.12 (0), address 90:59:af:82:2e:7e
> > +cpsw0 at omsysc46: version 1.12 (0), address 00:00:00:00:00:00
>
> I confirm this on beaglebone black but I
> Date: Tue, 22 Nov 2022 14:40:06 +0100
> From: Jan Stary
>
> On Nov 22 13:52:52, h...@stare.cz wrote:
> > On Nov 14 23:37:05, patr...@blueri.se wrote:
> > > the u-boot and dtb ports haven't been updated in a while, mostly because
> > > updating those regularly breaks working machines. I think i
> Date: Fri, 18 Nov 2022 17:15:30 +0100
> From: Mark Kettenis
>
> > Date: Fri, 18 Nov 2022 14:36:18 +0100
> > From: Jan Stary
> >
> > On Nov 18 12:51:32, mark.kette...@xs4all.nl wrote:
> > > > Date: Fri, 18 Nov 2022 12:19:46 +0100
> > > >
> Date: Fri, 18 Nov 2022 14:36:18 +0100
> From: Jan Stary
>
> On Nov 18 12:51:32, mark.kette...@xs4all.nl wrote:
> > > Date: Fri, 18 Nov 2022 12:19:46 +0100
> > > From: Jan Stary
> > >
> > > On Nov 17 14:44:59, h...@stare.cz wrote:
> > > > This is a freshly installed current/arm64 on a MAcBook
> Date: Fri, 18 Nov 2022 12:53:44 +
> From: Klemens Nanni
>
> On Mon, Nov 14, 2022 at 11:37:05PM +0100, Patrick Wildt wrote:
> > Hi,
> >
> > the u-boot and dtb ports haven't been updated in a while, mostly because
> > updating those regularly breaks working machines. I think it's time for
>
> From: Patrick Wildt
> Date: Thu, 17 Nov 2022 15:51:28 +0100
>
> If it wasn‘t supported, it wouldn‘t be able to know which firmware
> to load. I‘d say the manpage needs updating. The code should do, I‘m
> not sure how the firmware install situation looks like. kettenis@
> should know better!
Th
> Date: Fri, 18 Nov 2022 12:19:46 +0100
> From: Jan Stary
>
> On Nov 17 14:44:59, h...@stare.cz wrote:
> > This is a freshly installed current/arm64 on a MAcBook Air,
> > model 2337 (M1, 2020); full dmesg below.
>
> Upgrading the co-existing macOS to 12.6.1
> seems to have brken the working bsd
> Date: Wed, 16 Nov 2022 23:20:01 +0100
> From: Joel Carnat
>
> Hello,
>
> I have plugged a second disk in my ODROID HC4. The idea was to
> backup the data from sd0 to sd1 using rsync. So I stopped OpenBSD,
> inserted the second disk and rebooted. Then I formatted sd1, mounted
> it and started a
> From: Jan de Kruyf
> Date: Mon, 14 Nov 2022 20:29:08 +0100
>
> Jazzi, the driver is not configured, but that says nothing about
> whether the kernel or who-ever can speak to it.
> What you saw at netBSD is that the configuration is now done with the aid
> of the device tree file.
>
> That the
> Date: Fri, 4 Nov 2022 13:40:35 +0100
> From: Jan Stary
>
> On Nov 04 13:14:31, mark.kette...@xs4all.nl wrote:
> > The device names used by the bootloader differ from the names used by
> > the kernel. What gets printed as bootdevice/bootfile here is simply
> > the string that the bootloader pas
> Date: Fri, 4 Nov 2022 12:59:13 +0100
> From: Jan Stary
>
> On Nov 02 21:18:03, h...@stare.cz wrote:
> > This is current/armv7 on a BeagleBone Black, dmesg below.
> > The booting sequence ends with
> >
> > sd0 at scsibus0 targ 1 lun 0: removable
> > sd0: 1832MB, 512 bytes/sector, 3751936 s
> From: Jan de Kruyf
> Date: Tue, 1 Nov 2022 20:48:07 +0100
>
> > Hope that helps,
>
> No, let me show you what happens after the u-boot on mmc0 (just blank
> otherwise)
> ---
> Hit any key to stop autoboot: 0
> switch to partitions #0, OK
> mmc0 is current device
> Scanning mmc 0:1...
> l
> Date: Thu, 3 Nov 2022 01:33:03 +0100
> From: Joel Carnat
>
> Hello,
>
> Le 11/10/2022 à 01:48, Joel Carnat a écrit :
> > Le 10/10/2022 à 14:44, Mark Kettenis a écrit :
> >>> Date: Mon, 10 Oct 2022 14:14:49 +0200
> >>> From: Joel Carnat
> >
> From: Jan de Kruyf
> Date: Fri, 28 Oct 2022 15:35:09 +0200
>
> Hi,
> I am running armv7/7.2 on this board.
> This is how I got it to run:
>
> from one of the images at
>
> https://images.olimex.com/release/a20/
>
> you extract
> /usr/lib/linux-image-5.10.105-olimex/sun7i-a20-olinuxino-lime2.
> Date: Mon, 10 Oct 2022 14:14:49 +0200
> From: Joel Carnat
>
> Le 09/10/2022 à 18:50, Mark Kettenis a écrit :
> >> Date: Sun, 9 Oct 2022 17:54:51 +0200
> >> From: Joel Carnat
> >>
> >> Hello,
> >>
> >> As it was referenced o
> Date: Sun, 9 Oct 2022 17:54:51 +0200
> From: Joel Carnat
>
> Hello,
>
> As it was referenced on the arm64 web page, I bought a Hardkernel
> ODROID-HC4 to run OpenBSD. The thing is, I can't boot the OpenBSD
> installer at all.
>
> I have successfully ran an armbian instance from the microSD
Op 21-08-2022 10:22 schreef Otto Moerbeek :
On Sun, Aug 21, 2022 at 08:51:03AM +0200, Mark Kettenis wrote:
Op 20-08-2022 21:19 schreef Nick Holland :
On 8/20/22 09:50, Quattroporte wrote:
Hello arm@openbsd, I would like to install -current on the
internal ssd that has macOS
Op 20-08-2022 21:19 schreef Nick Holland :
On 8/20/22 09:50, Quattroporte wrote:
Hello arm@openbsd,
I would like to install -current on the internal ssd that has
macOS. I am a little unclear as to what disk choice I should make
in the installer. The Asahi docs say choosing (W)
> Date: Mon, 11 Jul 2022 18:28:22 +0200
> From: Anton Lindqvist
>
> On Mon, Jul 11, 2022 at 12:13:38PM +0200, Mark Kettenis wrote:
> > > Date: Wed, 06 Jul 2022 15:45:05 -0500
> > > From: j...@entropicblur.com
> > >
> > > Hi all,
> > >
&g
> Date: Wed, 06 Jul 2022 15:45:05 -0500
> From: j...@entropicblur.com
>
> Hi all,
>
> I had an unused Le Potato SBC lying around, so I took a crack at
> installing OpenBSD/arm64 on it. The board is similar to the supported
> ODROID-C4 and can boot the install kernel successfully, but there are
> Date: Sat, 18 Jun 2022 07:29:47 +
> From: Adam Steen
>
> Hi
>
> I have installed OpenBSD on my M1 Mac, see details and dmesg below.
>
> I am unable to change the resolution with xrandr
>
> $ xrandr --dpi 92
> grander: Failed to get size for gamma output.
All you get for now is a dumb fr
> From: Klaus Küchemann
> Date: Tue, 14 Jun 2022 00:00:55 +0200
>
> > Am 13.06.2022 um 23:44 schrieb Mark Kettenis :
> > ...
> > USB3 support (the "official"
> > CM4IO board does) ….
>
> cm4 official i/o reference board doesn’t include USB3
> Date: Mon, 13 Jun 2022 21:04:42 +0100
> From: Stuart Henderson
>
> On 2022/06/13 18:32, John M Trott wrote:
> > Good Afternoon,
> >
> > I have been trying to install OpenBSD 7.1 on to a Raspberry PI CM4, I
> > have read through the Mail archive and found my issue has already been
> > repo
=
RCS file: arch/arm64/dev/aplsart.c
diff -N arch/arm64/dev/aplsart.c
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ arch/arm64/dev/aplsart.c11 Jun 2022 19:27:57 -
@@ -0,0 +1,166 @@
+/* $OpenBSD$ */
+/*
+ * Copyright (c) 2022 Mark Kettenis
+ *
+ * Permission to use, copy, modify, a
> Date: Sun, 03 Apr 2022 23:13:48 +
> From: Joseph
>
> Hi ARM@,
>
> RockChip has upgraded the RK3399 (PCIe + 4GB RAM cap + 28nm lithography)
> with RK3588 (PCIe + 32GB RAM cap + 8nm lithography).
>
> It looks like a quite strong desktop computer/home/embedded server. It
> appears to me that
It has taken a while, but I'm pleased to announce that OpenBSD/arm64
works well enough on Apple M1 systems for some wider testing. A major
milestone was reached with the release of the Asahi Linux installer:
https://asahilinux.org/2022/03/asahi-linux-alpha-release/
This provides an easy way to
> Date: Thu, 6 Jan 2022 17:08:37 +0100
> From: Matyáš Vohralík
>
> Hello,
>
> my name is Matyáš Vohralík and I am a student of Faculty of Electrical
> Engineering, CTU, Prague, Czech Republic. And also a fan of OpenBSD project.
> I am currently working on my bachelor thesis about enhancing secu
> Date: Tue, 11 Jan 2022 20:13:59 +0900
> From: SASANO Takayoshi
>
> Hello.
>
> > I have a few more suggestions below. I think the other bits were
> > fine, but can you post the full diff with the fixes suggested below to
> > be sure?
>
> okay, I refelected your suggestion and attach the full
> Date: Sun, 09 Jan 2022 06:16:12 +0900
> From: SASANO Takayoshi
>
> Hello,
>
> > The com_read_reg() function returns a uint8_t, which means that only
> > the lower 8 bits of the CPR register are returned. So what you need
> > here is something like
> >
> > cpr = bus_space_read_4
> Date: Mon, 10 Jan 2022 18:35:05 +0100
> From: Patrick Wildt
>
> Am Mon, Jan 10, 2022 at 07:42:12PM +0900 schrieb SASANO Takayoshi:
> > Hi,
> >
> > To change AXP80x into RSB mode, put 0x7c value to register 0x3e.
> > The value defined RSB_DMCR_DEVICE_MODE_DATA in sxirsb.c works
> > 0x7e to the
1 - 100 of 293 matches
Mail list logo
