very minor 405GP and 405GPr PCI difference
> As Matt says, this would fall out naturally from a better control > structure. Howeever, I tend to think that leaving things like this to > the bootloader/firmware is a bad idea: > > The kernel has to know how PCI addresses are mapped anyway, so this > becomes yet another point at which the kernel and firmware are bound > together. Why should the kernel have code to deal with umpteen > different cases of how PCI might have been set up, or not set up by > the firmware/bootloader, when it can just take control of the host > bridge and reprogram it how it wants? Once the debugging cruft comes > out, it should only be a couple of hundred bytes of code. I believe that there are many cases where the kernel code is much too aggressive with configuration. Personally I believe that all BIOS code should totally initialize the processor state so you always have a known starting point. (whether you boot Linux or not) Many times I have had to track down where the kernel thinks it "knows" the proper configuration and unravels the work done by the BIOS. I am not sure how to solve this problem but I believe the kernel should attempt to detect and use a configuration before reconfiguring any hardware. I have implemented this technique in our UART and Ethernet configuration stuff on the 8260 with good success. Only a suggestion... ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
very minor 405GP and 405GPr PCI difference
On Tue, Oct 08, 2002 at 02:14:19PM +1000, David Gibson wrote: > > On Sun, Oct 06, 2002 at 06:31:20PM -0700, Matt Porter wrote: > > > > On Sat, Oct 05, 2002 at 10:23:14PM -0700, Andrew May wrote: > > > > > > It would be nice to have the option to let the boot loader set the > > > mapping. I have been happy with getting things done in PPCBoot and > > > ripping out the PCI scanning in the kernel. > > > > Yes, that's the ideal situation and going to what David and I would > > like to see makes that yet another simple fallout feature. > > > > Your custom port using a good implementation of PPCBoot simply > > would not call the pci macro init library nor would it use pci_auto. > > As Matt says, this would fall out naturally from a better control > structure. Howeever, I tend to think that leaving things like this to > the bootloader/firmware is a bad idea: A full featured bootloader like PPCboot will need to setup the PCI bus to work with PCI devices, so it is not like it is always an extra burden on the bootloader or useless work. > The kernel has to know how PCI addresses are mapped anyway, so this > becomes yet another point at which the kernel and firmware are bound > together. Why should the kernel have code to deal with umpteen > different cases of how PCI might have been set up, or not set up by > the firmware/bootloader, when it can just take control of the host > bridge and reprogram it how it wants? Once the debugging cruft comes > out, it should only be a couple of hundred bytes of code. I wouldn't want to see the kernel deal with all the possible mapping configurations. Right now with everything getting remapped a couple of times it makes it hard to follow what the final mapping will be. Then we also have the core Linux PCI code that will try to fixup things again, if it thinks it is needed. PPCBoot knows how the kernel wants things setup so there should be no need to fix it up. So I just want you to keep in mind the PCI bus fixup can be a config option that can be built out if desired. It really shouldn't be tied to the board itself, since it is also common to load in PPCboot into Walnut boards. Then there is always the case of hot-plugs, and the kernel will always have to do that mapping there. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
can not open crt1.o using ELDK
Hi, When I use the ELDK to compile one file, I got the following message saying can not find crt1.o. Can someone help me on that? I don't have problem compiling one other file. Thanks. Jin hyperion: 224 % make ppc-linux-gcc -D__KERNEL__ -DMODULE -I/u/jcheng/ppclinux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O -g -DDEBUG -fno-strict-aliasing -fno-common -fomit-frame-pointer -I/u/jcheng/ppclinux/arch/ppc -fsigned-char -msoft-float -pipe -ffixed-r2 -Wno-uninitialized -mmultiple -mstring -Wa,-m405 -nostdinc -I/opt/eldk/usr/lib/gcc-lib/ppc-linux/2.95.3/include vayu_main.c dbgprint.h:35: warning: `debug' defined but not used /opt/eldk/usr/ppc-linux/bin/ld: cannot open crt1.o: No such file or directory collect2: ld returned 1 exit status make: *** [vayu_main.o] Error 1 ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
ELDK iso image
Dear Bo, in message <0B0A39652BB0D411BCCF00508B9512EC08AEB42C at tx14exm05.ftw.mot.com> you wrote: > > Would you please provide the ELDK iso image (instead of directory tree) > on your web address: www.denx.de or ftp.leo.org ? No, I won't ;-) > Basically there are a lot of problems for me (perhaps others) to burn the > image on linux box. Well, you always have the option to buy the CDROM if you don't manage to burn one yourself. The main reason not to provide an ISO image whas that we expected our first release of the ELDK to require lots of updates. Actually, this was not really necessary. But it makes little sense to put ISO images out anyway: We will have a new version of the ELDK (based on YD-2.3) out before the end of the month. Even then, we will not provide ISO images. Instead, we intend to use Debian's "jigdo" mechanism to allow for easy creatsion of ISO images on the user side and easy updates on the developer's side. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de Man is the best computer we can put aboard a spacecraft ... and the only one that can be mass produced with unskilled labor. - Wernher von Braun ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
i2c on mpc850
Hello, I have a custom board (with an atmel microcontroller) over a rpxlite dw (mpc850) running linux. I want them to talk i2c to each other. I would like anyone of them to be able to initiate communication. The MPC850 is multimaster-capable. But i don't believe this feature is implemented in the linux kernel (i2c-algo-8xx.c). Am I right? If so, what is the best way of emulating multimaster mode? I thought a simple way of doing so would be for the custom board cto ause an interrupt which would trigger a i2c master-read command, therefore keeping the linux board in master-only mode and the atmel one in slave-only mode... Any comment/suggestion? Best regards, Patrick Mahoney ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
boot linux on fads mpc860
You have to download the FADS image. You have to create an image like this: mkimage -n 'Linux FADS image' -A ppc -O linux -T kernel -C gzip -a -e -d $(PATH_TO_VMLINUX)/vmlinux.gz fads-image where mkimage is created as a tool in ppcboot Then you can use tftpboot to download it (es. tftpboot 10 fads-image) Bye! Stefania rekha gvv wrote: > Hello, > I am new to this mailing list. > I am trying to boot linux from Fads MPC860 powerpc > board I have compiled the linux kernelversion > linux-2.4.4-2002-03-21 .Also i have put the PPcboot > 1.1.6 into the board.now i dont know how to download > this linux kernel into this board.Should i do any > sttings with ppcboot .please do let me know > i am using the tftpboot command but then > wheni tell go 10 it tells > > ## starting application at 0x0010 > > thenit hangs .. > i have tried to download the vmlinux file also > converted that to binary format and also tried but it > gives the same problem > one more thing is when i used the BOOTM command > it used to give > > ##Booting application at 0x0010 > Bad magic number > > I dont understand what to do.so kindly please help > Regards > Rekha > rekhagvvc at yahoo.co.in > > Faith Hill - Exclusive Performances, Videos & More > http://faith.yahoo.com > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
How to submit support for a new board
Hello We have a board based on a MPC850SR that I want to submit for inclusion to the main tree. Currently we work on the stable 2.4.19 branch. The thing is that this board in kind of peculiar. For example there's a driver for the multichannel controller so that means that no serial port is available after booting. That required to include the netconsole patch by Ingo and make it work without being a module. Given into account the scarcity of the dual port RAM under such conditions I've added support for a malloc like interface for DPRAM use, after taking into account the uCode patches and any holes left over by the enabled peripherals. As you can see there is no chance in hell of getting these included as they are. How should I go about this given the feature freeze for 2.6; but the 2.6 tree is too unstable for us. Any suggestions? Regards Pantelis Antoniou Intracom S.A. Greece ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
8260 configuration
Thanks for your help. But it seems that commands such as "CF MMU LINUX" etc could not be recognized as legitimate commands for visionICE2 I am using ? Is that some kind of add-ons ? Thanks. Bo -Original Message- From: Joe Hamman [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 02, 2002 4:40 PM To: Yu Bo-BOYU1; 'Flavio Pereira' Cc: linuxppc embedded Subject: RE: 8260 configuration To debug Linux with the visionICE or visionPROBE you need to tell the tool that the MMU is translating. Here are the commands I use: BKM>CF MMU LINUX BKM>CF MMUA C000 0 FF00 Use the CF MMUL to list the translation table entries in the tool. Convert the .elf file to generate a symbol file (.ab), set the source path in the debugger, and you can debug all the code through init(). You can try to get WindRiver to help, but they're not too keen on helping non-vxWorks customers. Joe -Original Message- From: [EMAIL PROTECTED] [mailto:owner-linuxppc-embedded at lists.linuxppc.org]On Behalf Of Yu Bo-BOYU1 Sent: Wednesday, October 02, 2002 1:10 PM To: 'Flavio Pereira' Cc: linuxppc embedded Subject: RE: 8260 configuration Thanks for your info. I modified est8260.h to map immr to 0xf800_. And the serial port did print out some unreadable stuff and I am very encouraged by this. My serial port setup is the minimal: 9600/8+1/no parity/no flow. Is this correct ? After I halt the processor, I read SRR0 register showing 0xc0153C90. Apparently this is above the 0xc000_ that you indicated. Is that true 0xc000_ is the virtual address as we only have 64M sdram on the board starting 0. [DOC3 Boot]: @ boot device : dbg unit number : 0 processor number : 0 host name: host file name: zImage inet on ethernet (e) : 10.0.0.25:0xff00 host inet (h): 10.0.0.1 user (u) : vx ftp password (pw): vx flags (f): 0x0 target name (tn) : doc3 Attached TCP/IP interface to dbg0. Attaching network interface lo0... done. Loading... 619152 Starting at 0x40... >BKM>GO >RUN> >RUN>halt >BKM>dr srr0 SRR0= C0153C90 >BKM>GO >RUN> >RUN>halt >BKM>dr srr0 SRR0= C0153C7C >BKM>GO >RUN> >RUN> Thanks. Bo -Original Message- From: Flavio Pereira [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 02, 2002 2:23 AM To: Yu Bo-BOYU1 Cc: linuxppc embedded Subject: RE: 8260 configuration Hi Bo 1. Yes the IMMR needs to be configured at least above 0xC000. The kernel executes code at 0xC000, and an IMMR lower that this will cause the kernel to crash as soon as it starts executing code. I recommend that you stay with the default value 0xF000. 2. The start address is fixed to 0x0 3. ? 4. No, not that I know of. 5. Try getting ELDK from the Denx site. (www.denx.de) -Original Message- From: Yu Bo-BOYU1 [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 02, 2002 3:08 AM To: linuxppc embedded Subject: 8260 configuration I am new to embedded linux but I had good experience in vxWorks. Right now I had a custom 8260 board with SMC1 connected to serial port and FCC3 for fast ethernet. I would like to try running linux on this custom board. I downloaded the latest monta vista preview kit 2.1 as my base release. I had boot code ( with vxWorks and it is based on EST8260 bsp) in my custom board already. I decide to download the linux object via tftp. But I have the following questions: 1. Do I have to configure IMMR as 0xF_ or higher. The default configuration in our boot is 0x0F00_ ? Is this a hard requirement or not ? If so, why can't linux init code do so by writing to IMMR+0x101a8 ? 2. How to specify the start address where linux runs when I build the zImage ? 3. When I make xconfig, what configuration I must have in order to run ? I certainly do not need VGA/HARD DISK/PCI (this board does not have pci devices). 4. Is there any good website/paper/documentation about linux for 8260 platform. 5. Can anyone access ftp.leo.org to get ELDK ? I can ping it but I cannot ftp it today. Thanks. Bo ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
ELDK iso image
Mr. Denk, Would you please provide the ELDK iso image (instead of directory tree) on your web address: www.denx.de or ftp.leo.org ? Basically there are a lot of problems for me (perhaps others) to burn the image on linux box. Thanks, Bo ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
boot linux on fads mpc860
Hello, I am new to this mailing list. I am trying to boot linux from Fads MPC860 powerpc board I have compiled the linux kernelversion linux-2.4.4-2002-03-21 .Also i have put the PPcboot 1.1.6 into the board.now i dont know how to download this linux kernel into this board.Should i do any sttings with ppcboot .please do let me know i am using the tftpboot command but then wheni tell go 10 it tells ## starting application at 0x0010 thenit hangs .. i have tried to download the vmlinux file also converted that to binary format and also tried but it gives the same problem one more thing is when i used the BOOTM command it used to give ##Booting application at 0x0010 Bad magic number I dont understand what to do.so kindly please help Regards Rekha rekhagvvc at yahoo.co.in Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
