- 26 Jan, 2008 7 commits
-
-
Grant Likely authored
Prune back Efika fixups to only include changes that are actually required to get a working system. Most of the drivers can accept the compatible properties, even if they don't match the what is recommented in the generic names recommended practice document. This patch also adds extra checks so that fixups are not performed blindly. Instead, the code first verifies that the device tree is faulty before making any changes. This way, if the Efika firmware is updated to fix these issues, then the fixups will no longer get applied. At this point; here is the list of fixups needed for the efika: 1. If the device_type property on the root node is 'chrp', then Linux won't boot. Change device_type to 'efika' to avoid this condition 2. Add full interrupt list to the bestcomm node. In actual fact, the bestcomm interrupts property is technically correct, it just doesn't expose the same granularity as the device driver expects. All other 5200 device trees provide a separate irq number for each bestcomm channel. Rather than hack the driver, it's simpler to fix it up 3. /builtin/sound node is missing an interrupts property 4. /builtin/ethernet node is missing a phy-handle property and the device driver doesn't know what to do without one. Signed-off-by:Grant Likely <grant.likely@secretlab.ca>
-
Grant Likely authored
Modify mpc5200 dts files to match Open Firmware's Generic Names recommended practice. Signed-off-by: -
Grant Likely authored
Update MPC5200 drivers to also look for compatible properties in the form "fsl,mpc5200-*" to better conform to open firmware generic names recommended practice as published here: http://www.openfirmware.org/1275/practice/gnames/gnamv14a.html This patch should *not* break compatibility with older device trees which do not use the 'fsl,' prefix. The drivers will still bind against the older names also. Signed-off-by:
-
Grant Likely authored
Put all the mpc5200 board config option behind a menu item to get them out of the top level of the platform support list Signed-off-by: -
Paul Gortmaker authored
The various 5200 dts files don't have values specified for the soc node, which in turn results in a warning from the processing of every child node (roughly 40 warnings per file). This explicitly sets the default values and gets rid of all the warnings. Signed-off-by:
Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by:
-
Paul Mackerras authored
This reverts commit 5c3f5892, basically because it changes behaviour even when no fake NUMA information is specified on the kernel command line. Firstly, it changes the nid, thus destroying the real NUMA information. Secondly, it also changes behaviour in that if a node ends up with no memory in it because of the memory limit, we used to set it online and now we don't. Also, in the non-NUMA case with no fake NUMA information, we do node_set_online once for each LMB now, whereas previously we only did it once. I don't know if that is actually a problem, but it does seem unnecessary. Signed-off-by:
Paul Mackerras <paulus@samba.org>
-
Paul Mackerras authored
-
- 25 Jan, 2008 33 commits
-
-
Roel Kluin authored
logical/bitand typo Signed-off-by:
Roel Kluin <12o3l@tiscali.nl> Signed-off-by:
Josh Boyer <jwboyer@linux.vnet.ibm.com>
-
Sean MacLennan authored
Add the defconfig for the PIKA Warp board Signed-off-by:
Sean MacLennan <smaclennan@pikatech.com> Signed-off-by:
-
Sean MacLennan authored
Add the cuboot wrapper for the PIKA Warp board Signed-off-by:
-
Sean MacLennan authored
Add the device tree for the PIKA Warp board Signed-off-by:
-
Sean MacLennan authored
Add the base platform support for the PIKA Warp boards. Signed-off-by:
-
Sean MacLennan authored
This adds the 440EP revision C PVR to the CPU table. The chip has an FPU on it, so we also match the logical PVR Signed-off-by:
-
David Gibson authored
This patch extends the Ebony and Walnut platform code to instantiate the existing ds1742 RTC class driver for the DS1743 RTC/NVRAM chip found on both those boards. The patch uses a helper function to scan the device tree and instantiate the appropriate platform_device based on it, so it should be easy to extend for other boards which have mmio mapped RTC chips. Along with this, the device tree binding for the ds1743 chips is tweaked, based on the existing DS1385 OF binding found at: http://playground.sun.com/1275/proposals/Closed/Remanded/Accepted/346-it.txt Although that document covers the NVRAM portion of the chip, whereas here we're interested in the RTC portion, so it's not entirely clear if that's a good model. This implements only RTC class driver support - that is /dev/rtc0, not /dev/rtc, and the low-level get/set time callbacks remain unimplemented. That means in order to get at the clock you will either need a modified version of hwclock which will look at /dev/rtc0, or you'll need to configure udev to symlink rtc0 to rtc. Signed-off-by:
David Gibson <david@gibson.dropbear.id.au> Signed-off-by:
-
Stefan Roese authored
The patch adds the Haleakala dts. The Haleakala is a stripped down version of the Kilauea (405EX) with only one EMAC and only one PCIe interface. Signed-off-by:
Stefan Roese <sr@denx.de> Signed-off-by:
-
Stefan Roese authored
This patch adds the 405EXr to the powerpc cuptable. Basically the 405EXr is a 405EX with only one EMAC and only one PCIe interface. Signed-off-by:
-
Olaf Hering authored
Signed-off-by:
Olaf Hering <olaf@aepfle.de> Signed-off-by:
-
Olaf Hering authored
Commit 6d98bda7 changed the init order for chrp_pci_fixup_vt8231_ata(). It can not work anymore because either the irq is not yet set to 14 or pci_get_device() returns nothing. At least the printk() in chrp_pci_fixup_vt8231_ata() does not trigger anymore. pata_via works again on Pegasos with the change below. Signed-off-by:
-
Michael Ellerman authored
Currently the IOMMU code allocates one page for the segment table, that isn't safe if we have more than 132 GB of RAM. Signed-off-by:
Michael Ellerman <michael@ellerman.id.au> Acked-by:
Jeremy Kerr <jk@ozlabs.org> Signed-off-by:
-
Michael Ellerman authored
Since commit c80d9133 (Make direct DMA use node local allocations) went in this comment makes no sense. Signed-off-by:
Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by:
-
Michael Ellerman authored
We no longer need the global dma_direct_offset, update the comment to reflect the new reality. Signed-off-by:
-
Michael Ellerman authored
Rather than using the global variable, have celleb use its own variable to store the direct DMA offset. Signed-off-by:
-
Michael Ellerman authored
Rather than using the global variable, have cell use its own variable to store the direct DMA offset. Signed-off-by:
-
Michael Ellerman authored
Now that all platforms using dma_direct_offset setup the archdata.dma_data correctly, we can change the dma_direct_ops to retrieve the offset from the dma_data, rather than directly from the global. While we're here, change the way the offset is used - instead of or'ing it into the value, add it. This should have no effect on current implementations where the offset is far larger than memory, however in future we may want to use smaller offsets. Signed-off-by:
-
Michael Ellerman authored
Celleb always uses dma_direct_ops, and sets dma_direct_offset, so it too should set dma_data to dma_direct_offset. Currently there's no pci_dma_dev_setup() routine for Celleb so add one. Signed-off-by:
-
Michael Ellerman authored
Store the direct_dma_offset in each device's dma_data in the case where we're using the direct DMA ops. We need to make sure we setup the ppc_md.pci_dma_dev_setup() callback if we're using a non-zero offset. Signed-off-by:
-
Benjamin Herrenschmidt authored
We must always hookup the pci_bus resource 0 to the PHB io_resource even if the latter is empty (the bus has no IO support). Otherwise, some other code will end up hooking it up to something bogus and the resource tree will end up being broken. This fixes boot on QS20 Cell blades where the IDE driver failed to allocate the IO resources due to breakage of the resource tree. Signed-off-by:
-
Geoff Levand authored
Update ps3_defconfig. Signed-off-by:
Geoff Levand <geoffrey.levand@am.sony.com> Signed-off-by:
-
Geoff Levand authored
Remove the PS3 workaround needed to support sparsemem SPU mappings. The SPU mappings no longer use sparsemem, so this workaround is no longer needed. Signed-off-by:
-
Geoff Levand authored
A general housekeeping change of the PS3 vuart variable vuart_bus_priv.probe_mutex from semaphore to mutex. Signed-off-by:
-
Takashi Yamamoto authored
Add PS3 logical performance monitor (lpm) device driver. The PS3's LV1 hypervisor provides a Logical Performance Monitor that abstracts the Cell processor's performance monitor features for use by guest operating systems. Signed-off-by:
Takashi Yamamoto <TakashiA.Yamamoto@jp.sony.com> Signed-off-by:
-
Geoff Levand authored
Add PS3 logical performance monitor device support to the PS3 system-bus and platform device registration routines. Signed-off-by:
-
Takashi Yamamoto authored
Add repository routines for the PS3 Logical Performance Monitor. Signed-off-by:
-
Geert Uytterhoeven authored
Cleanup coding errors in arch/powerpc/platforms/ps3/repository.c as reported by sparse and checkpatch. Signed-off-by:
Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com> Signed-off-by:
-
Geert Uytterhoeven authored
Cleanup coding errors in drivers/ps3/ps3-vuart.c as reported by checkpatch. Signed-off-by:
-
Geert Uytterhoeven authored
Cleanup coding errors in drivers/ps3/ps3-sys-manager.c as reported by checkpatch. Signed-off-by:
-
Geert Uytterhoeven authored
PS3: Refactor ps3_repository_find_device() to use the existing ps3_repository_read_bus_id() routine. Signed-off-by:
-
Geert Uytterhoeven authored
PS3: Kill unused routine ps3_repository_bump_device(). Signed-off-by:
-
Geert Uytterhoeven authored
PS3: Add repository polling loop to work around timing bug On some firmware versions (e.g. 1.90), the storage device may not show up in the repository immediately after receiving the notification message. Add a small polling loop to make sure we don't miss it. Signed-off-by:
-
Geert Uytterhoeven authored
The PS3 hypervisor has a storage device notification mechanism to wait until a storage device is ready. Unfortunately the storage device probing code used this mechanism in an incorrect way, needing a polling loop and handling of devices that are not yet ready. This change corrects this by: - First waiting for the reception of an asynchronous notification that a new storage device became ready, - Then looking up the storage device in the device repository. On shutdown, the storage probe thread is stopped and the storage notification device is closed using a reboot notifier. Signed-off-by:
-
