| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug#1: The GetStatus() function returns radically different pointers that
do not match any packets we transmitted. I think it might be pointing to
a copy of the packet or something. Since we do not transmit more than
one packet at a time, just wait for "anything".
Bug#2: The Receive() function takes a pointer and a length. However, it
either ignores the length or otherwise does bad things and writes outside
of ptr[0] through ptr[len-1]. This is bad and causes massive stack
corruption for us since we are receiving packets into small buffers on
the stack. Instead, Receive() into a large enough buffer and bcopy the
data to the requested area.
|
|
|
|
|
| |
box that I have. We have no EFI disk drivers yet anyway (maybe that is the
problem).
|
| |
|
| |
|
|
|
|
|
| |
We now talk to the memory and mmu instances directly rather than using the
OpenFirmware "claim" method.
|
|
|
|
| |
MFC after: 3 days
|
| |
|
|
|
|
| |
Most of them are not in a future tense already.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
cdrom support. This avoids having to distribute separate loaders.
|
|
|
|
|
|
|
|
| |
the actual code. Both use a ";" (not a ",") to delimit entries.
PR: 39679
Submitted by: Cyrille Lefevre <cyrille.lefevre@laposte.net>
MFC after: 3 days
|
| |
|
| |
|
|
|
|
|
| |
PR: i386/39085
Submitted by: David Yeske <dyeske@yahoo.com>
|
|
|
|
|
|
|
| |
Add definition of COMPILER_DEPENDENT_INT64 and also
fix definition of COMPILER_DEPENDENT_UINT64.
Pointed-out by: Michael Nottebrock <michaelnottebrock@gmx.net>
|
| |
|
| |
|
|
|
|
| |
ufs2 filesystems seems to work fine.
|
|
|
|
| |
to libi386, this issue was resolved already in a cleaner way.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
filesystem expands the inode to 256 bytes to make space for 64-bit
block pointers. It also adds a file-creation time field, an ability
to use jumbo blocks per inode to allow extent like pointer density,
and space for extended attributes (up to twice the filesystem block
size worth of attributes, e.g., on a 16K filesystem, there is space
for 32K of attributes). UFS2 fully supports and runs existing UFS1
filesystems. New filesystems built using newfs can be built in either
UFS1 or UFS2 format using the -O option. In this commit UFS1 is
the default format, so if you want to build UFS2 format filesystems,
you must specify -O 2. This default will be changed to UFS2 when
UFS2 proves itself to be stable. In this commit the boot code for
reading UFS2 filesystems is not compiled (see /sys/boot/common/ufsread.c)
as there is insufficient space in the boot block. Once the size of the
boot block is increased, this code can be defined.
Things to note: the definition of SBSIZE has changed to SBLOCKSIZE.
The header file <ufs/ufs/dinode.h> must be included before
<ufs/ffs/fs.h> so as to get the definitions of ufs2_daddr_t and
ufs_lbn_t.
Still TODO:
Verify that the first level bootstraps work for all the architectures.
Convert the utility ffsinfo to understand UFS2 and test growfs.
Add support for the extended attribute storage. Update soft updates
to ensure integrity of extended attribute storage. Switch the
current extended attribute interfaces to use the extended attribute
storage. Add the extent like functionality (framework is there,
but is currently never used).
Sponsored by: DARPA & NAI Labs.
Reviewed by: Poul-Henning Kamp <phk@freebsd.org>
|
|
|
|
|
| |
RB_MULTIPLE since this seems to be the easiest way to add these flags
for non-forth loaders etc.
|
| |
|
|
|
|
| |
Submitted by: ticso
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Sponsored by: DARPA & NAI Labs.
|
| |
|
|
|
|
| |
Sponsored by: DARPA & NAI Labs.
|
|
|
|
|
|
|
| |
Factor the ufs reading code out of the i386/boot2 loader so it can
be reused by for instance sparc64.
Sponsored by: DARPA and NAI Labs.
|
|
|
|
|
|
| |
Translators can ignore this commit.
MFC after: 2 weeks
|
|
|
|
|
|
| |
Translators can ignore this commit.
MFC after: 2 weeks
|
| |
|
|
|
|
|
| |
kernel text and data from the loader to the kernel, so that the tte format
is not part of the loader->kernel ABI.
|
|
|
|
| |
target, which conventiently moved it to loader.old, leaving no loader.
|
|
|
|
|
|
| |
CONSPEED -> COMSPEED
Approved by: nyan
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
this is called /boot/nextboot.conf. This file is required to have it's first
line be nextboot_enable="YES" for it to be read. Also, this file is
rewritten by the loader to nextboot_enable="NO"<space> after it is read.
This makes it so the file is read exactly once. Finally, the nextboot.conf
is removed shortly after the filesystems are mounted r/w.
Caution should be taken as you can shoot yourself in the foot. This is only
the loader piece. There will be a tool called nextboot(8) that will manage
the nextboot.conf file for you. It is coming shortly.
Reviewed by: dcs
Approved by: jake (mentor)
|
|
|
|
| |
Submitted by: Kaho Toshikazu <kaho@elam.kais.kyoto-u.ac.jp>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- Don't include ia64_cpu.h and cpu.h
- Guard definitions by _NO_NAMESPACE_POLLUTION
- Move definition of KERNBASE to vmparam.h
o Move definitions of IA64_RR_{BASE|MASK} to vmparam.h
o Move definitions of IA64_PHYS_TO_RR{6|7} to vmparam.h
o While here, remove some left-over Alpha references.
|
|
|
|
|
| |
style comments. This is not an attempt to conform to style(9).
Such has lower priority.
|
| |
|