public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "David Griffith" <dgriffith@ccimackay.com>
To: <mtd@infradead.org>
Subject: Modification to Doc2000.c for Virgin Webplayer
Date: Sun, 29 Apr 2001 16:22:53 +1000	[thread overview]
Message-ID: <004b01c0d074$d2c3b980$8264a8c0@dave> (raw)

Hi,
    Apologies for this note if someone else has been there / done that.

I have a few Virgin Webplayers with 48MB doc2000's in them.
(Basically a MediaGX 200Mhz sbc)

Anyways, I've been having trouble with the detection of the DOC. The MTD
drivers in the linux kernel have trouble finding
partitions on the DOC. (When I say "Have trouble" its means 99 out of 100
times the nftl layer can't find a valid boot record, gets all grumpy, and
gives up).

So I turned on debugging,  liberally sprinkled a few more printk's around..
and hmmm.... turning on level 3 debugging makes it work.

So, I says to meself, "Self, it must be some interaction with some sort of
delay thingy with the DoC :-)",  a quick poke through the source showed this
in doc2000.c in one of the functions near the front (I can't remember the
name! sorry - my code is at home!)

 what makes it work is to change this line (about 75 lines down in kernel
2.4.4):

    for (i = 0; i < cycles ; i++) {

    to this :

    for (i = 0; i < cycles*4 ; i++) {


This effectively *quadruples* the delay time for all sorts of things in the
code it seems.
With this in - I can detect partitions, mount them , read / write to them
just fine.
I did try just doubling it, and I could read it, but it wasn't very happy
about writing to it.
I'd post logs , but currently I boot to a ramdisk...

So,
Any ideas as to why? ;-)

Regards,
    David



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

                 reply	other threads:[~2001-04-29  6:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='004b01c0d074$d2c3b980$8264a8c0@dave' \
    --to=dgriffith@ccimackay.com \
    --cc=mtd@infradead.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