linux SPI driver for MPC852T
Hi, allI am entirely new to the PPC platform. I wish to know whether there is a existing port/code for SPI driver on MPC852T. Otherwise do we have any reference code.Also required is the help on the understanding document on SPI. Please let me know asap. ANy inputs will be highly appreciated.Cheers,Alfred.Get your free web-based e-mail account from http://www.Math.netYour online tourguide of Mathematics, with books, links, news,message boards, and much more! ___ Linuxppc-embedded mailing list [EMAIL PROTECTED] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Tri-mode auto-negotiation on ML405
Dear all, I have the Xilinx TEMAC (kind of) working on an ML405 using an adapter.c file posted by Rick Moleres on 8th Feb 2007. However, there are some serious issues with auto-negotiation: 1. link negotiation at startup is *very* slow - in the order of ten seconds 2. if no network is detected at the boot time the auto-negotiation runs through 1G, 100M, 10M before giving up. I guess this leaves the PHY in a 10M state. When I plug a link in the PHY says 10M. I have 100M and 1G links available (but no 10M link) neither work. 3. if a link is present boot time the auto-negotiation correctly chooses the link speed and the link appears to function. If I unplug the link and replace it with a different speed the link will not function. If the original link was 100M, the PHY identifies a 1G link as 100M and it does not work. If the original link was 1G the PHY gives up altogether and no link is detected. I guess this all makes sense: it just means that the PHY is not auto-negotiating the link speed. Being a newbie at this and really not knowing what I am doing I tried adding a call to set_mac_speed in poll_gmii where a link carrier is detected (after it prints link carrier restored). This successfully renegotiated the link speed when a link was inserted, but only in certain cases. If the link first inserted was 100M, or if there was no link present an inserted link of either 100M or 1G would renegotiate fine. After having a 100M link, inserting a 1G link would *say* it had renegotiated, the PHY lights up and tells me the link is running at 1G, but nothing works. Also, whenever this negotiation is going on, everything grinds to a halt. After having a 1G link, inserting a 100M link would result in the PHY not even picking up the link, as before. I'm clearly barking up the wrong tree here, please can someone tell me The Right Way? Many thanks in advance, -- Peter -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ Linuxppc-embedded mailing list [EMAIL PROTECTED] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: HOTO start with linux 2.6.* and ML403
I was able finally to build the kernel 2.6.19 by Denx. The problem was that I have previously used crosstool with gcc-3.2. At the end I was able to compile the kernel with crosstool gcc-4.0.2. I have compared the xparameters_ml403.h file which comes with the kernel and this one generated by EDK. They are very different. Thera are different macro definitions. In the Kernel xparameters_ml403.h I did not find any reference to the XILINX_TEMAC network interface. I did not find references to GPIO LEDS and end swiches. Many other definitions do not much. What would be than the best way to go: 1. To incoroprate to the linux 2.6.19, drivers generated by the EDK or 2. to somhow make use of the existing drivers which come with linux 2.6.19 Best Regards Mirek Andrei Konovalov wrote: Mohammad Sadegh Sadri wrote: snip from all of the files generated there you will need just xparameters.h and xparameters_ml403.h and nothing more if using mvista source, you will not even need these two files the files available in the source are ok themselves - they are OK if you use ML403 and the EDK reference design for this board. For custom FPGA configuration you should use the EDK generated xparameters_ml403.h (if you use EDK to build the bitstream). Thanks, Andrei ___ Linuxppc-embedded mailing list [EMAIL PROTECTED] https://ozlabs.org/mailman/listinfo/linuxppc-embedded -- View this message in context: http://www.nabble.com/HOTO-start-with-linux-2.6.*-and-ML403-tf3559287.html#a9979404 Sent from the linuxppc-embedded mailing list archive at Nabble.com. ___ Linuxppc-embedded mailing list [EMAIL PROTECTED] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
I2c interface on mpc8xx
Hello to all, I'm using linux 2.6.19 on mpc880. I'm trying to use the lm75 component connected to the i2c micro interface. I've inserted the lm75.ko module via insmod command but I haven't found the legacy directory into the sys filesystem (/sys/devices/legacy/). Is it correct that I haven't found it? If it isn't correct, what's the reason? Thanks in advance Luca ___ Linuxppc-embedded mailing list [EMAIL PROTECTED] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
RE: Linux 2.6 and uboot
Sorry, not quite the latest kernel. 2.6.19 as distributed in ELDK 4.1, built for the MPC8555CDS, although the actual board is slightly different. Here is the boot time output. U-boot succesfully enables the ethernet to get its kernel image from the TFTP server. ## Booting image at 0100 ... Image Name: Linux-2.6.19.2 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:1475429 Bytes = 1.4 MB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK Memory CAM mapping: CAM0=256Mb, CAM1=0Mb, CAM2=0Mb residual: 0Mb Linux version 2.6.19.2 ([EMAIL PROTECTED]) (gcc version 4.0.0 (DENX ELDK 4.1 4.0.0)) #3 Mon Apr 13:44:24 EDT 2007 mpc85xx_cds_setup_arch CDS Version = 80 in PCI slot 1 Zone PFN ranges: DMA 0 -65536 Normal 65536 -65536 early_node_map[1] active PFN ranges 0:0 -65536 Built 1 zonelists. Total pages: 65024 Kernel command line: root=/dev/nfs nfsaddrs=204.215.226.247:204.215.226.49:204.215.226.50:255.255.2 5.0 rw nfsroot=/opt/RFS_CAT console=ttyS0,9600 doPci=1 OpenPIC Version 1.2 (1 CPUs and 60 IRQ sources) at fcf78000 PID hash table entries: 1024 (order: 10, 4096 bytes) Warning: real time clock seems stuck! Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 256640k available (2276k kernel code, 704k data, 136k init, 0k highmem) Mount-cache hash table entries: 512 NET: Registered protocol family 16 PCI: Probing PCI hardware Generic PHY: Registered new driver SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 2, 16384 bytes) TCP: Hash tables configured (established 8192 bind 4096) TCP reno registered VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled serial8250.0: ttyS0 at MMIO 0xfdf04500 (irq = 106) is a 16550A serial8250.0: ttyS1 at MMIO 0xfdf04600 (irq = 106) is a 16550A RAMDISK driver initialized: 8 RAM disks of 32768K size 1024 blocksize loop: loaded (max 8 devices) nbd: registered device at major 43 Gianfar MII Bus: probed eth0: Gianfar Ethernet Controller Version 1.2, 00:01:af:07:9b:8b eth0: Running with NAPI enabled eth0: 256/256 RX/TX BD ring size eth1: Gianfar Ethernet Controller Version 1.2, df:f7:bf:7d:72:6f eth1: Running with NAPI enabled eth1: 256/256 RX/TX BD ring size Marvell 88E1101: Registered new driver Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx st: Version 20050830, fixed bufsize 32768, s/g segs 256 ehci_hcd :01:06.2: EHCI Host Controller ehci_hcd :01:06.2: new USB bus registered, assigned bus number 1 ehci_hcd :01:06.2: irq 130, io mem 0x9efbdf00 ehci_hcd :01:06.2: USB 2.0 started, EHCI 0.95, driver 10 Dec 2004 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 4 ports detected ohci_hcd :01:06.0: OHCI Host Controller ohci_hcd :01:06.0: new USB bus registered, assigned bus number 2 ohci_hcd :01:06.0: irq 130, io mem 0x9efbf000 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected ohci_hcd :01:06.1: OHCI Host Controller ohci_hcd :01:06.1: new USB bus registered, assigned bus number 3 ohci_hcd :01:06.1: irq 130, io mem 0x9efbe000 usb usb3: configuration #1 chosen from 1 choice hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. mice: PS/2 mouse device common for all mice i2c /dev entries driver TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 This is the point where it stops booting. Clint Thomas -Original Message- From: Kumar Gala [mailto:[EMAIL PROTECTED] Sent: Friday, April 13, 2007 4:18 PM To: Clint Thomas Cc: [EMAIL PROTECTED] Subject: Re: Linux 2.6 and uboot On Apr 13, 2007, at 2:55 PM, Clint Thomas wrote: Is there any correlation between the version of U-boot to use on a board and the version of the Linux kernel you plan to use? Current I'm running U-boot 1.1.2 with kernel 2.4.26 on my MPC85xx board, but i'm trying to migrate to the latest 2.6 kernel. I am getting a kernel hang at boot when it registers socket family 17, so I was wondering if it might have to
RE: Linux 2.6 and uboot
I found that when trying to build kernel 2.6.19.2 with the ELDK 4.1, and run it on an MPC8349EMDS with u-boot 1.1.3, I had to use ARCH=ppc. ARCH=powerpc would immediately hang. The different architectures use different default kernel configuration files for the same board. But now I am unable to get USB and MTD to work on the board, and am wondering if ARC=ppc is still a viable choice on kernels newer than about 2.6.15, or whether it lacks the best driver support. Could someone please offer a recommendation on this issue? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kumar Gala Sent: Friday, April 13, 2007 1:18 PM To: Clint Thomas Cc: [EMAIL PROTECTED] Subject: Re: Linux 2.6 and uboot On Apr 13, 2007, at 2:55 PM, Clint Thomas wrote: Is there any correlation between the version of U-boot to use on a board and the version of the Linux kernel you plan to use? Current I'm running U-boot 1.1.2 with kernel 2.4.26 on my MPC85xx board, but i'm trying to migrate to the latest 2.6 kernel. I am getting a kernel hang at boot when it registers socket family 17, so I was wondering if it might have to do with u-boot before exploring the debug route. That's an odd place to hang. Which 2.6 kernel are you using? Also are you using arch/ppc or arch/powerpc? - k ___ Linuxppc-embedded mailing list [EMAIL PROTECTED] https://ozlabs.org/mailman/listinfo/linuxppc-embedded ___ Linuxppc-embedded mailing list [EMAIL PROTECTED] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: RFC: MPC52xx serial port configuration from DT blob
Bartlomiej wrote:
We have a MPC5200B-based board running an arch/powerpc kernel and we
need the ability to configure a non-console serial port for a particular
baud rate during system start-up. It seems that the UART driver in
drivers/serial/mpc52xx_uart.c does not support this. It only allows to
set parameters for a port that is used as a console, and for which those
parameters are passed in the kernel command line. We would like to
extend the mpc52xx_uart.c driver to be able to retrieve port options
from the DT blob and configure a given port accordingly. A new
port-specific property called options would be used for this. It would
have syntax following its namesake in console kernel parameter, as
described in Documentation/kernel-parameters.txt.
For example, the following settings in the .dts file would make UART5 to
be configured at 115200 baud, no parity, 8 bits.
[EMAIL PROTECTED] { // PSC5
device_type = serial;
compatible = mpc5200b-psc-uart\0mpc5200-psc-uart;
port-number = 4; // Logical port assignment
options = 115200n8
cell-index = 4;
reg = 2800 100;
interrupts = 2 c 0;
interrupt-parent = 500;
};
In case a console port has conflicting options given in the kernel
command line and in the DT blob, the command line values would be used.
Any comments on the above will be appreciated.
The device tree is intended to be an OS-independent description of the
state of the platform hardware as left by firmware (or bootwrapper).
It is not intended to contain kernel configuration parameters or options,
though there are a few exceptions.
So, this kind of change is unlikely to be accepted.
-Dale
___
Linuxppc-embedded mailing list
[EMAIL PROTECTED]
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
