Age | Commit message (Collapse) | Author |
|
|
|
pass a pre-processed array of fdt_reg structs. This means
that the drivers don't have to understand the cell properties
themselves but can rely on the 64-bit addr/size pairs.
ok kettenis@
|
|
ok jasper@
|
|
used in the fdt attach args and the device tree.
ok kettenis@
|
|
physical memory. This makes it possible to boot OpenBSD on platforms that
have physical memory start at address 0x00000000 as the EFI bootloader will
only attempt to load kernels at address 0x10000000 and above to work around
a bug in the u-boot EFI API layer.
ok patrick@
|
|
is always the serial console. With device tree enumeration, this order
is not given anymore. The serial console might now attach with a
different minor and has to be updated, otherwise there will be no
further output on the serial. Thus, re-create the i.MX6 console with
the correct minor number on attach.
ok jsg@, kettenis@
|
|
the device tree says. As a result many device trees encode it as active-high
when active-low is needed. For now just override the device tree.
ok jsg@, patrick@
|
|
Don't advertise a hyperthreaded CPU. This doesn't make a lot of sense now
as we only provide UP guest support. This, combined with the other CPUID
issues fixed, fooled NetBSD's topology enumeration code into thinking we
had an unsupportable core/thread/package configuration.
Also fixed the unsupported CPUID functions by returning 0 in the return
registers instead of leaving whatever trash happened to be there before
the call was made.
|
|
(including vcpu state dump) on failure to enter due to an incorrect
guest state.
Added as a debug facility when diagnosing interruptibility state
problems seen while testing NetBSD guest VMs.
|
|
on the default settings.
Noticed when booting a NetBSD guest VM.
|
|
with i.mx6 quad but with more memory bandwidth and some graphics tweaks.
ok kettenis@
|
|
interrupts-extended property is missing or not the size we expect.
Some dtbs implement a workaround for "ERR006687 ENET: Only the ENET
wake-up interrupt request can wake the system from Wait mode" suggested
by the IMX6DQCE errata document to set an undocumented gpio mux mode and
handle the interrupt via gpio.
We don't support gpio interrupts yet, hopefully this change is enough
to make interrupts work on wandboard and sabre lite again till we do.
Discussed with kettenis and patrick, tested on sabre lite by patrick.
|
|
ok patrick@
|
|
in pmap_free_l1().
from aalm@ - thanks
ok patrick@
|
|
least this is what Linux does and it fixes a hang on the Olimex A10s boards.
While there, also preserve the clock selection when reloading the timer.
ok patrick@, jsg@, tom@
|
|
didn't attach previously on OMAP4 with the static device configuration
and now do with the fdt. Like most of the other OMAP4 prcm cases
these don't do anything, hopefully we'll properly configure clocks with
data from the fdt at some point in the future.
Tested by abieber@ on PandaBoard-ES.
|
|
just use the pv_flags. ('Twas a copy-paste from arm's pmap_clean_page(),
which did need it.)
Also remove even less used flags variable from pmap_page_remove().
First part from a diff from aalm@ - thanks
ok kettenis@ "looks good" patrick@
|
|
be used to translate one memory address to another. Currently we just
pass the child's memory address to bus space map. If one of the parent
busses implements a ranges property, the child's address property is
not the real address. This change hooks up a bus space map function
that is aware of the ranges property and translates the addresses if
needed.
ok kettenis@
looks fine jsg@
|
|
device tree like we do on omap. Add preliminary support for the sun5i
variant which corresponds to the A13 and A10s SoCs.
ok patrick@
|
|
pinctrl-single,pins to handle mux settings and pad configuration.
The fdt data has offsets from the start of the pinmux address range so
the am335x specific pinmux offset from the scm base is added to the
offsets. This as not a new driver as sitaracm does manual table
driven pad configuration for gpio. If all the offsets in the
ti_padconf_devmap table were reduced by the am335x pinmux offset (0x800)
it may make sense to map only the pinmux memory region and not the
scm superset.
looks good kettenis@
|
|
|
|
ok kettenis@ on an earlier version
|
|
ok kettenis@
|
|
(reducing the number of XXXs in vmm)
|
|
|
|
They are unused and equivalent to disableintr() and setsr().
While here, clean up a few other leftovers.
|
|
s/names are this level/names at this level/
from aalm@ - thanks
|
|
ok jsg@
|
|
are handled during cpu hatch.
|
|
list storage size. Noticed when attempting to get vmm(4) to nest under
Hyper-V.
|
|
anyway due to a missing #include.
the code was originally intended to handle i386 SMP EISA machines with an
IOAPIC. Since the code never was compiled, and nobody has noticed or
complained for 12 years, I think things are probably fine.
|
|
|
|
clkbase to be set to 0 (if it wasn't all commented out anyway).
ok patrick@
|
|
ok krw@
|
|
issues can be worked out, otherwise this driver will cause the
kernel to spin forever on certain chromebooks
|
|
PHYs based on device tree properties instead of the board ID. Untested as
I don't have the hardware.
ok jsg@, patrick@
|
|
For MSI-X (and also possibly for other transports), the interrupt
handler must do different things. Move it out of virtio.c and into
virtio_pci.
ARM part tested by patrick@
|
|
Network VSC is an RNDIS device using NVSP protocol to communicate
with the Hyper-V VMBus via VMBus channels and/or shared memory. The
code was ported from FreeBSD with some API changes and simplifications.
While the Rx path is nearly complete, packet transmition is not
implemented yet.
ok deraadt, mlarkin
|
|
of the memory address and length information. The root node passes
this information down to the children and it can be overwritten by
other nodes inbetween. Pass these properties as part of the fdt
attach args, so that we can grab that information quickly inside
the drivers.
ok kettenis@
|
|
bus. For this only supports "fixed" regulators that are controlled through a
gpio. But this covers all the case we currently handle with board ID specific
code. Note that the old code did explicitly remove power first on some boards,
which would reset bus-powered devices/hubs on the bus. The new code doesn't do
this. If that causes problems we can revisit the issue. The boards that would
be affected are sabrelight/nitrogen6x and utilite.
The plan is to evolve this into a generic regulator framework that supports
more complex regulator types as well.
ok jsg@, patrick@
|
|
need to do it again.
|
|
such that we can don't end up with conflicting attachments of other
SoC-specific glue code.
|
|
|
|
such that we can don't end up with conflicting attachments of other
SoC-specific glue code.
ok jsg@, patrick@
|
|
hardcoding particular gpios based on board IDs.
ok visa@, jsg@
|
|
gpios based on board IDs.
ok visa@, jsg@
|
|
ok visa@, jsg@
|
|
In that case, soft fail and return instead of allocating buffer with
a bogus size.
ok kettenis@
|
|
|
|
|