On Thu, Oct 18, 2012 at 08:06:17PM +0200, Jochen Kunz wrote:
I think he meant somthing different: The kernel collects messages in a
buffer. When the USB subsystem is up and running as a host, it attaches
a ucom(4) that was pluged in prior to boot. Then the kernel dumpes the
collected messages
Where can I find a description/discussion of the different strategies?
I think this question of mine is still open.
There must be some sort of information somewhere what the rationale behind
the different strategies is and what workload they are targeted at.
On Wed, 29 Feb 2012 15:02:46 +1100
Simon Burge sim...@netbsd.org wrote:
I did need to adjust the TRIMDEBUG printfs to use PRId64 instead of
lld to get it to compile on my amd64.
Thanks, I've done so in the version just committed.
One comment - the use of the name TRIM in the UFS layer could
I recently converted CSRG's SCCS repository holding the original BSD history
to a Subversion repository. As a derivative work of CSRG's code base, this
repository is available under the terms of the original UC Berkeley license.
You can browse the history at http://svnweb.freebsd.org/csrg/
John Baldwin j...@freebsd.org wrote:
I recently converted CSRG's SCCS repository holding the original BSD
history to a Subversion repository. As a derivative work of CSRG's code
base, this repository is available under the terms of the original UC
Berkeley license.
You can browse the
On Friday, October 19, 2012 3:00:13 pm Mindaugas Rasiukevicius wrote:
John Baldwin j...@freebsd.org wrote:
I recently converted CSRG's SCCS repository holding the original BSD
history to a Subversion repository. As a derivative work of CSRG's code
base, this repository is available under
(2012/09/28 1:57), SAITOH Masanobu wrote:
Hi.
(2012/09/27 2:59), Andy Ruhl wrote:
Hello all,
I posted this on port-arm a few weeks ago and I have someone helping
me look at it, but I figured I would post again.
My Seagate Dockstar has a panic with -current. The last time I built a
good
