On Tue, 6 May 2008 07:51:55 +0200 Segher Boessenkool <[EMAIL PROTECTED]> wrote:
>
> > OLPC? check?
>
> No check. The kernel hardly uses the device tree at all, there.
oh, OK.
--
Cheers,
Stephen Rothwell[EMAIL PROTECTED]
http://www.canb.auug.org.au/~sfr/
pgpNcFqKyidUf.pgp
Hi ,boys . I am in the XiDian universtiy of china . I am doing the things ike
yours.You can try set ttyUL0,if you use the Uartlite. If it don't work , may
be gcc 4.1.0 miscompile the kernel 2.6 , I am using the gcc3.4.4.
Good luck
张轶 wrote:
>
> -- Forwarded message --
> From:
Original-Nachricht
> Datum: Tue, 06 May 2008 09:44:18 +1000
> Von: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
> An: Gerhard Pircher <[EMAIL PROTECTED]>
> CC: Kumar Gala <[EMAIL PROTECTED]>, [EMAIL PROTECTED], linuxppc-dev@ozlabs.org
> Betreff: Re: [PATCH] Sam440ep support
>
> O
On Mon, May 05, 2008 at 01:22:40PM -0400, Jon Smirl wrote:
> On 5/5/08, Grant Likely <[EMAIL PROTECTED]> wrote:
> > On Mon, May 5, 2008 at 11:01 AM, Jon Smirl <[EMAIL PROTECTED]> wrote:
> > > Did this get fixed somehow? I used to need this to boot a pcm030.
> >
> >
> > I'm sorry; I'm at a lost as
On Mon, May 05, 2008 at 10:55:38PM +0400, Anton Vorontsov wrote:
> Sometimes (particularly on MPC8610HPCD) we want IRQ-less CMOS RTC for
> the boards without (or disabled) i8259 PICs.
>
> We lookup the device tree for "chrp,iic" compatible devices, and if not
> found we do not assign RTC IRQ.
I s
Hi Geoff,
On Monday 05 May 2008 21:00:47 you wrote:
> Marvin wrote:
> > what about adding these defaults:
> > - CONFIG_SCHED_SMT
> > - CONFIG_HUGETLBFS (needed by ibm cell sdk)
I'm using these for years now ;-)
> > not sure about:
> > - CONFIG_SPU_FS_64K_LS
I also have this option
Original-Nachricht
> Datum: Mon, 5 May 2008 22:55:38 +0400
> Von: Anton Vorontsov <[EMAIL PROTECTED]>
> An: Kumar Gala <[EMAIL PROTECTED]>
> CC: linuxppc-dev@ozlabs.org
> Betreff: [PATCH 1/2] [POWERPC] rtc_cmos_setup: assign interrupts only if
> there is i8259 PIC
> Someti
On Tue, 2008-05-06 at 09:51 +0200, Gerhard Pircher wrote:
> Takashi Iwai posted a preliminary patch a long time ago. I tested it
> on my
> machine and it failed with non coherent scatter-gather DMA allocations
> (I guess almost all ALSA PCI drivers use SG DMA?).
How does Alsa allocate such SG ?
>
> > +- compatible : should be "fsl,MPIC-MSI" for 85xx/86xx cpu,
> > + and "fsl,IPIC-MSI" for 83xx cpu.
>
> Please use a more specific name, "fsl,8599-msi" or similar?
>
Thanks for your input. I think the name "fsl,MPIC-MSI" and
"fsl,IPIC-MSI"
is somethind specific. Actually, from th
Hi Micheal,
Thank you for your comments.
I'll send the new version according to feedback.
Jason
> -Original Message-
> From: Michael Ellerman [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 05, 2008 7:24 PM
> To: Jin Zhengxiong
> Cc: [EMAIL PROTECTED]; linuxppc-dev@ozlabs.org
> Subject: R
Original-Nachricht
> Datum: Tue, 06 May 2008 18:48:39 +1000
> Von: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
> An: Gerhard Pircher <[EMAIL PROTECTED]>
> CC: linuxppc-dev@ozlabs.org, Takashi Iwai <[EMAIL PROTECTED]>, [EMAIL
> PROTECTED], [EMAIL PROTECTED]
> Betreff: Re: [PATCH]
On Tue, 2008-05-06 at 11:16 +0200, Gerhard Pircher wrote:
> I can't answer this question. *ducked* :-) Takashi?
>
> FYI: I posted the results of the test with Takashi's dma_mmap_coherent
> patch here:
> http://ozlabs.org/pipermail/linuxppc-dev/2006-June/024078.html
>
> On the other side it looks
On Tue, 6 May 2008 16:11:10 +1000
Stephen Rothwell <[EMAIL PROTECTED]> wrote:
> Hi Bryan,
>
> On Tue, 6 May 2008 03:28:13 +0100 Bryan O'Donoghue <[EMAIL PROTECTED]>
> wrote:
> >
> > +static void __init asp834x_init_IRQ(void)
> > +{
> > + struct device_node *np;
> > +
> > + np = of_find_node_b
Hi
On Tue, 2008-05-06 at 10:14 +0200, Marvin wrote:
> p.s. I installed fc9 last week and Xorg crashes when PCI is not
> enabled. just
> in case someone has the same problem.
The Ubuntu PS3 team is also working on an a couple of bugs relating to
lack of PCI info. I don't know if these are the sam
On Tue, 2008-05-06 at 10:14 +0200, Marvin wrote:
> Hi Geoff,
>
> On Monday 05 May 2008 21:00:47 you wrote:
> > Marvin wrote:
> > > what about adding these defaults:
> > > - CONFIG_SCHED_SMT
> > > - CONFIG_HUGETLBFS (needed by ibm cell sdk)
>
> I'm using these for years now ;-)
>
> > > not su
Current standard practice is not to represent the DCR bus as node with
subnodes for the DCR-controlled devices. That's because the DCR bus
tends to run in addition to other on-chip busses, and some things have
to go on another on-chip bus to make sense, but still have DCR control
registers (for e
Hi Ben,
thanks for signaling this long-standing issue again.
At Tue, 06 May 2008 10:08:28 +1000,
Benjamin Herrenschmidt wrote:
>
> Hi Takashi !
>
> I'm bringing up an old thread as I'm just discovering that the problem
> still hasn't been fixed.
>
> There seem to be a few issues with ALSA curr
At Tue, 06 May 2008 20:12:27 +1000,
Benjamin Herrenschmidt wrote:
>
>
> On Tue, 2008-05-06 at 11:16 +0200, Gerhard Pircher wrote:
> > I can't answer this question. *ducked* :-) Takashi?
> >
> > FYI: I posted the results of the test with Takashi's dma_mmap_coherent
> > patch here:
> > http://ozla
On Tue, 2008-05-06 at 13:14 +0200, Takashi Iwai wrote:
> > sg allocations are usually lists of page, so virt_to_page shouldn't
> be a
> > problem in the first place, though we still need some way to get the
> > right prot attributes.
>
> The problem is that ALSA SG buffer is composed from pages a
> Hrm... the problem is that you aren't supposed to make up sglists with
> the result of dma_alloc_coherent... It might be a limitation of our core
> DMA API, but that's we have to deal with today..
>
> If you're going to make up sglists and call vmap, you should allocate
> pages with normal GFP.
+- compatible : should be "fsl,MPIC-MSI" for 85xx/86xx cpu,
+ and "fsl,IPIC-MSI" for 83xx cpu.
Please use a more specific name, "fsl,8599-msi" or similar?
Thanks for your input. I think the name "fsl,MPIC-MSI" and
"fsl,IPIC-MSI"
is somethind specific.
This is the third MSI-on-MPIC
At Tue, 06 May 2008 21:25:53 +1000,
Benjamin Herrenschmidt wrote:
>
>
> On Tue, 2008-05-06 at 13:14 +0200, Takashi Iwai wrote:
> > > sg allocations are usually lists of page, so virt_to_page shouldn't
> > be a
> > > problem in the first place, though we still need some way to get the
> > > right
On Tue, 2008-05-06 at 13:31 +0200, Takashi Iwai wrote:
> > I don't think we can easily update the DMA API at this stage. What
> we
> > could do is provide a way to retrieve the struct page array from the
> > result of dma_alloc_coherent...
>
> In most cases, it can be obtained via pfn_to_page(),
On 5/6/08, Sascha Hauer <[EMAIL PROTECTED]> wrote:
> On Mon, May 05, 2008 at 01:22:40PM -0400, Jon Smirl wrote:
> > On 5/5/08, Grant Likely <[EMAIL PROTECTED]> wrote:
> > > On Mon, May 5, 2008 at 11:01 AM, Jon Smirl <[EMAIL PROTECTED]> wrote:
> > > > Did this get fixed somehow? I used to need t
@@ -0,0 +1,247 @@
+/*
+ * Analogue & Micro ASP8347 Device Tree Source
+ *
+ * Copyright 2008 Codehermit
+ *
+ * This program is free software; you can redistribute it and/or
modify it
+ * under the terms of the GNU General Public License as
published by the
+ * Free Software Foundation;
Hi Jochen,
I just had a debug session with a MPC8260 + eeprom and got some
questions:
> This driver uses the port of 2.4 code from Vitaly Bordug
> <[EMAIL PROTECTED]> and the actual algorithm used by the i2c
> driver of the DBox code on cvs.tuxboc.org from Felix Domke
> ([EMAIL PROTECTED]) and G
On Tue, May 6, 2008 at 12:43 AM, Sylvain Munaut <[EMAIL PROTECTED]> wrote:
> Patch, obviously correct, sent to me personally instead of the list.
>
> Sylvain
>
> Here is a fix for the unterminated mpc52xx_uart_of_match array when
> CONFIG_PPC_MPC512x is not defined. Should be quite self explon
On Mon, 5 May 2008 08:53:19 +0200
Stefan Roese <[EMAIL PROTECTED]> wrote:
> The new 440x6 core used on AMCC 460EX/GT introduces new storage attibure
> fields to the TLB2 word. Those are:
>
> Bit 11 12 13 14 15
> WL1 IL1I IL1D IL2I IL2D
>
> With these bits the cache (L1 and L2) ca
Hi Wolfram,
>> +/* Begin transmission */
>> +setbits8(&i2c_reg->i2com, 0x80);
> Hardcoded value. (I also wonder if 0x81 might be more suitable, as it
> keeps the "be-a-master"-bit set. Still, both values work with my setup.)
>> +#ifdef I2C_CHIP_ERRATA
>> +/*
>> + * Chip errata, cl
Opps, there is a bug in this patch. The file pika.h is not included. I
have attached it below, but a simpler solution might be to just delete
it from this file. It is not required to build the kernel.
The file currently contains the exported dtm functions. These functions
are only used by the tele
On Mon, May 5, 2008 at 12:12 PM, Fabio Tosetto <[EMAIL PROTECTED]> wrote:
> Hello, I have an embedded system with an on-board processor powerpc MPC5200B
> and Linux kernel 2.6.22,
> I must turn over to MMC SPI on the PSC6.
>
> First, I
> have enabled PSC6:
>
> in ../arch/ppc/platforms/lite5200
Hi Dan,
On Tuesday 06 May 2008 11:44:12 Dan Munckton wrote:
> Hi
>
> On Tue, 2008-05-06 at 10:14 +0200, Marvin wrote:
> > p.s. I installed fc9 last week and Xorg crashes when PCI is not
> > enabled. just
> > in case someone has the same problem.
>
> The Ubuntu PS3 team is also working on an a cou
Anton Vorontsov wrote:
The firmware on MPC8610HPCD boards enables ULI ethernet and leaves it
in some funky state before booting Linux. For drivers, it's always good
idea to (re)initialize the hardware prior to requesting interrupts.
This patch fixes the following oops:
Oops: Kernel access of ba
Becky Bruce wrote:
This driver has been superseded by fs_enet and is no longer in use.
Signed-off-by: Becky Bruce <[EMAIL PROTECTED]>
I cannot make an informed judgement on this.
ACK, and pass through platform tree, if all platform peeps are happy.
__
I've prepared another path to add the support for the sam440ep;
shortly I've merged arch/powerpc/boot/sam440ep.c in
arch/powerpc/boot/cuboot-sam440ep.c; I've inserted the code to make
the rtc works directly in arch/powerpc/platforms/44x/sam440ep.c (so
there isn't any arch/powerpc/sysdev/sam440ep.c
On Tuesday 06 May 2008, Josh Boyer wrote:
> > The new 440x6 core used on AMCC 460EX/GT introduces new storage attibure
> > fields to the TLB2 word. Those are:
> >
> > Bit 11 12 13 14 15
> > WL1 IL1I IL1D IL2I IL2D
> >
> > With these bits the cache (L1 and L2) can be configured in a m
On Tue, May 06, 2008 at 05:19:39PM +0200, Jochen Friedrich wrote:
> setbits8() and clrbits8() use a bitmask as second argument.
Ouch! Guess my mind wanted to read in_8 and out_8 for some reason...
Sorry and thanks for clarifying!
Wolfram
--
Dipl.-Ing. Wolfram Sang | http://www.pengutronix.d
Yes, but this is a symptom of a separate problem, which is that it is
sometimes valuable to generate an optimized kernel configuration for a
particular FPGA system. First order, I'm more concerned about getting a
kernel which is generic and can work with (more or less) any device
tree.
Steve
>
I'll fix it.
> -Original Message-
> From: Benjamin Herrenschmidt [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 05, 2008 9:02 PM
> To: Stephen Rothwell
> Cc: Stephen Neuendorffer; [EMAIL PROTECTED];
[EMAIL PROTECTED]; linuxppc-
> [EMAIL PROTECTED]
> Subject: Re: [PATCH 1/4] [v4][POWERPC] r
On Tue, 6 May 2008 10:34:36 -0700
"Stephen Neuendorffer" <[EMAIL PROTECTED]> wrote:
>
> I'll fix it.
Great. Otherwise the patch looks pretty good in my review. I'll queue
it up for 2.6.27.
josh
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
h
> -Original Message-
> From: David Gibson [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 05, 2008 11:15 PM
> To: Grant Likely
> Cc: Stephen Neuendorffer; linuxppc-dev@ozlabs.org
> Subject: Re: [PATCH 4/4] [POWERPC] Xilinx: Framebuffer: Use
dcrinfrastructure.
>
> On Mon, May 05, 2008 at 10
Not really... In this case 'faster' means 'faster ICAP core' not 'faster
processor':
This is really something that is bounded by the number of cycles.
Steve
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Grant Likely
> Sent: Monday, May 05, 2008 1:01
Previously, dcr support was configured at compile time to either using
MMIO or native dcr instructions. Although this works for most
platforms, it fails on FPGA platforms:
1) Systems may include more than one dcr bus.
2) Systems may be native dcr capable and still use memory mapped dcr interface.
Hi Paul,
>> -#ifdef CONFIG_OF_I2C
>> +#if defined(CONFIG_OF_I2C) || defined(CONFIG_OF_I2C_MODULE)
>>
>> void of_register_i2c_devices(struct i2c_adapter *adap,
>> struct device_node *adap_node);
>
> Why do we have that ifdef there at all? There's only that one
> exter
Remove #ifdef CONFIG_OF_I2C as this breaks module compilation.
Drivers using this header should depend on OF_I2C anyways, so
there's no need to make this conditional
Signed-off-by: Jochen Friedrich <[EMAIL PROTECTED]>
---
include/linux/of_i2c.h |4
1 files changed, 0 insertions(+), 4 del
Hi all,
Down here few question regarding networking throughput, I would
appreciate any thoughts or ideas.
On the MPC8315E-RDB board (CPU at 400MHz, CSB at 133 MHz) I'm observing
relatively low TCP throughput using gianfar driver...
The maximum value I've seen with the current kernels is 142 Mb/s
On Tue, 6 May 2008 18:41:44 +0200
Stefan Roese <[EMAIL PROTECTED]> wrote:
> On Tuesday 06 May 2008, Josh Boyer wrote:
> > > The new 440x6 core used on AMCC 460EX/GT introduces new storage attibure
> > > fields to the TLB2 word. Those are:
> > >
> > > Bit 11 12 13 14 15
> > > WL1 IL1
Hi Paul,
Please pull from:
master.kernel.org:/pub/scm/linux/kernel/git/jwboyer/powerpc-4xx.git for-2.6.26
to pick up a small number of fixes for 4xx. One corrects the PCI
addresses for Sequoia boards, another fixes TLB issues with newer 440x6
cores. Stefan's pci-e endpoint driver is also incl
Every arch/ppc defconfig I built today failed. Someone broke it.
Those interested in fixing it might want to see why. I suspect the
ppc/powerpc: use kbuild.h instead of defining macros in asm-offsets.c
is responsible, but I have no evidence of that.
josh
/home/jwboyer/src/linux-2.6/arch/ppc/
Anton Vorontsov wrote:
Hi all,
Down here few question regarding networking throughput, I would
appreciate any thoughts or ideas.
On the MPC8315E-RDB board (CPU at 400MHz, CSB at 133 MHz) I'm observing
relatively low TCP throughput using gianfar driver...
What is the "target" of the test - is
I've tried to tune gianfar driver in various ways... and it gave
some positive results with this patch:
diff --git a/drivers/net/gianfar.h b/drivers/net/gianfar.h
index fd487be..b5943f9 100644
--- a/drivers/net/gianfar.h
+++ b/drivers/net/gianfar.h
@@ -123,8 +123,8 @@ extern const char gfar_drive
Hi,
I get a rather strange error here with kernel v2.6.26-rc1 and gcc version
4.1.2 20061115 (prerelease) (Debian 4.1.1-21) (cross compile version).
This is the output of the build process:
> $ make ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- zImage
> CHK include/linux/version.h
> CHK
Hello all,
I am working on porting linux 2.6.25 with a custom MPC8313 based board, but am
having a little bit of trouble with the ethernet, more specifically ifconfig.
after typing "ifconfig eth0 10.196.31.84" I receive the following error
ifconfig: SIOCSIFFLAGS: Cannot assign requested address
Ronald Madrid wrote:
Hello all,
I am working on porting linux 2.6.25 with a custom MPC8313 based board,
but am having a little bit of trouble with the ethernet, more
specifically ifconfig.
after typing "ifconfig eth0 10.196.31.84" I receive the following error
ifconfig: SIOCSIFFLAGS: Cannot
I'm guessing by device tree you mean the .dts file? I'm using a modified
version of the mpc8313erdb.dts with minor changes (to the local bus only).
Here is a copy of it./* * MPC8313E RDB Device Tree Source * * Copyright 2005,
2006, 2007 Freescale Semiconductor Inc. * * This program is free sof
Ronald Madrid wrote:
I'm guessing by device tree you mean the .dts file? I'm using a
modified version of the mpc8313erdb.dts with minor changes (to the local
bus only). Here is a copy of it.
OK, according to that device tree, eth0 is associated with PHY address
1. Is that correct on your b
Every arch/ppc defconfig I built today failed. Someone broke it.
On a related note, arch/ppc defconfig doesn't even configure anymore;
common_defconfig was removed, but it is still the default. What config
should we use as default now?
Josh, I'll look into the build failure now.
Segher
___
I don't know, where would I find that out?
Sorry, I'm still kind of new to this.
Ron
> Date: Tue, 6 May 2008 16:35:38 -0500
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> CC: linuxppc-dev@ozlabs.org
> Subject: Re: ifconfig MPC8313
>
> Ronald Madrid wrote:
> > I'm guessing by device tree yo
Ronald Madrid wrote:
I don't know, where would I find that out?
Sorry, I'm still kind of new to this.
In the documentation/schematics/designer's-head of your custom board.
-Scott
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.o
On Tue, 6 May 2008 23:39:34 +0200
Segher Boessenkool <[EMAIL PROTECTED]> wrote:
> > Every arch/ppc defconfig I built today failed. Someone broke it.
>
> On a related note, arch/ppc defconfig doesn't even configure anymore;
> common_defconfig was removed, but it is still the default. What config
I believe that it is zero. Is that valid?
Ron
> Date: Tue, 6 May 2008 16:43:57 -0500
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> CC: linuxppc-dev@ozlabs.org
> Subject: Re: ifconfig MPC8313
>
> Ronald Madrid wrote:
> > I don't know, where would I find that out?
> >
> > Sorry, I'm still
Ronald Madrid wrote:
I believe that it is zero. Is that valid?
FWIH, it's not recommended, as it's interpreted as a broadcast address
in some cases. However, if that's the way the board is, then go ahead
and put a zero in the phy node's reg property.
-Scott
___
On a related note, arch/ppc defconfig doesn't even configure anymore;
common_defconfig was removed, but it is still the default. What
config
should we use as default now?
I'd be willing to guess that the answer is "nothing".
Plain "defconfig" should use _something_. Something that still ex
Thank you, that seems to have worked. I can now ping and whatnot. One
question though. I used the linux v2.6.20 that came with the BSP for the
MPC8313ERDB and the ethernet worked. Was there a bug earlier that would have
allowed this default .dts to work with my phy address of '0'? I was rat
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 v
It needs it:
arch/ppc/kernel/ppc_ksyms.c:152: error: '__flush_icache_range'
undeclared here (not in a function)
and a few more like that.
Signed-off-by: Segher Boessenkool <[EMAIL PROTECTED]>
---
arch/ppc/kernel/ppc_ksyms.c |1 +
1 files changed, 1 insertions(+), 0 deletions
arch/ppc doesn't have prom_init.o (anymore).
Signed-off-by: Segher Boessenkool <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/Makefile |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/kernel/Makefile b/arch/powerpc/kernel/Makefile
index d14cebf..2346d27 1006
We used to use common_defconfig, but it was removed some time ago.
Signed-off-by: Segher Boessenkool <[EMAIL PROTECTED]>
---
arch/ppc/Makefile |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/ppc/Makefile b/arch/ppc/Makefile
index 8df7f0e..2352d13 100644
--- a/arch/p
These three trivial patches make arch/ppc build again.
Segher
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
On Tue, 6 May 2008 08:37:16 -0500
Kumar Gala <[EMAIL PROTECTED]> wrote:
/;
> > +
> > +/ {
> > + model = "ASP8347E";
> > + compatible = "ASP8347E";
>
> "analogue-and-micro, ASP8347E";
Fair enough.
> > + memory {
> > + device_type = "memory";
> > + reg = <0x 0x80
When doing lockdep, I had two patches to initialize paca->_current
early. One bogus, and one correct. Unfortunately both got merged
as the bad one ended up being part of the main lockdep patch by
mistake. This causes memory corruption at boot. This patch removes
the offending code.
Signed-off-by:
When debugging early boot problems, it's common to sprinkle printk's
all over the place. However, on powerpc 64 bits, this can lead to
memory corruption if done too early due to the PACA pointer and
lockdep core not being initialized.
This adds some comments to early_setup() that document when it
This moves lockdep_init() to before udbg_early_init() as the later
can call things that acquire spinlocks etc... This also makes printk
safer to use earlier.
Signed-off-by: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
---
arch/powerpc/kernel/setup_64.c |6 +++---
1 file changed, 3 insertions(+
hi all,
I m using imx21ads board, Bootloader is Redboot.
linux is linux-2.6.22 version. Board with Jffs2 root filesystem as root is
not working.
But Ramdisk booting is working...so i tried to mount jffs2 root file system
after
booting board with ramdisk using mount command. It boots up with s
In message <[EMAIL PROTECTED]> you wrote:
>
> I m using imx21ads board, Bootloader is Redboot.
> linux is linux-2.6.22 version. Board with Jffs2 root filesystem as root is
> not working.
Argh.. You really are ignoring all good advice, aren't you?
After you have been told that this posting wa s
75 matches
Mail list logo
