[PATCH 8/8] Add support for Xilinx ML403 reference design

[PATCH 8/8] Add support for Xilinx ML403 reference design

[Grant Likely]

Add support for Xilinx ML403 reference design

Signed-off-by: Grant C. Likely <grant.likely@secretlab.ca>

---

 arch/ppc/boot/simple/embed_config.c              |   41 +++++
 arch/ppc/platforms/4xx/Kconfig                   |    8 +
 arch/ppc/platforms/4xx/Makefile                  |    2 
 arch/ppc/platforms/4xx/xilinx_ml403.c            |  177 ++++++++++++++++++++++
 arch/ppc/platforms/4xx/xilinx_ml403.h            |   49 ++++++
 arch/ppc/platforms/4xx/xparameters/xparameters.h |   13 ++
 include/asm-ppc/ibm4xx.h                         |    4 
 7 files changed, 291 insertions(+), 3 deletions(-)
 create mode 100644 arch/ppc/platforms/4xx/xilinx_ml403.c
 create mode 100644 arch/ppc/platforms/4xx/xilinx_ml403.h

03eaaad1784a4094cecd57f3aafbfe8832742505
diff --git a/arch/ppc/boot/simple/embed_config.c b/arch/ppc/boot/simple/embed_config.c
index df24202..0172eb0 100644
--- a/arch/ppc/boot/simple/embed_config.c
+++ b/arch/ppc/boot/simple/embed_config.c
@@ -745,7 +745,7 @@ embed_config(bd_t **bdp)
 }
 #endif /* WILLOW */
 
-#ifdef CONFIG_XILINX_ML300
+#if defined(CONFIG_XILINX_ML300)
 void
 embed_config(bd_t ** bdp)
 {
@@ -784,6 +784,45 @@ embed_config(bd_t ** bdp)
 }
 #endif /* CONFIG_XILINX_ML300 */
 
+#if defined(CONFIG_XILINX_ML403)
+void
+embed_config(bd_t ** bdp)
+{
+	static const unsigned long line_size = 32;
+	static const unsigned long congruence_classes = 256;
+	unsigned long addr;
+	unsigned long dccr;
+	bd_t *bd;
+
+	/*
+	 * Invalidate the data cache if the data cache is turned off.
+	 * - The 405 core does not invalidate the data cache on power-up
+	 *   or reset but does turn off the data cache. We cannot assume
+	 *   that the cache contents are valid.
+	 * - If the data cache is turned on this must have been done by
+	 *   a bootloader and we assume that the cache contents are
+	 *   valid.
+	 */
+	__asm__("mfdccr %0": "=r" (dccr));
+	if (dccr == 0) {
+		for (addr = 0;
+		     addr < (congruence_classes * line_size);
+		     addr += line_size) {
+			__asm__("dccci 0,%0": :"b"(addr));
+		}
+	}
+
+	bd = &bdinfo;
+	*bdp = bd;
+	bd->bi_memsize = XPAR_PLB_DDR_0_MEM0_HIGHADDR + 1;
+	bd->bi_intfreq = XPAR_CPU_PPC405_CORE_CLOCK_FREQ_HZ;
+	bd->bi_busfreq = XPAR_XUARTNS550_CLOCK_HZ;
+	bd->bi_pci_busfreq = 0;
+	timebase_period_ns = 1000000000 / bd->bi_tbfreq;
+	/* see bi_tbfreq definition in arch/ppc/platforms/4xx/xilinx_ml300.h */
+}
+#endif /* CONFIG_XILINX_ML403 */
+
 #ifdef CONFIG_IBM_OPENBIOS
 /* This could possibly work for all treeboot roms.
 */
diff --git a/arch/ppc/platforms/4xx/Kconfig b/arch/ppc/platforms/4xx/Kconfig
index 266280c..f7a5848 100644
--- a/arch/ppc/platforms/4xx/Kconfig
+++ b/arch/ppc/platforms/4xx/Kconfig
@@ -57,6 +57,10 @@ config XILINX_ML300
 	help
 	  This option enables support for the Xilinx ML300 evaluation board.
 
+config XILINX_ML403
+	bool "Xilinx-ML403"
+	help
+	  This option enables support for the Xilinx ML403 evaluation board.
 endchoice
 
 choice
@@ -194,7 +198,7 @@ config 405GPR
 
 config XILINX_VIRTEX
 	bool
-	depends on XILINX_ML300
+	depends on XILINX_ML300 || XILINX_ML403
 	default y
 
 config STB03xxx
@@ -204,7 +208,7 @@ config STB03xxx
 
 config EMBEDDEDBOOT
 	bool
-	depends on EP405 || XILINX_ML300
+	depends on EP405 || XILINX_ML300 || XILINX_ML403
 	default y
 
 config IBM_OPENBIOS
diff --git a/arch/ppc/platforms/4xx/Makefile b/arch/ppc/platforms/4xx/Makefile
index 4db749d..9dd5629 100644
--- a/arch/ppc/platforms/4xx/Makefile
+++ b/arch/ppc/platforms/4xx/Makefile
@@ -13,6 +13,7 @@ obj-$(CONFIG_REDWOOD_6)		+= redwood6.o
 obj-$(CONFIG_SYCAMORE)		+= sycamore.o
 obj-$(CONFIG_WALNUT)		+= walnut.o
 obj-$(CONFIG_XILINX_ML300)	+= xilinx_ml300.o
+obj-$(CONFIG_XILINX_ML403)	+= xilinx_ml403.o
 
 obj-$(CONFIG_405GP)		+= ibm405gp.o
 obj-$(CONFIG_REDWOOD_5)		+= ibmstb4.o
@@ -25,3 +26,4 @@ obj-$(CONFIG_440SP)		+= ibm440sp.o
 obj-$(CONFIG_405EP)		+= ibm405ep.o
 obj-$(CONFIG_405GPR)		+= ibm405gpr.o
 obj-$(CONFIG_XILINX_VIRTEX)	+= virtex.o
+
diff --git a/arch/ppc/platforms/4xx/xilinx_ml403.c b/arch/ppc/platforms/4xx/xilinx_ml403.c
new file mode 100644
index 0000000..4c0c7e4
--- /dev/null
+++ b/arch/ppc/platforms/4xx/xilinx_ml403.c
@@ -0,0 +1,177 @@
+/*
+ * arch/ppc/platforms/4xx/xilinx_ml403.c
+ *
+ * Xilinx ML403 evaluation board initialization
+ *
+ * Author: Grant Likely <grant.likely@secretlab.ca>
+ *
+ * 2005 (c) Secret Lab Technologies Ltd.
+ * 2002-2004 (c) MontaVista Software, Inc.
+ *
+ * This file is licensed under the terms of the GNU General Public License
+ * version 2.  This program is licensed "as is" without any warranty of any
+ * kind, whether express or implied.
+ */
+
+#include <linux/config.h>
+#include <linux/init.h>
+#include <linux/irq.h>
+#include <linux/tty.h>
+#include <linux/serial.h>
+#include <linux/serial_core.h>
+#include <linux/serial_8250.h>
+#include <linux/serialP.h>
+#include <asm/io.h>
+#include <asm/machdep.h>
+#include <asm/ppc_sys.h>
+
+#include <syslib/gen550.h>
+#include <platforms/4xx/xparameters/xparameters.h>
+
+/*
+ * As an overview of how the following functions (platform_init,
+ * ml403_map_io, ml403_setup_arch and ml403_init_IRQ) fit into the
+ * kernel startup procedure, here's a call tree:
+ *
+ * start_here					arch/ppc/kernel/head_4xx.S
+ *  early_init					arch/ppc/kernel/setup.c
+ *  machine_init				arch/ppc/kernel/setup.c
+ *    platform_init				this file
+ *      ppc4xx_init				arch/ppc/syslib/ppc4xx_setup.c
+ *        parse_bootinfo
+ *          find_bootinfo
+ *        "setup some default ppc_md pointers"
+ *  MMU_init					arch/ppc/mm/init.c
+ *    *ppc_md.setup_io_mappings == ml403_map_io	this file
+ *      ppc4xx_map_io				arch/ppc/syslib/ppc4xx_setup.c
+ *  start_kernel				init/main.c
+ *    setup_arch				arch/ppc/kernel/setup.c
+ * #if defined(CONFIG_KGDB)
+ *      *ppc_md.kgdb_map_scc() == gen550_kgdb_map_scc
+ * #endif
+ *      *ppc_md.setup_arch == ml403_setup_arch	this file
+ *        ppc4xx_setup_arch			arch/ppc/syslib/ppc4xx_setup.c
+ *          ppc4xx_find_bridges			arch/ppc/syslib/ppc405_pci.c
+ *    init_IRQ					arch/ppc/kernel/irq.c
+ *      *ppc_md.init_IRQ == ml403_init_IRQ	this file
+ *        ppc4xx_init_IRQ			arch/ppc/syslib/ppc4xx_setup.c
+ *          ppc4xx_pic_init			arch/ppc/syslib/xilinx_pic.c
+ */
+
+/* Board specifications structures */
+struct ppc_sys_spec *cur_ppc_sys_spec;
+struct ppc_sys_spec ppc_sys_specs[] = {
+	{
+		/* Only one entry, always assume the same design */
+		.ppc_sys_name	= "Xilinx ML403 Reference Design",
+		.mask 		= 0x00000000,
+		.value 		= 0x00000000,
+		.num_devices	= 1,
+		.device_list	= (enum ppc_sys_devices[])
+		{
+			VIRTEX_UART,
+		},
+	},
+};
+
+#if defined(XPAR_POWER_0_POWERDOWN_BASEADDR)
+
+static volatile unsigned *powerdown_base =
+    (volatile unsigned *) XPAR_POWER_0_POWERDOWN_BASEADDR;
+
+static void
+xilinx_power_off(void)
+{
+	local_irq_disable();
+	out_be32(powerdown_base, XPAR_POWER_0_POWERDOWN_VALUE);
+	while (1) ;
+}
+#endif
+
+void __init
+ml403_map_io(void)
+{
+	ppc4xx_map_io();
+
+#if defined(XPAR_POWER_0_POWERDOWN_BASEADDR)
+	powerdown_base = ioremap((unsigned long) powerdown_base,
+				 XPAR_POWER_0_POWERDOWN_HIGHADDR -
+				 XPAR_POWER_0_POWERDOWN_BASEADDR + 1);
+#endif
+}
+
+/* Early serial support functions */
+static void __init
+ml403_early_serial_init(int num, struct plat_serial8250_port *pdata)
+{
+#if defined(CONFIG_SERIAL_TEXT_DEBUG) || defined(CONFIG_KGDB)
+	struct uart_port serial_req;
+
+	memset(&serial_req, 0, sizeof(serial_req));
+	serial_req.mapbase	= pdata->mapbase;
+	serial_req.membase	= pdata->membase;
+	serial_req.irq		= pdata->irq;
+	serial_req.uartclk	= pdata->uartclk;
+	serial_req.regshift	= pdata->regshift;
+	serial_req.iotype	= pdata->iotype;
+	serial_req.flags	= pdata->flags;
+	gen550_init(num, &serial_req);
+#endif
+}
+
+void __init
+ml403_early_serial_map(void)
+{
+#ifdef CONFIG_SERIAL_8250
+	struct plat_serial8250_port *pdata;
+	int i = 0;
+
+	pdata = (struct plat_serial8250_port *) ppc_sys_get_pdata(VIRTEX_UART);
+	while(pdata && pdata->flags)
+	{
+		pdata->membase = ioremap(pdata->mapbase, 0x100);
+		ml403_early_serial_init(i, pdata);
+		pdata++;
+		i++;
+	}
+#endif /* CONFIG_SERIAL_8250 */
+}
+
+void __init
+ml403_setup_arch(void)
+{
+	ml403_early_serial_map();
+	ppc4xx_setup_arch();	/* calls ppc4xx_find_bridges() */
+
+	/* Identify the system */
+	printk(KERN_INFO "Xilinx ML403 Reference System (Virtex-4 FX)\n");
+}
+
+/* Called after board_setup_irq from ppc4xx_init_IRQ(). */
+void __init
+ml403_init_irq(void)
+{
+	ppc4xx_init_IRQ();
+}
+
+void __init
+platform_init(unsigned long r3, unsigned long r4, unsigned long r5,
+	      unsigned long r6, unsigned long r7)
+{
+	ppc4xx_init(r3, r4, r5, r6, r7);
+
+	identify_ppc_sys_by_id(mfspr(SPRN_PVR));
+
+	ppc_md.setup_arch = ml403_setup_arch;
+	ppc_md.setup_io_mappings = ml403_map_io;
+	ppc_md.init_IRQ = ml403_init_irq;
+
+#if defined(XPAR_POWER_0_POWERDOWN_BASEADDR)
+	ppc_md.power_off = xilinx_power_off;
+#endif
+
+#ifdef CONFIG_KGDB
+	ppc_md.early_serial_map = ml403_early_serial_map;
+#endif
+}
+
diff --git a/arch/ppc/platforms/4xx/xilinx_ml403.h b/arch/ppc/platforms/4xx/xilinx_ml403.h
new file mode 100644
index 0000000..4735969
--- /dev/null
+++ b/arch/ppc/platforms/4xx/xilinx_ml403.h
@@ -0,0 +1,49 @@
+/*
+ * arch/ppc/platforms/4xx/xilinx_ml403.h
+ *
+ * Include file that defines the Xilinx ML403 reference design
+ *
+ * Author: Grant Likely <grant.likely@secretlab.ca>
+ *
+ * 2005 (c) Secret Lab Technologies Ltd.
+ * 2002-2004 (c) MontaVista Software, Inc.
+ *
+ * This file is licensed under the terms of the GNU General Public License
+ * version 2.  This program is licensed "as is" without any warranty of any
+ * kind, whether express or implied.
+ */
+
+#ifdef __KERNEL__
+#ifndef __ASM_XILINX_ML403_H__
+#define __ASM_XILINX_ML403_H__
+
+/* ML403 has a Xilinx Virtex-4 FPGA with a PPC405 hard core */
+#include <platforms/4xx/virtex.h>
+
+#ifndef __ASSEMBLY__
+
+#include <linux/types.h>
+
+typedef struct board_info {
+	unsigned int	 bi_memsize;		/* DRAM installed, in bytes */
+	unsigned char	 bi_enetaddr[6];	/* Local Ethernet MAC address */
+	unsigned int	 bi_intfreq;		/* Processor speed, in Hz */
+	unsigned int	 bi_busfreq;		/* PLB Bus speed, in Hz */
+	unsigned int	 bi_pci_busfreq;	/* PCI Bus speed, in Hz */
+} bd_t;
+
+/* Some 4xx parts use a different timebase frequency from the internal clock.
+*/
+#define bi_tbfreq bi_intfreq
+
+#endif /* !__ASSEMBLY__ */
+
+/* We don't need anything mapped.  Size of zero will accomplish that. */
+#define PPC4xx_ONB_IO_PADDR	0u
+#define PPC4xx_ONB_IO_VADDR	0u
+#define PPC4xx_ONB_IO_SIZE	0u
+
+#define PPC4xx_MACHINE_NAME "Xilinx ML403 Reference Design"
+
+#endif /* __ASM_XILINX_ML403_H__ */
+#endif /* __KERNEL__ */
diff --git a/arch/ppc/platforms/4xx/xparameters/xparameters.h b/arch/ppc/platforms/4xx/xparameters/xparameters.h
index 26ee822..22b0088 100644
--- a/arch/ppc/platforms/4xx/xparameters/xparameters.h
+++ b/arch/ppc/platforms/4xx/xparameters/xparameters.h
@@ -32,6 +32,19 @@
   #define VIRTEX_INTC_BASEADDR           XPAR_DCR_INTC_0_BASEADDR
   #define VIRTEX_INTC_KIND_OF_INTR       XPAR_DCR_INTC_0_KIND_OF_INTR
 
+#elif defined(CONFIG_XILINX_ML403)
+  #include "xparameters_ml403.h"
+
+  /* Serial ports */
+  #define VIRTEX_UART_0_BASEADDR  (XPAR_OPB_UART16550_0_BASEADDR + 0x1000)
+  #define VIRTEX_UART_0_IRQ  XPAR_OPB_INTC_0_OPB_UART16550_0_IP2INTC_IRPT_INTR
+  #define VIRTEX_UART_0_CLK  XPAR_XUARTNS550_CLOCK_HZ
+
+  /* Values for setting up interrupt controller */
+  #define VIRTEX_XINTC_USE_DCR           XPAR_XINTC_USE_DCR
+  #define VIRTEX_INTC_BASEADDR           XPAR_OPB_INTC_0_BASEADDR
+  #define VIRTEX_INTC_KIND_OF_INTR       XPAR_OPB_INTC_0_KIND_OF_INTR
+
 #else
   /* Add other board xparameter includes here before the #else */
   #error No *_xparameters.h file included
diff --git a/include/asm-ppc/ibm4xx.h b/include/asm-ppc/ibm4xx.h
index e992369..c49c462 100644
--- a/include/asm-ppc/ibm4xx.h
+++ b/include/asm-ppc/ibm4xx.h
@@ -51,6 +51,10 @@
 #include <platforms/4xx/xilinx_ml300.h>
 #endif
 
+#if defined(CONFIG_XILINX_ML403)
+#include <platforms/4xx/xilinx_ml403.h>
+#endif
+
 #ifndef __ASSEMBLY__
 
 #ifdef CONFIG_40x
-- 
1.0.6-g58e3

Re: [PATCH 8/8] Add support for Xilinx ML403 reference design

[Grant Likely]

David H. Lynch Jr. wrote:
> 	I am working on a port of 2.6.14.5 to the Pico E-12 which is a Xilinx
> Virtex-IV system in a CF card. It is very similar to the ML403 but with
> alot less hardware. I would love to be able to pull a whole tree of the
> stuff you are working on - is there a git, svn, or cvs tree that the
> linuxppc-embedded patches are getting merged into ? and How can it be
> accessed ?
I don't have a public git tree at the moment for the xilinx virtex
stuff.  I can certainly create and maintain one if there is demand.  I
guess it depends on how many people want to colaborate on V2Pro/V4
support.  Anyone else interested?

> 	Right now I am trying to get /init to run - actually it runs but I am
> not getting IO on the console. Anyway, I hope to put out a collection of
> patches when I have it really working. Aside from the Pico  e-12 itself,
> I have Uartlite drivers that are consistent with the way the rest of the
> 2.6 serial drivers are layed out as well as a custom serial driver
> specific to the E-12. The E-12 stuff might not make it into the
> distribution kernel, but I would think there might be some interest in
> the UartLite driver.
Since the E-12 is a commercially available board, it would be useful to
have the patches on the ML, even if they don't get applied to mainline.

> 
> 	Anyway it would be nice to work against whatever all the
> linuxppc-embedded patches are going into.
I'm working off the mainline linux-2.6 tree from kernel.org.  PPC
patches are getting merged into mainline frequently.

Cheers,
g.

-- 
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
(403) 663-0761

Re: [PATCH 8/8] Add support for Xilinx ML403 reference design

[David H. Lynch Jr.]

Grant Likely wrote:
> David H. Lynch Jr. wrote:

> 
> Since the E-12 is a commercially available board, it would be useful to
> have the patches on the ML, even if they don't get applied to mainline.

	So at what state should things be at before posting them ?

	Right now:
		The basic E-12 stuff is complete - though it couls use some polish. It
was based on the ML300 code, and almost certainly overlaps and conflicts
with your ML403 work. I would be happy to reconcile them, but I would
need to know what to work against.

		I am not a git expert at this point. I am working against the 2.6.14.5
source3 on kernel.org. There are numerous git trees what is the right one ?

	
		The serial/console drivers for the "Keyhole" - a bidirectional link
between a Linux/Windows development host and the E-12, and the Xilinx
UartLite are in (hopefully) late debugging, Output is probably complete,
UartLite input needs testing, Keyhole input needs alot of work - among
other things the host side is still only a display, so it is somewhat
difficult to do the Linux input side.

Re: [PATCH 8/8] Add support for Xilinx ML403 reference design

[Grant Likely]

Florian wrote:
>> I don't have a public git tree at the moment for the xilinx virtex
>> stuff.  I can certainly create and maintain one if there is demand.  I
>> guess it depends on how many people want to colaborate on V2Pro/V4
>> support.  Anyone else interested?
> 
> 
> Yes. I am also working on a Virtex-4 system with Linux.
> Do you support also a Linux 2.4 tree?
Sorry, no.  I'm focusing on the 2.6 stuff.  IIRC, the Denx tree is
tracking the virtex support in 2.4.

Are you strictly working on 2.4?  Or are you interested in 2.6 as well?

Cheers,
g.

-- 
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
(403) 663-0761

Re: [PATCH 8/8] Add support for Xilinx ML403 reference design

[Grant Likely]

David H. Lynch Jr. wrote:
> Grant Likely wrote:
> 
>>David H. Lynch Jr. wrote:
> 
> 
>>Since the E-12 is a commercially available board, it would be useful to
>>have the patches on the ML, even if they don't get applied to mainline.
> 
> 
> 	So at what state should things be at before posting them ?
> 
> 	Right now:
> 		The basic E-12 stuff is complete - though it couls use some polish. It
> was based on the ML300 code, and almost certainly overlaps and conflicts
> with your ML403 work. I would be happy to reconcile them, but I would
> need to know what to work against.
If you want initial comments, then don't worry about polish; Send your
raw diff (in unified format please!) and put [RFC] in the subject line
so nobody mistakes it as stable code.  :)  I'll happily comment on it.

I'm sure it conflicts with my ML403 work considering I've moved from the
OCP to the platform bus.

> 
> 		I am not a git expert at this point. 
Neither am I.  :)

Try this:
install GIT:     http://linux.yyz.us/git-howto.html#installing_git
install Cogito:  http://www.kernel.org/pub/software/scm/cogito/README
easy user guide: http://wellington.pm.org/archive/200510/git/

> I am working against the 2.6.14.5
> source3 on kernel.org. There are numerous git trees what is the right one ?
I'm using Linus's tree, seeked to tag v2.6.14.

git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git

> 
> 	
> 		The serial/console drivers for the "Keyhole" - a bidirectional link
> between a Linux/Windows development host and the E-12, and the Xilinx
> UartLite are in (hopefully) late debugging, Output is probably complete,
> UartLite input needs testing, Keyhole input needs alot of work - among
> other things the host side is still only a display, so it is somewhat
> difficult to do the Linux input side.
> 


-- 
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
(403) 663-0761

Re: [PATCH 8/8] Add support for Xilinx ML403 reference design

[Grant Likely]

Florian wrote:
>>> Yes. I am also working on a Virtex-4 system with Linux.
>>> Do you support also a Linux 2.4 tree?
>>
>>
>> Sorry, no.  I'm focusing on the 2.6 stuff.  IIRC, the Denx tree is
>> tracking the virtex support in 2.4.
>>
>> Are you strictly working on 2.4?  Or are you interested in 2.6 as well?
> 
> 
> I am working with the Montavista 2.4 sources.
> 2.6 is also possible but I read 2.6 is not better than 2.4 for embedded
> systems.
> We didn't make a final decision so you can convince me to try 2.6.
Nah, that sounds like to much work.  :)  Choose what works for you.  If
2.4 has the features you need then go for it.  (just keep in mind that
most new development it focused on 2.6)

g.

-- 
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
(403) 663-0761

Re: [PATCH 8/8] Add support for Xilinx ML403 reference design

[Paula Saameño]

[-- Attachment #1: Type: text/plain, Size: 739 bytes --]

I am working with ML403 as well. Right now, I am using a 2.4.26 kernel, but
I would be interested in a 2.6 one, it would be great!!

Happy 2006!!
Paula Saameno

Florian wrote:
>> I don't have a public git tree at the moment for the xilinx virtex
>> stuff.  I can certainly create and maintain one if there is demand.  I
>> guess it depends on how many people want to colaborate on V2Pro/V4
>> support.  Anyone else interested?
>
>
> Yes. I am also working on a Virtex-4 system with Linux.
> Do you support also a Linux 2.4 tree?
Sorry, no.  I'm focusing on the 2.6 stuff.  IIRC, the Denx tree is
tracking the virtex support in 2.4.

Are you strictly working on 2.4?  Or are you interested in 2.6 as well?

Cheers,
g.

[-- Attachment #2: Type: text/html, Size: 889 bytes --]

Re: [PATCH 8/8] Add support for Xilinx ML403 reference design

[Grant Likely]

Paula Saameño wrote:
> I am working with ML403 as well. Right now, I am using a 2.4.26 kernel,
> but I would be interested in a 2.6 one, it would be great!!
> 
> Happy 2006!!
> Paula Saameno

Thanks Paula.

Can you try the posted patches on your ML403?  It should compile and
boot with no problems with the reference design.  (However, I got the
memory size initialization wrong; add mem=64M to the kernel command line)

I'll send a patch to fix the mem size tomorrow.

Thanks,
g.

> 
> Florian wrote:
>>> I don't have a public git tree at the moment for the xilinx virtex
>>> stuff.  I can certainly create and maintain one if there is demand.  I
>>> guess it depends on how many people want to colaborate on V2Pro/V4
>>> support.  Anyone else interested?
>>
>>
>> Yes. I am also working on a Virtex-4 system with Linux.
>> Do you support also a Linux 2.4 tree?
> Sorry, no.  I'm focusing on the 2.6 stuff.  IIRC, the Denx tree is
> tracking the virtex support in 2.4.
> 
> Are you strictly working on 2.4?  Or are you interested in 2.6 as well?
> 
> Cheers,
> g.
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded


-- 
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
(403) 663-0761

Re: [PATCH 8/8] Add support for Xilinx ML403 reference design

[Paula Saameño]

[-- Attachment #1: Type: text/plain, Size: 1682 bytes --]

Hi Grant,

I´ll try the patches today and I let you know how is going.

See you!

On 1/3/06, Grant Likely <grant.likely@secretlab.ca> wrote:
>
> Paula Saameño wrote:
> > I am working with ML403 as well. Right now, I am using a 2.4.26 kernel,
> > but I would be interested in a 2.6 one, it would be great!!
> >
> > Happy 2006!!
> > Paula Saameno
>
> Thanks Paula.
>
> Can you try the posted patches on your ML403?  It should compile and
> boot with no problems with the reference design.  (However, I got the
> memory size initialization wrong; add mem=64M to the kernel command line)
>
> I'll send a patch to fix the mem size tomorrow.
>
> Thanks,
> g.
>
> >
> > Florian wrote:
> >>> I don't have a public git tree at the moment for the xilinx virtex
> >>> stuff.  I can certainly create and maintain one if there is demand.  I
> >>> guess it depends on how many people want to colaborate on V2Pro/V4
> >>> support.  Anyone else interested?
> >>
> >>
> >> Yes. I am also working on a Virtex-4 system with Linux.
> >> Do you support also a Linux 2.4 tree?
> > Sorry, no.  I'm focusing on the 2.6 stuff.  IIRC, the Denx tree is
> > tracking the virtex support in 2.4.
> >
> > Are you strictly working on 2.4?  Or are you interested in 2.6 as well?
> >
> > Cheers,
> > g.
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
> --
> Grant Likely, B.Sc. P.Eng.
> Secret Lab Technologies Ltd.
> (403) 663-0761
>

[-- Attachment #2: Type: text/html, Size: 2318 bytes --]

Re: [PATCH 8/8] Add support for Xilinx ML403 reference design

[Grant Likely]

Paula Saameño wrote:
> Hi Grant,
> 
> I´ll try the patches today and I let you know how is going.

BTW, 'make ml403_defconfig' should work


> 
> See you!
> 
> On 1/3/06, *Grant Likely* <grant.likely@secretlab.ca
> <mailto:grant.likely@secretlab.ca>> wrote:
> 
>     Paula Saameño wrote:
>     > I am working with ML403 as well. Right now, I am using a 2.4.26
>     kernel,
>     > but I would be interested in a 2.6 one, it would be great!!
>     >
>     > Happy 2006!!
>     > Paula Saameno
> 
>     Thanks Paula.
> 
>     Can you try the posted patches on your ML403?  It should compile and
>     boot with no problems with the reference design.  (However, I got the
>     memory size initialization wrong; add mem=64M to the kernel command
>     line)
> 
>     I'll send a patch to fix the mem size tomorrow.
> 
>     Thanks,
>     g.
> 
>     >
>     > Florian wrote:
>     >>> I don't have a public git tree at the moment for the xilinx virtex
>     >>> stuff.  I can certainly create and maintain one if there is
>     demand.  I
>     >>> guess it depends on how many people want to colaborate on V2Pro/V4
>     >>> support.  Anyone else interested?
>     >>
>     >>
>     >> Yes. I am also working on a Virtex-4 system with Linux.
>     >> Do you support also a Linux 2.4 tree?
>     > Sorry, no.  I'm focusing on the 2.6 stuff.  IIRC, the Denx tree is
>     > tracking the virtex support in 2.4.
>     >
>     > Are you strictly working on 2.4?  Or are you interested in 2.6 as
>     well?
>     >
>     > Cheers,
>     > g.
>     >
>     >
>     >
>     ------------------------------------------------------------------------
>     >
>     > _______________________________________________
>     > Linuxppc-embedded mailing list
>     > Linuxppc-embedded@ozlabs.org <mailto:Linuxppc-embedded@ozlabs.org>
>     > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 
> 
>     --
>     Grant Likely, B.Sc. P.Eng.
>     Secret Lab Technologies Ltd.
>     (403) 663-0761
> 
> 


-- 
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
(403) 663-0761