Attach ampintc/ampintcmsi0 early. Makes it possible to use qemu_arm64
U-Boot (which isn't aware of virtio devices) with root on pci ahci.
U-Boot 2018.01-00547-g651bfbd6dd (Jan 28 2018 - 13:00:19 +1100)
DRAM: 2 GiB
In:pl011@900
Out: pl011@900
Err: pl011@900
Net: No ethernet
semarie reported problems with running arm64 on qemu which turned
out to be triggered by the psci version call.
[ using 979488 bytes of bsd ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
Copyright (c) 1995-20
> Date: Sat, 27 Jan 2018 21:30:38 +0100
> From: Christian Weisgerber
>
> The nam2blk[] array contains MD mappings between block device names and
> major device numbers.
>
> This patch syncs the nam2blk entries with the bdevsw table, which
> is the definitive list of block devices supported on an
The nam2blk[] array contains MD mappings between block device names and
major device numbers.
This patch syncs the nam2blk entries with the bdevsw table, which
is the definitive list of block devices supported on an architecture.
This fixes the non-OpenBSD entries on arm64, removes obsolete
mentio
Thank you (for the quick response) and sorry if I was not as clear
as I should have been! what I meant and was hoping to find was
a source code debugger support, like gdb[1], where one can debug
a running kernel with full access to the source code in a gdb session
environment from a remote machine
On Sat, 27 Jan 2018 20:46:18 +0330, bijan wrote:
> does OpenBSD support on-line kernel debugging as FreeBSD does[1]?
Yes, see the ddb(4) manual page.
- todd
Hi! (Don't know if tech@ is the right place to ask such questions, just
hope it is)
does OpenBSD support on-line kernel debugging as FreeBSD does[1]?
The only document I managed to find was a fairly old one[2] by QEMU
over GNU/Linux but it seems kgdb(7) is removed since 6.2 (apparently
for not ev
Hi all,
Its my first time to contributing to a OpenBSD Project!
so ...
I have Atheros AR2425 Wi-Fi chip (MAC: 0xe2, PHY: 0x70) on my
FijitsuSiemens Laptop (U9210)
I'm trying to connect to my WPA2 wireless but my DMESG is like this:
> ath0: unable to reset hardware.
Please see an attachment
This brings the arm64 genassym.cf file a bit closer to what we have on
other architectures. No functional change.
ok?
Index: arch/arm64/arm64/genassym.cf
===
RCS file: /cvs/src/sys/arch/arm64/arm64/genassym.cf,v
retrieving revision
On Wed, Jan 24, 2018 at 11:27:51PM +, Tom Smyth wrote:
> Hello, Martin, Remi, All
> Im very excited about this feature, Thanks Martin,
> Please see Comments inline below
>
> On 23 January 2018 at 18:06, Remi Locherer wrote:
> > On Mon, Jan 22, 2018 at 04:23:59PM +0100, Martin Pieuchot wrote:
10 matches
Mail list logo