XSysAce driver cant mount DOS part

[Robertson, Joseph M.]

Hi!

Wow, quick replies.

RE: Tree.  
Its the mainline 2.6.17.1, with
denx ppc patches from 4.0.0?  IIRC.
I redid the patch set for the xsysace to get a known baseline.
Its a custom build system, which I developed over the years, ported to use a ppc405 crosscompiler I made from
CrossTool-0.42. Its very similar to uClinux, but with a simpler config system.
The compiler is gcc.3.4.1 with glibc 2.3.3 (yeah we use glibc).

The XsysAce patch is in the normal place, only change I made was to define the major number.
And I moved xbasic_types.c/h to another folder onthe path since xilinx_iic drivers uses it too, and I was getting redefine errors.
One thing I just thought of was I did not run the 'normal' config stuff, any deps in there?
I can go look at the kconfigs and see.

RE: Xilinx SysAce driver
The HW group used Xilinx env 8.2.02i, and the project shows Sysace_compactflash driver:  sysace_v1_01_a

The HW is a Virtex-4 with the embedded ppc405.  The Xsysace chip is supposed tobe using irq_intr = 2.

The system actually works fine using the Ext2 fs, but if we want to upgrade the fpga code, I need to be able to write to the dos part.

Thanks so much.


Joe Robertson
Joseph.Robertson at sanmina-sci.com





-----Original Message-----
From: glikely at secretlab.ca on behalf of Grant Likely
Sent: Thu 7/12/2007 1:16 PM
To: Robertson, Joseph M.
Cc: linuxppc-embedded at ozlabs.org
Subject: Re: XSysAce driver cant mount DOS part
 
On 7/12/07, Robertson, Joseph M. <joseph.robertson at sanmina-sci.com> wrote:
>
>  I've been workig with this for a while but have made no progress.
>  Today I got the latest XSysAce patch for kernel 2.6.17.1 and applied it to
> get clean code.
>  I inherited the previous code from another developer.

Who's tree are you using?  Montavistas?  Mainline?

Which sysace driver are you using?  The old one from Xilinx or the new one?

>
>  My problem is that mounting the DOS partition always fails in a short time
> with a kernel oops.
>
>  ECAU-9999:# Oops: kernel access of bad area, sig: 11 [#1]
>
>  PREEMPT
---8<---snip--->8---
>  LR [C0070C18] drain_array+0xb8/0x124
>
>  Call Trace:

Did you trim off the call trace?  The call trace is pretty useful for
figuring out what happened.

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely at secretlab.ca
(403) 399-0195




CONFIDENTIALITY
This e-mail message and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail message, you are hereby notified that any dissemination, distribution or copying of this e-mail message, and any attachments thereto, is strictly prohibited.  If you have received this e-mail message in error, please immediately notify the sender and permanently delete the original and any copies of this email and any prints thereof.
ABSENT AN EXPRESS STATEMENT TO THE CONTRARY HEREINABOVE, THIS E-MAIL IS NOT INTENDED AS A SUBSTITUTE FOR A WRITING.  Notwithstanding the Uniform Electronic Transactions Act or the applicability of any other law of similar substance and effect, absent an express statement to the contrary hereinabove, this e-mail message its contents, and any attachments hereto are not intended to represent an offer or acceptance to enter into a contract and are not otherwise intended to bind the sender, Sanmina-SCI Corporation (or any of its subsidiaries), or any other person or entity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20070712/0e111a8a/attachment.htm