On Thu, 2010-11-25 at 01:03 +1100, Michael Ellerman wrote:
Hi all,
There were some murmurings on IRC last week about renaming the of_*()
routines.
...
The thinking is that on many platforms that use the of_() routines
OpenFirmware is not involved at all, this is true even on many powerpc
On Thu, Nov 25, 2010 at 6:34 AM, Michael Ellerman
mich...@ellerman.id.au wrote:
On Thu, 2010-11-25 at 01:03 +1100, Michael Ellerman wrote:
Hi all,
There were some murmurings on IRC last week about renaming the of_*()
routines.
...
The thinking is that on many platforms that use the of_()
ioapic_xlate provides a translation from the information in device tree
to ioapic related informations. This includes
- obtaining hw irq which is the vector number = pin number + gsi
- obtaining type (level/edge/..)
- programming this information into ioapic
ioapic_add_ofnode adds an irq_host
This patch adds minimal support for device tree support on x86. It will
be passed to the kernel via setup_data which requires atleast boot
protocol 2.09.
Memory size, restricted memory regions, boot arguments are gathered the
traditional way so things like cmd_line are just here to let the code
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
CC: x...@kernel.org
Cc: devicetree-discuss@lists.ozlabs.org
Signed-off-by: Dirk Brandewie dirk.brande...@gmail.com
---
arch/x86/platform/ce4100/ce4100.dts | 210 +++
1 files changed, 210 insertions(+),
For now we probe these busses and we change is to board dependent probes
once we have to.
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
CC: x...@kernel.org
Cc: devicetree-discuss@lists.ozlabs.org
Signed-off-by: Dirk Brandewie dirk.brande...@gmail.com
---
arch/x86/kernel/prom.c |
On Fri, Nov 19, 2010 at 4:13 PM, David Daney dda...@caviumnetworks.com wrote:
Some aspects of PHY initialization are board dependent, things like
indicator LED connections and some clocking modes cannot be determined
by probing. The dev_flags element of struct phy_device can be used to
Hi Wolfram,
I'm surprised that this would work. I've patched the at24 driver as well
to use OF data, but took a different approach.
As far as I could tell, using compatible = 24c64; didn't load the right
module
(module name is at24) and using at24 caused a device id mismatch because
at24 is
Hi Wolfram,
I seem to be mistaken. I retried compatible=linux,24c64 and it did
all the right
things. I was mistaken that request_module() only takes the driver
name, at24 in this
case, and not all device names in the table_ids.
This pretty much makes my patch redundant. Thanks for helping me
The here introduced irq_host abstraction represents a generic irq_host.
The xlate callback is resposible to parse irq informations like irq type
and number and returns the hardware irq number which is reported by the
hardware as active.
[...]
diff --git
diff --git a/arch/x86/include/asm/prom.h b/arch/x86/include/asm/prom.h
new file mode 100644
index 000..8fdb0d2
--- /dev/null
+++ b/arch/x86/include/asm/prom.h
@@ -0,0 +1,60 @@
+/*
+ * Definitions for Device tree / OpenFirmware handling on X86
+ *
+ * based on
On Thu, 2010-11-25 at 09:17 -0700, Grant Likely wrote:
On Thu, Nov 25, 2010 at 6:34 AM, Michael Ellerman
mich...@ellerman.id.au wrote:
On Thu, 2010-11-25 at 01:03 +1100, Michael Ellerman wrote:
Hi all,
There were some murmurings on IRC last week about renaming the of_*()
routines.
On 11/25/2010 5:15 PM, Michael Ellerman wrote:
On Thu, 2010-11-25 at 09:17 -0700, Grant Likely wrote:
On Thu, Nov 25, 2010 at 6:34 AM, Michael Ellerman
mich...@ellerman.id.au wrote:
On Thu, 2010-11-25 at 01:03 +1100, Michael Ellerman wrote:
Hi all,
There were some murmurings on IRC last
13 matches
Mail list logo
