Odd behavior of JFFS with AMD chips - kernel panic!

[Nicolas Pitre]

On Tue, 5 Dec 2000, David Woodhouse wrote:

>
> nico at cam.org said:
> >  David --> This is really really misleading and non-intuitive.  Is
> > there a good reason to have a separate device node only for read-only
> > access?
>
> No good reason. I inherited the device nodes from a previous driver - as
> they're already been registered, it made sense at the time to use them as
> they were.

Well... At the time of my original inquiry my device nodes were as follows:
crw-rw-r--   1 root     root      90,   0 Dec  1 17:21 /dev/mtd0
crw-rw-r--   1 root     root      90,   1 Dec  1 17:21 /dev/mtd1
crw-rw-r--   1 root     root      90,   2 Dec  1 17:21 /dev/mtd2
crw-rw-r--   1 root     root      90,   3 Dec  1 17:21 /dev/mtd3
crw-rw-r--   1 root     root      90,   4 Dec  1 17:21 /dev/mtd4
crw-rw-r--   1 root     root      90,   5 Dec  1 17:21 /dev/mtd5

Now having discovered mtd/util/MAKEDEV things aren't as bad as before.

;-)


Nicolas



To unsubscribe, send "unsubscribe mtd" to majordomo at infradead.org