David, Off the top of my head, I am pretty sure that you will not be able to support RTS/CTS flow control over the SMC/SCC's, I believe that at one time we thought that the SCC's could do it but it isn't truely done in hardware. You will have to refer the the Motorola PowerQUICC Manual, or look through the list's archives. The ethernet driver included in the mpc8xx-2.2.13.tgz works great, you will need to tweak the kernel in several places to fit your board configuration, especially the GPIO for your ethernet signals, but it is straightforward. Also, you will have to modify fadsrom.tgz pretty significantly to support the DRAM timings for your board, chip selects, and so on... mpc8xx-2.2.13 will not work right out of the box on your custom board, you have a lot of work to do with the bootrom (fadsrom is a great starting point) and kernel changes. Drop me a line if you run into problems and I'll see if I can assist you.
Jason -----Original Message----- From: [EMAIL PROTECTED] [mailto:owner-linuxppc-embedded at lists.linuxppc.org]On Behalf Of Brown, David (dbrown03) Sent: Thursday, April 06, 2000 12:04 PM To: 'linuxppc-embedded at lists.linuxppc.org' Subject: Interfaces supported on PPC860? I am planning on running Linux on an existing custom 860-based board, and on a second board which is still being designed. The application will include TCP/IP over Ethernet and PPP interfaces. Can someone please give me feedback on how difficult this will be? Specifically, are all of the interfaces I require currently supported in the kernel? Or will I have to tweak the kernel code? Or will I have to write some new drivers? What could I change on the new board to work better with Linux? Do the serial drivers support RTS/CTS flow control? If I should be reading some existing document or web-page instead of asking the list, please kindly redirect me. I have looked at the mpx8xx-2.2.13.tgz code from ppc.kernel.org (I think that's where I got it from), and I have successfully built and loaded it on a BSE ipEngine. I haven't looked at the 2.3.x series code yet. Interfaces of the existing board: Flash: 1MB(AMD) + 8MB(Intel) SCC1: Ethernet (external PHY), using RXD, TXD, RTS, CTS, CD, and RCLKI (ethernet chip supplies 20MHz clock on RCLKI) SCC3: Async serial: RXD, TXD SCC4: Ethernet loopback and enable (using RXD and TXD lines) SMC1: Async serial: RXD, TXD SMC2: Async serial: RXC, TXD PortC: general purpose I/O, for a user-space driver of a simple LCD display and keyboard. Interfaces of the new board: Flash: 1MB(AMD) + 8MB(Intel) SCC1: Ethernet (external PHY), using RXD, TXD, RTS, CTS, CD, and RCLKI SCC2: Async serial: RXD, TXD (and flow control if possible) SCC3: Async serial: RXD, TXD (and flow control if possible) SCC4: Async serial: RXD, TXD (and flow control if possible) SMC1: Async serial: RXD, TXD SMC2: Async serial: RXC, TXD PortA: Ethernet loopback and enable control signals SPI: Communication with another processor. Does the Linux kernel use this at all today? If not, I'd probably try to expose it to user space. PCMCIA: no use for it now, but looking to the future -- Dave Brown <dbrown03 at harris.com> ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
