* RE: MPC5200 kernel with IDE *and* FEC?
From: Stephen Warren @ 2005-03-08 20:16 UTC (permalink / raw)
To: wd; +Cc: linuxppc-embedded
From: wd@denx.de [mailto:wd@denx.de]=20
> In message
<DBFABB80F7FD3143A911F9E6CFD477B0056A92B5@hqemmail02.nvidia.com> you
wrote:
> >=20
> > By the way, to the people who mentioned using Debian and Gentoo on
the
> > MPC5200, are there any web-sites that have info on how to do this
> > (toolchain and/or distro)? I haven't managed to find anything
remotely
> > detailed on cross-building either of these distros. But I'll
probably
> > just do it from scratch now I have NPTL-aware toolchain:-)
>=20
> You don't have to cross-build anything; you can just use the existing
> ISO images for installation. For Debian Woody you can find a detailed
> description (thanks to bernhard Kuhn for this!) at
>
http://www.denx.de/twiki/bin/view/DULG/DebianOnPowerpcInstallationHowto=20
That could save a lot of time, but is this kernel 2.4-based? The docs
there imply that (buildling a kernel natively section references paths
with 2_4 in them).
We already have a 2.4-based MontaVista, but we're trying to get a 2.6
kernel up and running with NPTL to compare the pthreads performance
differences...
Thanks for the pointer though.
--=20
Stephen Warren, Software Engineer, NVIDIA, Fort Collins, CO
swarren@nvidia.com http://www.nvidia.com/
swarren@wwwdotorg.org http://www.wwwdotorg.org/pgp.html
^ permalink raw reply
* Re: MPC5200 kernel with IDE *and* FEC?
From: Wolfgang Denk @ 2005-03-08 20:03 UTC (permalink / raw)
To: Stephen Warren; +Cc: linuxppc-embedded
In-Reply-To: <DBFABB80F7FD3143A911F9E6CFD477B0056A92B5@hqemmail02.nvidia.com>
In message <DBFABB80F7FD3143A911F9E6CFD477B0056A92B5@hqemmail02.nvidia.com> you wrote:
>
> By the way, to the people who mentioned using Debian and Gentoo on the
> MPC5200, are there any web-sites that have info on how to do this
> (toolchain and/or distro)? I haven't managed to find anything remotely
> detailed on cross-building either of these distros. But I'll probably
> just do it from scratch now I have NPTL-aware toolchain:-)
You don't have to cross-build anything; you can just use the existing
ISO images for installation. For Debian Woody you can find a detailed
description (thanks to bernhard Kuhn for this!) at
http://www.denx.de/twiki/bin/view/DULG/DebianOnPowerpcInstallationHowto
In the meantime we swithched to using Ubuntu Linux on the 5200, but
here installation is a bit more complicated as you will have to
twiddle with the installation ramdisk image, and later perform
certain steps manually. It's probably easier to copy the filesystem
from a "real" PowerPC system ;-)
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
If I can have honesty, it's easier to overlook mistakes.
-- Kirk, "Space Seed", stardate 3141.9
^ permalink raw reply
* Re: MPC5200 kernel with IDE *and* FEC?
From: Wolfgang Denk @ 2005-03-08 20:00 UTC (permalink / raw)
To: Stephen Warren; +Cc: linuxppc-embedded
In-Reply-To: <DBFABB80F7FD3143A911F9E6CFD477B0056A92CC@hqemmail02.nvidia.com>
In message <DBFABB80F7FD3143A911F9E6CFD477B0056A92CC@hqemmail02.nvidia.com> you wrote:
>
> We've used IDE (for a DVD-ROM) using the Denx kernel. This didn't have
> DMA suppport, but Freescale gave us a derivate kernel that it, which
The kernel on our CVS server does support DMA - at least to the lavel
that is available with the current IDE driver and microcode.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
On a clear disk you can seek forever.
^ permalink raw reply
* Re: [PATCH] final mv643xx_eth pegasos patch set ...
From: Sven Luther @ 2005-03-08 19:52 UTC (permalink / raw)
To: Benjamin Herrenschmidt
Cc: linuxppc-dev list, Dale Farnsworth, linuxppc-embedded,
Nicolas DET
In-Reply-To: <20050308192805.GA13884@pegasos>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
On Tue, Mar 08, 2005 at 08:28:05PM +0100, luther wrote:
> Hello,
>
> Ok, thanks for your help, here is the final (hopefully) and cleaned up version
> of my patches :
>
> 1) mv643xx-eth-pegasos.diff
> This is the arch/ppc/platform diff, benh, could you look it over, and merge
> it in ? It is not really usefull without the mv643xx_eth.c changes, but dale
> is going to move those in together with his patches.
>
> 2) linux-2.5-mv643xx-enet-pegasos.diff
> This is just two small hunks against dale's linux-2.5-mv643xx-enet tree,
> which include the SA_INTERRUPT -> SA_IRQ and the Kconfig change. Dale said
> he would merge them with his stuff, hopefully for 2.6.12.
>
> 3) mv643xx-eth.diff
> This is the linux-2.5-mv643xx-enet diff against 2.6.11, together with the
> linux-2.5-mv643xx-enet-pegasos.diff changes, for those who want to build
> against 2.6.11.
>
> So to build against the linux-2.5-mv643xx-enet tree, you need 1) and 2) and to
> build against 2.6.11 you need 1) and 3).
>
> I am currently running the patches included in these changes, and will include
> them in the debian 2.6.11 kernels unless i hear otherwise.
Oh well, with the patches this time :/
Friendly,
Sven Luther
[-- Attachment #2: mv643xx-eth-pegasos.diff --]
[-- Type: text/plain, Size: 3683 bytes --]
--- linux-dale/arch/ppc/platforms/Makefile 2005-03-08 09:52:44.000000000 +0100
+++ kernel-source-2.6.11-marvell/arch/ppc/platforms/Makefile 2005-03-08 17:33:29.000000000 +0100
@@ -12,7 +12,7 @@
obj-$(CONFIG_PPC_PMAC) += pmac_pic.o pmac_setup.o pmac_time.o \
pmac_feature.o pmac_pci.o pmac_sleep.o \
pmac_low_i2c.o pmac_cache.o
-obj-$(CONFIG_PPC_CHRP) += chrp_setup.o chrp_time.o chrp_pci.o
+obj-$(CONFIG_PPC_CHRP) += chrp_setup.o chrp_time.o chrp_pci.o mv643xx_eth_pegasos.o
obj-$(CONFIG_PPC_PREP) += prep_pci.o prep_setup.o
ifeq ($(CONFIG_PPC_PMAC),y)
obj-$(CONFIG_NVRAM) += pmac_nvram.o
--- linux-dale/arch/ppc/platforms/mv643xx_eth_pegasos.c 1970-01-01 01:00:00.000000000 +0100
+++ kernel-source-2.6.11-marvell/arch/ppc/platforms/mv643xx_eth_pegasos.c 2005-03-08 20:21:33.000000000 +0100
@@ -0,0 +1,112 @@
+/*
+ * arch/ppc/platforms/mv643xx_eth_pegasos.c
+ *
+ * Copyright (C) 2005 Sven Luther <sl@bplan-gmbh.de>
+ * Thanks to :
+ * Dale Farnsworth <dale@farnsworth.org>
+ * Mark A. Greer <mgreer@mvista.com>
+ * Nicolas DET <nd@bplan-gmbh.de>
+ * Benjamin Herrenschmidt <benh@kernel.crashing.org>
+ * And anyone else who helped me on this.
+ */
+
+#include <linux/types.h>
+#include <asm/prom.h>
+#include <linux/init.h>
+#include <linux/ioport.h>
+#include <linux/device.h>
+#include <linux/mv643xx.h>
+#include <linux/pci_ids.h>
+
+/* Pegasos 2 specific Marvell MV 64361 gigabit ethernet port setup */
+static struct resource mv643xx_eth_shared_resources[] = {
+ [0] = {
+ .name = "ethernet shared base",
+ .start = 0xf1000000 + MV643XX_ETH_SHARED_REGS,
+ .end = 0xf1000000 + MV643XX_ETH_SHARED_REGS +
+ MV643XX_ETH_SHARED_REGS_SIZE - 1,
+ .flags = IORESOURCE_MEM,
+ },
+};
+
+static struct platform_device mv643xx_eth_shared_device = {
+ .name = MV643XX_ETH_SHARED_NAME,
+ .id = 0,
+ .num_resources = ARRAY_SIZE(mv643xx_eth_shared_resources),
+ .resource = mv643xx_eth_shared_resources,
+};
+
+#ifdef CONFIG_MV643XX_ETH_0
+static struct resource mv643xx_eth0_resources[] = {
+ [0] = {
+ .name = "eth0 irq",
+ .start = 9,
+ .end = 9,
+ .flags = IORESOURCE_IRQ,
+ },
+};
+
+static struct mv643xx_eth_platform_data eth0_pd;
+
+static struct platform_device eth0_device = {
+ .name = MV643XX_ETH_NAME,
+ .id = 0,
+ .num_resources = ARRAY_SIZE(mv643xx_eth0_resources),
+ .resource = mv643xx_eth0_resources,
+ .dev = {
+ .platform_data = ð0_pd,
+ },
+};
+#endif
+
+#ifdef CONFIG_MV643XX_ETH_1
+static struct resource mv643xx_eth1_resources[] = {
+ [0] = {
+ .name = "eth1 irq",
+ .start = 9,
+ .end = 9,
+ .flags = IORESOURCE_IRQ,
+ },
+};
+
+static struct mv643xx_eth_platform_data eth1_pd;
+
+static struct platform_device eth1_device = {
+ .name = MV643XX_ETH_NAME,
+ .id = 1,
+ .num_resources = ARRAY_SIZE(mv643xx_eth1_resources),
+ .resource = mv643xx_eth1_resources,
+ .dev = {
+ .platform_data = ð1_pd,
+ },
+};
+#endif
+
+static struct platform_device *mv643xx_eth_pd_devs[] __initdata = {
+ &mv643xx_eth_shared_device,
+#ifdef CONFIG_MV643XX_ETH_0
+ ð0_device,
+#endif
+#ifdef CONFIG_MV643XX_ETH_1
+ ð1_device,
+#endif
+};
+
+static int __init
+mv643xx_eth_add_pds(void)
+{
+ int ret = 0;
+ struct device_node *np;
+ np = find_devices("host");
+ if (np != NULL) {
+ unsigned short *vendorid = (unsigned short *) get_property (np, "vendor-id", NULL);
+ unsigned short *deviceid = (unsigned short *) get_property (np, "device-id", NULL);
+
+ if (vendorid && *vendorid == PCI_VENDOR_ID_MARVELL &&
+ deviceid && *deviceid == PCI_DEVICE_ID_MARVELL_MV64360)
+ ret = platform_add_devices(mv643xx_eth_pd_devs,
+ ARRAY_SIZE(mv643xx_eth_pd_devs));
+ }
+ return ret;
+}
+arch_initcall(mv643xx_eth_add_pds);
[-- Attachment #3: mv643xx-eth-pegasos.diff --]
[-- Type: text/plain, Size: 3683 bytes --]
--- linux-dale/arch/ppc/platforms/Makefile 2005-03-08 09:52:44.000000000 +0100
+++ kernel-source-2.6.11-marvell/arch/ppc/platforms/Makefile 2005-03-08 17:33:29.000000000 +0100
@@ -12,7 +12,7 @@
obj-$(CONFIG_PPC_PMAC) += pmac_pic.o pmac_setup.o pmac_time.o \
pmac_feature.o pmac_pci.o pmac_sleep.o \
pmac_low_i2c.o pmac_cache.o
-obj-$(CONFIG_PPC_CHRP) += chrp_setup.o chrp_time.o chrp_pci.o
+obj-$(CONFIG_PPC_CHRP) += chrp_setup.o chrp_time.o chrp_pci.o mv643xx_eth_pegasos.o
obj-$(CONFIG_PPC_PREP) += prep_pci.o prep_setup.o
ifeq ($(CONFIG_PPC_PMAC),y)
obj-$(CONFIG_NVRAM) += pmac_nvram.o
--- linux-dale/arch/ppc/platforms/mv643xx_eth_pegasos.c 1970-01-01 01:00:00.000000000 +0100
+++ kernel-source-2.6.11-marvell/arch/ppc/platforms/mv643xx_eth_pegasos.c 2005-03-08 20:21:33.000000000 +0100
@@ -0,0 +1,112 @@
+/*
+ * arch/ppc/platforms/mv643xx_eth_pegasos.c
+ *
+ * Copyright (C) 2005 Sven Luther <sl@bplan-gmbh.de>
+ * Thanks to :
+ * Dale Farnsworth <dale@farnsworth.org>
+ * Mark A. Greer <mgreer@mvista.com>
+ * Nicolas DET <nd@bplan-gmbh.de>
+ * Benjamin Herrenschmidt <benh@kernel.crashing.org>
+ * And anyone else who helped me on this.
+ */
+
+#include <linux/types.h>
+#include <asm/prom.h>
+#include <linux/init.h>
+#include <linux/ioport.h>
+#include <linux/device.h>
+#include <linux/mv643xx.h>
+#include <linux/pci_ids.h>
+
+/* Pegasos 2 specific Marvell MV 64361 gigabit ethernet port setup */
+static struct resource mv643xx_eth_shared_resources[] = {
+ [0] = {
+ .name = "ethernet shared base",
+ .start = 0xf1000000 + MV643XX_ETH_SHARED_REGS,
+ .end = 0xf1000000 + MV643XX_ETH_SHARED_REGS +
+ MV643XX_ETH_SHARED_REGS_SIZE - 1,
+ .flags = IORESOURCE_MEM,
+ },
+};
+
+static struct platform_device mv643xx_eth_shared_device = {
+ .name = MV643XX_ETH_SHARED_NAME,
+ .id = 0,
+ .num_resources = ARRAY_SIZE(mv643xx_eth_shared_resources),
+ .resource = mv643xx_eth_shared_resources,
+};
+
+#ifdef CONFIG_MV643XX_ETH_0
+static struct resource mv643xx_eth0_resources[] = {
+ [0] = {
+ .name = "eth0 irq",
+ .start = 9,
+ .end = 9,
+ .flags = IORESOURCE_IRQ,
+ },
+};
+
+static struct mv643xx_eth_platform_data eth0_pd;
+
+static struct platform_device eth0_device = {
+ .name = MV643XX_ETH_NAME,
+ .id = 0,
+ .num_resources = ARRAY_SIZE(mv643xx_eth0_resources),
+ .resource = mv643xx_eth0_resources,
+ .dev = {
+ .platform_data = ð0_pd,
+ },
+};
+#endif
+
+#ifdef CONFIG_MV643XX_ETH_1
+static struct resource mv643xx_eth1_resources[] = {
+ [0] = {
+ .name = "eth1 irq",
+ .start = 9,
+ .end = 9,
+ .flags = IORESOURCE_IRQ,
+ },
+};
+
+static struct mv643xx_eth_platform_data eth1_pd;
+
+static struct platform_device eth1_device = {
+ .name = MV643XX_ETH_NAME,
+ .id = 1,
+ .num_resources = ARRAY_SIZE(mv643xx_eth1_resources),
+ .resource = mv643xx_eth1_resources,
+ .dev = {
+ .platform_data = ð1_pd,
+ },
+};
+#endif
+
+static struct platform_device *mv643xx_eth_pd_devs[] __initdata = {
+ &mv643xx_eth_shared_device,
+#ifdef CONFIG_MV643XX_ETH_0
+ ð0_device,
+#endif
+#ifdef CONFIG_MV643XX_ETH_1
+ ð1_device,
+#endif
+};
+
+static int __init
+mv643xx_eth_add_pds(void)
+{
+ int ret = 0;
+ struct device_node *np;
+ np = find_devices("host");
+ if (np != NULL) {
+ unsigned short *vendorid = (unsigned short *) get_property (np, "vendor-id", NULL);
+ unsigned short *deviceid = (unsigned short *) get_property (np, "device-id", NULL);
+
+ if (vendorid && *vendorid == PCI_VENDOR_ID_MARVELL &&
+ deviceid && *deviceid == PCI_DEVICE_ID_MARVELL_MV64360)
+ ret = platform_add_devices(mv643xx_eth_pd_devs,
+ ARRAY_SIZE(mv643xx_eth_pd_devs));
+ }
+ return ret;
+}
+arch_initcall(mv643xx_eth_add_pds);
[-- Attachment #4: mv643xx-eth.diff.gz --]
[-- Type: application/octet-stream, Size: 39442 bytes --]
^ permalink raw reply
* Re: [Bugme-new] [Bug 4310] New: ppc 8260 fcc ethernet driver cannot read LXT971 PHY id
From: Andrew Morton @ 2005-03-08 19:48 UTC (permalink / raw)
To: oray; +Cc: linuxppc-dev, netdev
In-Reply-To: <200503081415.j28EF9CG002475@fire-1.osdl.org>
I'm not sure that we have a maintainer for fcc_enet.c. Could you
please send in a tested diff?
bugme-daemon@osdl.org wrote:
>
> http://bugme.osdl.org/show_bug.cgi?id=4310
>
> Summary: ppc 8260 fcc ethernet driver cannot read LXT971 PHY id
> Kernel Version: 2.6.10
> Status: NEW
> Severity: normal
> Owner: platform_ppc-32@kernel-bugs.osdl.org
> Submitter: oray@lucent.com
>
>
> Distribution: www.kernel.org
> Hardware Environment: Target: PowerPC 8260 custom board
> Software Environment: Red Hat 9 cross development using ELDK 3.1 distribution.
> Problem Description: Fast ethernet driver (fcc_enet.c) initialization fails to
> read a valid id from registers 2 and 3 of the LXT971 PHY device and calls the
> panic routine. The bug is in the mii_send_receive() function. During the read
> phase, per LXT971 data sheet, the device starts driving the MDIO line after the
> rising edge of the MDC clock and it could take up to 150ns before the data
> settles. The driver reads the MDIO line before waiting for the data to settle
> down and thus reads in garbage. I fixed the problem by moving the sampling of
> the MDIO line to after the MDC clock is taken low. The code snippet follows:
>
>
> for (i = 0, off = 15; i < 16; i++, off--)
> {
> #define FCC_8260_BUG
> FCC_PDATC_MDC(1);
> retval <<= 1;
> #ifndef FCC_8260_BUG
> if (io->iop_pdatc & fip->fc_mdio)
> retval++;
> udelay(1);
> FCC_PDATC_MDC(0);
> #else
> udelay(1);
> FCC_PDATC_MDC(0);
> if (io->iop_pdatc & fip->fc_mdio)
> retval++;
> #endif
> udelay(1);
> #undef FCC_8260_BUG
> }
>
>
> Steps to reproduce: Is likely to happen on an 8260 target with any kind of PHY,
> not just the LXT971, hooked up to the FCC port.
>
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply
* [PATCH] final mv643xx_eth pegasos patch set ...
From: Sven Luther @ 2005-03-08 19:28 UTC (permalink / raw)
To: Benjamin Herrenschmidt
Cc: linuxppc-dev list, Dale Farnsworth, linuxppc-embedded,
Nicolas DET
In-Reply-To: <1110266832.13607.267.camel@gaston>
Hello,
Ok, thanks for your help, here is the final (hopefully) and cleaned up version
of my patches :
1) mv643xx-eth-pegasos.diff
This is the arch/ppc/platform diff, benh, could you look it over, and merge
it in ? It is not really usefull without the mv643xx_eth.c changes, but dale
is going to move those in together with his patches.
2) linux-2.5-mv643xx-enet-pegasos.diff
This is just two small hunks against dale's linux-2.5-mv643xx-enet tree,
which include the SA_INTERRUPT -> SA_IRQ and the Kconfig change. Dale said
he would merge them with his stuff, hopefully for 2.6.12.
3) mv643xx-eth.diff
This is the linux-2.5-mv643xx-enet diff against 2.6.11, together with the
linux-2.5-mv643xx-enet-pegasos.diff changes, for those who want to build
against 2.6.11.
So to build against the linux-2.5-mv643xx-enet tree, you need 1) and 2) and to
build against 2.6.11 you need 1) and 3).
I am currently running the patches included in these changes, and will include
them in the debian 2.6.11 kernels unless i hear otherwise.
Friendly,
Sven Luther
^ permalink raw reply
* RE: MPC5200 kernel with IDE *and* FEC?
From: Stephen Warren @ 2005-03-08 19:09 UTC (permalink / raw)
To: Dale Farnsworth, linuxppc-embedded
From: Dale Farnsworth [mailto:dale@farnsworth.org]=20
> On Tue, Mar 08, 2005 at 05:34:20PM +0000, Stephen Warren wrote:
> > I looked at the 2.6.11 kernel.org kernel, and it has MPC5200 IDE
> > support, but apparently no FEC driver support.
>=20
> Are you sure it has MPC5200 IDE support? I have yet to see reliable
> 5200 IDE support and haven't seen a 5200 IDE driver for 2.6 at all.
Not sure, no. Looking at "xconfig", I don't see an option for it. A
colleague said it did.
We've used IDE (for a DVD-ROM) using the Denx kernel. This didn't have
DMA suppport, but Freescale gave us a derivate kernel that it, which
seemed to work well. They said they were going to push this up through
Denx into the main kernel. Didn't they bother to do this?
> I did the FEC driver in Sylvain's tree. He has promised to push
> it to kernel.org RSN.
That'd be great.
--=20
Stephen Warren, Software Engineer, NVIDIA, Fort Collins, CO
swarren@nvidia.com http://www.nvidia.com/
swarren@wwwdotorg.org http://www.wwwdotorg.org/pgp.html
^ permalink raw reply
* Re: Lots of memory on 826x
From: Mark Chambers @ 2005-03-08 18:54 UTC (permalink / raw)
To: Rune Torgersen; +Cc: linuxppc-embedded
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B8592E9@ismail.innsys.innovsys.com>
>Now I can almost boot....:
>It craches when trying to read from harddisk
>(only happens with more than 512MB)
Don't rule out a hardware problem, namely addressing to SDRAM. It could be
consistent with what you're seeing - when you start to load a lot of data
and
cross some address you step on older data (or code).
--Mark C.
> > Anybody know how to get more than 512MB (1-2GB) of RAM to work with
> > 2.6.11 on a 8265?
> >
> > Weird stuff and crashes keep happening on kernel start
> (vmalloc out of
> > memory, and a pci driver ups) when I tell the kernel I have
> more than
> > 512MB of ram.
> > The pci craches happens when I tell the kernel I have 740-760MB or
> > more.
> >
> > Any idea of where to start to look for this?
> >
^ permalink raw reply
* RE: Lots of memory on 826x
From: Rune Torgersen @ 2005-03-08 18:37 UTC (permalink / raw)
To: Kumar Gala; +Cc: linuxppc-embedded
Ok... Got a little closer....
I have PCI (outbound) mapped in the area 0x80000000-0x8fffffff
(prefetch/non-prefetch and IO)
IMMR of cource is at 0xf0000000
So I map the IO as following:
/* Map IMMR region to a 256MB BAT */
addr =3D (cpm2_immr !=3D NULL) ? (uint)cpm2_immr : CPM_MAP_ADDR;
io_block_mapping(addr, addr, 0x10000000, _PAGE_IO);
io_block_mapping(0x80000000, 0x80000000, 0x10000000, _PAGE_IO);
Now I can almost boot....:
It craches when trying to read from harddisk
(only happens with more than 512MB)
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem).
Freeing unused kernel memory: 288k init
Machine check in kernel mode.
Caused by (from SRR1=3D49030): Transfer error ack signal
Oops: machine check, sig: 7 [#1]
PREEMPT
NIP: C000E3FC LR: C0037728 SP: EFC11C50 REGS: efc11ba0 TRAP: 0200 Not
tainted
MSR: 00049030 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
TASK =3D c0be9ae0[1] 'swapper' THREAD: efc10000
Last syscall: 11
GPR00: 00000001 EFC11C50 C0BE9AE0 00000024 FE402FFC 00000000 EFE939FC
81040008
GPR08: 8124000C C02A0000 3FF80581 00000004 00000092 100C1B1C EFE9E98C
EFEA6498
GPR16: 00000007 00000001 00000000 00000000 EFC11D18 EFC11DC8 00000000
EFE9E940
GPR24: 00000000 00000000 00000080 000074A0 C0B06000 FE403000 00000080
EFC11D18
NIP [c000e3fc] __copy_tofrom_user+0xb4/0x234
LR [c0037728] file_read_actor+0x148/0x258
Call trace:
[c00373e4] do_generic_mapping_read+0x408/0x604
[c0037a5c] __generic_file_aio_read+0x224/0x254
[c0037ac8] generic_file_aio_read+0x3c/0x5c
[c005ef84] do_sync_read+0xa0/0xe4
[c005f090] vfs_read+0xc8/0x150
[c006ccbc] kernel_read+0x40/0x58
[c006d994] prepare_binprm+0xd0/0xec
[c006e098] do_execve+0x138/0x21c
[c0006bb8] sys_execve+0x98/0xf8
[c0003c80] ret_from_syscall+0x0/0x44
[c00063ac] execve+0x8/0x1c
[c0003a98] init+0xb0/0xf8
[c0006384] kernel_thread+0x44/0x60
Kernel panic - not syncing: Attempted to kill init!
<0>Rebooting in 180 seconds..=20
> -----Original Message-----
> From: Kumar Gala [mailto:kumar.gala@freescale.com]=20
> Sent: Tuesday, March 08, 2005 12:07
> To: Rune Torgersen
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: Lots of memory on 826x
>=20
> I would start looking at what addresses are getting assigned for=20
> VMALLOC vs any io_block_mapping() calls. I know I've had=20
> problems with=20
> large amount of memory in systems if the virt addrs allocated in=20
> io_block_mapping calls conflict with vmalloc addrs.
>=20
> - kumar
>=20
> On Mar 8, 2005, at 11:33 AM, Rune Torgersen wrote:
>=20
> > Anybody know how to get more than 512MB (1-2GB) of RAM to work with
> > 2.6.11 on a 8265?
> >
> > Weird stuff and crashes keep happening on kernel start=20
> (vmalloc out of
> > memory, and a pci driver ups) when I tell the kernel I have=20
> more than
> > 512MB of ram.
> > The pci craches happens when I tell the kernel I have 740-760MB or=20
> > more.
> >
> > Any idea of where to start to look for this?
> >
> > Rune Torgersen
> > System Developer
> > Innovative Systems LLC
> > 1000 Innovative Drive
> > Mitchell, SD 57301
> > Ph: 605-995-6120
> > www.innovsys.com
> > _______________________________________________
> > Linuxppc-embedded mailing list
> > Linuxppc-embedded@ozlabs.org
> > https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>=20
>=20
>=20
^ permalink raw reply
* Re: mv643xx_eth SA_SHIRQ support patch
From: Sven Luther @ 2005-03-08 18:19 UTC (permalink / raw)
To: Mark A. Greer; +Cc: Nicolas DET, Dale Farnsworth, linuxppc-dev list
In-Reply-To: <422DECA6.1090408@mvista.com>
On Tue, Mar 08, 2005 at 11:19:18AM -0700, Mark A. Greer wrote:
> Sven Luther wrote:
>
> >Also going to add the explicit detection of the marvell bridge in the OF
> >tree,
> >
>
> Do you really need to do that, though? Just finding "Pegasos" or
> "Pegasos2" in the 'model' field of the device tree should be sufficient,
> shouldn't it? (if I'm reading the code correctly)
Well, benh suggested it, so ... Basically i look for a host named node which
is a marvel discovery 2 pci id.
> >but need to decide what to check for there.
>
> The only way that I know of to tell if you're on a mv64x60 bridge is to
> do a pci cfg read of the vendor/device id fields of fcn 0 of the
Yep, this is what i chose. Well in the of device tree not the pci-config
thingy.
> bridge's device on that pci hose. By default, the bus number of both
> hoses are 0 (but OF probably sets the second one to be > 0 depending on
> how many pci buses there are hanging off hose 0), the bridge will be
> device 0 on both hoses, the vendor id will be PCI_VENDOR_ID_MARVELL
> (0x11ab) and the device id will be PCI_DEVICE_ID_MARVELL_MV64360
> (0x6460) for a mv64360.
Nice, didn't think about using the #defines, will modify this.
> Unfortunately, the bus number of each hose, the device # of the bridge's
> device on that hose (see "PCI P2P Configuration" register offsets 0x1d14
> & 0x1d94), and the vendor & device ids (by a pci cfg write to those
> fields) can all be changed by the fw . I guess the device tree tells
> you the bus number of each hose so you can generate the proper cfg
> access and I doubt OF changes the bridge's device # and pci vendor/dev
> id but I wanted to make you aware of the potential.
The only problem would be if there is more than one 'host' node in the OF
device-tree, but i guess chances are good that even if there are more than
one, the first one would be the marvell one. Well, there are at least two,
one per bus, but i mean beyond that.
The driver seems to work, i was able to launch a dhclient on top of it, but
didn't do more testing. I will do some additional cleanup, and then i think
the patch will be ready.
Thanks for your help, you and Dale and Ben and the others who gave hints on
how to make this happen.
Friendly,
Sven Luther
^ permalink raw reply
* 2.6.11 prep image on radstone ppc4a not booting
From: Brian V. Madzarevic @ 2005-03-08 18:11 UTC (permalink / raw)
To: linuxppc-dev
I am trying to boot a Linux 2.6.11 prep image on a Radstone PPC4A.
PPC4A Specifications http://www.radstone.com/rtcd/pdfs/ppc4a.pdf
I was trying to get an nfs filesystem mounted, but after the bios
retrieves the kernel using tftp, no more packets are even sent out. I
don't know if there is a problem with the network driver or the PCI bus
or what.
Here is my boot log:
Radstone Technology.
SilverChip PowerPC PReP Boot Firmware
Version: 4.05
Built (Jan 20 2004 10:34:02)
PPC4a-7400 333MHz, 83MHz Bus Rev. 3B Ser. No. 0003815 ID No. 0xd
PCI devices
0 0 ID 0x00021057 Motorola MPC106 PowerPC Chipset, Rev. 4.0
0 1 Fn 0 ID 0x056510ad Winbond W83C553F ISA bridge, Rev. 1.0
0 1 Fn 1 ID 0x010510ad Winbond W83C553F IDE controller, Rev. 0.5
0 2 ID 0x00061000 LSI 53C860 Ultra SCSI/Narrow, Rev. 0.2
0 3 ID 0x00191011 DEC DC21143 PCI/CardBus 10/100 Mbit Ethernet Ctlr,
Rev. 4.1
0 4 ID 0x000010e3 Tundra CA91C042 VMEbus Bridge, Rev. 0.1
2 Mbytes of L2 cache on a 133MHz cache bus
128 Mbytes of SDRAM
Floppy drive 0
Floppy drive 1
SCSI id 0
SCSI id 1
SCSI id 2
SCSI id 3
SCSI id 4
SCSI id 5
SCSI id 6
No keyboard found. Using COM1 for input.
No boot authentication required
Opening File
"multi()net()server(192.168.1.73)clientip(192.168.1.147)brian26.prp"
Loading ...
loaded at: 00800400 00912F4C
relocated to: 00800000 00912B4C
zimage at: 0080A86C 00909B2E
avail ram: 00400000 00800000
Linux/PPC load: console=3DttyS0,9600 console=3Dtty0 panic=3D0 =
root=3D/dev/nfs
nfsroot=3D192.168.1.73:/export/nfsroot
ip=3D192.168.1.147:192.168.1.73::255.255.255.0::eth0
Uncompressing Linux...done.
Now booting the kernel
Total memory =3D 128MB; using 256kB for hash table (at c0240000)
Linux version 2.6.11 (brian@rex) (gcc version 3.4.1) #6 Mon Mar 7
15:50:16 PST 2005
PReP architecture
Built 1 zonelists
Kernel command line: console=3DttyS0,9600 console=3Dtty0 panic=3D0
root=3D/dev/nfs nfsroot=3D192.168.1.73:/export/nfsroot
ip=3D192.168.1.147:192.168.1.73::255.255.255.0::eth0
PID hash table entries: 1024 (order: 10, 16384 bytes)
TODC real-time-clock was stopped. Now starting...
time_init: decrementer frequency =3D 20.833333 MHz
Warning: real time clock seems stuck!
Console: colour dummy device 80x25
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 127232k available (1512k kernel code, 640k data, 136k init, 0k
highmem)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
NET: Registered protocol family 16
PCI: Probing PCI hardware
Setting PCI interrupts for a "Blackhawk (Powerstack)"
PCI: Cannot allocate resource region 0 of device 0000:00:0b.1
PCI: Cannot allocate resource region 1 of device 0000:00:0b.1
PCI: Cannot allocate resource region 2 of device 0000:00:0b.1
PCI: Cannot allocate resource region 3 of device 0000:00:0b.1
PCI: Cannot allocate resource region 4 of device 0000:00:0b.1
PCI: Cannot allocate resource region 5 of device 0000:00:0b.1
PCI: Cannot allocate resource region 0 of device 0000:00:0c.0
PCI: Cannot allocate resource region 0 of device 0000:00:0d.0
PCI: Cannot allocate resource region 0 of device 0000:00:0e.0
PCI: I/O Region 0000:00:0e.0/0 too large (4096 bytes)
PCI: I/O Region 0000:00:0e.0/0 too large (4096 bytes)
PCI: I/O Region 0000:00:0e.0/0 too large (4096 bytes)
PCI: I/O Region 0000:00:0e.0/0 too large (4096 bytes)
PCI: I/O Region 0000:00:0e.0/0 too large (4096 bytes)
PCI: I/O Region 0000:00:0e.0/0 too large (4096 bytes)
PCI: I/O Region 0000:00:0e.0/0 too large (4096 bytes)
PCI: I/O Region 0000:00:0e.0/0 too large (4096 bytes)
PCI: I/O Region 0000:00:0e.0/0 too large (4096 bytes)
PCI: I/O Region 0000:00:0e.0/0 too large (4096 bytes)
PCI: I/O Region 0000:00:0e.0/0 too large (4096 bytes)
PCI: I/O Region 0000:00:0e.0/0 too large (4096 bytes)
PCI: I/O Region 0000:00:0e.0/0 too large (4096 bytes)
Generic RTC Driver v1.07
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing
disabled
ttyS0 at I/O 0x3f8 (irq =3D 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq =3D 3) is a 16550A
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
Linux Tulip driver version 1.1.13 (May 11, 2002)
tulip0: EEPROM default media type Autosense.
tulip0: Index #0 - Media 10baseT (#0) described by a 21140 non-MII (0)
block.
tulip0: Index #1 - Media 10base2 (#1) described by a <unknown> (8)
block.
tulip0: Index #2 - Media 10baseT (#0) described by a 21140 non-MII (0)
block.
tulip0: Index #3 - Media 10baseT (#0) described by a 21140 non-MII (0)
block.
eth0: Digital DS21143 Tulip rev 65 at 80001080, 00:80:8E:00:5D:5B, IRQ
0.
mice: PS/2 mouse device common for all mice
atkbd.c: keyboard reset failed on isa0060/serio1
atkbd.c: keyboard reset failed on isa0060/serio0
NET: Registered protocol family 2
IP: routing cache hash table of 1024 buckets, 8Kbytes
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
NET: Registered protocol family 1
NET: Registered protocol family 17
IP-Config: Complete:
device=3Deth0, addr=3D192.168.1.147, mask=3D255.255.255.0,
gw=3D255.255.255.255,
host=3D192.168.1.147, domain=3D, nis-domain=3D(none),
bootserver=3D192.168.1.73, rootserver=3D192.168.1.73, rootpath=3D
Looking up port of RPC 100003/2 on 192.168.1.73
portmap: server 192.168.1.73 not responding, timed out
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 192.168.1.73
portmap: server 192.168.1.73 not responding, timed out
Root-NFS: Unable to get mountd port number from server, using default
NETDEV WATCHDOG: eth0: transmit timed out
eth0: 21140 transmit timed out, status f8678105, SIA 000000c5 ffff0001
fffbff7f 8ff04008, resetting...
eth0: transmit timed out, switching to 100baseTx media.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: 21140 transmit timed out, status f8278517, SIA 000000cb ffff0001
fffbff7f 8ff04008, resetting...
eth0: transmit timed out, switching to 10baseT media.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: 21140 transmit timed out, status f8678117, SIA 000000cb ffff0001
fffbff7f 8ff04008, resetting...
eth0: transmit timed out, switching to 10baseT media.
mount: server 192.168.1.73 not responding, timed out
Root-NFS: Server returned error -5 while mounting /export/nfsroot
VFS: Unable to mount root fs via NFS, trying floppy.
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(2,0)
<6>NETDEV WATCHDOG: eth0: transmit timed out
eth0: 21140 transmit timed out, status f8278517, SIA 000000cb ffff0001
fffbff7f 8ff04008, resetting...
eth0: transmit timed out, switching to 10baseT media.
Here is my .config file:=20
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.11
# Mon Mar 7 15:44:49 2005
#
CONFIG_MMU=3Dy
CONFIG_GENERIC_HARDIRQS=3Dy
CONFIG_RWSEM_XCHGADD_ALGORITHM=3Dy
CONFIG_GENERIC_CALIBRATE_DELAY=3Dy
CONFIG_HAVE_DEC_LOCK=3Dy
CONFIG_PPC=3Dy
CONFIG_PPC32=3Dy
CONFIG_GENERIC_NVRAM=3Dy
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=3Dy
# CONFIG_CLEAN_COMPILE is not set
CONFIG_BROKEN=3Dy
CONFIG_BROKEN_ON_SMP=3Dy
#
# General setup
#
CONFIG_LOCALVERSION=3D""
CONFIG_SWAP=3Dy
CONFIG_SYSVIPC=3Dy
CONFIG_POSIX_MQUEUE=3Dy
CONFIG_BSD_PROCESS_ACCT=3Dy
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_SYSCTL=3Dy
# CONFIG_AUDIT is not set
CONFIG_LOG_BUF_SHIFT=3D14
CONFIG_HOTPLUG=3Dy
CONFIG_KOBJECT_UEVENT=3Dy
CONFIG_IKCONFIG=3Dy
CONFIG_IKCONFIG_PROC=3Dy
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=3Dy
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_FUTEX=3Dy
CONFIG_EPOLL=3Dy
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SHMEM=3Dy
CONFIG_CC_ALIGN_FUNCTIONS=3D0
CONFIG_CC_ALIGN_LABELS=3D0
CONFIG_CC_ALIGN_LOOPS=3D0
CONFIG_CC_ALIGN_JUMPS=3D0
# CONFIG_TINY_SHMEM is not set
#
# Loadable module support
#
CONFIG_MODULES=3Dy
CONFIG_MODULE_UNLOAD=3Dy
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=3Dy
CONFIG_MODVERSIONS=3Dy
CONFIG_MODULE_SRCVERSION_ALL=3Dy
CONFIG_KMOD=3Dy
#
# Processor
#
CONFIG_6xx=3Dy
# CONFIG_40x is not set
# CONFIG_44x is not set
# CONFIG_POWER3 is not set
# CONFIG_POWER4 is not set
# CONFIG_8xx is not set
# CONFIG_E500 is not set
# CONFIG_ALTIVEC is not set
# CONFIG_TAU is not set
# CONFIG_CPU_FREQ is not set
# CONFIG_PPC601_SYNC_FIX is not set
CONFIG_PPC_STD_MMU=3Dy
#
# Platform options
#
CONFIG_PPC_MULTIPLATFORM=3Dy
# CONFIG_APUS is not set
# CONFIG_KATANA is not set
# CONFIG_WILLOW is not set
# CONFIG_CPCI690 is not set
# CONFIG_PCORE is not set
# CONFIG_POWERPMC250 is not set
# CONFIG_CHESTNUT is not set
# CONFIG_SPRUCE is not set
# CONFIG_EV64260 is not set
# CONFIG_LOPEC is not set
# CONFIG_MCPN765 is not set
# CONFIG_MVME5100 is not set
# CONFIG_PPLUS is not set
# CONFIG_PRPMC750 is not set
# CONFIG_PRPMC800 is not set
# CONFIG_SANDPOINT is not set
# CONFIG_ADIR is not set
# CONFIG_K2 is not set
# CONFIG_PAL4 is not set
# CONFIG_GEMINI is not set
# CONFIG_EST8260 is not set
# CONFIG_SBC82xx is not set
# CONFIG_SBS8260 is not set
# CONFIG_RPX8260 is not set
# CONFIG_TQM8260 is not set
# CONFIG_ADS8272 is not set
# CONFIG_PQ2FADS is not set
# CONFIG_LITE5200 is not set
CONFIG_PPC_CHRP=3Dy
CONFIG_PPC_PMAC=3Dy
CONFIG_PPC_PREP=3Dy
CONFIG_PPC_OF=3Dy
CONFIG_PPCBUG_NVRAM=3Dy
# CONFIG_SMP is not set
# CONFIG_PREEMPT is not set
# CONFIG_HIGHMEM is not set
CONFIG_BINFMT_ELF=3Dy
# CONFIG_BINFMT_MISC is not set
# CONFIG_PROC_DEVICETREE is not set
CONFIG_PREP_RESIDUAL=3Dy
CONFIG_PROC_PREPRESIDUAL=3Dy
CONFIG_CMDLINE_BOOL=3Dy
CONFIG_CMDLINE=3D"console=3DttyS0,9600 console=3Dtty0 panic=3D0 =
root=3D/dev/nfs
nfsroot=3D192.168.1.73:/export/nfsroot
ip=3D192.168.1.147:192.168.1.73::255.255.255.0::eth0"
#
# Bus options
#
# CONFIG_ISA is not set
CONFIG_GENERIC_ISA_DMA=3Dy
CONFIG_PCI=3Dy
CONFIG_PCI_DOMAINS=3Dy
# CONFIG_PCI_LEGACY_PROC is not set
# CONFIG_PCI_NAMES is not set
#
# PCCARD (PCMCIA/CardBus) support
#
# CONFIG_PCCARD is not set
#
# PC-card bridges
#
#
# Advanced setup
#
# CONFIG_ADVANCED_OPTIONS is not set
#
# Default settings for advanced configuration options are used
#
CONFIG_HIGHMEM_START=3D0xfe000000
CONFIG_LOWMEM_SIZE=3D0x30000000
CONFIG_KERNEL_START=3D0xc0000000
CONFIG_TASK_SIZE=3D0x80000000
CONFIG_BOOT_LOAD=3D0x00800000
#
# Device Drivers
#
#
# Generic Driver Options
#
CONFIG_STANDALONE=3Dy
CONFIG_PREVENT_FIRMWARE_BUILD=3Dy
# CONFIG_FW_LOADER is not set
# CONFIG_DEBUG_DRIVER is not set
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
# CONFIG_PARPORT is not set
#
# Plug and Play support
#
#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_MAC_FLOPPY is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_RAM is not set
CONFIG_BLK_DEV_RAM_COUNT=3D16
CONFIG_INITRAMFS_SOURCE=3D""
# CONFIG_LBD is not set
# CONFIG_CDROM_PKTCDVD is not set
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=3Dy
CONFIG_IOSCHED_AS=3Dy
CONFIG_IOSCHED_DEADLINE=3Dy
CONFIG_IOSCHED_CFQ=3Dy
# CONFIG_ATA_OVER_ETH is not set
#
# ATA/ATAPI/MFM/RLL support
#
# CONFIG_IDE is not set
#
# SCSI device support
#
CONFIG_SCSI=3Dm
CONFIG_SCSI_PROC_FS=3Dy
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=3Dm
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
# CONFIG_CHR_DEV_SG is not set
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
# CONFIG_SCSI_MULTI_LUN is not set
CONFIG_SCSI_CONSTANTS=3Dy
CONFIG_SCSI_LOGGING=3Dy
#
# SCSI Transport Attributes
#
CONFIG_SCSI_SPI_ATTRS=3Dm
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
CONFIG_SCSI_SYM53C8XX_2=3Dm
CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=3D1
CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=3D16
CONFIG_SCSI_SYM53C8XX_MAX_TAGS=3D64
# CONFIG_SCSI_SYM53C8XX_IOMAPPED is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=3Dm
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
# CONFIG_SCSI_MESH is not set
# CONFIG_SCSI_MAC53C94 is not set
#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Macintosh device drivers
#
# CONFIG_ADB is not set
# CONFIG_ADB_CUDA is not set
# CONFIG_ADB_PMU is not set
# CONFIG_MAC_SERIAL is not set
#
# Networking support
#
CONFIG_NET=3Dy
#
# Networking options
#
CONFIG_PACKET=3Dy
# CONFIG_PACKET_MMAP is not set
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=3Dy
# CONFIG_NET_KEY is not set
CONFIG_INET=3Dy
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_PNP=3Dy
CONFIG_IP_PNP_DHCP=3Dy
CONFIG_IP_PNP_BOOTP=3Dy
CONFIG_IP_PNP_RARP=3Dy
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_TUNNEL is not set
CONFIG_IP_TCPDIAG=3Dy
# CONFIG_IP_TCPDIAG_IPV6 is not set
# CONFIG_IPV6 is not set
# CONFIG_NETFILTER is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
# CONFIG_NET_CLS_ROUTE is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
CONFIG_NETDEVICES=3Dy
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=3Dy
# CONFIG_MII is not set
# CONFIG_MACE is not set
# CONFIG_BMAC is not set
# CONFIG_OAKNET is not set
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
#
# Tulip family network device support
#
CONFIG_NET_TULIP=3Dy
# CONFIG_DE2104X is not set
CONFIG_TULIP=3Dy
# CONFIG_TULIP_MWI is not set
# CONFIG_TULIP_MMIO is not set
# CONFIG_TULIP_NAPI is not set
# CONFIG_DE4X5 is not set
# CONFIG_WINBOND_840 is not set
# CONFIG_DM9102 is not set
# CONFIG_HP100 is not set
# CONFIG_NET_PCI is not set
#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set
#
# Token Ring devices
#
# CONFIG_TR is not set
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
#
# ISDN subsystem
#
# CONFIG_ISDN is not set
#
# Telephony Support
#
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=3Dy
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=3Dy
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_MOUSEDEV_SCREEN_X=3D1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=3D768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set
#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=3Dy
CONFIG_SERIO=3Dy
CONFIG_SERIO_I8042=3Dy
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=3Dy
# CONFIG_SERIO_RAW is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=3Dy
CONFIG_KEYBOARD_ATKBD=3Dy
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set
#
# Character devices
#
CONFIG_VT=3Dy
CONFIG_VT_CONSOLE=3Dy
CONFIG_HW_CONSOLE=3Dy
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=3Dy
CONFIG_SERIAL_8250_CONSOLE=3Dy
CONFIG_SERIAL_8250_NR_UARTS=3D4
# CONFIG_SERIAL_8250_EXTENDED is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=3Dy
CONFIG_SERIAL_CORE_CONSOLE=3Dy
# CONFIG_SERIAL_PMACZILOG is not set
CONFIG_UNIX98_PTYS=3Dy
# CONFIG_LEGACY_PTYS is not set
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_NVRAM is not set
CONFIG_GEN_RTC=3Dy
# CONFIG_GEN_RTC_X is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
#
# Ftape, the floppy tape device driver
#
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_RAW_DRIVER is not set
#
# I2C support
#
# CONFIG_I2C is not set
#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set
#
# Misc devices
#
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
#
# Graphics support
#
# CONFIG_FB is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=3Dy
CONFIG_DUMMY_CONSOLE=3Dy
#
# Sound
#
# CONFIG_SOUND is not set
#
# USB support
#
# CONFIG_USB is not set
CONFIG_USB_ARCH_HAS_HCD=3Dy
CONFIG_USB_ARCH_HAS_OHCI=3Dy
#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' may also be
needed; see USB_STORAGE Help for more information
#
#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
#
# MMC/SD Card support
#
# CONFIG_MMC is not set
#
# InfiniBand support
#
# CONFIG_INFINIBAND is not set
#
# File systems
#
# CONFIG_EXT2_FS is not set
# CONFIG_EXT3_FS is not set
# CONFIG_JBD is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
#
# XFS support
#
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=3Dy
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
#
# CD-ROM/DVD Filesystems
#
# CONFIG_ISO9660_FS is not set
# CONFIG_UDF_FS is not set
#
# DOS/FAT/NT Filesystems
#
# CONFIG_MSDOS_FS is not set
# CONFIG_VFAT_FS is not set
# CONFIG_NTFS_FS is not set
#
# Pseudo filesystems
#
CONFIG_PROC_FS=3Dy
CONFIG_PROC_KCORE=3Dy
CONFIG_SYSFS=3Dy
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=3Dy
# CONFIG_TMPFS_XATTR is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=3Dy
#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
#
# Network File Systems
#
CONFIG_NFS_FS=3Dy
CONFIG_NFS_V3=3Dy
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
# CONFIG_NFSD is not set
CONFIG_ROOT_NFS=3Dy
CONFIG_LOCKD=3Dy
CONFIG_LOCKD_V4=3Dy
CONFIG_SUNRPC=3Dy
# CONFIG_RPCSEC_GSS_KRB5 is not set
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=3Dy
#
# Native Language Support
#
# CONFIG_NLS is not set
#
# Library routines
#
# CONFIG_CRC_CCITT is not set
CONFIG_CRC32=3Dy
# CONFIG_LIBCRC32C is not set
#
# Profiling support
#
# CONFIG_PROFILING is not set
#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=3Dy
CONFIG_MAGIC_SYSRQ=3Dy
# CONFIG_SCHEDSTATS is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_INFO is not set
# CONFIG_DEBUG_FS is not set
# CONFIG_KGDB is not set
CONFIG_XMON=3Dy
# CONFIG_BDI_SWITCH is not set
CONFIG_BOOTX_TEXT=3Dy
#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
# CONFIG_CRYPTO is not set
#
# Hardware crypto devices
#
^ permalink raw reply
* Re: mv643xx_eth SA_SHIRQ support patch
From: Mark A. Greer @ 2005-03-08 18:19 UTC (permalink / raw)
To: Sven Luther; +Cc: Nicolas DET, Dale Farnsworth, linuxppc-dev list
In-Reply-To: <20050308121501.GC4556@pegasos>
Sven Luther wrote:
>Also going to add the explicit detection of the marvell bridge in the OF tree,
>
Do you really need to do that, though? Just finding "Pegasos" or
"Pegasos2" in the 'model' field of the device tree should be sufficient,
shouldn't it? (if I'm reading the code correctly)
>but need to decide what to check for there.
>
The only way that I know of to tell if you're on a mv64x60 bridge is to
do a pci cfg read of the vendor/device id fields of fcn 0 of the
bridge's device on that pci hose. By default, the bus number of both
hoses are 0 (but OF probably sets the second one to be > 0 depending on
how many pci buses there are hanging off hose 0), the bridge will be
device 0 on both hoses, the vendor id will be PCI_VENDOR_ID_MARVELL
(0x11ab) and the device id will be PCI_DEVICE_ID_MARVELL_MV64360
(0x6460) for a mv64360.
Unfortunately, the bus number of each hose, the device # of the bridge's
device on that hose (see "PCI P2P Configuration" register offsets 0x1d14
& 0x1d94), and the vendor & device ids (by a pci cfg write to those
fields) can all be changed by the fw . I guess the device tree tells
you the bus number of each hose so you can generate the proper cfg
access and I doubt OF changes the bridge's device # and pci vendor/dev
id but I wanted to make you aware of the potential.
Mark
^ permalink raw reply
* Re: MPC5200 kernel with IDE *and* FEC?
From: Dale Farnsworth @ 2005-03-08 18:10 UTC (permalink / raw)
To: Stephen Warren, linuxppc-embedded
In-Reply-To: <DBFABB80F7FD3143A911F9E6CFD477B0056A92B5@hqemmail02.nvidia.com>
On Tue, Mar 08, 2005 at 05:34:20PM +0000, Stephen Warren wrote:
> I looked at the 2.6.11 kernel.org kernel, and it has MPC5200 IDE
> support, but apparently no FEC driver support.
Are you sure it has MPC5200 IDE support? I have yet to see reliable
5200 IDE support and haven't seen a 5200 IDE driver for 2.6 at all.
I did the FEC driver in Sylvain's tree. He has promised to push
it to kernel.org RSN.
-Dale Farnsworth
^ permalink raw reply
* Re: Lots of memory on 826x
From: Kumar Gala @ 2005-03-08 18:06 UTC (permalink / raw)
To: Rune Torgersen; +Cc: linuxppc-embedded
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B8592E8@ismail.innsys.innovsys.com>
I would start looking at what addresses are getting assigned for
VMALLOC vs any io_block_mapping() calls. I know I've had problems with
large amount of memory in systems if the virt addrs allocated in
io_block_mapping calls conflict with vmalloc addrs.
- kumar
On Mar 8, 2005, at 11:33 AM, Rune Torgersen wrote:
> Anybody know how to get more than 512MB (1-2GB) of RAM to work with
> 2.6.11 on a 8265?
>
> Weird stuff and crashes keep happening on kernel start (vmalloc out of
> memory, and a pci driver ups) when I tell the kernel I have more than
> 512MB of ram.
> The pci craches happens when I tell the kernel I have 740-760MB or
> more.
>
> Any idea of where to start to look for this?
>
> Rune Torgersen
> System Developer
> Innovative Systems LLC
> 1000 Innovative Drive
> Mitchell, SD 57301
> Ph: 605-995-6120
> www.innovsys.com
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
^ permalink raw reply
* Re: Adding machine types to the kernel tree...
From: Debian User @ 2005-03-08 18:01 UTC (permalink / raw)
To: Matt Porter; +Cc: Linux PPC Embedded list, Jakob Viketoft
In-Reply-To: <20050307052732.A26339@cox.net>
On Mon, Mar 07, 2005 at 05:27:32AM -0700, Matt Porter wrote:
> On Mon, Mar 07, 2005 at 11:07:58AM +0100, Jakob Viketoft wrote:
> > Thanks for the comments!
> >
> > Andrew May wrote:
> > > I think a huge first step would be to banish xparameters.h from all the
> > > kernel code.
....
> >
> > I understand that there is numerous resentment against having this file
> > in the kernel and I've been thinking of a solution without it. One such
> > path would be serving the kernel with a OCP list of the devices used,
> > but I'm unsure about the current status of OCP. Is this The Right Way to
> > do it, or are OCP likely to be abandoned further along the 2.6 road?
Not so much resentment, as a realization that xparamters.h is where all
the work is going to flow from.
> > Matt (Porter), I've seen that you've "ported" this to the 2.6 kernel,
> > what do you say?
>
> Don't tie anything permanently to OCP. :) Eventually, 4xx will convert
> to platform devices like other similar SoC type subarches in ppc32 have
> already done. The only reason it hasn't been done yet is that there
> are some other higher priority things on my plate at the moment.
I am still working with an old 2_4_devel kernel myself.
The something better is comming has always held me back from working
on things as well.
Even now OCP is being dropped for platform devices.
And birecs is being dropped for OF.
The kernel I am working with is a step behind both of those.
> However, it seems you are talking about passing information to
> the kernel from some bootrom or full featured firmware. That is
> a separate issue from how information is passed from the arch-code
> into drivers (this is what OCP and platform devices accomplish).
> For now, you could define a birec type for xparameters and
> standardize around passing the info in that. In the future,
> birecs should be replaced by the "flattened OF device tree" method
> that has been discussed here a bit (I know Jon Masters is lurking
> around here, maybe with some code).
A simple fucntion that would take the xparameters.h and create the
birecs/OF data would be a nice way to go.
I would think the func could run on the host to generate a binary
blob that could be attached to the kernel or dropped in flash, for
simple bootloaders.
For a better bootloader it could run the func itself on the target
and put the data in ram, and then fixup the data if needed.
> Even the smallest bootloader rom could put the xparameters.h info in
> a location and point to it using the standard birec method when
> transferring control to the kernel.
I am a U-boot person myself, but I think there will be a higher number
of users that just stick with the standard loader providied by the vendor
and do the wrapper thing in the kernel.
> I belive this would give Andrew the kind of flexibility he would like.
Yes, I think it would.
^ permalink raw reply
* MPC5200 kernel with IDE *and* FEC?
From: Stephen Warren @ 2005-03-08 17:34 UTC (permalink / raw)
To: linuxppc-embedded
I looked at the 2.6.11 kernel.org kernel, and it has MPC5200 IDE
support, but apparently no FEC driver support.
Sylvain's kernel has FEC, but no IDE support.
I don't suppose anyone had any patches hidden away to add one of the
missing pieces to either of these kernels?
By the way, to the people who mentioned using Debian and Gentoo on the
MPC5200, are there any web-sites that have info on how to do this
(toolchain and/or distro)? I haven't managed to find anything remotely
detailed on cross-building either of these distros. But I'll probably
just do it from scratch now I have NPTL-aware toolchain:-)
--=20
Stephen Warren, Software Engineer, NVIDIA, Fort Collins, CO
swarren@nvidia.com http://www.nvidia.com/
swarren@wwwdotorg.org http://www.wwwdotorg.org/pgp.html
^ permalink raw reply
* Lots of memory on 826x
From: Rune Torgersen @ 2005-03-08 17:33 UTC (permalink / raw)
To: linuxppc-embedded
Anybody know how to get more than 512MB (1-2GB) of RAM to work with
2.6.11 on a 8265?
Weird stuff and crashes keep happening on kernel start (vmalloc out of
memory, and a pci driver ups) when I tell the kernel I have more than
512MB of ram.
The pci craches happens when I tell the kernel I have 740-760MB or more.
Any idea of where to start to look for this?
Rune Torgersen
System Developer
Innovative Systems LLC
1000 Innovative Drive
Mitchell, SD 57301
Ph: 605-995-6120
www.innovsys.com
^ permalink raw reply
* Re: [PATCH] WDT Driver for Book-E [1/2] Architecture specific part.
From: Takeharu KATO @ 2005-03-08 17:08 UTC (permalink / raw)
To: Kumar Gala; +Cc: ppcembed
In-Reply-To: <5e548efff8924e163b562381a93ffe35@freescale.com>
Hi Kumar:
Kumar Gala wrote:
> Out of interest how did you test this? If I find some time I will test
> it on an e500 system, just havent given much thought on how to test the
> watchdog though.
>
> - kumar
>
I tested the WDT driver with folowing test programs:
1) API test program which tests ioctl commands.
2) Test program which tests the behavior of the driver when
system hung up due to making interrupt disabled(MSR[EE]=0 case).
This test program is made as a kernel module.
Shall I send these programs off-list?
Regards,
--
Takeharu KATO
^ permalink raw reply
* Re: mv643xx_eth SA_SHIRQ support patch
From: Sven Luther @ 2005-03-08 12:42 UTC (permalink / raw)
To: Sven Luther; +Cc: Nicolas DET, Dale Farnsworth, linuxppc-dev list
In-Reply-To: <20050308121501.GC4556@pegasos>
On Tue, Mar 08, 2005 at 01:15:01PM +0100, Sven Luther wrote:
> On Tue, Mar 08, 2005 at 05:20:48AM -0700, Dale Farnsworth wrote:
> > On Tue, Mar 08, 2005 at 06:27:12PM +1100, Benjamin Herrenschmidt wrote:
> > > > Notice that benh is telling me that you should use SA_SHIRQ always and that
> > > > SA_INTERRUPT should go away, and that you should contact him online if you
> > > > have trouble with that.
> > > >
> > > > > For the pegasos 2, you'll need the second patch which applies after
> > > > > the one I previously sent for chrp_setup.c.
> > > >
> > > > Ok, will test this anyway, and tell you how it works.
> > >
> > > GHeh, ok, just picked up the discussion. Yes, there is really no reason
> > > to use SA_INTERRUPT here, this is a thing of the past.
> >
> > Excellent. Thanks.
> >
> > Here's a new patch to try. :-)
>
> Hehe, i did that myself :)
>
> Anyway, i have another problem though, namely that even though i do
> arch_initcall(mv643xx_eth_add_pds), mv643xx_eth_add_pds is never called, and
> in the mv643xx_eth driver itself, altough the module init is done, _probe
> never gets called. I will now do a build without any #ifdefs around the
> chrp_setup.c stuff (And Christophe Hellwig proposed moving the stuff into
> arch/ppc/platform/pegasos_mv643xx_eth.c), and see if that will solve it.
>
> Also going to add the explicit detection of the marvell bridge in the OF tree,
> but need to decide what to check for there.
Ah, yes, indifinitely a problem with the #ifdefs, will submit a cleaned up
patch in a bit.
Friendly,
Sven Luther
^ permalink raw reply
* Re: mv643xx_eth SA_SHIRQ support patch
From: Sven Luther @ 2005-03-08 12:15 UTC (permalink / raw)
To: Dale Farnsworth; +Cc: linuxppc-dev list, Nicolas DET
In-Reply-To: <20050308122048.GA22866@xyzzy>
On Tue, Mar 08, 2005 at 05:20:48AM -0700, Dale Farnsworth wrote:
> On Tue, Mar 08, 2005 at 06:27:12PM +1100, Benjamin Herrenschmidt wrote:
> > > Notice that benh is telling me that you should use SA_SHIRQ always and that
> > > SA_INTERRUPT should go away, and that you should contact him online if you
> > > have trouble with that.
> > >
> > > > For the pegasos 2, you'll need the second patch which applies after
> > > > the one I previously sent for chrp_setup.c.
> > >
> > > Ok, will test this anyway, and tell you how it works.
> >
> > GHeh, ok, just picked up the discussion. Yes, there is really no reason
> > to use SA_INTERRUPT here, this is a thing of the past.
>
> Excellent. Thanks.
>
> Here's a new patch to try. :-)
Hehe, i did that myself :)
Anyway, i have another problem though, namely that even though i do
arch_initcall(mv643xx_eth_add_pds), mv643xx_eth_add_pds is never called, and
in the mv643xx_eth driver itself, altough the module init is done, _probe
never gets called. I will now do a build without any #ifdefs around the
chrp_setup.c stuff (And Christophe Hellwig proposed moving the stuff into
arch/ppc/platform/pegasos_mv643xx_eth.c), and see if that will solve it.
Also going to add the explicit detection of the marvell bridge in the OF tree,
but need to decide what to check for there.
Friendly,
Sven Luther
^ permalink raw reply
* Re: mv643xx_eth SA_SHIRQ support patch
From: Dale Farnsworth @ 2005-03-08 12:20 UTC (permalink / raw)
To: Benjamin Herrenschmidt; +Cc: Nicolas DET, linuxppc-dev list
In-Reply-To: <1110266832.13607.267.camel@gaston>
On Tue, Mar 08, 2005 at 06:27:12PM +1100, Benjamin Herrenschmidt wrote:
> > Notice that benh is telling me that you should use SA_SHIRQ always and that
> > SA_INTERRUPT should go away, and that you should contact him online if you
> > have trouble with that.
> >
> > > For the pegasos 2, you'll need the second patch which applies after
> > > the one I previously sent for chrp_setup.c.
> >
> > Ok, will test this anyway, and tell you how it works.
>
> GHeh, ok, just picked up the discussion. Yes, there is really no reason
> to use SA_INTERRUPT here, this is a thing of the past.
Excellent. Thanks.
Here's a new patch to try. :-)
-Dale
mv643xx: Always pass SA_SHIRQ to request_irq()
Signed-off-by: Dale Farnsworth <dale@farnsworth.org>
Index: linux-2.5-enet/drivers/net/mv643xx_eth.c
===================================================================
--- linux-2.5-enet.orig/drivers/net/mv643xx_eth.c
+++ linux-2.5-enet/drivers/net/mv643xx_eth.c
@@ -668,7 +668,7 @@
spin_lock_irq(&mp->lock);
err = request_irq(dev->irq, mv643xx_eth_int_handler,
- SA_INTERRUPT | SA_SAMPLE_RANDOM, dev->name, dev);
+ SA_SHIRQ | SA_SAMPLE_RANDOM, dev->name, dev);
if (err) {
printk(KERN_ERR "Can not assign IRQ number to MV643XX_eth%d\n",
^ permalink raw reply
* Re: MPC82xx and linux-2.6.
From: Adam Kent @ 2005-03-08 10:41 UTC (permalink / raw)
To: linuxppc-dev
In-Reply-To: <20050308030424.DA5D367A79@ozlabs.org>
leo wrote:
> Anyone who has experience in booting linux-2.6 on Motorola ADS8260 platform?
Yes. It boots and runs fine. I suggest you have a browse through the
linuxppc-embedded archives...
http://ozlabs.org/pipermail/linuxppc-embedded/
^ permalink raw reply
* Re: MPC82xx and linux-2.6.
From: Marc Leeman @ 2005-03-08 8:35 UTC (permalink / raw)
To: leo; +Cc: linuxppc-dev
In-Reply-To: <20050308030424.DA5D367A79@ozlabs.org>
[-- Attachment #1: Type: text/plain, Size: 387 bytes --]
> Anyone who has experience in booting linux-2.6 on Motorola ADS8260 platform?
MPC8245, don't know if this is close enough.
I had little problems porting a 2.4 to a 2.6 kernel.
--
greetz, marc
Repent? We have less than an arn. I was a Dominar. It'd take me longer
than that to repent.
Rygel - Suns and Lovers
scorpius 2.6.11 #1 Wed Mar 2 16:38:38 CET 2005 GNU/Linux
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply
* Re: mv643xx_eth SA_SHIRQ support patch
From: Benjamin Herrenschmidt @ 2005-03-08 7:27 UTC (permalink / raw)
To: Sven Luther; +Cc: linuxppc-dev list, Dale Farnsworth, Nicolas DET
In-Reply-To: <20050308064945.GC27722@pegasos>
> Notice that benh is telling me that you should use SA_SHIRQ always and that
> SA_INTERRUPT should go away, and that you should contact him online if you
> have trouble with that.
>
> > For the pegasos 2, you'll need the second patch which applies after
> > the one I previously sent for chrp_setup.c.
>
> Ok, will test this anyway, and tell you how it works.
GHeh, ok, just picked up the discussion. Yes, there is really no reason
to use SA_INTERRUPT here, this is a thing of the past.
Ben.
^ permalink raw reply
* Re: mv643xx_eth SA_SHIRQ support patch
From: Sven Luther @ 2005-03-08 6:49 UTC (permalink / raw)
To: Dale Farnsworth; +Cc: Nicolas DET, linuxppc-dev
In-Reply-To: <20050307225401.GA31041@xyzzy>
On Mon, Mar 07, 2005 at 03:54:01PM -0700, Dale Farnsworth wrote:
> On Mon, Mar 07, 2005 at 12:57:39PM +0000, Nicolas DET wrote:
> > Hello James,
> > > - why do you need to use SA_SHIRQ in the ethernet driver?
> >
> > Because the IRQ we use for ethernet is shared with others devices.
>
> I've included an untested patch below that adds support for passing
> IRQ flags via platform device.
Notice that benh is telling me that you should use SA_SHIRQ always and that
SA_INTERRUPT should go away, and that you should contact him online if you
have trouble with that.
> For the pegasos 2, you'll need the second patch which applies after
> the one I previously sent for chrp_setup.c.
Ok, will test this anyway, and tell you how it works.
> Sven + Nicolas, please let me know if this compiles/works for you.
Yep.
Friendly,
Sven Luther
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox