public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <David.Woodhouse@mvhi.com>
To: "Mark Ferrell" <mferrell@nortelnetworks.com>
Cc: mtd@infradead.org
Subject: Re: pmc551 status
Date: Thu, 21 Oct 1999 08:52:43 +0100	[thread overview]
Message-ID: <E11eD1f-0002cH-00@devel2.axiom.internal> (raw)


mferrell@nortelnetworks.com said:
>  And that's it.  It opens the device for a short duration of time ..
> but nothing comes forth.  I tried all sortsa fun with noluck.  Any
> ideas, suggestions, large bat's to beat the system about the head
> with? 

Hmmm. To test your driver itself, use the character devices, which are what 
/dev/mtd0 ought to be.

When you're sure that's OK, you ought just to be able to load the mtdblock 
device (after your driver) and use /dev/mtdblock0 too. There may be bugs in 
the mtdblock code, however.

Can you trace and send me the oops that you get if you load mtd, pmc551, then 
mtdblock in that order?

Also, it's worth checking that the mtdblock code actually sets the size of the 
block device. The kernel might be refusing to pass on any read() requests 
because we've left the device size set to zero.

----                                ----                                 ----
David Woodhouse       David.Woodhouse@mvhi.com      Office: (+44) 1223 810302
 Project Leader,    Process Information Systems     Mobile: (+44) 7976 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-10-21  7:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-21  7:52 David Woodhouse [this message]
1999-10-22  4:24 ` pmc551 status Mark Ferrell
1999-10-25 21:15   ` Mark Ferrell
  -- strict thread matches above, loose matches on Subject: below --
1999-10-21  4:13 Mark Ferrell

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=E11eD1f-0002cH-00@devel2.axiom.internal \
    --to=david.woodhouse@mvhi.com \
    --cc=mferrell@nortelnetworks.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