All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <David.Woodhouse@mvhi.com>
To: mtd@imladris.mvhi.com
Subject: Disk-On-Chip progress.
Date: Thu, 20 May 1999 22:21:49 +0100	[thread overview]
Message-ID: <E10kaGD-0004A7-00@devel2.axiom.internal> (raw)

I seem to be able to read the flash. I can also detect the presence of a 
Disk-On-Chip. I can't yet work out the size of the DOC automatically, or 
decode the filesystem on it.

There are some files in ftp://imladris.mvhi.com/pub/mtd/DOCdocs/ which may be 
useful.

BIOS-startupcode.asm: Disassembly of the BIOS ROM which loads the main code 
		from flash. It's this on which I based the C code.

linuxdriver.asm: A disassembly of the binary-only Linux driver, with as many 
		symbols put back in for readability as possible. 

doc-kernel.c: My preliminary kernel driver for the beast. It appears to be 
		able to read lots of interesting stuff off the DoC. Strangely,
		I can't see anything on there that looks even vaguely like FTL,
		so perhaps I'm missing something.



----                                 ----                                 ----
David Woodhouse        David.Woodhouse@mvhi.com       Office: (+44) 1223 810302
 Project Leader,     Process Information Systems      Mobile: (+44) 976 658355
    Axiom (Cambridge) Ltd., Swaffham Bulbeck, Cambridge, CB5 0NA, UK.
             finger dwmw2@ferret.lmh.ox.ac.uk for PGP key.




To unsubscribe, send "unsubscribe mtd" to majordomo@imladris.demon.co.uk

             reply	other threads:[~1999-05-20 21:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-20 21:21 David Woodhouse [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-07-06 21:11 Disk-On-Chip progress David Woodhouse
1999-07-06 22:29 ` Jason Gunthorpe
1999-07-06 22:46 David Woodhouse
1999-07-08 15:06 David Woodhouse
1999-07-08 16:27 ` David Hinds

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=E10kaGD-0004A7-00@devel2.axiom.internal \
    --to=david.woodhouse@mvhi.com \
    --cc=mtd@imladris.mvhi.com \
    /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.