Skip to contentSkip to conversation

no success

DISCUSSION Rodrigo Moya 4 participants 5 messages Apr 17, 2000 – Apr 28, 2000 1 message not in the archive Memory technology devices (MTD)

lore
Share & tools
lore
#0 lore raw

Hi all!

I've put the MTD drivers into the kernel, and I'm booting linux from the ZIP drive. Once it boots, I try to access the nftl* devices with fdisk, but I've got always the same error about:

could not open /dev/nftl*

What am I doing wrong?

I'm using the 1.23 version of nftl.c, as David said this was the last one which worked, but with the current CVS version of this file the results are the same.

Cheers

To unsubscribe, send "unsubscribe mtd" to [email protected]

#2 lore raw
In reply to a message not in the archive
Quoted 7 lines · Dvir Oren

Rodrigo Moya writes ("no success"):

Quoted 1 line

could not open /dev/nftl*

Does /dev/nftl? have the correct major number (93)?

yes, all the nftla* devices have 93 as major number. Another thing, is that the kernel displays no messages about the MTD drivers. Should it show something?

To unsubscribe, send "unsubscribe mtd" to [email protected]

#3 lore raw
Quoted 3 lines · Rodrigo Moya

yes, all the nftla* devices have 93 as major number. Another thing, is that the kernel displays no messages about the MTD drivers. Should it show something?

It should. Are you sure you patched the init routines in properly? The patch in the CVS patches (?) directory ought to work. Anyway, I'm supposed to be on holiday. Trevor?

--
dwmw2

To unsubscribe, send "unsubscribe mtd" to [email protected]

#4 lore raw
Quoted 7 lines · David Woodhouse
Quoted 3 lines · Rodrigo Moya

yes, all the nftla* devices have 93 as major number. Another thing, is that the kernel displays no messages about the MTD drivers. Should it show something?

Quoted 6 lines

It should. Are you sure you patched the init routines in properly? The patch in the CVS patches (?) directory ought to work. Anyway, I'm supposed to be on holiday. Trevor?

--
dwmw2

Hi,

Apologies but I've been away for 10 days or so.
It sounds to me as if the init routines have not been set-up correctly as Dave suggested.

linux/init/main.c - do_basic_setup() calls init_mtd() mtd.c - init_mtd() calls the rest of the configured init routines.

I can't remember if there's much screen output to see, there should be something. If in doubt, try enabling the DBG output, (recompile with -DZDBG).

Hope this helps, if not get back to me with some more details

Cheers

Trev.

Signature · 9 lines
Zentropix Inc - a Lineo company

Tel: +44 (0)1273 234 647	 Fax: +44 (0)1273 704 482

Visit http://www.zentropix.com/ for Real Time Linux Tools
Visit http://www.realtimelinux.org/ for Real Time Linux Information


To unsubscribe, send "unsubscribe mtd" to [email protected]
#5 lore raw
Quoted 7 lines

Hi,

Apologies but I've been away for 10 days or so.
It sounds to me as if the init routines have not been set-up correctly as Dave suggested.

Quoted 9 lines

linux/init/main.c - do_basic_setup() calls init_mtd() mtd.c - init_mtd() calls the rest of the configured init routines.

I can't remember if there's much screen output to see, there should be something. If in doubt, try enabling the DBG output, (recompile with -DZDBG).

Hope this helps, if not get back to me with some more details

It was my fault, I had applied the patch, but in a different directory, and my makefile wasn't copying the patched init/main.c file. Sorry.

But now, I'm compiling with this fixed, and I get undefined references to register_mtd_notifier and unregister_mtd_notifier, which are not in the source tree I've got here. I've even dropped today the directory and checked out from CVS a fresh copy.

And these two functions are neither in the linux source tree.

Thanks for your help!

To unsubscribe, send "unsubscribe mtd" to [email protected]