public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Dvir Oren <dviro@ibm.net>
To: Trevor Woolven <trevw@zentropix.com>, , MTD <mtd@infradead.org>
Subject: Re: Request for kernel with DOC2000
Date: Mon, 20 Mar 2000 21:43:44 +0200	[thread overview]
Message-ID: <E12X9bb-00042u-00@infradead.org> (raw)

>From Trever Woolven:

>2	I'm getting an error, where I cannot mount the DOC device > as the driver complains about the major/minor number. I am 
> investigating  whether or not this is due to uninitialised data 
> structures. 
> 3	My collegue had a lot of problems with this driver: failing 
> during 'fdisk'; DOC read/writes; e2fsck; mke2fs; etc, etc. 
> The big problem I'm having so far (apart from understanding the 
> sequence of events and what the code's actually doing) is that 
> none of  these errors is repeatable, (except the one I mentioned
> in 2 above)

More or less my problems.  Though I was able to compile the 
drivers for 2.2.14, I can't seem to mount, or fdisk, or do anything.  It 
seems to me like the 2.3 initialization does not work under 2.2.  I've 
compared it to m-systems' code, and to a book I have, and it what 
is written should work for modules, not for kernel drivers, which is 
exactly what happens.

If anybody was able to fix this, I'll be glad to see what they did.  I'll 
work on it myself, when I have the time.




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

             reply	other threads:[~2000-03-20 21:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-20 19:43 Dvir Oren [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-02-19 20:01 Request for kernel with DOC2000 Dvir Oren
2000-02-19 21:22 ` Brian K. Michalk
2000-02-20 12:13   ` wbh
2000-02-22 12:56     ` Trevor Woolven
2000-02-25  0:21       ` Dvir Oren
2000-02-25  0:21     ` Dvir Oren
2000-02-28 22:10       ` wbh

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=E12X9bb-00042u-00@infradead.org \
    --to=dviro@ibm.net \
    --cc=mtd@infradead.org \
    --cc=trevw@zentropix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox