> 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: 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
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: 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
> 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: 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: 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: 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
> 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: 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
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
> 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
> 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
> 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.
>
The diff below removes the last board ID dependent code for the i.MX6
platform. It affects all boards that use a Micrel PHY, which would
show up as "ukphy0" in your dmesg. If you have such a board (udoo,
novena and sabrelight, there may be others), I'd apprciate if you
could test this diff and ch
> Date: Mon, 25 Jul 2016 10:58:09 -0300
> From: Daniel Bolgheroni
>
> On Thu, Jul 21, 2016 at 01:06:50PM +1000, Jonathan Gray wrote:
> >
> > Actually the pad configuration in those commits may mean this isn't
> > enough.
>
> Hi,
>
> I saw the r1.9 for if_fec.c and then it says it was tested on
Here are two diffs for the sunxi armv7 platform that I can't test
myself. The first one is for sxiahci(4), and changes it to use the
regulator API to power on the bus. The second one is for sxie(4), and
changes it to use the pinctrl API to select the appropriate pins.
If anybody with a Allwinner
> Date: Sun, 14 Aug 2016 13:59:00 +0200 (CEST)
> From: Mark Kettenis
>
> Here are two diffs for the sunxi armv7 platform that I can't test
> myself. The first one is for sxiahci(4), and changes it to use the
> regulator API to power on the bus. The second one is for sx
Hi John,
I fixed the sxie(4) tx watchdog issue yesterday. So new snapshots
should be working much better.
It is not really possible for us to provide install media for all the
different armv7 boards supported by our kernel. However, for the
boards in the "sunxi" family (such as the Cubieboard)
> From: John DiMarco
> Date: Tue, 13 Sep 2016 12:32:05 -0400
>
> In message <201609120838.u8c8cvhf002...@glazunov.sibelius.xs4all.nl> Mark
> Kettenis writes:
> >I fixed the sxie(4) tx watchdog issue yesterday. So new snapshots
> >should be working much better.
> Date: Sun, 18 Sep 2016 15:35:18 +1000
> From: Jonathan Gray
>
> On Wed, Sep 14, 2016 at 11:43:31PM +0200, Mark Kettenis wrote:
> > > From: John DiMarco
> > > Date: Tue, 13 Sep 2016 12:32:05 -0400
> > >
> > > In message <2016091208
> Date: Fri, 30 Sep 2016 12:49:43 +0100
> From: Stuart Henderson
>
> On 2016/09/30 12:32, Francisco Gaitan wrote:
> > Peter J. Philipp kindly donated me a Banana PI R1 to test, I have
> > successfully installed OpenBSD-current. Wifi works fine even without
> > connecting the antennas, ethernet dw
Plese stop sending large attachments. The lists will drop them, and
they're overflowing my inbox.
Thanks,
Mark
> From: "Luiz Gustavo dos S. Costa"
> Date: Thu, 24 Nov 2016 01:23:58 -0200
>
> 2016-09-30 7:32 GMT-03:00 Francisco Gaitan :
> > Hello arm@,
> >
> > Peter J. Philipp kindly donated me a Banana PI R1 to test, I have
> > successfully installed OpenBSD-current. Wifi works fine even without
> > con
those new trees have landed in u-boot yet. I any case I
decided to wait a bit for things to stablise in Linux-land.
commit f6ad0c701632a02ec03ea219394c14981abe7aab
Author: Mark Kettenis
Date: Sun Sep 18 17:49:05 2016 +0200
ARM: dts: sun8i: Enable pull-ups for bananapi-m2-plus SD slot
> From: "Luiz Gustavo dos S. Costa"
> Date: Wed, 28 Dec 2016 22:17:32 -0200
>
> 2016-12-23 21:26 GMT-02:00 Mark Kettenis :
> >
> > The H3 support is still somewhat under development. My H3-based
> > Banana Pi M2+ had similar sd/mmc issues which I tracke
> Date: Tue, 27 Dec 2016 22:42:15 -0200
> From: Daniel Bolgheroni
>
> OpenBSD 6.0-current (GENERIC) #0: Thu Dec 22 13:45:42 MST 2016
> bu...@armv7.openbsd.org:/usr/src/sys/arch/armv7/compile/GENERIC
> real mem = 536870912 (512MB)
> avail mem = 517820416 (493MB)
> warning: no entropy supplied
> Date: Sat, 8 Apr 2017 14:54:34 -0700 (MST)
> From: mordant47
>
> Hi,
>
> I've looked through here quite a bit, so I hope this hasn't been answered
> yet. I'm using a recent OpenBSD snapshot on a Banana Pi BPI-M1+. I've
> prepared the uSD card exactly per the instructions. The uSD image boots
>
> From: Laurence Rochfort
> Date: Sat, 15 Apr 2017 05:45:50 +
>
> How have the closed blob issues been overcome? I believed they were a
> blocker for support of the Pi?
It's never been a blocking issue.
The firmware that runs on the graphics core of the Pi is
closed-source. This isn't real
> From: Tuyosi T
> Date: Tue, 18 Apr 2017 03:02:04 +0900
>
> how about odroid ?
The Odroid-XU4, and almost certainly the Odroid-XU3 use a Samsung
Exynos5 SoC and are supported by OpenBSD/armv7. Only USB works, but
the onboard ethernet is ure(4), so that works as well. You need a
closed-source
> From: "Stephen Graf"
> Date: Sat, 22 Apr 2017 12:01:43 -0700
>
> Is the Raspberry PI Zero W a better choice to use with OpenBSD? Is there
> OpenBSD support for the onboard WIFI?
OpenBSD will not (ever) run on the Pi Zero as we target ARMv7 and up.
> I chose the CHIP device because of the neat
> Date: Mon, 01 May 2017 08:44:46 -0700
> From: lawgi...@nym.hush.com
>
> I periodically follow -current snapshots on a Banana Pi M1. Booting
> the May 1 2017 bsd.rd (saved as /bsd.rd.snap on a USB thumbdrive)
> has the following (USB?) errors and will not boot:
Thanks. We know about the proble
> From: Tuyosi T
> Date: Mon, 8 May 2017 17:36:06 +0900
>
> raspberry pi 3's openbsd arm can use SATA hard disk if i use a
> ***specific*** sata usb converter .
>
> are there anyone who uses banana pi M1's sata port which is directly
> connected sata harddisk ?
That works fine. I use a Samsu
> Date: Sun, 14 May 2017 14:15:10 -0400
> From: Patrick YU
>
> After a fresh installation on a Olinuxino A10 board, some devices under
> /dev isn't configured as in boot-up message, when they're there. Any
> advice what I can do next ?
>
> # ls -l pf* k*
> crw--- 1 root wheel6, 0
> Date: Mon, 19 Jun 2017 16:44:35 +
> From: Tinker
>
> On 2017-06-15 14:04, Stuart Henderson wrote:
> ..
>
> Aha. Have there been any new commits so that users(me etc.) should go
> test, and report kernel debugger output in case of any instability?
No; pmap hackers are in short supply and
A bit of dmesg pr0n. Same form-factor as the Raspberry Pi (fits in a
standard Pi case) but has real Gigabit Ethernet. The micro-SD card
slot works as well. Ethernet works as well, but needs an ifconfig up
and down after booting. Still working on the external USB ports,
which are unfortunately D
> From: "Stephen Graf"
> Date: Wed, 16 Aug 2017 14:45:30 -0700
>
> The big problem is that the ethernet device did not show up in OpenBSD,
> neither on the install nor on the built system.
>
> On linux the driver is sun8i-emac. Is there a driver for this interface on
> OpenBSD?
No driver yet;
> From: "Stephen Graf"
> Date: Thu, 17 Aug 2017 21:41:07 -0700
>
> Yesterday I was enjoying working with OpenBSD on my orange pi one.
>
> Today when I turned it on it would not boot properly with an error setting
> up the mmc:
>
> sximmc0: timeout updating clock
> sdmmc0: can't change bus clock
> From: "Stephen Graf"
> Date: Sat, 19 Aug 2017 18:29:59 -0700
>
> I continue to bang away at my orangepi one.
>
> Now my problem is how to set up the gpio. First off, the boot shows multiple
> gpio devices:
>
> ampintc0 at simplebus0 nirq 160, ncpu 4
> sxirtc0 at simplebus0
> gpio0 at sxipio0:
I just committed a change to the armv7 bootloader that makes it pass
the EFI memory map to the kernel. This will be used in the future to
avoid stomping on memory used for the firmware, framebuffers etc.
This change is incompatible with older versions of U-Boot. U-Boot
2017.03 that shipped with O
> From: "Stephen Graf"
> Date: Sat, 26 Aug 2017 11:58:58 -0700
>
> Thank you again for your suggestions. I tried to follow your example but it
> did not work out as expected.
> For some reason the gpioctl set command is not working at secure level 0 and
> without that it is impossible to do anyth
> Date: Sun, 27 Aug 2017 19:33:11 +0300
> From: Artturi Alm
>
> On Sun, Aug 27, 2017 at 07:26:19PM +0300, Artturi Alm wrote:
> > On Mon, Aug 21, 2017 at 10:18:04PM +0200, Mark Kettenis wrote:
> > > I just committed a change to the armv7 bootloader that makes it pass
> From: "Stephen Graf"
> Date: Mon, 28 Aug 2017 10:30:51 -0700
>
> I tied your suggested change with the following results.
> Not yet what I am thinking is correct.
> sxirtc0 at simplebus0
> A0 mux 7- skipping
> A1 mux 7- skipping
> A2 mux 7- skipping
> A3 mux 7- skipping
> A4 mux 2- skipping
>
I just committed a fix for the bug that Arturri noticed. And here is
a diff on top of that that hopefully makes it possible to configure
pins that have not been touched by the firmware or OpenBSD on the
newer Allwinner SoCs.
Can you try this? You may need to wait a bit for my commit to
propagate
Olivier Cherrier schreef op 2017-09-26 10:52:
Hi,
While trying to use a SATA disk with my Cubieboard2, it fails and
prints
repeatedly :
sxiahci0: stopping the port, softreset slot 31 was still active.
sxiahci0: stopping the port, softreset slot 31 was still active.
sxiahci0: stopping the port
Jonathan Gray schreef op 2017-09-28 05:02:
On Wed, Sep 27, 2017 at 10:56:44PM +0200, Patrick Wildt wrote:
So, first of all copying the dtb entries is not a good idea. The
reason
is that the phandles are gonna be all wrong and overriden, because
those
are _generated_ on compile time. As you c
Patrick Wildt schreef op 2017-09-27 23:11:
If you got your device tree correctly set up, maybe try this diff:
diff --git a/sys/dev/fdt/if_dwxe.c b/sys/dev/fdt/if_dwxe.c
index 85c5098af31..ce6a4e0f338 100644
--- a/sys/dev/fdt/if_dwxe.c
+++ b/sys/dev/fdt/if_dwxe.c
@@ -236,6 +236,7 @@ struct dwxe_d
Jonathan Gray schreef op 2017-09-28 09:51:
On Thu, Sep 28, 2017 at 09:34:49AM +0200, Mark Kettenis wrote:
Jonathan Gray schreef op 2017-09-28 05:02:
> On Wed, Sep 27, 2017 at 10:56:44PM +0200, Patrick Wildt wrote:
> > So, first of all copying the dtb entries is not a good idea. The
&
Myself schreef op 2017-10-03 16:00:
I would like to run OpenBSD on an odroid xu4 however it doesn't seem
that any of the arm ports support it specifically. Would it still be
possible to run it by using a generic Exynos port (assuming that
exists)
and adding the boot firmware to the image?
In
> From: "Stephen Graf"
> Date: Mon, 16 Oct 2017 13:44:51 -0700
>
> I am trying to get dwxe to run on an H3 device. I have run into a problem
> where dwxe cannot load the syscon register map. Could this be because dwxe
> runs before syscon in the boot process and syscon has not yet registered th
> Date: Thu, 26 Oct 2017 12:47:57 +0200
> From: Patrick Wildt
>
> On Mon, Oct 23, 2017 at 12:03:28PM -0700, Stephen Graf wrote:
> > Thank you for the advice. Yes that works, at least for the orange pi one.
>
> So, do things work for you now? You should send the full diff you're
> running with
> From: "Stephen Graf"
> Date: Tue, 10 Oct 2017 23:09:07 -0700
>
> Hi Mark,
>
> Have you had any time to look further at the sxipio driver changes required
> for H3 devices? As you noted in an earlier email, the H3 device initializes
> the configuration registers to all 1s, in contrast to the A
N_H3_EPHY_SHUTDOWN;
> +syscon |= SYSCON_H3_EPHY_SELECT|SYSCON_H3_EPHY_CLK_SEL;
> +if (OF_getproplen(sc->sc_node, "allwinner,leds-active-low")
> >= 0)
> + syscon |= SYSCON_H3_EPHY_LED_POL;
> +
> From: "Stephen Graf"
> Date: Tue, 12 Dec 2017 11:30:59 -0800
>
> I tested the new code on my orange pi one (H3) and it works for the most
> part. The communications works but the yellow LED that indicates line speed
> (I think) does not light up. I compared the code to my working version and
> From: Hannu Vuolasaho
> Date: Wed, 13 Dec 2017 21:51:43 +0200
>
> Hello!
>
> I have OpenBSD running on the RPi 3. Unfortunately SD card isn't supported
> so I run from USB stick like everybody else. My blazing fast USB stick is
> really slow on RPi :( So I have some motivation to scratch my it
> From: Vadim Zhukov
> Date: Sun, 17 Dec 2017 12:45:32 +0300
>
> Hi all.
>
> First, I have to sorry for likely stupid questions, I'm a totally
> newbie in the ARM world.
>
> I'm looking toward BeagleBone Enhanced -
> https://elinux.org/SanCloud:BeagleBoneEnhanced . And there are a few
> questio
> From: "Stephen Graf"
> Date: Thu, 14 Dec 2017 12:54:02 -0800
>
> My recent experience with the dwxe driver has emboldened me to look at the
> sxitwi driver again. A few months ago I worked with Artturi Alm to get the
> driver working with a driver he wrote for a BME280 sensor. At that time I
see things a bit more clearly.
>
> As I mentioned above there is an issue trying to use interrupts on system
> boot.
>
> -Original Message-
> From: owner-...@openbsd.org [mailto:owner-...@openbsd.org] On Behalf Of
> Stephen Graf
> Sent: Sunday, December 31, 2017 11:57 AM
&
s instead of spaces
when possible and not following our standards results in noisy diffs
that are harder to review.
Cheers,
Mark
> -Original Message-
> From: owner-...@openbsd.org [mailto:owner-...@openbsd.org] On Behalf Of Mark
> Kettenis
> Sent: Wednesday, January 3, 20
> Date: Sat, 6 Jan 2018 22:15:19 +0100
> From: Robert
>
> Hi,
>
> I tried to connect a USB-to-serial cable to a Banana Pi 1 USB port,
> but it caused no reaction. No detected device, no kernel or usbdevs
> output, nothing. Other USB devices work (so the USB ports seem to
> be fine). Same behav
Hi Folks.
I'm looking for somebody who can test a bootloader image on a
Firefly-RK3399 with the default firmware still on the eMMC. If you
have a board in that state, can you try to write the image at:
http://www.xs4all.nl/~sibelius/rk3399.fs
to an SD card and attempt to boot from it? I'm cu
> From: Heinrich Rebehn
> Date: Tue, 13 Feb 2018 17:57:32 +0100
>
> Hello List,
>
> I am trying to install current snapshot on a Raspberry 3 B. I have
> problems setting up the serial communication needed to access the
> installer. I connected the serial pins (6,8,10) to the serial port
> of my
> Date: Wed, 14 Feb 2018 13:08:20 -0700 (MST)
> From: Diana Eichert
>
> Do any of the developers have access to the following system?
>
> Gigabyte R270-T68 (rev. 100)
> http://b2b.gigabyte.com/ARM-Server/R270-T68-rev-100#ov
>
> It has qty 2 dual 48 core Cavium ThunderX CPUs.
>
> At work we hav
> 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: 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: 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: 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: 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: 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: 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, 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
> 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: 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
> 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
> 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
> 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
> 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: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
> 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
> 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
> 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
> 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
> 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(-)
>
>
> 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: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: 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,
201 - 293 of 293 matches
Mail list logo
