From: "Mark Ferrell" <mferrell@nortelnetworks.com>
To: mtd@infradead.org
Subject: pmc551 status
Date: Wed, 20 Oct 1999 23:13:47 -0500 [thread overview]
Message-ID: <380E92FB.743C3D9C@americasm01.nt.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]
Anyway, I have what appears to be a very ruff around the edges driver
for the pmc551 cPCI Memory module by Ramix Inc.
The module detects the start address in memory and the onboard DRAM size
and all that crazy stuff and appears to work fairly well all in all.
Unfortunately I am having 'issues' w/ getting the mtdblock layer to work
on it. Is there something special I should do far handling that?
If I load the mtd.o then the pmc551.o then then mtdblock.o I get a
kernel panic
If I load the mtd.o then the mtdblock.o then the pmc551.o everything
appears to work, but /dev/mtd0 is unussable.
Apon cat'ing /dev/mtd0 I get the following kernel messages
mtdblock_open
ok
mtdblock_open
ok
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?
--
Mark Ferrell : mferrell@nortelnetworks.com
(972) 685-7868 : Desk
(972) 685-4210 : Lab
(972) 879-4326 : Pager
[-- Attachment #2: Type: text/html, Size: 1180 bytes --]
next reply other threads:[~1999-10-21 4:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-21 4:13 Mark Ferrell [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-10-21 7:52 pmc551 status David Woodhouse
1999-10-22 4:24 ` Mark Ferrell
1999-10-25 21:15 ` 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=380E92FB.743C3D9C@americasm01.nt.com \
--to=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