public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Thomas Gleixner" <tglx@linutronix.de>
To: "Carlos, John J USAATC" <john.carlos@atc.army.mil>,
	linux-mtd@lists.infradead.org
Subject: Re: DoC MilPlus32 try to get working???
Date: Fri, 18 Jun 2004 17:11:35 +0200	[thread overview]
Message-ID: <200406181711.35243.tglx@linutronix.de> (raw)
In-Reply-To: <EFF9A3506F74924AB5CC77BDC66E79351812BB@atcml01.atc.army.mil>

On Friday 18 June 2004 14:56, Carlos, John J USAATC wrote:
> Hi,
> I have been trying to get diskonchip to work with the MilPlus chip.  I
> have merged the drivers in the devices directory in diskonchip.c  I still
> have to see if the bad block table is working/implemented.  This is the
> error message I get the first time after a boot up that I insmod
> diskonchip. Subsequent insmods of diskonchip just report no valid boot
> record.

You insmod drivers/mtd/nand/diskonchip .
Why does it show INFTL messages ?
Who is calling INFTL functions?
Before you start playing with INFTL the chip driver itself must be fully 
functional.

>   Could anyone tell me what the cause is.  I guess I need to get the bad
> block checking working first before anything else?
>
> mtd: Giving out device 4 to DiskOnChip Millennium Plus
> in inftl_add_mtd
> INFTL: add_mtd for DiskOnChip Millennium Plus
> INFTL: INFTL_mount(inftl=0xc1cc6600)
> INFTL: find_boot_record(inftl=0xc1cc6600)
> INFTL: block read at 0x0 of mtd4 failed: -22
> INFTL: block read at 0x8000 of mtd4 failed: -22
> INFTL: block read at 0x10000 of mtd4 failed: -22
> INFTL: block read at 0x18000 of mtd4 failed: -22
> INFTL: block read at 0x20000 of mtd4 failed: -22
> INFTL: further failures for this block will not be printed
> INFTL: could not find valid boot record?
> INFTL: could not mount device
> NFTL: add_mtd for DiskOnChip Millennium Plus
> Block read at 0x0 of mtd4 failed: -22
> Block read at 0x8000 of mtd4 failed: -22
> Block read at 0x10000 of mtd4 failed: -22
> Block read at 0x18000 of mtd4 failed: -22
> Block read at 0x20000 of mtd4 failed: -22
> Further failures for this block will not be printed
> Could not find valid boot record
> NFTL: could not mount device
> #
>
> Thanks to all who have been answering my calls for help!!!!
> John
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

-- 
Thomas
_____________________________________________________________________
From slash dot org
"When customers are visiting, engineers are not allowed to wear ties. 
That way the customer can tell who is the engineer and who is the 
salesman (and therefore whom to believe.). Ties cut off blood flow 
to the brain, making it easier for the salesmen to do their jobs." 
_____________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de

      reply	other threads:[~2004-06-18 15:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18 12:56 DoC MilPlus32 try to get working??? Carlos, John J USAATC
2004-06-18 15:11 ` Thomas Gleixner [this message]

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=200406181711.35243.tglx@linutronix.de \
    --to=tglx@linutronix.de \
    --cc=john.carlos@atc.army.mil \
    --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