Hi Gonzo,
I got your patch of port mips
(http://lists.freebsd.org/pipermail/freebsd-current/2012-March/032182.html), in
which you noted that fbt, pid are not implemented.
Would you pls. explain the reason why fbt and pid aren't implemented?
If I want to use fbt and pid, what should I do ?
Guys,
I'm running into a build break that relates to the temporary files
that LLVM creates:
svl-junos-j019% cc --version
FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
Target: arm--freebsd10.0-gnueabi
Thread model: posix
On a build machine /tmp/b is a directory and created
On Feb 13, 2014, at 9:42 AM, David Chisnall david.chisn...@cl.cam.ac.uk wrote:
This looks like a bug, please file an llvm PR. The offending code seems to
be createUniqueEntity() in lib/Support/Unix/Path.inc, which does...
something. Something weird and convoluted that seems to try to
I have a server setup with FreeBSD-10.0-RELEASE. It has 3 Intel gigabit
network cards in it, em0, em1, and em2. I have multiple ezjails setup that
run various things.
One jail, called db, runs a postgresql database. It was my intention to
give it em0 all to itself. The other jails and host
Hi Michael,
I am curious if any progress has been made with regard to the automatic
enabling of serial consoles?
Nathan W checked in the base code for this in r260913. I'll make the
change to the amd64/i386 ttys file after some more testing.
later,
Peter.
This looks like a bug, please file an llvm PR. The offending code seems to be
createUniqueEntity() in lib/Support/Unix/Path.inc, which does... something.
Something weird and convoluted that seems to try to implement mkstemp() /
mkdtemp() in an incomprehensible way.
David
On 13 Feb 2014, at
On 2014-02-13 13:59, Preston Hagar wrote:
I have a server setup with FreeBSD-10.0-RELEASE. It has 3 Intel gigabit
network cards in it, em0, em1, and em2. I have multiple ezjails setup that
run various things.
One jail, called db, runs a postgresql database. It was my intention to
give it
On Tuesday, December 24, 2013 12:21:01 PM Roger Pau Monne wrote:
Xen PV guests doesn't have a lapic, so disable the lapic call in mca
initialization.
I think this is fine, but I wonder if it wouldn't be cleaner to have
lapic_enable_cmc() do the check instead. Where else do you check
On Tuesday, December 24, 2013 12:20:57 PM Roger Pau Monne wrote:
Change order of some of the services in the SI_SUB_INTR stage, so
that it follows the order:
- System intr initialization
- Xen intr initalization
- IO APIC source registration
This is ok.
--
John Baldwin
On Tuesday, December 24, 2013 12:21:00 PM Roger Pau Monne wrote:
Add a new event that will fire each time a PCI device is added to the
system, and allows us to register the device with Xen.
It's really hackish to make this PCI specific. OTOH, I can't think of a
good place to have a more
On Tuesday, December 24, 2013 12:20:59 PM Roger Pau Monne wrote:
Also disable a couple of ACPI devices that are not usable under Dom0.
Hmm, setting debug.acpi.disabled in this way is a bit hacky. It might
be fine however if there's no way for the user to set it before booting
the kernel (as
On Tuesday, December 24, 2013 12:20:58 PM Roger Pau Monne wrote:
Lower the quality of the MADT ACPI enumerator, so on Xen Dom0 we can
force the usage of the Xen mptable enumerator even when ACPI is
detected.
Hmm, so I think one question is why does the existing MADT parser
not work with the
On Tuesday, December 24, 2013 12:20:56 PM Roger Pau Monne wrote:
Use madt_setup_io (from madt.c) on Xen apic_enumerator, in order to
parse the interrupt sources from the IO APIC.
I would like to get opinions, but I think we should rename and move
madt_setup_io to io_apic.c.
It wouldn't be
On 08/02/2014 21:42, John Baldwin wrote:
On Tuesday, December 24, 2013 12:20:58 PM Roger Pau Monne wrote:
Lower the quality of the MADT ACPI enumerator, so on Xen Dom0 we can
force the usage of the Xen mptable enumerator even when ACPI is
detected.
Hmm, so I think one question is why does the
14 matches
Mail list logo
