| Age | Commit message (Collapse) | Author |
|---|
|
|
|
just not there.
ok jakemsr@ drahn@
|
|
Why this code, which must be executed, is not failing on disk is an utter
mystery. More investigation needed.
|
|
allowed to match on old gdium artwork, as newer artwork have nothing
connected to the usb pins, and this causes the empty bus probe to stall the
boot a few seconds.
|
|
but documentation for it only exists in Chinese. I still don't have the
slightest idea why flipping it is important, but I am more confident flipping
it now (-:
|
|
information and a few other things not yet wired.
|
|
|
|
No functional change.
|
|
|
|
|
|
by deraadt@
|
|
ok oga@, pirofti@
|
|
the kb3310b embedded controller chip on the yeeloong. With help & ok miod@
|
|
(1GB@1GB); that's the best we can do on 2F due to the way the crossbar
windows work.
Necessary for upcoming Fuloong2F changes.
|
|
|
|
timecounter.
|
|
where jumping to the "standard" video BIOS entry point locks up or even
resets the machine. This will break resume on some other machines in the
sense that the display on them will remain disabled. But hopefully those
machines make it into a state where the kernel is running and we can fix that.
ok deraadt@, marco@, mlarkin@
|
|
the preprocessor.
|
|
- remove some '//' commented code
ok ratchov, kettenis, edd
|
|
|
|
isn't currently doing so. Fixes hangs on large data transfers.
|
|
if it fires.
|
|
messages are usually lower case (exceptions are manufacturer codenames
as "Pentium" or "Horse").
|
|
|
|
(auglx.c is not modified in this commit yet, only moved around)
|
|
|
|
|
|
found on the Gdium Liberty. These machines finally no longer complain about
a missing todclock.
|
|
not only a framebuffer. Allow smfb to attach either at pci or at voyager.
Add gpio@voyager and gdiumiic@gpio, a derivative of the MI gpioiic driver.
This allows us to get lmtemp@iic on the Lemote; the next step being to
write a driver for the i2c todclock chip found on the same bus.
|
|
side effect, this change makes displayed messages shorter.
miod@ has observed that `Horse' is the codename of the chip, which
gets paired with a `Saddle' companion chip. there is one hose
(i.e., bus) per chip; others (`Tsunami') have two hoses per chip,
or even four (`Typhoon'); so, `Horse' is not really a typo.
written with clever advice from krw@ and miod@
miod@ has suggested the capitalization for `Saddle'.
ok krw@, miod@
|
|
a 64-bit version of the old ABI), which explains why these wrappers are needed.
Update comments to match reality, and make cpp write all the code of this file.
(``survival of the laziest'' motto)
Keep the misleading file name though (lazyness again)
|
|
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.
|
|
RAM work.
help and ok miod@
|
|
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.
|
|
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.
|
|
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.
|
|
|
|
|
|
ok drahn
|
|
|
|
|
