pcmcia terminology

Hi, I have another PCMCIA/CF question to ask of this list. I have a PPC405gp-based device (similar to the Walnut) that has a CF slot on the front that we'd like to get working. I did some looking around in the archives and came across this: http://lists.linuxppc.org/linuxppc-embedded/200

Basic Config file

In message <3EA84246.9050101 at catapult.com> you wrote: > > Read the ELDK manual, however, did not see anything > on the kernel configuration and building it. Went to > kernelnewbies for that...anywhere else I can go for > kernel configuration. There is also http://www.denx.de/re/DPLG.html (b

Basic Config file

Read the ELDK manual, however, did not see anything on the kernel configuration and building it. Went to kernelnewbies for that...anywhere else I can go for kernel configuration. Unresolveds are: va_to_pte and get_IMMR in traps.c the get_IMMR seems to be 8xx specific. va_to_pte is in several hea

boot/simple in ROM?

On Thu, Apr 24, 2003 at 11:06:32AM -0700, Kerl, John wrote: > I based mine off boot/simple. It runs fine from ROM. > > Suppose for example I have 32MB SDRAM from 0x > to 0x01ff, and 16MB flash from 0xff00 to 0x. > The key is that arch/ppc/boot/ld.script, and ...suddenly I

bdigdb flash

Hi, is there someone who has a config file (for bdigdb) for a AMD flash (AM29DL323G)? thanks greggiraud at netcourrier.com grego ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

boot/simple in ROM?

Mark A. Greer wrote: > You're a little sparse on info here but try lopping off the first 64KB > of your zImage (or jump 0x1 into the zImage that you have). Oh yeah...good point. It's just a reflex for me to check this, so I seldom think of it anymore. I think some board builds automaticall

Basic Config file

Hello all, I recently downloaded and installed the ELDK under RedHat 8 targeting a 74xx. Everything went pretty smooth (Thanks Wolfgang!). I am utterly inexperienced at building the kernel. This is the first one. I have everything compiling, but getting various linker unresolves. Can someone

cache init problems - (non multi-mimed mail )

Hi.. I have a problem for porting PPC-BOOT to STT755EMC. Here is my BD spec. CPU: MPC750 ( main core ) + MPC8260 ( companion only ) L2 cache: 1M SDRAM on 60x bus: 64M SDRAM on Local bus: 32M FLASH: 8MB 10/100 Base T port on FFC2 Dual RS232 port residing SMC1 & SMC2. The problem is cache. Wh

Library size

Hi all, I am working on custome design board based on IBM power PC 405. We have seen the libraries like : ld-2.2.3.so libcrypt-2.2.3.so ld.so.1 libpthread-0.9.so libSegFault.so libc-2.2.3.so in the filesystem, lib folder. "libc-2.2.3.so" is taking arounr 1.5MB space. Is there any way to reduce t

boot/simple in ROM?

The "simple" boot loaders are loaders, they are NOT bootroms. They expect the board to have a firmware/bootrom/monitor that does the necessary very low level very hardware specific initialization (things like setting up memory maps, initializing the SDRAM controller, etc.). The "simple" boot loa

boot/simple in ROM?

On Thu, Apr 24, 2003 at 01:13:35PM -0400, Dan Malek wrote: > The other really nice thing about these bootloaders, compressed > kernels, and attached initrd, is you can boot the identical image > from all "devices." For example, during development you can tftp > load the image, get everything work

boot/simple in ROM?

Kent Borg wrote: > The boot loader thingie in arch/ppc/boot/simple is nifty. So why > isn't there a provision for putting it on ROM? Well, you normally place it in ROM along with the kernel that is attached. The purpose of all of these "bootloaders" is to convert a rom calling sequence into a

boot/simple in ROM?

The boot loader thingie in arch/ppc/boot/simple is nifty. So why isn't there a provision for putting it on ROM? (Or is there and I missed it?) Because boot/simple decompresses to RAM at 0x0, it seems obvious that it might be decompressing from ROM. What is the right way to do this? (Or, point

boot/simple in ROM?

Dan Malek wrote: > > The old PPCBoot, and probably the new U-boot, kind of perform > some of these functions. The reason I'm not a fan of doing this > is if we make a change to the Linux calling sequence (which happens > rarely) you also have to update the boot rom to match. Not a good > t

I2C having issues

- Original Message - From: "Pagnotta, Chris" <[EMAIL PROTECTED]> To: Sent: Tuesday, April 22, 2003 8:48 PM Subject: I2C having issues > > I tried a couple of things to to get the i2c device up and working and I > am stil having some problems. The I2C registers are mappped to internal > m

boot/simple in ROM?

I based mine off boot/simple. It runs fine from ROM. Suppose for example I have 32MB SDRAM from 0x to 0x01ff, and 16MB flash from 0xff00 to 0x. The key is that arch/ppc/boot/ld.script, and arch/ppc/boot/simple/Makefile with -Ttext (say) 0x0040, make zImage.initrd an E

boot/simple in ROM?

Jerry Van Baren wrote: > > The "simple" boot loaders are loaders, they are NOT bootroms. They > expect > the board to have a firmware/bootrom/monitor that does the necessary very > low level very hardware specific initialization (things like setting up > memory maps, initializing the SDRAM contr

initrd problems

Hello, I am unable to boot up my linux with my ramdisk image. Board: MPC8260 ADS Kernel: 2.4.1 PPC Boot: 2.0.0 When I boot up the kernel without ramdisk, the same kernel image is booting up fine. But when I use a ramdisk ## Booting image at 0010 ... Image Name: Embedix for MPC8260ADS

Linux & DMA transfer (applied to 8245)

Hi , I am implementing DMA transfers initiated by the processor for the MPC8245. Since the standard pci_alloc_consistent take only a pci_dev structure but no addresses, I added a configuration function to set the target address (PCI) and the other parameters. I can see that the DMA transfer is sta

boot/simple in ROM?

Kent Borg wrote: >On Thu, Apr 24, 2003 at 01:13:35PM -0400, Dan Malek wrote: > > >>The other really nice thing about these bootloaders, compressed >>kernels, and attached initrd, is you can boot the identical image >>from all "devices." For example, during development you can tftp >>load the ima

booting MGT5100?

Thanks for the info! I'm also using an icecube board. I'll grab the code from mv when you post it there. Do you use a bootloader or do you just use dbug to run a zImage? -Chris H. >On Wed, Apr 23, 2003 at 09:55:42PM +, Chris Heintzelman wrote: > > >>I noticed that a few months ago someone

initrd problems

In message <3EA776EC.3090805 at tataelxsi.co.in> you wrote: > > ## Booting image at 0010 ... >Image Name: Embedix for MPC8260ADS >Image Type: PowerPC Linux Kernel Image (gzip compressed) >Data Size:531861 Bytes = 519.4 kB >Load Address: >Entry Point: 0

cache init problems - (non multi-mimed mail )

In message <200304240452.h3O4qrq04070 at www.cnetia.com> you wrote: > > I have a problem for porting PPC-BOOT to STT755EMC. Do not spend effort for PPCBoot. PPCBoot is a dead project, development has been discontiuned half a year ago. Please use the successort project U-Boot instead

booting MGT5100?

On Thu, Apr 24, 2003 at 03:31:42PM +, Chris Heintzelman wrote: > Thanks for the info! I'm also using an icecube board. I'll grab the > code from mv when you post it there. > Do you use a bootloader or do you just use dbug to run a zImage? > > -Chris H. I'm using the boot_simple boot wrapper

Library size

Search the list archives for Library Optimization. There a ways to reduce the size of a glibc C library, or you should us an alternative C library such as uClibc. --Mark Rakesh Jagota wrote: > Hi all, > I am working on custome design board based on IBM power PC 405. We have seen > the libraries

Library size

Hi Look at www.uclibc.org cedric > -Original Message- > From: owner-linuxppc-embedded at lists.linuxppc.org > [mailto:owner-linuxppc-embedded at lists.linuxppc.org]On Behalf Of Rakesh > Jagota > Sent: Thursday, April 24, 2003 10:20 AM > To: linuxppc-embedded at lists.linuxppc.org > Subj