All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Nicolas Pouillon <nipo@ssji.net>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Patch !
Date: Mon, 04 Oct 2004 10:05:11 +0200	[thread overview]
Message-ID: <1096877111.21297.208.camel@thomas> (raw)
In-Reply-To: <20041003221827.7bea56fc.nipo@ssji.net>

On Sun, 2004-10-03 at 22:18, Nicolas Pouillon wrote:
> Unless... Is there some means to access DoC through JTAG ?
> I've seens some pages saying it works, but I'm not too sure it actually
> was speaking of the case I have : A PXA and a M-Sys DoC.

If you can start something like a kernel or a repairtool via JTAG you
should have access.

> > The new code supports the usage of NAND aware
> > filesystems like JFFS2 too. So you don't even need the INFTL stuff, if
> > you must not provide compability with the M-Sys stuff.
> 
> Mh, what is "compatibility with M-Sys stuff" ?

The M-Sys INFTL format.

> > The MTD CVS patch (use patches/patchin.sh) should work with 2.6.7.
> > Hmm, the __iomem related changes are not in 2.6.7. Thats just a simple
> > #define. The code runs on 2.4 too. See compatmac.h
> 
> I'll have a look at it ;)

I really recommend you to use the new code, so ppl. which have such
devices around can help you.

> > > 
> > That's the only one I found on the M-Sys webpage which has a similar
> > type code.
> 
> This is it. Is chip ID 0xa5 ?

Of course not. It's 0x75 :)

Maybe that helps:

> *Interestingly* I got a5ec as the ID for my chip, but this was an 
> incorrect ID.
> the reason I got it was that on the toshiba controller I used, accessing 
> the data register bytewise read every *other* byte, returning ec and 
> garbage (which was  a5 always).
> Using a word access worked as expected and I got the correct id, 75 ec

Is the chip configured for 16-bit interface mode ? 
If yes, there are more tweaks neccecary.

tglx

  reply	other threads:[~2004-10-04  8:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-01 13:46 Issues with a Doc Milplus Nicolas Pouillon
2004-10-01 13:57 ` David Woodhouse
2004-10-01 14:27   ` Nicolas Pouillon
2004-10-02 13:55     ` Patch ! Nicolas Pouillon
2004-10-02 20:42       ` Thomas Gleixner
2004-10-03  1:11         ` Nicolas Pouillon
     [not found]         ` <20041003030653.2e0452a7.nipo@ssji.net>
     [not found]           ` <1096768161.21297.129.camel@thomas>
2004-10-03 20:18             ` Nicolas Pouillon
2004-10-04  8:05               ` Thomas Gleixner [this message]
2004-10-04 16:38                 ` Nicolas Pouillon
2004-10-04 17:59                   ` Thomas Gleixner
2004-10-04 20:47                     ` Nicolas Pouillon
2004-10-04 21:04                       ` Thomas Gleixner
  -- strict thread matches above, loose matches on Subject: below --
2007-04-28 21:47 PATCH: Mark Lord
2004-11-21 23:58 Patch, Andreas Fenkart
2004-11-22  6:37 ` Patch, Jaroslav Kysela
2000-07-12 16:24 PATCH: Juan J. Quintela

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=1096877111.21297.208.camel@thomas \
    --to=tglx@linutronix.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nipo@ssji.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.