From: "Jonathan M. Schlueter" <jonschl@umd.umich.edu>
To: Andre Sodermans <andreesje_werk@yahoo.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: diskonchip2000 support in 2.4.22
Date: Sun, 9 May 2004 15:41:05 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.58.0405091537500.27031@login1> (raw)
In-Reply-To: <20040509192651.76331.qmail@web41502.mail.yahoo.com>
On Sun, 9 May 2004, Andre Sodermans wrote:
> hello all,
> I can't access my diskonchip2000 partitions from
> linux. I have linuxmz 2.4.18 installed on it and it
> boots fine from diskonchip.
>
> The kernel I built for LFS5.0 is based on 2.4.22.
> I compiled the kernel with:
> CONFIG_MTD = m
> CONFIG_MTD_CHAR = m
> CONFIG_NFTL = m
>
> Running modprobe docprobe, I get:
>
> DiskOnChip Millennium found at address: 0xD000
> no flash chips recognized
>
> It is actually a diskonchip2000.
> There is no entry in /proc/mtd.
Which driver are you using?
> After I installed the kernel I noticed that I was
> missing the /dev/msys/fla* so I created those. Also
> the /dev/nftl* were missing, so I downloaded the
> latest mtd snapshot and ran the MAKEDEV script.
/dev/msys/fla* are the dev files from M-Sys's custom driver
/dev/nftla are the dev files for the mtd subsystem (this list)
They are two seperate and different methods of accessing the DiskonChip
> I tried to mount -t ext2 /dev/msys/fla1 /mnt/doc -
> result:
> mount: /dev/msys/fla1 is not a valid block device
>
> I tried to mount -t ext2 /dev/nftla
> mount: /dev/nftla1: unknown device
>
>
> Did I miss something?
>
Jon Schlueter
next prev parent reply other threads:[~2004-05-09 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-09 19:26 diskonchip2000 support in 2.4.22 Andre Sodermans
2004-05-09 19:41 ` Jonathan M. Schlueter [this message]
2004-05-09 20:32 ` Andre Sodermans
2004-05-10 1:47 ` Andre Sodermans
2004-05-10 6:55 ` David Woodhouse
2004-05-11 15:53 ` Andre Sodermans
2004-05-11 15:58 ` 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=Pine.GSO.4.58.0405091537500.27031@login1 \
--to=jonschl@umd.umich.edu \
--cc=andreesje_werk@yahoo.com \
--cc=linux-mtd@lists.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