Compact Flash on 8349mITX
Hello All, I'm using the latest 2.2.26 kernel image from linux/kernel/git/benh/powerpc.git on a mpc8349mITX, and trying to get Compact Flash to work. The kernel booted fine, but I was surprised to see Compact Flash IRQ was not being handled. Does irq polling need to be used for compact flash to work with this version of the kernel on this board? Here's snip of the unhandled IRQ, for your edification. irq 23: nobody cared (try booting with the "irqpoll" option) Call Trace: [cf829a30] [c00087d4] 0xc00087d4 (unreliable) [cf829a60] [c0052844] 0xc0052844 [cf829a80] [c0052ac4] 0xc0052ac4 [cf829ac0] [c0053520] 0xc0053520 [cf829ad0] [c000581c] 0xc000581c [cf829ae0] [c0012adc] 0xc0012adc --- Exception: 501 at 0xc002f1e0 LR = 0xc00058c8 [cf829ba0] [c02d4ef8] 0xc02d4ef8 (unreliable) [cf829bd0] [c00058c8] 0xc00058c8 [cf829be0] [c002f394] 0xc002f394 [cf829bf0] [c0005820] 0xc0005820 [cf829c00] [c0012adc] 0xc0012adc --- Exception: 501 at 0xc0052450 LR = 0xc0052574 [cf829cf0] [c00527e0] 0xc00527e0 [cf829d20] [c0053a04] 0xc0053a04 [cf829d40] [c01a7d88] 0xc01a7d88 [cf829d70] [c029a5bc] 0xc029a5bc [cf829db0] [c029a8b4] 0xc029a8b4 [cf829e40] [c0202d10] 0xc0202d10 [cf829e60] [c017ab60] 0xc017ab60 [cf829e80] [c017ad6c] 0xc017ad6c [cf829ea0] [c0179758] 0xc0179758 [cf829ed0] [c017adc4] 0xc017adc4 [cf829ee0] [c017a180] 0xc017a180 [cf829f10] [c017b39c] 0xc017b39c [cf829f30] [c0202f80] 0xc0202f80 [cf829f40] [c0320750] 0xc0320750 [cf829f50] [c03007ac] 0xc03007ac [cf829fd0] [c0300994] 0xc0300994 [cf829ff0] [c0012268] 0xc0012268 handlers: [] Disabling IRQ #23 Thanks for the help, Sam ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
RE: Compact Flash on 8349mITX
>From: Sparks, Sam >Sent: Thursday, July 31, 2008 8:15 AM >Does irq polling need to be used for compact flash to work >with this version of the kernel on this board? When I remove the interrupt definition from the DTS (to cause irqpolling), the ata driver gets stuck in a loop displaying the following. Does anyone have any insight? ata1.00: status: { DRDY } ata1.00: qc timeout (cmd 0xec) ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) ata1.00: revalidation failed (errno=-5) ata1: hard resetting link ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) ata1.00: configured for UDMA/100 ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x20 (host bus error) ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
RE: Compact Flash on 8349mITX
I have taken over this effort to get Compact Flash working on the 8349mITX board and am running into these same issues. I can get uBoot to list the contents of a CF card, but am running into a couple problems through the kernel. There appears to be an IRQ problem and a general communication problem with the CF card, possibly related. Note that I am very new to Linux so please don't assume obvious things are correct I am using the latest from /linux/kernel/git/benh/powerpc.git, and created my dtb from: arch/powerpc/dts/mpc8349emitx.dts. Any ideas on what I could try or look into next with either issue? boot info: [...] Kernel command line: root=/dev/ram ramdisk_size=65000 rw ip=10.100.17.83:10.100.10.74:10.100.17.1:255.255.255.0::eth0:off irqpoll console=ttyS0,115200 mtdparts=physmap-flash.0:64k,8128k,- Misrouted IRQ fixup and polling support enabled [...] Using MPC834x ITX machine description Linux version 2.6.27-rc5-11100-g7c12d90-dirty ([EMAIL PROTECTED]) (gcc version 3.4.5) #4 Thu Oct 9 07:56:48 CDT 2008 [...] eth1: Running with NAPI enabled eth1: 256/256 RX/TX BD ring size Driver 'sd' needs updating - please use bus_type methods sata_sil :00:10.0: Applying R_ERR on DMA activate FIS errata fix scsi0 : sata_sil scsi1 : sata_sil scsi2 : sata_sil scsi3 : sata_sil ata1: SATA max UDMA/100 mmio [EMAIL PROTECTED] tf 0x9080 irq 22 ata2: SATA max UDMA/100 mmio [EMAIL PROTECTED] tf 0x90c0 irq 22 ata3: SATA max UDMA/100 mmio [EMAIL PROTECTED] tf 0x9280 irq 22 ata4: SATA max UDMA/100 mmio [EMAIL PROTECTED] tf 0x92c0 irq 22 ata1: SATA link down (SStatus 0 SControl 310) ata2: SATA link down (SStatus 0 SControl 310) ata3: SATA link down (SStatus 0 SControl 310) ata4: SATA link down (SStatus 0 SControl 310) irq 23: nobody cared (try booting with the "irqpoll" option) Call Trace: [cec29a30] [c00089a4] 0xc00089a4 (unreliable) [cec29a60] [c00467d8] 0xc00467d8 [...] Disabling IRQ #23 scsi4 : pata_platform ata5: PATA max PIO6 mmio cmd 0xf000 ctl 0xf20c irq 23 ata5.00: CFA: SanDisk SDCFJ-512, HDX 3.13, max MWDMA2 ata5.00: 1000944 sectors, multi 0: LBA ata5.00: configured for PIO scsi 4:0:0:0: Direct-Access ATA SanDisk SDCFJ-51 HDX PQ: 0 ANSI: 5 sd 4:0:0:0: [sda] 1000944 512-byte hardware sectors (512 MB) sd 4:0:0:0: [sda] Write Protect is off sd 4:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA sd 4:0:0:0: [sda] 1000944 512-byte hardware sectors (512 MB) sd 4:0:0:0: [sda] Write Protect is off sd 4:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA sda:<3>ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen ata5.00: cmd 20/00:08:00:00:00/00:00:00:00:00/e0 tag 0 pio 4096 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) ata5.00: status: { DRDY } ata5: soft resetting link ata5.00: configured for PIO ata5: EH complete ata5.00: limiting speed to UDMA7:PIO5 ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen ata5.00: cmd 20/00:08:00:00:00/00:00:00:00:00/e0 tag 0 pio 4096 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) ata5.00: status: { DRDY } ata5: soft resetting link ata5.00: configured for PIO ata5: EH complete ata5.00: limiting speed to PIO0 [...] -- View this message in context: http://www.nabble.com/Compact-Flash-on-8349mITX-tp18754330p19900326.html Sent from the linuxppc-dev mailing list archive at Nabble.com. ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: Compact Flash on 8349mITX
On Thu, Oct 9, 2008 at 10:52 AM, Jeff Borlin <[EMAIL PROTECTED]> wrote: > > I have taken over this effort to get Compact Flash working on the 8349mITX > board and am running into these same issues. I can get uBoot to list the > contents of a CF card, but am running into a couple problems through the > kernel. There appears to be an IRQ problem and a general communication > problem with the CF card, possibly related. I've heard on-and-off that there are problems with the CF support on the 8349 ITX, but I've never had the chance to investigate it. Can you try using the latest BSP kernel and see if the problem is present there? Sometimes the BSP has a hacked-up kernel that addresses hardware issues, but these patches aren't pushed upstream, so the mainline kernel has problems. -- Timur Tabi Linux kernel developer at Freescale ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: Compact Flash on 8349mITX
Can you point me to where that can be found? Timur Tabi-3 wrote: > > I've heard on-and-off that there are problems with the CF support on > the 8349 ITX, but I've never had the chance to investigate it. > > Can you try using the latest BSP kernel and see if the problem is > present there? Sometimes the BSP has a hacked-up kernel that > addresses hardware issues, but these patches aren't pushed upstream, > so the mainline kernel has problems. > > -- > Timur Tabi > Linux kernel developer at Freescale > ___ > Linuxppc-dev mailing list > Linuxppc-dev@ozlabs.org > https://ozlabs.org/mailman/listinfo/linuxppc-dev > > -- View this message in context: http://www.nabble.com/Compact-Flash-on-8349mITX-tp18754330p19903135.html Sent from the linuxppc-dev mailing list archive at Nabble.com. ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: Compact Flash on 8349mITX
On Thu, Oct 09, 2008 at 08:52:09AM -0700, Jeff Borlin wrote: > > I have taken over this effort to get Compact Flash working on the 8349mITX > board and am running into these same issues. I can get uBoot to list the > contents of a CF card, U-Boot doesn't use interrupts. > but am running into a couple problems through the > kernel. There appears to be an IRQ problem and a general communication > problem with the CF card, possibly related. Note that I am very new to > Linux so please don't assume obvious things are correct > > I am using the latest from /linux/kernel/git/benh/powerpc.git, and created > my dtb from: arch/powerpc/dts/mpc8349emitx.dts. > > Any ideas on what I could try or look into next with either issue? > > boot info: > [...] [...] This happens just before the PATA information is printed. I'm not libata expert; and from the brief look I don't see where libata clears any pending "unexpected" irqs. Just a guesswork, could you try this patch? diff --git a/drivers/ata/pata_platform.c b/drivers/ata/pata_platform.c index 8f65ad6..3b7c79d 100644 --- a/drivers/ata/pata_platform.c +++ b/drivers/ata/pata_platform.c @@ -15,6 +15,7 @@ #include #include #include +#include #include #include #include @@ -171,6 +172,8 @@ int __devinit __pata_platform_probe(struct device *dev, pata_platform_setup_port(&ap->ioaddr, ioport_shift); + ioread8(ap->ioaddr.status_addr); + ata_port_desc(ap, "%s cmd 0x%llx ctl 0x%llx", mmio ? "mmio" : "ioport", (unsigned long long)io_res->start, (unsigned long long)ctl_res->start); > irq 23: nobody cared (try booting with the "irqpoll" option) > Call Trace: > [cec29a30] [c00089a4] 0xc00089a4 (unreliable) > [cec29a60] [c00467d8] 0xc00467d8 > [...] > Disabling IRQ #23 > scsi4 : pata_platform > ata5: PATA max PIO6 mmio cmd 0xf000 ctl 0xf20c irq 23 > ata5.00: CFA: SanDisk SDCFJ-512, HDX 3.13, max MWDMA2 > ata5.00: 1000944 sectors, multi 0: LBA > ata5.00: configured for PIO Can you check if the CF will work w/o IRQs? To try it: 1. open the arch/powerpc/dts/mpc8349emitx.dts file, find the pata node: [EMAIL PROTECTED],0 { compatible = "fsl,mpc8349emitx-pata", "ata-generic"; reg = <0x3 0x0 0x10 0x3 0x20c 0x4>; reg-shift = <1>; pio-mode = <6>; interrupts = <23 0x8>; interrupt-parent = <&ipic>; }; 2. delete interrupts = <>; and interrupt-parent = <>; lines. 3. recompile the dts to dtb. 4. Apply this patch to the kernel http://lkml.org/lkml/2008/10/6/176 5. And try to boot the patched kernel using the re-compiled dtb file. > scsi 4:0:0:0: Direct-Access ATA SanDisk SDCFJ-51 HDX PQ: 0 ANSI: 5 > sd 4:0:0:0: [sda] 1000944 512-byte hardware sectors (512 MB) > sd 4:0:0:0: [sda] Write Protect is off > sd 4:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't > support DPO or FUA > sd 4:0:0:0: [sda] 1000944 512-byte hardware sectors (512 MB) > sd 4:0:0:0: [sda] Write Protect is off > sd 4:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't > support DPO or FUA > sda:<3>ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen > ata5.00: cmd 20/00:08:00:00:00/00:00:00:00:00/e0 tag 0 pio 4096 in > res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > ata5.00: status: { DRDY } > ata5: soft resetting link > ata5.00: configured for PIO > ata5: EH complete > ata5.00: limiting speed to UDMA7:PIO5 > ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen > ata5.00: cmd 20/00:08:00:00:00/00:00:00:00:00/e0 tag 0 pio 4096 in > res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > ata5.00: status: { DRDY } > ata5: soft resetting link > ata5.00: configured for PIO > ata5: EH complete > ata5.00: limiting speed to PIO0 > [...] Thanks, -- Anton Vorontsov email: [EMAIL PROTECTED] irc://irc.freenode.net/bd2 ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: Compact Flash on 8349mITX
On Thu, Oct 9, 2008 at 12:00 PM, Jeff Borlin <[EMAIL PROTECTED]> wrote: > > Can you point me to where that can be found? It's on the CD that came with the board. -- Timur Tabi Linux kernel developer at Freescale ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: Compact Flash on 8349mITX
The version on the CD does not seem to see it at all: [...] U-Boot 1.3.4-rc1-00012-g1953d12 (Jul 28 2008 - 09:09:09) MPC83XX [...] Linux version 2.6.13.4 ([EMAIL PROTECTED]) (gcc version 3.4.3) #1 Thu Oct 19 16:27:15 EDT 2006 PCI2 confirm: isa_io_base = 0xfc00 Configure PCI2 controller isa_io_base = 0xfc00 hose2->io_base_virt = 0xfd00 Built 1 zonelists Kernel command line: root=/dev/ram ramdisk_size=65000 rw ip=10.100.17.83:10.100.10.74:10.100.17.1:255.255.255.0::eth0:off console=ttyS0,115200 mtdparts=physmap-flash.0:64k,8128k,- IPIC (128 IRQ sources, 8 External IRQs) at fe000700 PID hash table entries: 2048 (order: 11, 32768 bytes) Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 244096k available (2432k kernel code, 884k data, 120k init, 0k highmem) Mount-cache hash table entries: 512 checking if image is initramfs...it isn't (no cpio magic); looks like an initrd Freeing initrd memory: 11910k freed NET: Registered protocol family 16 PCI: Probing PCI hardware PCI: Cannot allocate resource region 0 of device :00:00.0 PCI: Cannot allocate resource region 2 of device :00:00.0 PCI: Cannot allocate resource region 0 of device 0001:01:00.0 PCI: Cannot allocate resource region 2 of device 0001:01:00.0 PCI: Failed to allocate mem resource #2:[EMAIL PROTECTED] for :00:00.0 PCI: Failed to allocate mem resource #2:[EMAIL PROTECTED] for 0001:01:00.0 SCSI subsystem initialized usbcore: registered new driver usbfs usbcore: registered new driver hub NTFS driver 2.1.23 [Flags: R/W DEBUG]. Generic RTC Driver v1.07 Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled ttyS0 at MMIO 0xe0004500 (irq = 9) is a 16550A ttyS1 at MMIO 0xe0004600 (irq = 10) is a 16550A io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered RAMDISK driver initialized: 16 RAM disks of 65000K size 1024 blocksize loop: loaded (max 8 devices) Intel(R) PRO/1000 Network Driver - version 6.0.60-k2 Copyright (c) 1999-2005 Intel Corporation. eth0: Gianfar Ethernet Controller Version 1.1, 08:00:3e:03:01:10 eth0: Running with NAPI enabled eth0: 32/32 RX/TX BD ring size eth1: Gianfar Ethernet Controller Version 1.1, 08:00:3e:03:01:11 eth1: Running with NAPI enabled eth1: 32/32 RX/TX BD ring size sata_sil(:00:10.0): cache line size not set. Driver may not function ata1: SATA max UDMA/100 cmd 0xD1000C80 ctl 0xD1000C8A bmdma 0xD1000C00 irq 22 ata2: SATA max UDMA/100 cmd 0xD1000CC0 ctl 0xD1000CCA bmdma 0xD1000C08 irq 22 ata3: SATA max UDMA/100 cmd 0xD1000E80 ctl 0xD1000E8A bmdma 0xD1000E00 irq 22 ata4: SATA max UDMA/100 cmd 0xD1000EC0 ctl 0xD1000ECA bmdma 0xD1000E08 irq 22 ata1: no device found (phy stat ) scsi0 : sata_sil ata2: no device found (phy stat ) scsi1 : sata_sil ata3: no device found (phy stat ) scsi2 : sata_sil ata4: no device found (phy stat ) scsi3 : sata_sil usbmon: debugfs is not available driver fsl-usb2-mph, $Revision: 1.11 $ [...] Will try Anton's suggestions next. -Jeff Timur Tabi-3 wrote: > > On Thu, Oct 9, 2008 at 12:00 PM, Jeff Borlin <[EMAIL PROTECTED]> > wrote: >> >> Can you point me to where that can be found? > > It's on the CD that came with the board. > > -- > Timur Tabi > Linux kernel developer at Freescale > ___ > Linuxppc-dev mailing list > Linuxppc-dev@ozlabs.org > https://ozlabs.org/mailman/listinfo/linuxppc-dev > > -- View this message in context: http://www.nabble.com/Compact-Flash-on-8349mITX-tp18754330p19904213.html Sent from the linuxppc-dev mailing list archive at Nabble.com. ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: Compact Flash on 8349mITX
How 8349mITX's compact flash is wired? If it is wired using 8 bit data bus line, without another patch, data transfer can't be done. Looking at logs Sam Sparks provided (without irq): ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) it seems data transfer failed. I have a 8 bit data transfer mode dirty hack on pata_platform. I am waiting for the no irq handling patch goes in and then make my patch more generic. Anton Vorontsov wrote: On Thu, Oct 09, 2008 at 08:52:09AM -0700, Jeff Borlin wrote: I have taken over this effort to get Compact Flash working on the 8349mITX board and am running into these same issues. I can get uBoot to list the contents of a CF card, U-Boot doesn't use interrupts. but am running into a couple problems through the kernel. There appears to be an IRQ problem and a general communication problem with the CF card, possibly related. Note that I am very new to Linux so please don't assume obvious things are correct I am using the latest from /linux/kernel/git/benh/powerpc.git, and created my dtb from: arch/powerpc/dts/mpc8349emitx.dts. Any ideas on what I could try or look into next with either issue? boot info: [...] [...] This happens just before the PATA information is printed. I'm not libata expert; and from the brief look I don't see where libata clears any pending "unexpected" irqs. Just a guesswork, could you try this patch? diff --git a/drivers/ata/pata_platform.c b/drivers/ata/pata_platform.c index 8f65ad6..3b7c79d 100644 --- a/drivers/ata/pata_platform.c +++ b/drivers/ata/pata_platform.c @@ -15,6 +15,7 @@ #include #include #include +#include #include #include #include @@ -171,6 +172,8 @@ int __devinit __pata_platform_probe(struct device *dev, pata_platform_setup_port(&ap->ioaddr, ioport_shift); + ioread8(ap->ioaddr.status_addr); + ata_port_desc(ap, "%s cmd 0x%llx ctl 0x%llx", mmio ? "mmio" : "ioport", (unsigned long long)io_res->start, (unsigned long long)ctl_res->start); irq 23: nobody cared (try booting with the "irqpoll" option) Call Trace: [cec29a30] [c00089a4] 0xc00089a4 (unreliable) [cec29a60] [c00467d8] 0xc00467d8 [...] Disabling IRQ #23 scsi4 : pata_platform ata5: PATA max PIO6 mmio cmd 0xf000 ctl 0xf20c irq 23 ata5.00: CFA: SanDisk SDCFJ-512, HDX 3.13, max MWDMA2 ata5.00: 1000944 sectors, multi 0: LBA ata5.00: configured for PIO Can you check if the CF will work w/o IRQs? To try it: 1. open the arch/powerpc/dts/mpc8349emitx.dts file, find the pata node: [EMAIL PROTECTED],0 { compatible = "fsl,mpc8349emitx-pata", "ata-generic"; reg = <0x3 0x0 0x10 0x3 0x20c 0x4>; reg-shift = <1>; pio-mode = <6>; interrupts = <23 0x8>; interrupt-parent = <&ipic>; }; 2. delete interrupts = <>; and interrupt-parent = <>; lines. 3. recompile the dts to dtb. 4. Apply this patch to the kernel http://lkml.org/lkml/2008/10/6/176 5. And try to boot the patched kernel using the re-compiled dtb file. scsi 4:0:0:0: Direct-Access ATA SanDisk SDCFJ-51 HDX PQ: 0 ANSI: 5 sd 4:0:0:0: [sda] 1000944 512-byte hardware sectors (512 MB) sd 4:0:0:0: [sda] Write Protect is off sd 4:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA sd 4:0:0:0: [sda] 1000944 512-byte hardware sectors (512 MB) sd 4:0:0:0: [sda] Write Protect is off sd 4:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA sda:<3>ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen ata5.00: cmd 20/00:08:00:00:00/00:00:00:00:00/e0 tag 0 pio 4096 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) ata5.00: status: { DRDY } ata5: soft resetting link ata5.00: configured for PIO ata5: EH complete ata5.00: limiting speed to UDMA7:PIO5 ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen ata5.00: cmd 20/00:08:00:00:00/00:00:00:00:00/e0 tag 0 pio 4096 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) ata5.00: status: { DRDY } ata5: soft resetting link ata5.00: configured for PIO ata5: EH complete ata5.00: limiting speed to PIO0 [...] Thanks, ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: Compact Flash on 8349mITX
Anton Vorontsov-2 wrote: > > This happens just before the PATA information is printed. I'm not > libata expert; and from the brief look I don't see where libata > clears any pending "unexpected" irqs. Just a guesswork, > could you try this patch? > This patch did not appear to change anything. Anton Vorontsov-2 wrote: > > Can you check if the CF will work w/o IRQs? To try it: > Your directions did result in progress: [...] scsi4 : pata_platform ata5: PATA max PIO6 no IRQ, using PIO polling mmio cmd 0xf000 ctl 0xf20c ata5.00: CFA: SanDisk SDCFJ-512, HDX 3.13, max MWDMA2 ata5.00: 1000944 sectors, multi 0: LBA ata5.00: configured for PIO scsi 4:0:0:0: Direct-Access ATA SanDisk SDCFJ-51 HDX PQ: 0 ANSI: 5 sd 4:0:0:0: [sda] 1000944 512-byte hardware sectors (512 MB) sd 4:0:0:0: [sda] Write Protect is off sd 4:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA sd 4:0:0:0: [sda] 1000944 512-byte hardware sectors (512 MB) sd 4:0:0:0: [sda] Write Protect is off sd 4:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA sda: sda1 sda2 sd 4:0:0:0: [sda] Attached SCSI removable disk sd 4:0:0:0: Attached scsi generic sg0 type 0 physmap platform flash device: 0100 at fe00 [...] / # dd if=/dev/sda of=/dev/null count=2 2+0 records in 2+0 records out / # mount -t vfat /dev/sda /mnt/cf mount: Mounting /dev/sda on /mnt/cf failed: Invalid argument / # mount -t vfat /dev/sda2 /mnt/cf mount: Mounting /dev/sda2 on /mnt/cf failed: Invalid argument I still need to figure out what I may be doing wrong here, but wanted to post the results I have so far in case they are useful. -- View this message in context: http://www.nabble.com/Compact-Flash-on-8349mITX-tp18754330p19911261.html Sent from the linuxppc-dev mailing list archive at Nabble.com. ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: Compact Flash on 8349mITX
Jeff Borlin wrote: Anton Vorontsov-2 wrote: This happens just before the PATA information is printed. I'm not libata expert; and from the brief look I don't see where libata clears any pending "unexpected" irqs. Just a guesswork, could you try this patch? This patch did not appear to change anything. Without this patch, you can't use it without irq. Anton Vorontsov-2 wrote: Can you check if the CF will work w/o IRQs? To try it: Your directions did result in progress: [...] scsi4 : pata_platform ata5: PATA max PIO6 no IRQ, using PIO polling mmio cmd 0xf000 ctl 0xf20c ata5.00: CFA: SanDisk SDCFJ-512, HDX 3.13, max MWDMA2 ata5.00: 1000944 sectors, multi 0: LBA ata5.00: configured for PIO scsi 4:0:0:0: Direct-Access ATA SanDisk SDCFJ-51 HDX PQ: 0 ANSI: 5 sd 4:0:0:0: [sda] 1000944 512-byte hardware sectors (512 MB) sd 4:0:0:0: [sda] Write Protect is off sd 4:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA sd 4:0:0:0: [sda] 1000944 512-byte hardware sectors (512 MB) sd 4:0:0:0: [sda] Write Protect is off sd 4:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA sda: sda1 sda2 sd 4:0:0:0: [sda] Attached SCSI removable disk sd 4:0:0:0: Attached scsi generic sg0 type 0 physmap platform flash device: 0100 at fe00 [...] / # dd if=/dev/sda of=/dev/null count=2 2+0 records in 2+0 records out / # mount -t vfat /dev/sda /mnt/cf mount: Mounting /dev/sda on /mnt/cf failed: Invalid argument / # mount -t vfat /dev/sda2 /mnt/cf mount: Mounting /dev/sda2 on /mnt/cf failed: Invalid argument I still need to figure out what I may be doing wrong here, but wanted to post the results I have so far in case they are useful. The CF card seems to work fine. See if your kernel supports vfat by # cat /proc/filesystems Of course, you need to mount /proc properly first. If your kernel doesn't support vfat, make it support. Or you can insert a blank CF card and play with it (ext2, etc) ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: Compact Flash on 8349mITX
On Fri, Oct 10, 2008 at 03:26:00PM +0800, Wang Jian wrote: > Jeff Borlin wrote: >> >> Anton Vorontsov-2 wrote: >>> This happens just before the PATA information is printed. I'm not >>> libata expert; and from the brief look I don't see where libata >>> clears any pending "unexpected" irqs. Just a guesswork, >>> could you try this patch? >>> >> This patch did not appear to change anything. > > Without this patch, you can't use it without irq. I purposed two patches to Jeff: one is + ioread8(ap->ioaddr.status_addr); I.e. clear an interrupt before requesting (just to be sure, I guess libata is doing this already, just don't see where exactly). That didn't work. :-/ And another approach was to try IRQ-less pata (another patch). -- Anton Vorontsov email: [EMAIL PROTECTED] irc://irc.freenode.net/bd2 ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: Compact Flash on 8349mITX
On Thu, Oct 09, 2008 at 08:27:05PM -0700, Jeff Borlin wrote: > > > Anton Vorontsov-2 wrote: > > > > This happens just before the PATA information is printed. I'm not > > libata expert; and from the brief look I don't see where libata > > clears any pending "unexpected" irqs. Just a guesswork, > > could you try this patch? > > > This patch did not appear to change anything. :-( > Anton Vorontsov-2 wrote: > > > > Can you check if the CF will work w/o IRQs? To try it: > > > Your directions did result in progress: > [...] > scsi4 : pata_platform > ata5: PATA max PIO6 no IRQ, using PIO polling mmio cmd 0xf000 ctl > 0xf20c > ata5.00: CFA: SanDisk SDCFJ-512, HDX 3.13, max MWDMA2 > ata5.00: 1000944 sectors, multi 0: LBA > ata5.00: configured for PIO > scsi 4:0:0:0: Direct-Access ATA SanDisk SDCFJ-51 HDX PQ: 0 ANSI: 5 > sd 4:0:0:0: [sda] 1000944 512-byte hardware sectors (512 MB) > sd 4:0:0:0: [sda] Write Protect is off > sd 4:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't > support DPO or FUA > sd 4:0:0:0: [sda] 1000944 512-byte hardware sectors (512 MB) > sd 4:0:0:0: [sda] Write Protect is off > sd 4:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't > support DPO or FUA > sda: sda1 sda2 > sd 4:0:0:0: [sda] Attached SCSI removable disk > sd 4:0:0:0: Attached scsi generic sg0 type 0 > physmap platform flash device: 0100 at fe00 > [...] > / # dd if=/dev/sda of=/dev/null count=2 > 2+0 records in > 2+0 records out Ok, it basically works w/o IRQs... I'll try to find bunch of CF flashes to test, but to my knowledge they all worked for me on the mitx (i.e. with IRQs)... :-/ If I could find the non-working CF (or non-working mITX board) I would investigate this... > / # mount -t vfat /dev/sda /mnt/cf > mount: Mounting /dev/sda on /mnt/cf failed: Invalid argument > / # mount -t vfat /dev/sda2 /mnt/cf > mount: Mounting /dev/sda2 on /mnt/cf failed: Invalid argument This seems unrelated, either there isn't vfat support enabled in the kernel, or there is another filesystem on the CF). -- Anton Vorontsov email: [EMAIL PROTECTED] irc://irc.freenode.net/bd2 ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: Compact Flash on 8349mITX
On Fri, Oct 10, 2008 at 10:14:17AM +0800, Wang Jian wrote: > How 8349mITX's compact flash is wired? FYI, the schematics are openly available. http://www.freescale.com/files/32bit/hardware_tools/schematics/MPC8349EMITXESCH.pdf?WT_TYPE=Schematics&WT_VENDOR=FREESCALE&WT_FILE_FORMAT=pdf&WT_ASSET=Downloads > If it is wired using 8 bit data bus line, > without another patch, data transfer can't be done. It is wired that way: LBD[7:0]D[0:7] LBD[15:8] D[8:15] LBA[30..28] A[0..2] I.e. 16 bits for data. > Looking at logs Sam Sparks provided (without irq): > > ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) > > it seems data transfer failed. Well, w/o IRQs everything is OK. I think it's just a bogus message after the interrupt issues. Thanks, -- Anton Vorontsov email: [EMAIL PROTECTED] irc://irc.freenode.net/bd2 ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev