Age | Commit message (Collapse) | Author |
|
sr_boot_assembly->readdisklabel->readdoslabel->biowait)
is what happens on late-cold architectures. something else has to be fixed
first before that is permitted, i guess.
|
|
ipx related files (doesn't compile anyway)
|
|
Note: this is a work in progress! this is under active development and
things will change.
prompted and ok deraadt
|
|
adosfs has the issue and in an entirely different way. noone uses this
code so this is hte best way to handle the problem
diff from pedro who went to sleep but we need to move ahead; ok thib
|
|
|
|
this type of code is implemented many times already in the kernel, this is
a generic version of all those replicated code bases.
originally from tedu@
ok tedu@ tom@ deraadt@
|
|
calculation until the problem is fixed, okay beck@ art@
|
|
|
|
|
|
of the existing code
|
|
decomissioned aeon ago. We will not miss it at all.
OK dlg@ henning@ and a lot of cheers by other in the room
|
|
|
|
prompted by/ok dlg@ deraadt@
|
|
deraadt@ dlg@.
|
|
grudgingly ok deraadt@
|
|
option. Every architecture implements mutexes now.
|
|
it is split up into a bus independant chunk (dev/ic/sli*) and the attach
glue (dev/pci/sli_pci.c) cos there are sbus varaints of this chip which i
hope to get my hands on one day.
this does nothing except attach to the LP8000 controllers.
|
|
|
|
|
|
were using some of their routines in the bcw driver, I decided to stop
working on it. To avoid any further license chit chat I plain drop the
driver.
|
|
silicon image 3124/3132/3531 sata chipsets eventually.
so far this is the autoconf glue, an actual match routine for the 3124, and
interrupt establishment code. it is split up between pci and ic cos there
are cardbus variants of these controllers that we can support in the
future.
thanks to jolan@ for the name, it was better liked than my initial
suggestion of siisl(4).
|
|
way, rather than requiring some glue in each machines mainbus probe.
it is still commented out.
based on a discussion with miod@ ok marco@ deraadt@
|
|
implementation of a RAID 1 is included in this but it does not deal with
failures yet. Disabled in GENERIC.
Suggestions from and ok beck@ miod@ krw@ dlg@ deraadt@
|
|
|
|
|
|
|
|
tree. ive lost two large changes today thanks to my own stupidity which
could have been avoided if they were in the tree.
discussed with deraadt@
ok jsg@ grange@ an older version was ok marco@
|
|
(this is in preparation for approaching GBC work)
|
|
|
|
driver from NetBSD
ok brad@ reyk@
additional testing Nick Nauwelaerts
|
|
using ovbcopy() in the erasecols emulop, as the ovbcopy implementation might
do larger-than-byte loads and store, which will not have the expected result
if the source and destination addresses are not similarly aligned.
Instead, roll our own byte-only ovbcopy() in this case. This is made dependent
on a config(8) attribute to avoid bloating platforms which do not need this,
thus frame buffers which may set RI_BSWAP in ri_flg need to depend on this
attribute.
Problem spotted by matthieu@ using tcsh on sparc64 console.
|
|
for PXA27x/Zaurus, not enabled yet; for dlg and dale :)
|
|
|
|
Broadcom BCM43xx chipset. Device attaches, but has no further
functionality yet.
The work has been done by Jon Simola <jsimola@gmail.com>, based on the
existing bce(4) code. He will continue to work on the driver and try
to make further progress.
ok deraadt@
|
|
|
|
The card correctly loads the firmware and it is possible to send a few
simple commands to the card but that's it. No packet are sent or received.
Only the Netgear WG511v2 cardbus card is tested.
A cheese fondue and a bigger amount of white wine was needed to make the
interrupts work -- until last night the driver was uploading the firmware
to fast and the card garbled the image without moaning. It took us a full
day and hundreds of test kernels to figure that out.
Joint work with mglocker@, fondue by mbalmer@
OK mglocker@, get it in deraadt@
|
|
|
|
|
|
|
|
ok deraadt@
|
|
|
|
referencing tb(4).
ok deraadt
|
|
ok deraadt@ jsg@
|
|
|
|
help from mickey@, "commit it" miod@
|
|
code. however, it is still cluttering up the kernel namespace a bit. it is
better gone.
ok claudio@
|
|
cleaner driver that supports more hardware.
|
|
so that things can use it; tested on all architectures; ok kettenis
|
|
ok brad@
|
|
ok deraadt
|