Hi Andy,
On Tue, May 06, 2008 at 05:54:02PM -0500, Andy Fleming wrote:
Now back to the first an bigger problem :
currently, I have an old U-boot and I have written myself a dts file.
Problem is : ethernet does not work, but that's not a mac-address problem,
but something else that I do not
Hi Philippe,
On Wed, 7 May 2008 09:50:48 +0200 Philippe De Muyter [EMAIL PROTECTED] wrote:
What's the recommended way to make a powerpc patch (e.g. my defconfig) appear
in the official kernel sources ? Should I send it to linuxppc-dev@ozlabs.org,
lkml or somewhere else ?
linuxppc-dev would
Now back to the first an bigger problem :
currently, I have an old U-boot and I have written myself a dts
file.
Problem is : ethernet does not work, but that's not a mac-address
problem,
but something else that I do not understand yet. The symptom is I get
ip route add default
Hi David,
On Tue, Mar 11, 2008 at 11:32:49AM +1100, David Gibson wrote:
On Sun, Mar 09, 2008 at 11:31:09PM +0100, Philippe De Muyter wrote:
Hi Ben,
I now have a working linux on my mpc8540 based board, with support for
the compactflash disk and the i2c rtc.
The network tough, does
On Tue, Mar 11, 2008 at 12:46:02PM +0100, Philippe De Muyter wrote:
Hi David,
On Tue, Mar 11, 2008 at 11:32:49AM +1100, David Gibson wrote:
On Sun, Mar 09, 2008 at 11:31:09PM +0100, Philippe De Muyter wrote:
Hi Ben,
I now have a working linux on my mpc8540 based board, with support
On Sun, Mar 09, 2008 at 11:31:09PM +0100, Philippe De Muyter wrote:
Hi Ben,
I now have a working linux on my mpc8540 based board, with support for
the compactflash disk and the i2c rtc.
The network tough, does not work yet. altough the the integrated ethernet
controller (FEC) seems to be
Hi Ben,
I now have a working linux on my mpc8540 based board, with support for
the compactflash disk and the i2c rtc.
The network tough, does not work yet. altough the the integrated ethernet
controller (FEC) seems to be recognized. Could it be a problem with the phy ?
I notice that I do not
On Sun, 2008-03-09 at 23:31 +0100, Philippe De Muyter wrote:
Hi Ben,
I now have a working linux on my mpc8540 based board, with support for
the compactflash disk and the i2c rtc.
The network tough, does not work yet. altough the the integrated ethernet
controller (FEC) seems to be
Hi Ben,
On Thu, Mar 06, 2008 at 10:46:51AM +1100, Benjamin Herrenschmidt wrote:
From your .dts, I see you've been doing some swizzling of slots using
interrupts 1...4 ... do that correspond to EXTIRQ 58 ?
No, those correspond to the EXT1-4 that are the other side of the #ifdef
On Fri, 2008-03-07 at 01:10 +0100, Philippe De Muyter wrote:
But I already noticed that the interrupt numbers that the arch/powerpc tree
uses for the parts that do already work (compact-flash and serials) are
different from the ones I saw on the running arch/ppc tree. e.g.,
the serial
Hi Ben,
thanks for all the answers,
On Wed, Mar 05, 2008 at 04:01:04PM +1100, Benjamin Herrenschmidt wrote:
I also attach my current (not working) dts file attempt. It is actually
a modified mpc8540ads.dts file.
I now thinks that the ide-cs (hda) discovery or not depends on the cold
Benjamin Herrenschmidt wrote:
So at this stage, that's not enough information. We need to know exactly how
you have wired things on your board, and somebody from fsl needs to tell
me how the ExtIrq are routed to the MPIC on that guy.
This part's easy -- the external IRQ is used as the mpic
On Wed, 2008-03-05 at 17:15 +0100, Philippe De Muyter wrote:
I asked the guy who designed the hardware, and if I understand
correctly :
- the i/o and memory resources of the pci device are connected to the
pci bus
- the interrupts are directly connected to the MPIC
Can I describe that
Hi Ben,
On Thu, Mar 06, 2008 at 07:14:28AM +1100, Benjamin Herrenschmidt wrote:
On Wed, 2008-03-05 at 17:15 +0100, Philippe De Muyter wrote:
I asked the guy who designed the hardware, and if I understand
correctly :
- the i/o and memory resources of the pci device are connected to
From your .dts, I see you've been doing some swizzling of slots using
interrupts 1...4 ... do that correspond to EXTIRQ 58 ?
No, those correspond to the EXT1-4 that are the other side of the #ifdef
for this board in arch/ppc. :-)
Yes, that's what I was thinking. So that's what he got
Hi Scott,
On Mon, Mar 03, 2008 at 03:55:26PM -0600, Scott Wood wrote:
Philippe De Muyter wrote:
The following seems important also :
/*
interrupts = 18 2;
*/
/* interrupts number are coded in hexa ! */
interrupts = 12 2 19 2 1a 2 1b 2 35 2 36
Hi Ben,
On Tue, Mar 04, 2008 at 08:41:33AM +1100, Benjamin Herrenschmidt wrote:
Thanks
The following seems important also :
/*
interrupts = 18 2;
*/
/* interrupts number are coded in hexa ! */
interrupts = 12 2 19 2 1a 2 1b 2
On Tue, 2008-03-04 at 09:08 +0100, Philippe De Muyter wrote:
With ARCH=ppc, all those interrupt's info's are hardcoded in the .c
files.
But I expected I could fill the dts file for ARCH=powerpc from info's
I
could collect in /proc on a running ARCH=ppc linux without dts file
for the same
On Tue, Mar 04, 2008 at 10:10:59AM +0100, Philippe De Muyter wrote:
Hi Ben,
On Tue, Mar 04, 2008 at 07:22:19PM +1100, Benjamin Herrenschmidt wrote:
These comments aren't relevant to the problems you're seeing, but
they're a good idea for writing device trees in general.
First, you may want
I also attach my current (not working) dts file attempt. It is actually
a modified mpc8540ads.dts file.
I now thinks that the ide-cs (hda) discovery or not depends on the cold
or warm reboot.
Here are the patches for my config (MEIP_8540) relative to a vanilla
linux-2.6.24. I hacked
Hi all,
I have a currently almost working ARCH=ppc linux-2.6.24 configuration for a
new mpc8540 board (except for a RTC chip connected to an i2c bus).
Knowing that ARCH=ppc will be removed, I try to make the ARCH=powerpc version
work, but that's not easy.
I have copied the mpc8540ads.dts file
On Mon, Mar 3, 2008 at 7:47 AM, Philippe De Muyter [EMAIL PROTECTED] wrote:
My root device is on a compact-flash connected to a PCI yenta chip from TI,
and this one is not working, altough it seems to be discovered :
Yenta: CardBus bridge found at :00:12.0 [:]
On Mon, Mar 03, 2008 at 03:47:27PM +0100, Philippe De Muyter wrote:
My root device is on a compact-flash connected to a PCI yenta chip from TI,
and this one is not working, altough it seems to be discovered :
Yenta: CardBus bridge found at :00:12.0 [:]
Yenta: Using
Hi Scott,
On Mon, Mar 03, 2008 at 11:07:20AM -0600, Scott Wood wrote:
On Mon, Mar 03, 2008 at 03:47:27PM +0100, Philippe De Muyter wrote:
My root device is on a compact-flash connected to a PCI yenta chip from TI,
and this one is not working, altough it seems to be discovered :
Philippe De Muyter wrote:
Is the PCI-interrupt map that part of the dts file :
interrupt-map =
/* IDSEL 0x02 */
1000 0 0 1 mpic 1 1
1000 0 0 2 mpic 2 1
1000 0 0 3 mpic 3 1
Hi Scott,
On Mon, Mar 03, 2008 at 03:11:08PM -0600, Scott Wood wrote:
Philippe De Muyter wrote:
Is the PCI-interrupt map that part of the dts file :
interrupt-map =
/* IDSEL 0x02 */
1000 0 0 1 mpic 1 1
Maybe your PCI interrupt-map is wrong...
Is the PCI-interrupt map that part of the dts file :
interrupt-map =
/* IDSEL 0x02 */
1000 0 0 1 mpic 1 1
1000 0 0 2 mpic 2 1
Thanks
The following seems important also :
/*
interrupts = 18 2;
*/
/* interrupts number are coded in hexa ! */
interrupts = 12 2 19 2 1a 2 1b 2 35 2 36 2 37 2;
I have replaced the interrupts spec in comments by the longer interrupts
Philippe De Muyter wrote:
The following seems important also :
/*
interrupts = 18 2;
*/
/* interrupts number are coded in hexa ! */
interrupts = 12 2 19 2 1a 2 1b 2 35 2 36 2 37 2;
I have replaced the interrupts spec in comments by the
29 matches
Mail list logo
