dev/ic/wd33c93.c. This may not be the best WD33C93 driver we've
got, but it's the most recently worked on and probably the most
portable, so it seems like a good basis for further work (and in
particular an acorn26 driver for the Acorn SCSI card). There's
no functional change in this commit, and sgimips kernels still
compile.
increase the number of retries by two orders of magnitude wont affect
most systems but will make transitions smoother on marginal ones.
From gwk@openbsd.
Modernise the linker script and make sure we have a symbol after the
link_sets.
Make sure that pmap_bootstrap doesn't tell uvm that some of the kernel
phys pages are free. Previously uvm would very likely allocate the phys
pages used for the link_sets to a MALLOC and they'd get overwritten.
Thanks to David H. Gutteridge for testing various things.
- remove unused code
- KNF
- ANSI function declarations
- replace printf() with aprint_error() except in debug functions
- a few minor indentation/whitespace changes
History: This cleans up another long standing inconsistency where timerblurb for delay() was
calibrated against the stat timer instead the clock timer. Before timecounters
this didn't matter at al as both timer run with the same frequency and the
calibration was a frequency based calibration.
Misbehaving clock found by Fanch (at) kekpar dot net on current-users@ - Thanks.
Fix verified to work by Fanch.
x86/include/powernow.h
- Protect k[78]_powernow_init() functions with #ifdef POWERNOW_K[78] to
make it build without these options.
This fixes the problem reported by hubertf.
interfaces ippp(4) and pppoe(4). Insufficient checking of options presented
by the peer may cause writing of copies of the malicious input beyond the
end of a buffer allocated for that purpose.
Issue found by pavel@
Fix from martin@
This is SA2006-019 (CVE-2006-4304)
Members of the thread group must die without reporting to the parent and
without going to zombie stage. We do that by reparenting to init before
catching a SIGKILL. The parent will not see the child death.
The thread group leader must report the exit status, even if it exits
because of another thread calling exit_group(). We do that by storing the
exit status in struct linux_emuldata_shared, and the exit hook has the
duty of setting struct proc's p_xstat for the thread group leader.
2) For exit/fork/exec hooks, move the NPTL specific code to separate functions
that are shared between COMPAT_LINUX and COMPAT_LINUX32
3) Fix LINUX_CLONE_PARENT_SETTID semantics
that callers are not responsible for initializing the fields. Store the name
inside the struct instead of maintaining a pointer to external storage, or
leaked memory (nfs case).
Place the securelevel checks in their logical locations.
This will be clearer in the future when code changes to use kauth(9) calls.
input and okay ad@
(1) failsafe.c allows character input from the failsafe
console device. This is the early console device that is used for output before
the pmap layer is initialized.
(1) locore.S: make sure that the size of the cacheline for
dcbz is set to the default of 128 bytes. It also sets up other mode bits on
the 970. This fix allows the G5 to boot into full multi user mode using a
NFS mounted root file system.
it was initialised quite late due to its reliance on disc data the mount
process could have stopped before initialising and thus could panic again
only now for uninitialising an not initialised pool! *sigh*
---
# XXX Disable zero-copy page loaning in sosend() temporarily:
# PV mappings created by sosend_loan() in sys/kern/uipc_socket.c may
# produce virtual cache aliases and it seems to cause TLB MISS panic
# in cache flush code called from bus_dmamap_sync(9) PREWRITE ops
# during heavy TX packet traffic on tlp(4).
user supplied a bad name or anamelen parameter to accept(2).
If bad paramaters were suplied and a copyout() failed, the
struct file was cleaned up but not the associated socket. This
could leave sockets in CLOSE_WAIT that could never be closed.
the same memory block allocated as before and it bombs out on its
descriptor pool allready being initialised. It turns out that the pool was
not allways destroyed. This fix ought to clean it up whatever the cause of
the mishap that results in a reject.
an Amiga DMA controller, and #if 0'ed WD33C93 definitions that are duplicated
in sbicreg.h. uPD71071 definitions can stay for now, since they're not
actually useless even though they're unused.
evidence that this is actually needed except for the existence of the
code itself, but if it's going to be here, it should compile. Tested
briefly on my ASUS motherboard with built-in sk interface.
the nearest one, rather than the first one with the same resolution. This
is likely to be useful when the bootloader finally passes a valid frame rate.
For now, it just favours flickery over non-functional.
While it can be made to compile, the paradigm is not quite right because
it attempts to contact the filesystem during autoconfig which sometimes
causes a panic. Even if that was fixed, there is another potential problem
in that the driver tries/sleeps/tries/sleeps and the sleep could
theoretically sleep past the rc.d/btconfig stage and the controller
would remain unconfigured.
So, I have prepared a different method for loading the firmware to
Broadcom BCM2033 chip based devices. A package 'sysutils/bcmfw' will load
the firmware files via a ugen(4) device interface.
This update removes the ubtbcmfw(4) driver and adds a table to the ubt(4)
driver so that it will not attach to Broadcom BCM2033 based devices before
the firmware was loaded.
This fixes kern/34219
we use the standard mode list from videomode.c rather than one generated
by makemodes.awk. This is less useful than it might be since without a useful
frame rate from the bootloader we're likely to end up choosing a screen mode
that's either flickery or too fast for the monitor (or DRAM bandwidth).
used for anything. Rearrange things so that it doesn't any more, and
just produces an array of struct videomode. modedefs.c is looking
suspiciously much like videomode.c now.
fixes and caveats:
- will switch to 32bit colour, 8bit support needs some more work
- added support for fonts with widths that aren't multiples of 8
- for now the driver will always try to become system console
- mode switching works but is ugly
- all the acceleration bits work
- X should work with wsfb, mmap() needs some more work
- it still needs a hack to allow wsdisplay_cnattach to be called twice
the kernel, removing an element from struct vidc_mode. The calculation
is a bit pointless at the moment anyway, since both bootloaders pass in
a constant 56, but that might get fixed one day.
struct videomode doesn't have a way to record border widths (though I
wonder if VESA's "margins" are the same thing), so we now just treat them
as zero. Tested on my NC, which still seems to be working.
Most of the testing was done on MIPS hardware -- it probably needs work before
it will be useful with x86 hardware, and it is probably incompatible with
the X11 server.
"ATI Technologies Inc. ("ATI") has not assisted in the creation of, and
does not endorse, this software. ATI will not be responsible or liable
for any actual or alleged damage or loss caused by or in connection with
the use of or reliance on this software."
Enjoy!
Attached diff let's call kauth_register_scope() with a NULL default
listener. from tn2127:
"callback is the address of the listener callback function for this
scope; this becomes the scope's default listener. This parameter may be
NULL, in which case a callback that always returns KAUTH_RESULT_DEFER is
assumed."
Setup cache bits in HID5 early on so that dcbz/icbi use the
128 byte cache line size. The mismatch was causing dynamically linked
apps to randomly coredump.
With this fix, the G5 can boot into full multi-user by using a NFS
mounted root file system.
to RiscBSD and had been lurking in dark corners scaring people (mostly me)
for far too long. It will be missed, but not much, and I hope we can clear
up any fallout before 5.0.
While I'm in the area, also remove rpckbd(4), since pckbd(4) has
been supported on acorn32 for ages.
253 of the superblock be zero. Searching the net failed to find any
justification for checking these bytes; all available references say
that they are part of the boot code and not BOOTSIG2 and BOOTSIG3.
Modify the MSDOS 7.1 bootsector definition to have 420 bytes of boot
code and no BOOTSIG[23], rather than 418 bytes of boot code, to follow
available references and apparent Windows practice. A test build
showed that these defines are not used other than in the check removed
by this commit.
Patch tested on netbsd-3, and enabled mounting of a 4 GB CF formatted
under Windows XP and then in a digital camera. The CF was previously
unmountable.
Concept approved on tech-kern by christos@ and martin@.
it had claimed while acting as the initial console device. This allows
(for example) vga to be the initial console, and an accelerated
framebuffer driver to take over later.
This support is not based on a datasheet, because a datasheet is not readily
available for this chip. However, Promise have partially open sourced their
driver for Linux, and all suggestions are that the PDC20771 is pretty similar
to other recent SATA chips.
The TX2300 has two ports, but there is unoccupied space on the board for a
third PATA port. It isn't entirely obvious how many channels the PDC20771 can
support.
The pdc205xx_drv_probe probe is necessary to avoid probing two wd* devices for
every physical device.
christos