ioremap() fails for 64 MB

2006-08-24 Thread alva
I think 64MB limitation of ioremap() is due to the kernel's page size. When compiling kernel, it has an option to choose the memory page size which is default 64MB. To use memory greater than 64MB, there is two methods. One is to make the kernel's page size larger as Phil Nitschke said. Another is

I2C driver for SAA7121 on MPC855 and linux-2.4.25

2006-08-24 Thread Xu, Li (GE, Research)
Hi, I am trying to setup i2c driver for saa7121 on my mpc855 based board normally the address for saa7121 is 0x88, but when I enable i2c bus scan, the driver detect it's address is 0x34, so I just stick to 0x34. Anyway, I can write to saa7121via i2c bus successfully, but I can't enable color

atomic operations in user space

2006-08-24 Thread Li Yang-r58472
Why do you need atomic operations in user land? IPC will be sufficient to deal with race conditions between processes. Best Regards, Leo -Original Message- From: linuxppc-embedded-bounces+leoli=freescale.com at ozlabs.org [mailto:linuxppc-embedded-bounces+leoli=freescale.com at

I2C driver for SAA7121 on MPC855 and linux-2.4.25

2006-08-24 Thread Li Yang-r58472
-Original Message- From: linuxppc-embedded-bounces+leoli=freescale.com at ozlabs.org [mailto:linuxppc-embedded-bounces+leoli=freescale.com at ozlabs.org] On Behalf Of Xu, Li (GE, Research) Sent: Thursday, August 24, 2006 4:02 PM To: linuxppc-embedded at ozlabs.org Subject: I2C

ARCH=ppc or ARCH=powerpc

2006-08-24 Thread Benjamin Delagoutte
Hello, I'm new to Linux PowerPC platform, and I'm wondering what ARCH we should use to build the kernel. There seems to be 'ppc' and 'powerpc'. What's the difference between the two ? Thank you ! Benjamin

ARCH=ppc or ARCH=powerpc

2006-08-24 Thread Parav Pandit
- Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail. -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060824/8ce76255/attachment.htm

ARCH=ppc or ARCH=powerpc

2006-08-24 Thread Josh Boyer
On Thu, 2006-08-24 at 05:38 -0700, Parav Pandit wrote: ppc = 32bit. powerpc= 64bit. Correct me if I am wrong. Yes, you're wrong. Some 32 bit boards are also under arch/powerpc now. I am not sure why community didn't adopt the name ppc and ppc64 just like ia-32 and ia64. They did

MPC8555 PCI interrupts are not coming

2006-08-24 Thread Parav Pandit
, Parav Pandit - Do you Yahoo!? Get on board. You're invited to try the new Yahoo! Mail. -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060824/068788be

ARCH=ppc or ARCH=powerpc

2006-08-24 Thread Benjamin Delagoutte
Le jeudi 24 ao?t 2006 ? 07:49 -0500, Josh Boyer a ?crit : On Thu, 2006-08-24 at 05:38 -0700, Parav Pandit wrote: ppc = 32bit. powerpc= 64bit. Correct me if I am wrong. Yes, you're wrong. Some 32 bit boards are also under arch/powerpc now. I am not sure why community didn't adopt

ARCH=ppc or ARCH=powerpc

2006-08-24 Thread Parav Pandit
... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060824/54a92665/attachment.htm

ARCH=ppc or ARCH=powerpc

2006-08-24 Thread Josh Boyer
On Thu, 2006-08-24 at 14:58 +0200, Benjamin Delagoutte wrote: I'm currently working on a PPC 405 based developement card. Does it mean I have to work using the arch/ppc tree ? For now, yes. Set ARCH=ppc when you compile the kernel. What about the includes ? Do I have to use only

ARCH=ppc or ARCH=powerpc

2006-08-24 Thread Matt Porter
On Thu, Aug 24, 2006 at 02:58:15PM +0200, Benjamin Delagoutte wrote: Le jeudi 24 ao?t 2006 ? 07:49 -0500, Josh Boyer a ?crit : On Thu, 2006-08-24 at 05:38 -0700, Parav Pandit wrote: ppc = 32bit. powerpc= 64bit. Correct me if I am wrong. Yes, you're wrong. Some 32 bit boards are

ARCH=ppc or ARCH=powerpc

2006-08-24 Thread Matt Porter
On Thu, Aug 24, 2006 at 08:07:20AM -0500, Josh Boyer wrote: On Thu, 2006-08-24 at 14:58 +0200, Benjamin Delagoutte wrote: What about the includes ? Do I have to use only include/asm-ppc or are include/asm-powerpc necessary as well ? I believe there are some hacks in the makefiles to pull

ioremap() fails for 64 MB

2006-08-24 Thread Matt Porter
On Thu, Aug 24, 2006 at 10:54:23AM +0800, alva wrote: I think 64MB limitation of ioremap() is due to the kernel's page size. When compiling kernel, it has an option to choose the memory page size which is default 64MB. To use memory greater than 64MB, there is two methods. One is to make the

ioremap() fails for 64 MB

2006-08-24 Thread Matt Porter
On Wed, Aug 23, 2006 at 07:30:37PM +0930, Phil Nitschke wrote: On Tue, 2006-08-22 at 09:22 -0500, Matt Porter wrote: On Tue, Aug 22, 2006 at 05:11:09PM +0930, Phil Nitschke wrote: Hi all, I have 2 GB memory on a 7448 processor, and want to reserve a huge chunk of it at boot-time,

MontaVista 2.6 Kernel support for Xilinx ML40x

2006-08-24 Thread Frank D Lombardo
I noticed that MontaVista now has their Pro 4.0 version (2.6 Kernel) available for the Xilinx ML40x series of boards. I would assume that means driver support for at least most of the hardware on the boards. Is this code that should be freely available? How would one get a copy of these

atomic operations in user space

2006-08-24 Thread Brent Cook
-embedded at ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060824/4f60ee9d/attachment.htm

CompactFlash on PQII Pro

2006-08-24 Thread Ben Warren
Thanks Kumar, As always, you're several steps ahead of me. On Wed, 2006-08-23 at 18:04 -0500, Kumar Gala wrote: I know I posted a patch for cf-ide.c to lkml some time ago, this was to do a CF in true ide mode using the 83xx localbus.

MontaVista 2.6 Kernel support for Xilinx ML40x

2006-08-24 Thread Claus Gindhart
Frank, due to my understanding of the GPL (and i have already invested some time in understanding the various flavours of open source licences), you should contact Montavista, and ask them for the sources. This board adaption is derivative work of the GPL Kernel, so the result of this work also

MontaVista 2.6 Kernel support for Xilinx ML40x

2006-08-24 Thread Michael Galassi
I too had high hopes when I heard an LSP for the ML40x was imminent, I nabbed it and was disappointed to find that their drivers still only support relatively old versions of the Xilinx IP. It would seem that they are still creating the design they ported to with EDK/ISE v7.2 rather than the

MontaVista 2.6 Kernel support for Xilinx ML40x

2006-08-24 Thread Wade Maxfield
Linuxppc-embedded at ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060824/053fa0d2/attachment.htm

MontaVista 2.6 Kernel support for Xilinx ML40x

2006-08-24 Thread Rick Moleres
Note that Xilinx plans to update the MV drivers to support the latest IP in EDK 8.2.2 (due out around October), and these drivers would be part of the BSP generation process of Platform Studio. Sorry, the timing of the MV ML40x work and our EDK 8.1.x release was such that MV had no choice but to

MontaVista 2.6 Kernel support for Xilinx ML40x

2006-08-24 Thread Peter Ryser
/linuxppc-embedded -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060824/05ebc36d/attachment.htm

Platform device style question

2006-08-24 Thread Ben Warren
Hello, A 'newbie-to-platform-devices' question: In a patch that Kumar just sent for a compact flash device, the resource data (I/O addresses, IRQ # etc.) are retrieved from the platform system. I guess I can either modify the device tree in U-boot by adding additional nodes, or instantiate a

MontaVista 2.6 Kernel support for Xilinx ML40x

2006-08-24 Thread Wade Maxfield
/linuxppc-embedded -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060824/d020126a/attachment.htm

Platform device style question

2006-08-24 Thread Vitaly Bordug
On Thu, 24 Aug 2006 13:53:17 -0400 Ben Warren bwarren at qstreams.com wrote: Hello, A 'newbie-to-platform-devices' question: In a patch that Kumar just sent for a compact flash device, the resource data (I/O addresses, IRQ # etc.) are retrieved from the platform system. I guess I can

CompactFlash on PQII Pro

2006-08-24 Thread Kumar Gala
On Aug 24, 2006, at 9:44 AM, Ben Warren wrote: Thanks Kumar, As always, you're several steps ahead of me. On Wed, 2006-08-23 at 18:04 -0500, Kumar Gala wrote: I know I posted a patch for cf-ide.c to lkml some time ago, this was to do a CF in true ide mode using the 83xx localbus.

CompactFlash on PQII Pro

2006-08-24 Thread Ben Warren
Kumar, On Thu, 2006-08-24 at 13:25 -0500, Kumar Gala wrote: The only code in u-boot was the UPM setup code, I'm happy to send that to you. If it's no trouble, that would be great. My HW guy is calculating the settings, but this stuff can be frustrating to debug. BTW - was the system bus

Platform device style question

2006-08-24 Thread Ben Warren
Thanks Vitaly, On Thu, 2006-08-24 at 22:06 +0400, Vitaly Bordug wrote: I'd suggest to make a look at LDD concerning linux device model... Thanks. I'll read it again. My little brain absorbs this stuff very slowly. For platform device, there's no need to cope with u-boot at all. You'll

MontaVista 2.6 Kernel support for Xilinx ML40x

2006-08-24 Thread Frank D Lombardo
The ml403 reference design has several evaluation cores: opb_uart16550, opb_iic and opb_ethernet. They seem to time-out after about eight hours. Frank Wade Maxfield wrote: Good question. How long before lockup? The only core that should be licensed is the ethernet, and I know it was

MontaVista 2.6 Kernel support for Xilinx ML40x

2006-08-24 Thread T Ziomek
[top-posting fixed :-) ] On Thu, 24 Aug 2006, Wade Maxfield wrote: On 8/24/06, Peter Ryser peter.ryser at xilinx.com wrote: Wade, are you sure that you did not build your hardware with evaluation cores of the licenses? If you are using the evaluation licenses the hardware (FPGA

communication with i2c client

2006-08-24 Thread Ladislav Klenovič
Hi, I've create an i2c client and my questions is how to access it from userspace. This client is sitttng on adapter that I was able to access via /dev interface. After the client were successfuly loaded and detected, ioctl(fd,I2C_SLAVE,...) and read/write functions didn't work and error

MontaVista 2.6 Kernel support for Xilinx ML40x

2006-08-24 Thread Wade Maxfield
/linuxppc-embedded/attachments/20060824/98b158bc/attachment.htm

ip= command line strangeness...

2006-08-24 Thread T Ziomek
On my previous project, a 2.4 kernel on PPC, I frequently used ip=w.x.y.z on the kernel command line to specify a static IP address for my target board (when booting with a flash- or RAM-based root filesystem). Similarly, when using an NFS-mounted root fs, I would use ip=w.x.y.z:a.b.c.d,

communication with i2c client

2006-08-24 Thread Ladislav Klenovič
Hi, I've create an i2c client and my questions is how to access it from userspace. This client is sitttng on adapter that I was able to access via /dev interface. After the client were successfuly loaded and detected, ioctl(fd,I2C_SLAVE,...) and read/write functions didn't work and error

Help with booting with very large initrd

2006-08-24 Thread Howard, Marc
Hi, I'm developing a PPC440GX based board that uses U-Boot to boot a multi-file boot image composed of the kernel and a very large ( 96MB uncompressed) initrd file. The board has 512MB of RAM of which the upper 16MB is reserved for dedicated hardware. The 16MB block is reserved via mem=496M and

communication with i2c client

2006-08-24 Thread Frank
--- Ladislav Klenovi? lk99336 at pobox.sk wrote: Hi, I've create an i2c client and my questions is how to access it from userspace. This client is sitttng on adapter that I was able to access via /dev interface. After the client were successfuly loaded and detected,