I have tried to make a simple change to the kernel to include all the code
need to come up and mount the DOC. For some reason when the kernel comes up
I am unable to mount the DOC. I believe that is my stumbling block right
now. When I try to actually load from DOC I get a kernel panic because it is
unable to find root. And since booting the same kernel up that points to
/dev/hda1 doesn't have that problem, and also can't mount /dev/nftla1 I
believe I am not choosing the correct options to properly build DOC access
into the kernel. (When I try to mount I get the error message - "mount :
/dev/nftla1 has wrong major or minor number" This same item works fine when
I use a kernel with Mods and manually load the mods.)
Options being selected :
# User modules and translation layers for MTD devices
#
CONFIG_MTD_CHAR=y
CONFIG_MTD_BLOCK=y
CONFIG_FTL=y
CONFIG_NFTL=y
CONFIG_NFTL_RW=y
#
# Memory Technology Devices (MTD)
#
CONFIG_MTD=y
CONFIG_MTD_DEBUG=y
CONFIG_MTD_DEBUG_VERBOSE=3
#
# Disk-On-Chip Device Drivers
#
# CONFIG_MTD_DOC1000 is not set
# CONFIG_MTD_DOC2000 is not set
CONFIG_MTD_DOC2001=y
CONFIG_MTD_DOCPROBE=y
CONFIG_MTD_DOCPROBE_ADDRESS=0000
CONFIG_MTD_DOCPROBE_HIGH=y
# CONFIG_MTD_DOCPROBE_55AA is not set
Any suggestions?
> -----Original Message-----
> From: Ronald G Minnich [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, April 05, 2001 9:12 PM
> To: Greg Pratt
> Cc: Benson, Chris M; [EMAIL PROTECTED]
> Subject: RE: root filesystem on DoC Millenium
>
> On Thu, 5 Apr 2001, Greg Pratt wrote:
>
> > As far as I know, you have to use CRAMFS. Basically
> > what you're doing is taking the first 1MB of the chip
> > for the bootstrap & kernel and then formatting the
> > rest of the chip (2MB-8MB) as a file system.
>
> you can use any file system that linux supports. You can format the
> flash as ext2 (we've done this), or cramfs, or DOS, or whatever.
>
> If linux supports it you can format that flash with any filesystem you
> please.
>
>
> ron
