public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: ASA <atris@mail.ru>
To: linux-mtd@lists.infradead.org
Subject: got stuck with DoC 2000
Date: Wed, 1 Aug 2001 14:34:42 +0400	[thread overview]
Message-ID: <12120674119.20010801143442@mail.ru> (raw)

Hello all,

 I'm trying to set up DiskOnChip 2000 in order to work with Linux 2.2.18.
 After downloading latest snapshot (20010730 by tuesday, ie yesterday)
 and applying 'mtd-2.2.17.patch' to the pure 2.2.18 kernel (from
 kernel.org) there was 5 rejected hunks but I handled them manually.

 then I created:
   /dev/mtd char 90,0
   /dev/nftl block 93,0
   /dev/nftl1 block 93,1
   /dev/nftl2 block 93,2
   /dev/nftl3 block 93,3
   /dev/nftl4 block 93,4

 configured kernel with: 'MTD Support' 'NFTL Support' and 'DOC 2000
 support' as modules

 after compiling, rebooting and trying
   insmod mtdcore.o
   insmod docprobe.o
 I got
   Possible DiskOnChip with unknown Chip ID FF found at 0xc8000
   Possible DiskOnChip with unknown Chip ID FF found at 0xcc000
   cannot find driver for DiskOnChip Millenium at 0xd0000
   cannot find driver for DiskOnChip Millenium at 0xd2000
   Possible DiskOnChip with unknown Chip ID FF found at 0xd4000
   Possible DiskOnChip with unknown Chip ID FF found at 0xd8000
   ...
   Possible DiskOnChip with unknown Chip ID FF found at 0xe8000
   Possible DiskOnChip with unknown Chip ID FF found at 0xec000
   
 and loading other modules has no effect. lsmod reports that they are
 loaded. I think that all of these not works:

 # cat /dev/mtd
 ... no such device
 # cat /dev/nftl
 ... no such device

 Compiling these modules as builtin parts of kernel has errors, mainly
 for drivers/mtd/chips/chipres.c at line 67. After quick digging this
 line was split and #ifdef KMOD ... #endif inserted. There was another
 two compilation errors due to unneeded modularization (fix: move last
 #endif to nearly end of text).
 After rebooting the same message about "Millenium" was remain and
 shown during bootup.

 Then I've thied the same patches on pure 2.2.17 kernel. No rejected
 hunks and so on... But during compilation as builtin there was
 linking error "unresolved symbol init_mtd_devices". After compiling
 as module and trying to "insmod mtd_core" - the same linking error.

 And, my DoC is working fine under MS DOS and acts as DoC 2000, not
 Millenium.

 Where I was wrong? Is there any detailed step-by-step instruction to
 set up DoC2000?

 I can use 2.4 kernel but I don't want this - I'm developing embedded
 device and do not want to enlarge system even by 150-200K. In fact,
 I cannot fit kernel 2.4 (even packed with UPX) and initrd with glibc
 2.1 together on single bootable standard-formatted floppy.

 Also, I'm limited to use only 2.2.18 or only 2.4.1 (but not 2.2.17,
 2.2.19, 2.4.2 ... 2.4.7, etc...) due to strict nature of RTLinux 3.0.

-- 
Best regards,
 ASA                          mailto:atris@mail.ru

             reply	other threads:[~2001-08-01 10:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-01 10:34 ASA [this message]
2001-08-07  9:42 ` got stuck with DoC 2000 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=12120674119.20010801143442@mail.ru \
    --to=atris@mail.ru \
    --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