From: "Brian T" <btuch@usa.net>
To: <linux-mtd@lists.infradead.org>
Subject: 2.6.x nettel.c compile problems
Date: Fri, 2 Jul 2004 09:32:01 -0500 [thread overview]
Message-ID: <03c201c46041$57b3fa10$fd0ba8c0@briantpc> (raw)
Sorry if this was covered, but I didn't see anything when searching. I'm
trying to get the 2.6.2 kernel working with JFFS2 and MTD (Snapgear/Intel
chipset). The standard ~/mtd/maps/nettel.c gave me an error when compiling,
so I patched to the CVS from 6/30, but I was still getting the same error :
CC drivers/mtd/maps/nettel.o
drivers/mtd/maps/nettel.c: In function `nettel_init':
drivers/mtd/maps/nettel.c:429: error: `ROOT_DEV' undeclared (first use in
this function)
drivers/mtd/maps/nettel.c:429: error: (Each undeclared identifier is
reported only once
drivers/mtd/maps/nettel.c:429: error: for each function it appears in.)
drivers/mtd/maps/nettel.c:429: warning: implicit declaration of function
`MKDEV'
make[3]: *** [drivers/mtd/maps/nettel.o] Error 1
make[2]: *** [drivers/mtd/maps] Error 2
make[1]: *** [drivers/mtd] Error 2
make: *** [drivers] Error 2
If I add this to the top of nettel.c ...
#ifndef CONFIG_BLK_DEV_INITRD
#include <linux/config.h>
#include <linux/fs.h>
#include <linux/major.h>
#include <linux/root_dev.h>
#endif
...then it compiles fine, but when booting the kernel it is unable to mount
mtd1 :
JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc.
Initializing Cryptographic API
Serial: 8250/16550 driver $Revision: 1.90 $ 56 ports, IRQ sharing enabled
ÿttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 24576K size 1024 blocksize
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
Using anticipatory io scheduler
JEDEC: Found no SnapGear AMD device at location zero
SnapGear Intel: Found 1 x16 devices at 0x0 in 16-bit mode
Intel/Sharp Extended Query Table at 0x0031
cfi_cmdset_0001: Erase suspend on write enabled
Using buffer write method
SnapGear Intel: Found 1 x16 devices at 0x0 in 16-bit mode
Intel/Sharp Extended Query Table at 0x0031
cfi_cmdset_0001: Erase suspend on write enabled
Using buffer write method
SNAPGEAR: Intel flash device size = 16384K
Creating 6 MTD partitions on "SnapGear Intel":
0x00000000-0x000e0000 : "JBM kernel"
mtd: Giving out device 0 to JBM kernel
0x00100000-0x00fe0000 : "JBM filesystem"
mtd: Giving out device 1 to JBM filesystem
0x000e0000-0x00100000 : "JBM config"
mtd: Giving out device 2 to JBM config
0x00000000-0x01000000 : "JBM Intel"
mtd: Giving out device 3 to JBM Intel
0x00fe0000-0x01000000 : "JBM BIOS Config"
mtd: Giving out device 4 to JBM BIOS Config
0x00fe0000-0x01000000 : "JBM BIOS"
mtd: Giving out device 5 to JBM BIOS
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
NET: Registered protocol family 1
NET: Registered protocol family 17
Kernel panic: VFS: Unable to mount root fs on mtdblock1
I also tried enabling INITRD without the headers I added at the top, but
with the same result.
Any ideas on this?
Thanks,
-Brian
next reply other threads:[~2004-07-02 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 14:32 Brian T [this message]
2004-07-02 16:58 ` 2.6.x nettel.c compile problems Brian T
2004-07-02 17:28 ` Josh Boyer
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='03c201c46041$57b3fa10$fd0ba8c0@briantpc' \
--to=btuch@usa.net \
--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