public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Ian Yap <d2army@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: Please help in getting kernel 2.6.8.1 to work with a DOC 2000
Date: Fri, 17 Dec 2004 11:43:54 -0600	[thread overview]
Message-ID: <d52a4b1c041217094333b5bf0@mail.gmail.com> (raw)

Hi there everyone

I was wondering if anyone has been able to boot from a kernel 2.6.8.1
on with an M-Sys Disk-On-Chip(DOC) 2000 on an AMP (Advanced Micro
Peripherals) MICRO886ULP Single-Board-Computer with a Crusoe Transmeta
800 Mhz processor?

I have enabled DOC probing for both self contained MTD and NAND flash
devices when compiling the 2.6.8.1 kernel. However, when I try to boot
from this kernel image I made on the SBC, I get :

DiskOnChip 2000 found at address 0xD8000

Flash Chip found: Manufactureer ID: EC, Chip ID: 73 (Samsung: NAND 16
MiB 3 , 3V 8-bit)

(slight pause)

3 flash chips found. Total DiskOnChip size: 48 MiB

Ignoring DiskOnChip 2000 at 0xDA000 - already configured
Ignoring DiskOnChip 2000 at 0xDC000 - already configured
Ignoring DiskOnChip 2000 at 0xDE000 - already configured

DiskOnChip 2000 found at address 0xD8000

DiskOnChip 2000 responds to DWORD access

NAND device: Manufacturer ID: 0xec, Chip ID: 0x73 (Samsung NAND 16MiB
3, 3V 8-bit)

(hangs forever)

There is no kernel panic message though

I have a patched LILO on this machine already and someone got it to
work with 2.4.x using an initrd image that he would use to boot the
kernel from using "initrd="

Therefore, I am wondering if I really need to figure out how to make
an initrd boot image like that in order to make the 2.6.8.1 kernel
work as well

Thank a lot in advance!
I.S.

                 reply	other threads:[~2004-12-17 17:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=d52a4b1c041217094333b5bf0@mail.gmail.com \
    --to=d2army@gmail.com \
    --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