All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ollie Lho <ollie@sis.com.tw>
To: David Woodhouse <dwmw2@infradead.org>
Cc: mtd@infradead.org, linuxbios@lanl.gov
Subject: Re: DiskOnChip 2000/Millennium driver merge.
Date: Sat, 02 Dec 2000 09:40:44 +0800	[thread overview]
Message-ID: <3A28531C.4F5C8E14@sis.com.tw> (raw)
In-Reply-To: 8574.975681632@redhat.com

David Woodhouse wrote:
> 
> I've now cleaned up some of the differences between the new combined
> doc200[01] driver and the doc2001-only driver, and enabled
> DOC_SINGLE_DRIVER in the docprobe code.
> 
> I haven't removed the conditional stuff for two reasons -
>         1. Ollie wants to keep the separate doc2001 driver for easier
>                 development and testing
>         2. The doc2000 driver doesn't actually _work_ for writing. It
>                 exhibits the same behaviour with both types of device -
>                 writes to NFTL just don't appear to _stay_ written.
> 
> If you need write support for the Millennium right now, just comment out
> the definition of DOC_SINGLE_DRIVER in docprobe.c and continue to use
> the doc2001 module.
> 
> As the doc2001 driver is working fine, I'm fairly sure it's a hardware
> driver problem, not an NFTL code problem. Writes to the main body of the
> flash appear to work too, so I currently suspect that it's an OOB data write
> problem.
> 
> If anyone else with Millennium hardware could take a look at the
> differences between doc2000.c and doc2001.c, especially Ollie who actually
> knows what he's doing, that'd be very much appreciated.
> 

David,
	I just tried the updated CVS version. The Millennium part of 
doc2000.c works for some extend. It has some bugs which will offset/lost
1 or 2 bytes at begin/end of each 512byte page. It is a common problem if
you are not programming the chip fully comply to M-Systems Spec (actually
you have to do some "undocumented" tricks too). I will review the new code
next week possiblly after you get the SiS 630 LinuxBIOS demo/devel platform.

Ollie


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

  parent reply	other threads:[~2000-12-02  1:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-01 14:40 DiskOnChip 2000/Millennium driver merge David Woodhouse
2000-12-01 17:45 ` David Woodhouse
2000-12-01 17:50   ` David Woodhouse
2000-12-02  1:40 ` Ollie Lho [this message]
2000-12-02 11:10   ` David Woodhouse
2000-12-04  2:08     ` Ollie Lho
  -- strict thread matches above, loose matches on Subject: below --
2000-12-03  9:45 Vadim Khamlinsky
2000-12-04 16:44 Miguel Freitas
2000-12-04 15:53 ` David Woodhouse

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=3A28531C.4F5C8E14@sis.com.tw \
    --to=ollie@sis.com.tw \
    --cc=dwmw2@infradead.org \
    --cc=linuxbios@lanl.gov \
    --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 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.