| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
panel of the Xserve G4 and G5. The leds will provide an indication of the
system load slowing as the load climbs, and system health e.g. no
lights means its dead or in DDB.
Split some of the shared registers and clock divisors from i2s into
i2sreg.h while there nuke some evil C++ style comments.
Man page to follow shortly.
ok deraadt
|
|
|
|
is invalid now, it doesn't serve any purpose any more anyway since that is
the default. ok mcbride
|
|
|
|
for some reason, so i had some code in there that tried to guarantee that.
however, newly allocated mbufs and clusters are physically contiguous and
bigger than 128 bytes. therefore we dont need to do that check.
while here check if there is enough space in the fifo before trying to
fill any of it. this means we can skip dma syncs if we're not going to end
up writing anything in the fifo.
|
|
keep a list of used pkts in tht_pkt_list as well as free ones. add
tht_pkt_used which can be used to see if a tht_pkt_list is in use by
returning the head of the used list inside itself.
(ab)use this to drain the rx free fifo when the interface is brought down.
tht_rxf_drain pulls used pkts off, unmaps their mbufs, frees them, and then
returns the pkt to the free list. the whole tht_pkt_list can then be freed
safely.
|
|
more work coming soon.
kettenis@ ok
|
|
possible. it loops till it runs out of tht_pkts to use on the rx descriptor
free list, until it runs out of space in the fifo, or until it cant
allocate or map any more mbufs.
tht has a weird requirement that the first physical buffer in an sg list is
at least 128 bytes long. i have code that tries to guarantee that, but id
like someone else to look at it and tell me if its necessary or dumb.
|
|
the hardware. oops.
|
|
|
|
|
|
|
|
their dmamaps. so far it looks like the same thing can be used to look
after both the transmitted and recved packets.
this also adds code to allocate a list of them and set up their dmamaps,
some free list handling, and code to free them when you dont want them
anymore.
|
|
two u_int32_ts
|
|
a bit so theyre less offensive to my eyes. massage tht_rx_free a bit.
|
|
going to cause problems if they're not cleaned from time to time.
|
|
|
|
|
|
ok joris@ xsa@ jmc@
|
|
|
|
ok kettenis@
|
|
reminded by Stuart Henderson
ok jasper@
|
|
We're doing DMA transfers without interrupts or some other indication and
100 microseconds is not enough on my X40 and so the firmware gets corrupted.
Increasing it to 500 microseconds this should give us enough safety margin.
OK mglocker@
|
|
since time_t will have to be crank to 64 bits at some point in the
future. OK pedro@
|
|
|
|
do not manage a freelist ourselves, but release them in pmap_destroy().
|
|
will try to bring the interface up in the middle of it being brought down.
im sleeping in tht_down while waiting for the tx fifos to drain, so its
possible something else can enter the ioctl handler while that's happening.
|
|
brought up they allocate all four fifos and set the interface flags. when
theyre brought down they clear the flags, wait for the tx fifos to drain,
and then free all the fifos.
interrupts are not yet dealt with.
|
|
(From ray's code in sendbug(1))
- nuke cvs_exec() as it is not used anymore
Prompted by deraadt@ a few weeks ago.
OK ray@.
|
|
to reflect this;
whilst there i had to wrap -t in Xo/Xc to stop line split,
and i zapped some extra whitespace in usage();
fixes user/5441 from sthen
|
|
|
|
|
|
|
|
is up or not.
|
|
|
|
ifmedia about it.
im not sure what the point of the ifmedia goo is if the only link type we
support is "autoselect". using it to show the link state seems to be
easier than implementing that ioctl ourselves.
|
|
|
|
|
|
one phy on Sun ERI; gets rid of the duplicate phy on the blade1k.
tested by many, ok drahn@
|
|
From NetBSD, miod@ ok
|
|
From mickey. art@ ok
|
|
From mickey.
|
|
|
|
Replace nfs_kqinit() wich just calls lockinit with
RWLOCK_INITALIZER. Assorted cleanup.
ok tedu@
"reads good" art@
|
|
the first is the addition of handlers for the fifos. you can now check if
there the fifo is ready to be used, pre sync it for use, do many
incremental updates to it, then post sync it to tell the hardware that
you've done something. the ready, pre, and post funcs are done for both
the reader and writer fifos, but only updates to the writer fifos is
implemented so far.
the second change is the firmware loading. i needed the above changes to do
this, and i needed firmware loading to test them, so this change gets both.
so we have a mountroot hook (that was the half change) that allocates the
tx task fifo, reads the firmware from disk, and then pushes the firmware
onto the fifo. once that is done it spins till the firmware is ready, then
cleans up everything it allocated for loading the firmware.
this diff wont time out if anything goes wrong during fw_load. if anyone
wants to look at a nice way of doing it, please do.
|
|
using a static message structure. Similar diffs went into bgpd and ospfd.
|
