linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wang Jian <lark@linux.net.cn>
To: Jeff Borlin <jborlin@aclaratech.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Compact Flash on 8349mITX
Date: Fri, 10 Oct 2008 15:26:00 +0800	[thread overview]
Message-ID: <48EF0388.3070006@linux.net.cn> (raw)
In-Reply-To: <19911261.post@talk.nabble.com>

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 0xf0000000 ctl
> 0xf000020c
> 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: 01000000 at fe000000
> [...]
> / # dd if=/dev/sda of=/dev/null count=20000
> 20000+0 records in
> 20000+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)

  reply	other threads:[~2008-10-10  7:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6011A7C9CD0EE74792C3ED2A835560861FA9C0@mail.twacs.com>
2008-07-31 14:24 ` Compact Flash on 8349mITX Sparks, Sam
2008-10-09 15:52   ` Jeff Borlin
2008-10-09 16:28     ` Timur Tabi
2008-10-09 17:00       ` Jeff Borlin
2008-10-09 17:28         ` Timur Tabi
2008-10-09 18:05           ` Jeff Borlin
2008-10-09 17:23     ` Anton Vorontsov
2008-10-10  2:14       ` Wang Jian
2008-10-10 12:03         ` Anton Vorontsov
2008-10-10  3:27       ` Jeff Borlin
2008-10-10  7:26         ` Wang Jian [this message]
2008-10-10 11:40           ` Anton Vorontsov
2008-10-10 11:47         ` Anton Vorontsov
2008-07-31 13:14 Sparks, Sam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48EF0388.3070006@linux.net.cn \
    --to=lark@linux.net.cn \
    --cc=jborlin@aclaratech.com \
    --cc=linuxppc-dev@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).