From: Ciro Cattuto <ciro@prosa.it>
To: mtd@infradead.org
Subject: Re: DOC2000 & NFTL problems
Date: Fri, 4 Aug 2000 04:17:19 +0200 [thread overview]
Message-ID: <20000804041719.A3648@localhost> (raw)
In-Reply-To: <398A226D.8E19BF9F@sis.com.tw>; from ollie@sis.com.tw on Fri, Aug 04, 2000 at 09:54:53AM +0800
On Fri, Aug 04, 2000 at 09:54:53AM +0800, Ollie Lho wrote:
> The DoC is not properly nftl_formatted, or the OOB areas are broken
> or not correctly accessed by doc2000.c
That's what I thought. The point is, which one of the above?
The DOC2000 shouldn't be broken, because I can use it without the least
problem under DOS _and_ under Linux 2.0.38, with the binary module provided
by M-systems (or IGEL, whatever). I will re-try all of this, just to be sure.
But given this, what could possibly go wrong with the way doc2000.c accesses
OOB areas? This SBC is a common PC104 board manufactured by Eurotech.
It features a 386SX, 2 Mb RAM (yes, I'm running Linux in 2 Mb of RAM)
and a DOC socket, besides many other devices. It's pretty standard stuff.
I'm confused...
Thank you for you help/hints/whatever :)
Ciro
--
Ciro Cattuto, Open Source Developer, Linuxcare Italia SpA
Tel. +39.338.3002140 Fax +39.049.8036484
ciro@linuxcare.com http://www.linuxcare.com/
ciro@prosa.it http://www.prosa.it/
Linuxcare. Support for the revolution.
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-08-04 2:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-02 11:48 DOC2000 & NFTL problems Ciro Cattuto
[not found] ` <3988F8D2.FD1AB1E2@sis.com.tw>
2000-08-03 10:58 ` Ciro Cattuto
2000-08-04 1:54 ` Ollie Lho
2000-08-04 2:17 ` Ciro Cattuto [this message]
2000-08-04 7:45 ` 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=20000804041719.A3648@localhost \
--to=ciro@prosa.it \
--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.