On Tue, 2006-09-19 at 23:43 +0100, agnel juni wrote: > First, I would like to know if the driver tested in interrupt mode.
Does it work for you in polling mode? If not, you probably have a problem with the way you are accessing the system ace - cache, endianess, byte alignment, etc. If it does work in polling, the usual suspects are interrupt masking errors or some low level problems with your IRQ signals. Since you know the size of a sector and the size of the sysace buffers, how many interrupts do you get per sector read? Do you see extras or not enough? > We are able to mount the CF, but it is very inconsistent. Dump the sector data to the screen that you are reading from the CF. Especially look at the results from the initial identify command to verify that they make sense, and because that is the easiest to check. > Same is the case with fdisk command. When it fails,we get errors which you > could see in the screen-dump below. > Are we missing to apply the right patch? Please let us know your > inputs to go forward. > Looking forwards for your reply. > > # mount -t msdos /dev/xsysace /root/cf Shouldn't this be /dev/xsysace1? You want to mount a partition not the entire block device. -- Jeff Angielski The PTR Group _______________________________________________ Linuxppc-embedded mailing list [email protected] https://ozlabs.org/mailman/listinfo/linuxppc-embedded
