search for: newbus

I'm trying to understand the newbus and acpi interactions on this Dell R620 that result in the Broadcom adapter board being probed "backwards" or just plain out of order in comparison to the connector layout and the linux tg3 driver. We seem to be detecting PCI0:2:0 before PCI0:1:0. This seems odd to me. When I replace t...

...@ -27,6 +27,8 @@ * */ +#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt + #include <linux/module.h> #include <linux/slab.h> #include <linux/pci.h> @@ -51,13 +53,13 @@ static struct bus_node * __init alloc_error_bus (struct ebda_pci_rsrc * curr, u8 struct bus_node * newbus; if (!(curr) && !(flag)) { - err ("NULL pointer passed\n"); + pr_err("NULL pointer passed\n"); return NULL; } newbus = kzalloc(sizeof(struct bus_node), GFP_KERNEL); if (!newbus) { - err ("out of system memory\n"); + pr_err("out of system...

...@ -27,6 +27,8 @@ * */ +#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt + #include <linux/module.h> #include <linux/slab.h> #include <linux/pci.h> @@ -51,13 +53,13 @@ static struct bus_node * __init alloc_error_bus (struct ebda_pci_rsrc * curr, u8 struct bus_node * newbus; if (!(curr) && !(flag)) { - err ("NULL pointer passed\n"); + pr_err("NULL pointer passed\n"); return NULL; } newbus = kzalloc(sizeof(struct bus_node), GFP_KERNEL); if (!newbus) { - err ("out of system memory\n"); + pr_err("out of system...

...@ -27,6 +27,8 @@ * */ +#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt + #include <linux/module.h> #include <linux/slab.h> #include <linux/pci.h> @@ -51,13 +53,13 @@ static struct bus_node * __init alloc_error_bus (struct ebda_pci_rsrc * curr, u8 struct bus_node * newbus; if (!(curr) && !(flag)) { - err ("NULL pointer passed\n"); + pr_err("NULL pointer passed\n"); return NULL; } newbus = kzalloc(sizeof(struct bus_node), GFP_KERNEL); if (!newbus) { - err ("out of system memory\n"); + pr_err("out of system...

FreeBSD is now, with the notable exception of suspend, a stable functionally complete domU on xen 3.0. I am currently in the process of adding dom0 support. Suspend support will be turned on as soon as the xenbus + newbus integration work goes in. It is unclear how much sense it would make to post a sparse tree as this is all being done in -CURRENT (the development branch). However, as soon as dom0 support goes in, xen support will be pulled into RELENG_6, and in all likelihood full xen support will go out with the...

Well this is new. I haven't a clue what Dell has done on this R620, but this popped up today after I did a boat load of BIOS updates and tried to install stable/9 from our yahoo tree. If anyone sees the obvious solution here, I'd love to figure it out. found-> vendor=0x14e4, dev=0x165f, revid=0x00 domain=0, bus=2, slot=0, func=1 class=02-00-00, hdrtype=0x00, mfdev=1

...ore that we have to resolve some issues with tcpdump and kame. _________________________________________________________________ PowerPC Port Contact: Peter Grehan <grehan@FreeBSD.org> Work has restarted after a hiatus. Current focus is on getting loadable modules working, NEWBUSing the NetBSD dbdma code, and completing the BMAC ethernet driver. There is a huge amount of work to do. Volunteers more than welcome! _________________________________________________________________ Release Engineering Status Contact: Scott Long <re@FreeBSD.org> The rel...

...on-Transparent Bridges allow the creation of memory windows between different systems using the regular PCIe links of CPUs as a transport. During the last quarter, the NTB subsystem gained a significant set of improvements and fixes: * The code was modularized, utilizing FreeBSD's NewBus interfaces to allow support for different hardware types with different drivers, support for multiple NTB instances in a system, using the ntb_transport module for consumers other than if_ntb, etc. * Support for splitting NTB resources between different applications...

...on-Transparent Bridges allow the creation of memory windows between different systems using the regular PCIe links of CPUs as a transport. During the last quarter, the NTB subsystem gained a significant set of improvements and fixes: * The code was modularized, utilizing FreeBSD's NewBus interfaces to allow support for different hardware types with different drivers, support for multiple NTB instances in a system, using the ntb_transport module for consumers other than if_ntb, etc. * Support for splitting NTB resources between different applications...