| Age | Commit message (Collapse) | Author |
|---|
|
from the individual drivers now that ether_ioctl() handles this.
Shrinks the i386 kernels by..
RAMDISK - 2176 bytes
RAMDISKB - 1504 bytes
RAMDISKC - 736 bytes
Tested by naddy@/okan@/sthen@/brad@/todd@/jmc@ and lots of users.
Build tested on almost all archs by todd@/brad@
ok naddy@
|
|
This should take care of the simpler ones (i.e., timeout values of
integer multiples of hz).
ok krw@, art@
|
|
committed over a rum(4) donated by Maxim Belooussov, thanks!
ok jsing@
|
|
Move calling ether_ioctl() from the top of the ioctl function, which
at the moment does absolutely nothing, to the default switch case.
Thus allowing drivers to define their own ioctl handlers and then
falling back on ether_ioctl(). The only functional change this results
in at the moment is having all Ethernet drivers returning the proper
errno of ENOTTY instead of EINVAL/ENXIO when encountering unknown
ioctl's.
Shrinks the i386 kernels by..
RAMDISK - 1024 bytes
RAMDISKB - 1120 bytes
RAMDISKC - 832 bytes
Tested by martin@/jsing@/todd@/brad@
Build tested on almost all archs by todd@/brad@
ok jsing@
|
|
ok miod@
|
|
ok miod@
|
|
with and ok jsing@
|
|
create just partitions 'i' -> 'l'. jsing@ had noted same discord.
|
|
looking for the place to write the disklabel, i.e. partoffp != NULL.
tested & ok jsing@
|
|
ok mglocker@
|
|
together with the previous commits by jsing@, OpenBSD/sgi does USB now.
ok jsing@ miod@
|
|
us to use sgivol on devices which have a sector size != DEV_BSIZE, such as
a CD drive.
ok miod@ krw@
|
|
accessors to OpenBSD/sgi.
ok miod@
|
|
ok miod@ jasper@
|
|
ok miod@
|
|
Prompted by jasper@
ok miod@
|
|
512) bytes; ffs is inextricably tied to using b_blkno and disklabel
always uses sectorsize units.
Thus use DEV_BSIZE units for all fields describing ffs filesystems
and convert to/from sectors where required. This enables the creation
and use of ffs filesystems on non-512 byte sectorsize devices.
This diff allows i386 and sgi (the two test platforms) to find
disklabels that are not on a sectorsize boundary. Same change to
further archs coming.
This is a no-op on 512-byte sectorsize devices.
This work triggered by jsing@'s need to create ffs filesystems on
sgi cdroms so we can create cdrom install media for sgi.
sgi testing by jsing@
ok jsing@ pedro@ "looks sane" beck@ weingart@
|
|
|
|
declaring another.
ok miod@
|
|
|
|
endianness conversion on pci bridges.
ok deraadt@ jsing@
|
|
developer documentation some time ago.
|
|
|
|
|
|
ok marco@ no objection miod@ need this for regress djm@ no objection krw@
|
|
ok jsing@
|
|
ok jsing@
|
|
restrict the memory allocation range in _dmamem_alloc().
|
|
ok deraadt@
|
|
ok deraadt@
|
|
Not sure what's more surprising: how long it took for NetBSD to
catch up to the rest of the BSDs (including UCB), or the amount of
code that NetBSD has claimed for itself without attributing to the
actual authors.
OK deraadt@
|
|
rely on this very soon.
|
|
shortly.
OK todd@
|
|
ok thib beck art
|
|
file copies to nfsv2 causes the system to eventually peg the console.
On the console ^T indicates that the load is increasing rapidly, ddb
indicates many calls to getbuf, there is some very slow nfs traffic
making none (or extremely slow) progress. Eventually some machines
seize up entirely.
|
|
biowait() reads that do *not* come from the buffer cache - we use the
B_RAW flag to identify these at art's suggestion - since it makes sense
and the flag was not being used. this just flags all these buffers with
B_RAW - biodone already ignores returned buffers marked B_RAW.
ok art@
|
|
|
|
than rolling our own load functions.
tested jasper@, feedback and ok miod@
|
|
glass console set comconsaddr to zero so we don't switch to serial when
com* attach.
spotted by jasper@, ok miod@
|
|
sgi.
|
|
contiguous 64MB DIMMs in a single 128MB one) are not reported as memory at
offset zero, but actually as duplicates of the first entry (which always
matches real memory).
If the DIMMs are set up in decreasing sizes, as recommanded by SGI, the
first entry will be configured at offset zero, so the existing code would
run fine.
If, however, you order your DIMMs in a different order, the first entry
might not be at offset zero, so the kernel will mess up its memory
information, which will cause random effects from simply misreported memory
sizes, to the inability to boot.
Fix this by strengthening the check for an empty bank.
Problem reported by Jason Bergstrom (bergie, bergie dot net), analysis
and fix by me.
|
|
tested by maja@
|
|
|
|
If it exists assume that the boot loader has provided a pointer to the end
of the symbol table. If it does not exist fall back to the previous
behaviour and expect that pointers to the symbol table have been provided
directly after the kernel.
ok miod@
|
|
ok dlg@
|
|
ok dlg@
|
|
Specify the serial configuration from within the MD code, rather than
passing things via macros. This will allow other platforms to more readily
change the serial console configuration.
Committing this so it actually gets tested.
ok dlg@
|
|
instead of 8-bit mono mulaw @ 8kHz.
this is just the infrastructure; no drivers are specifying a default
yet.
ok ratchov@, deanna@
|
|
|
|
|
