Age | Commit message (Collapse) | Author |
|
ELF image, assume it's the kernel and try to boot it immediately.
This allows a Gdium system with both the bootloader and the kernel image on
an ext2fs partition, with `al' pointing to the bootblocks and `rd' pointing
to the kernel in PMON environment, to boot a kernel with proper kernel
symbols, for the first time.
(please don't get me started on how reliable `load -k' is on the Gdium)
Bump bootblocks version to 0.2.
|
|
|
|
|
|
from the same sources with different CFLAGS; the need for this has not arisen
yet but I fear it will hit the fan soon enough; no functional change in the
meantime.
|
|
is received. The creation of a new node is already handled in
ieee80211_recv_probe_resp() when necessary.
This avoids creating empty nodes with wrong channels when beacons
are received on the wrong channel (overlapping channels).
Those empty nodes may also prevent the real node from being
discovered because of ieee80211_find_node_for_beacon() filtering.
This should prevent entries of the form:
nwid "" chan 3 bssid 00:01:02:03:04:05 0dB 54M
in "ifconfig if0 scan" output, like reported by Rivo Nurges.
|
|
bit on 6x50 if version>=6.
|
|
|
|
RAM work.
help and ok miod@
|
|
|
|
TEMPerHUM hardware. (It uses 3.38-3.48V as SHT1X's VDD).
mentiond by Michael Fuckner
|
|
ok sthen@ henning@
|
|
correct root device identification for Gdium (assuming it is booted from the
G-Key), although it will not attach as sd0 if there is anything connected to
the usb port next to the Ethernet port.
|
|
|
|
|
|
before transferring control to any binary, so trying to boot anything
on the Gdium without bringing half the kernel code is a no-go.
So, only keep `wd' as a possible boot device, for the Lemote systems,
and complain loudly if run on a Gdium.
|
|
|
|
From Brad, ok jsg@ kettenis@
|
|
|
|
|
|
|
|
is what the function pointer type uses.
ok grange
|
|
since it makes a fairly decent template for fdisk -i. Change the procedure
that makes the rb600 installation miniroot image to use fdisk -i instead of
dd(1) to create the MBR for the image. Adjust the miniroot disk type in
/etc/disktab to the slightly different layout that fdisk -i creates.
|
|
|
|
|
|
vice-versa, and do a full reset of the chip when it happens.
This does not affect the AR9280 since a full reset is always
necessary when the channel changes.
Should fix dual-band AR5416 devices (problem reported by Rivo Nurges).
|
|
- call athn_set_multi on SIOCADDMULTI/SIOCDELMULTI
|
|
do so during install.
|
|
|
|
|
|
load a kernel from the OpenBSD partition, with symbols.
However:
- does not work on gdium (usb i/o errors)
- no countdown due to PMON limitations, so either `bsd' in the PMON
environment contains a kernel filename to load, and it will get loaded
immediately, or it doesn't (e.g. the variable does no exist) and you get
a prompt and can pass options to the kernel. Note that /etc/boot.conf
commands can still be used in both cases.
- does not work for me when loaded automatically from PMON (put in the `al'
environment variable). However, `boot $al' works fine. Need to investigate.
|
|
|
|
|
|
To prevent PCI read or write bursts, we issue a read to a non-contiguous
register before accessing a register. This problem does not show up on
the x86 architecture since the memory model makes it almost impossible
to generate PCI bursts without doing DMA.
This bug is "documented" in the Ralink Linux driver as:
"//Patch for ASIC turst read/write bug, needs to remove after metel fix"
This fix makes the RT2561S chip on the Gdium (loongson) work.
It fails to load the firmware without it.
Tested by miod@ of the Gdium (slightly different diff though)
|
|
ok drahn
|
|
chunks from being reordered on an existing volume.
ok marco@
|
|
ok marco@
|
|
ok @marco
|
|
ok marco@
|
|
|
|
|
|
to the handler code in the kernel, we can use relative branches in it to
make it a bit faster.
Also, get rid of the tlbmiss handler and have both the tlb and xtlb refill
exceptions branch to the xtlbmiss handler.
|
|
layout.
|
|
|
|
|
|
|
|
|
|
while pmon is still available, and one for reset (in addition to the already
existing powerdown routine).
Add reset and powerdown code to the fuloong 2f platform; this also fixes
reset on yeeloong.
Tested by otto@
|
|
`looks right' drahn
|
|
This code is basically sys/arch/socppc/stand/mkboot/ but fixed to work
on little endian machines and extended slightly to allow specifying the
image OS and platform.
Input from drahn and kettenis.
ok kettenis
|
|
per-platform structs or function pointers; therefore bonito(4) no longer needs
to know about particular systems.
While there, bring little bits of Fuloong 2F support, tested on otto@'s
machine.
|