Perl

2006-11-20 Thread Wolfgang Denk
In message 406A31B117F2734987636D6CCC93EE3C0438F0 at 
ehost011-3.exch011.intermedia.net you wrote:

 I've done this successfully with ELDK 4.0 and 3.1.1 on PPC440EP Yosemite
 board. Resulting perl binary is working with ELDK ppc_4xx filesystem
 (linux 2.6.13 has been used).
 
 However it doesn't run on original Yosemite filesystem (I've copied all
 perl files there) - it doesn't find certain glibc symbols. With ELDK 4.0

What is your original filesystem? Any standard distro, or what?

 tmp # /opt/bin/perl warnings.pl
 /opt/bin/perl: relocation error: /opt/bin/perl: symbol __floatsidf,
 version GLIBC_2.3.2 not defined in file libc.so.6 wie

Looks as if you used the ppc_4xx packages for  this,  which  are  for
FPU-less  4xx  processors.  On  the  yosemite,  you  should  use  the
ppc_4xxFP tools instead.

 Did I something wrong?

Yes. You mixed soft-fload and hard-float binaries and libraries.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
A princess should not be afraid -- not with a brave knight to protect
her.
-- McCoy, Shore Leave, stardate 3025.3



[PATCH] serial: Use real irq on UART0 (IRQ = 0) on PPC4xx systems

2006-11-20 Thread Stefan Roese
This patch fixes a problem seen on multiple 4xx platforms, where
the UART0 interrupt number is 0. The macro is_real_interrupt lead
on those systems to not use an real interrupt but the timer based
implementation.

This problem was detected and fixed by
Charles Gales cgales at amcc.com and John Baxter jbaxter at amcc.com
from AMCC.

Signed-off-by: Stefan Roese sr at denx.de

---
commit f83094acd3258575c9a5cdb1d65e241c16eff03a
tree 72582c5eeb2a9c8ea57287616d51e42fff8ed641
parent f56f68c4e1977f0e884a304af4c617bed4909417
author Stefan Roese sr at denx.de Sat, 18 Nov 2006 10:28:50 +0100
committer Stefan Roese sr at denx.de Sat, 18 Nov 2006 10:28:50 +0100

 drivers/serial/8250.c |   22 ++
 1 files changed, 14 insertions(+), 8 deletions(-)

diff --git a/drivers/serial/8250.c b/drivers/serial/8250.c
index e34bd03..a51679e 100644
--- a/drivers/serial/8250.c
+++ b/drivers/serial/8250.c
@@ -76,8 +76,14 @@ static unsigned int nr_uarts = CONFIG_SE
  * We default to IRQ0 for the no irq hack.   Some
  * machine types want others as well - they're free
  * to redefine this in their header file.
+ * NOTE:  Some PPC4xx use IRQ0 for a UART Interrupt, so
+ * we will assume that the IRQ is always real
  */
+#ifdef CONFIG_4xx
+#define is_real_interrupt(irq) (1)
+#else
 #define is_real_interrupt(irq) ((irq) != 0)
+#endif

 #ifdef CONFIG_SERIAL_8250_DETECT_IRQ
 #define CONFIG_SERIAL_DETECT_IRQ 1




[PATCH] serial: Use real irq on UART0 (IRQ = 0) on PPC4xx systems

2006-11-20 Thread Peter Korsgaard
 Stefan == Stefan Roese ml at stefan-roese.de writes:

Hi,

Stefan This patch fixes a problem seen on multiple 4xx platforms,
Stefan where the UART0 interrupt number is 0. The macro
Stefan is_real_interrupt lead on those systems to not use an real
Stefan interrupt but the timer based implementation.

That's not the proper way to fix this. Instead remap the interrupt
number to make 0 invalid.

I sent a similar patch some months ago and that was the reply I got:

http://marc.theaimsgroup.com/?t=11436352153r=1w=2

-- 
Bye, Peter Korsgaard



[PATCH] serial: Use real irq on UART0 (IRQ = 0) on PPC4xx systems

2006-11-20 Thread Alan
On Mon, 20 Nov 2006 12:00:36 +0100
Stefan Roese ml at stefan-roese.de wrote:

 This patch fixes a problem seen on multiple 4xx platforms, where
 the UART0 interrupt number is 0. The macro is_real_interrupt lead
 on those systems to not use an real interrupt but the timer based
 implementation.

NAK.

Zero means no interrupt in the Linux space. If you have a physical IRQ
0 remap it to a convenient number (eg map IRQ's + 1, or stick it on the
end). The logical and physical IRQ numbering in Linux don't have to match
up - and given some platforms have IRQ numbering per bus and the like
clearly doesn't in many cases.



[PATCH] serial: Use real irq on UART0 (IRQ = 0) on PPC4xx systems

2006-11-20 Thread Russell King
On Mon, Nov 20, 2006 at 12:10:15PM +, Alan wrote:
 On Mon, 20 Nov 2006 12:54:32 +0100 (MET)
 Stefan Roese ml at stefan-roese.de wrote:
  Let's see, if I got this right. You mean that on such a platform, where 0 
  is a 
  valid physical IRQ, we should assign another value as virtual IRQ number 
  (not 
  0 and not -1 of course). And then the platform pic implementation should 
  take care of the remapping of these virtual IRQ numbers to the physical 
  numbers.
  
  Correct?
 
 Absolutely correct in all the detail.

Since IRQ0 is not valid, can we arrange for the generic interrupt
infrastructure to always fail it's allocation, and then remove the
utterly unused bloatful irq_desc[0] ?

Didn't think so since x86 folk would scream.  Wait a moment, x86 can
map IRQ0 to some other number for the timer interrupt, just like
other architectures are being forced to map their UART interrupts.

-- 
Russell King
 Linux kernel2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core



[PATCH] serial: Use real irq on UART0 (IRQ = 0) on PPC4xx systems

2006-11-20 Thread Sergei Shtylyov
Hello.

Stefan Roese wrote:
 This patch fixes a problem seen on multiple 4xx platforms, where
 the UART0 interrupt number is 0. The macro is_real_interrupt lead
 on those systems to not use an real interrupt but the timer based
 implementation.

 This problem was detected and fixed by
 Charles Gales cgales at amcc.com and John Baxter jbaxter at amcc.com
 from AMCC.

 Signed-off-by: Stefan Roese sr at denx.de

 ---
 commit f83094acd3258575c9a5cdb1d65e241c16eff03a
 tree 72582c5eeb2a9c8ea57287616d51e42fff8ed641
 parent f56f68c4e1977f0e884a304af4c617bed4909417
 author Stefan Roese sr at denx.de Sat, 18 Nov 2006 10:28:50 +0100
 committer Stefan Roese sr at denx.de Sat, 18 Nov 2006 10:28:50 +0100

  drivers/serial/8250.c |   22 ++
  1 files changed, 14 insertions(+), 8 deletions(-)

 diff --git a/drivers/serial/8250.c b/drivers/serial/8250.c
 index e34bd03..a51679e 100644
 --- a/drivers/serial/8250.c
 +++ b/drivers/serial/8250.c
 @@ -76,8 +76,14 @@ static unsigned int nr_uarts = CONFIG_SE
   * We default to IRQ0 for the no irq hack.   Some
   * machine types want others as well - they're free
   * to redefine this in their header file.
 + * NOTE:  Some PPC4xx use IRQ0 for a UART Interrupt, so
 + * we will assume that the IRQ is always real
   */
 +#ifdef CONFIG_4xx
 +#define is_real_interrupt(irq)   (1)
 +#else
  #define is_real_interrupt(irq)   ((irq) != 0)
 +#endif

This should have been done in asm/serial.h instead, like this:

#undef is_real_interrupt(irq)
#define is_real_interrupt(irq)  1

Not too smart as well,but at least this wasy you won't be pulluting the 
generic code...

WBR, Sergei



NFS Server Settings

2006-11-20 Thread Goel, Mudit (Mudit)
All,
   Are there differnet settings for NFS Server if used with Kernel 2.4 and
Kernel 2.6 ?   
   If so could someone point out the configuraiton to be used with 2.6 ?

Mudit Goel
Lucent Technologies 




Perl

2006-11-20 Thread Leonid
On Monday, November 20, 2006 12:35 AM Wolfgang Denk wrote:
 In message 406A31B117F2734987636D6CCC93EE3C0438F0 at ehost011-
 3.exch011.intermedia.net you wrote:

  I've done this successfully with ELDK 4.0 and 3.1.1 on PPC440EP
Yosemite
  board. Resulting perl binary is working with ELDK ppc_4xx filesystem
  (linux 2.6.13 has been used).
  
  However it doesn't run on original Yosemite filesystem (I've copied
all
  perl files there) - it doesn't find certain glibc symbols. With ELDK
4.0

 What is your original filesystem? Any standard distro, or what?
[Leonid] The one, supplied by AMCC with Yosemite board - came from DENX
originally I believe though I'm not sure.

  tmp # /opt/bin/perl warnings.pl
  /opt/bin/perl: relocation error: /opt/bin/perl: symbol __floatsidf,
  version GLIBC_2.3.2 not defined in file libc.so.6 wie

 Looks as if you used the ppc_4xx packages for  this,  which  are  for
 FPU-less  4xx  processors.  On  the  yosemite,  you  should  use  the
 ppc_4xxFP tools instead.
[Leonid] That must be it! I'll recompile, using ppc_4xxFP target.

Thanks a lot,

Leonid.



Perl

2006-11-20 Thread Leonid
On Monday, November 20, 2006 12:35 AM Wolfgang Denk wrote:
 In message 406A31B117F2734987636D6CCC93EE3C0438F0 at ehost011-
 3.exch011.intermedia.net you wrote:

  I've done this successfully with ELDK 4.0 and 3.1.1 on PPC440EP
Yosemite
  board. Resulting perl binary is working with ELDK ppc_4xx filesystem
  (linux 2.6.13 has been used).
  
  However it doesn't run on original Yosemite filesystem (I've copied
all
  perl files there) - it doesn't find certain glibc symbols. With ELDK
4.0

  tmp # /opt/bin/perl warnings.pl
  /opt/bin/perl: relocation error: /opt/bin/perl: symbol __floatsidf,
  version GLIBC_2.3.2 not defined in file libc.so.6 wie

 Looks as if you used the ppc_4xx packages for  this,  which  are  for
 FPU-less  4xx  processors.  On  the  yosemite,  you  should  use  the
 ppc_4xxFP tools instead.
[Leonid] Wee, this really was it, now it works!

Thanks a lot again,

Leonid.



[PATCH] powerpc: Add of_platform support for ROM devices

2006-11-20 Thread Hollis Blanchard
On Mon, 2006-11-20 at 16:32 +0300, Vitaly Wool wrote:
 +
 +Required properties:
 +
 + - device_type : has to be rom
 + - compatible : Should specify what this ROM device is compatible with
 +   (i.e. onenand). Currently, this is most likely to be direct-mapped
 +   (which corresponds to the MTD physmap mapping driver).
 + - regs : Offset and length of the register set (or memory mapping) for
 +   the device.
 +
 +Recommended properties :
 +
 + - bank-width : Width of the flash data bus in bytes. Required
 +   for the NOR flashes (compatible == direct-mapped and others) ONLY.

Maybe you should put this in the Required section then, with a note that
it's only Recommended for non-NOR flashes. I can easily imagine somebody
ignoring every Recommendation section and missing this requirement.

 + - partitions : Several pairs of 32-bit values where the first value is
 +   partition's offset from the start of the device and the second one is
 +   partition size in bytes with LSB used to signify a read only
 +   partititon (so, the parition size should always be an even number).

^^^ partition misspelled, twice. :)

-Hollis




[PATCH] serial: Use real irq on UART0 (IRQ = 0) on PPC4xx systems

2006-11-20 Thread Guennadi Liakhovetski
On Mon, 20 Nov 2006, Russell King wrote:

  On Mon, 20 Nov 2006 12:54:32 +0100 (MET)
  Stefan Roese ml at stefan-roese.de wrote:
   Let's see, if I got this right. You mean that on such a platform, where 0 
   is a 
   valid physical IRQ, we should assign another value as virtual IRQ number 
   (not 
   0 and not -1 of course). And then the platform pic implementation 
   should 
   take care of the remapping of these virtual IRQ numbers to the physical 
   numbers.
 
 Since IRQ0 is not valid, can we arrange for the generic interrupt
 infrastructure to always fail it's allocation, and then remove the
 utterly unused bloatful irq_desc[0] ?
 
 Didn't think so since x86 folk would scream.  Wait a moment, x86 can
 map IRQ0 to some other number for the timer interrupt, just like
 other architectures are being forced to map their UART interrupts.

I think, what Russell means, is this:

#define is_real_interrupt(irq) ((irq) != NO_IRQ)

where the NO_IRQ macro has been introduced a LONG time ago specifically 
for this purpose, and is conveniently defined on some platforms to 
(unsigned int)-1 or similar, including asm-powerpc/irq.h. And yes, this 
has been discussed MANY times.

Thanks
Guennadi
---
Guennadi Liakhovetski



passwd : error

2006-11-20 Thread Wolfgang Denk
In message 730037.99224.qm at web33015.mail.mud.yahoo.com you wrote:

 I use TQM8xxl board with kernel 2.6.11.7 and Ramdisk of ELDK4.0

You are aware that we don't support TQM8xxL systems in the context of
the 2.6 kernel tree yet, aren't you?

 and in /home/ I see 
 drwxr-sr-x2 -2   -2   1024 Nov 20  2006 van
 in /etc/  i see three file passwd 
 -rwxrwxrwx  1 root   root291 Nov 20 20:20 passwd
 -rw---  1 -2 -2  291 Nov 20 20:20 passwd-
 -rwxrwxrwx  1 -2 -20 Nov 20 20:20 passwd+
 
 in nfs dir correlative with /home/ i see
 drwxr-sr-x  2 4294967294 4294967294 1024 Nov 20 20:20 van
 and /etc/
 -rwxrwxrwx  1 root   root291 Nov 20 20:20 passwd
 -rw---  1 4294967294 4294967294  291 Nov 20 20:20 passwd-
 -rwxrwxrwx  1 4294967294 42949672940 Nov 20 20:20 passwd+

Looks as if you missed to add the no_root_squash option to  your  NFS
server's /etc/exports file...

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Knowledge, sir, should be free to all!
-- Harry Mudd, I, Mudd, stardate 4513.3



FYI: SM5xx toolchain project berliOS registration

2006-11-20 Thread Wolfgang Denk
In message 4561F9F2.8020706 at 126.com you wrote:

 is Here a  successful  story  about using SM501 on PPC platform with
 this driver?  and would you please give me some advices to drive this
 devices?

Not in the context of the 2.6 kernel. But we have a working
configuration of MPC5200 + SM501 in our 2.4 kernel tree; see the
TQM5200 board config at
http://www.denx.de/cgi-bin/gitweb.cgi?p=linuxppc_2_4_devel.git

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
If a group of N persons implements a COBOL compiler,  there  will  be
N-1 passes. Someone in the group has to be the manager. - T. Cheatham



Wolfgang Denk

2006-11-20 Thread Adrian
This a general notice to all users.

*** WARNING ***

Wolfgang Denk has done a lot of hard work to make porting Linux to as many 
hardware platforms as you can imagine.

If some of his stuff does not work in precisely the way that you ordered, 
and paid *nothing* for, please dont slag Wolfgang off, or even imply that 
he's done something really badly.

He might stop offering us these tools, for FREE.

Then what would we do ?

START FROM SCRATCH (again).

So :-

1) if you can't read, do not post a question.
2) if you can't be bothered reading, go away completely.
3) if you have a problem (after reading) then ask.
4) if it still does not work, try reading again. You might have missed 
something.
5) This stuff is hard.There aren't many that can cross-port linux to a new 
platform, and fewer still that understand what to do if the ELDK was not 
there.

Please stop implying that Wolfgang has done something dreadfully wrong. It's 
more likely to be you. Read more.

For me, it took about a month to get what I wanted, based on the EDLK 
downloaded from Wolfgang's site, but now i have what i want.

Without the ELDK i would still be no-where near.

Thanks to Wolfgang.

Adrian Atkins.
IT Live Ltd. 




Memec v4fx12lc - problem booting linux on ppc

2006-11-20 Thread Olivier Goudard
Hi,

we have a v4fx12lc fpga board from memec which we are trying to get
Linux to boot on the ppc processor. We have generated a linux kernel for
nfs using the MontaVista support package. We generate a bitfile with the
following hardware peripherals in it :

RS232
Ethernet_MAC
Led_4bit
Push_buttons_3bits
DIP_switches_8bit
OPB_INTC_0

When we download the linux image with xmd we see nothing on the screen.
When we type run nothing appears on the screen and Linux does not
boot.

Has anyone had a similar problem ? We are stuck! Any ideas would be
appreciated.

We can boot a linux ramdisk kernel provided by Memec on the same board
using their bitfile. So the board seems to be working in general.

Thansk for any pointers and excuse us if we are posting to the wrong
list (this is the only list we could find which seemed useful) ! 

Olivier Goudard




Wolfgang Denk

2006-11-20 Thread Steve Iribarne (GMail)
I second this.  He has saved me countless hours!!!



On 11/20/06, Adrian adrian at it-live.co.uk wrote:
 This a general notice to all users.

 *** WARNING ***

 Wolfgang Denk has done a lot of hard work to make porting Linux to as many
 hardware platforms as you can imagine.

 If some of his stuff does not work in precisely the way that you ordered,
 and paid *nothing* for, please dont slag Wolfgang off, or even imply that
 he's done something really badly.

 He might stop offering us these tools, for FREE.

 Then what would we do ?

 START FROM SCRATCH (again).

 So :-

 1) if you can't read, do not post a question.
 2) if you can't be bothered reading, go away completely.
 3) if you have a problem (after reading) then ask.
 4) if it still does not work, try reading again. You might have missed
 something.
 5) This stuff is hard.There aren't many that can cross-port linux to a new
 platform, and fewer still that understand what to do if the ELDK was not
 there.

 Please stop implying that Wolfgang has done something dreadfully wrong. It's
 more likely to be you. Read more.

 For me, it took about a month to get what I wanted, based on the EDLK
 downloaded from Wolfgang's site, but now i have what i want.

 Without the ELDK i would still be no-where near.

 Thanks to Wolfgang.

 Adrian Atkins.
 IT Live Ltd.

 ___
 Linuxppc-embedded mailing list
 Linuxppc-embedded at ozlabs.org
 https://ozlabs.org/mailman/listinfo/linuxppc-embedded



-- 
/*
 * Steve Iribarne
 * Software Engineer
 * (aka Grunt)
 */